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.

Optional build jobs

Similar to the conversation going on here I would like to have the option to define optional workflow jobs that would not affect the status of the test suite. Imagine I have a flow that runs the tests, but it only does the deployment of specific branches. I would like to add optional jobs that can be triggered manually (this is already supported using `hold` requirement) and also would not affect the outcome result of the tests - if all tests passed this flow should be marked as green regardless of the optional jobs state.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 25 2018
  • Future consideration
  • Attach files
  • Admin
    Nathan Dintenfass commented
    May 25, 2018 07:21

    Another way we think about this is to provide another status other than Pass or Fail that can be a "Warn" or other intermediate state that would not cause the Workflow or downstream jobs to be skipped. We have also thought about making it easier to continue to running even after a failure, which would be another way to solve the kind of flows you are describing. Both features are under consideration but not yet committed.