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.

Workflows - Serialize jobs

There is currently no non-hacky way to make sure we don't run multiple deploys.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 5 2017
  • Future consideration
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    February 1, 2018 18:34

    Much needed feature!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    April 2, 2018 17:43

    Any ETA on this feature?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    May 10, 2018 20:55

    right now we have 2 workflows.. a build-and-test and a build-test-and-deploy.. the later is only used for our staging and production branches.. (the ones that actually do the deploys)

    So I'd see this as either done at the entire workflow e.g. define this workflow as serialize only so only one instance (per branch) is run at a time..  Or have it done per job within the workflow.. e.g. stating the "deploy to staging" or "deploy to production" step can only be run in a serialized fashion.