Add support for ordering jobs explicitly #205
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zyga
force-pushed
the
feature/explicit-order
branch
2 times, most recently
from
99b1ba5 to
fbd59f6
Compare
When debugging failures caused by interactions between jobs, being able to order jobs explicitly is critical. The new -explicit-order option strongly orders jobs following the order in which they were matched to command line arguments. Signed-off-by: Zygmunt Krynicki <me@zygoon.pl>
zyga
force-pushed
the
feature/explicit-order
branch
from
fbd59f6 to
19d87bc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When debugging failures caused by interactions between jobs, being able to order jobs explicitly is critical. The new -explicit-order option strongly orders jobs following the order in which they were matched to command line arguments.