(Hierarchical) Stage Labels, Conditions, and Transitions #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RENDERED
Summary
Reorganizes the system scheduling API with better separation of responsibilities. Introduces a single schedule executor, reincarnates stages into topological system labels, and splits run criteria into conditions and transitions.
Motivation
The current system scheduling API packs great functional coverage into a tasteful number of tools, but there are some key things missing, and the overall cohesion isn't as good as it could be.
See #2801 for more background.