Submit Your Ideas

We want to hear from you - vote for the features and improvements you'd most like to see, or submit your own ideas if you don't find them already listed.

save_cache when node is 0

With the new units based pricing model, we are finding that we can fan-out faster and while doing some repetitive work (and spending more build minutes), we probably shouldn't be doing things like updating a cache from 20 concurrent containers.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 14 2018
  • Already exists
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    14 May 16:26

    It would seem this is unnecessary - I see this in the log for extra nodes:

     

    Skipping cache generation, cache already exists for key