Add a No-Op Job Type that does Nothing

In developing complicated workflows with multiple fanned out jobs, it can be really time consuming to manage lists of required jobs to "join" the work flow from multiple fanned out jobs. Especially as one changes what comes before or after the "join" point. Currently, we have to setup a job that kicks off a vm that does nothing. But that wastes resources spinning up a vm. Adding a no-op job type that does not require a vm to be spun up would save time and resource, but allow workflow authors to maintain that join point more easily.

  • Guest
  • Jul 14 2020
  • New
  • Attach files