Always run the pipeline evaluation step#154
Merged
Conversation
Contributor
|
I would add a note in the documentation that says that the ML pipeline actually cancels itself. If you write the code yourself, that's obvious but if not, it's not particularly obvious. |
Contributor
Author
|
@omartin2010 , @sudivate's change yesterday added a flag to disable the cancellation. The docs will need to be updated to mention both the default cancellation state and how to disable it. |
sbaidachni
approved these changes
Jan 29, 2020
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Set the ci-build-train pipeline to always run the evaluation step (even if the pipeline is cancelled). This will cause the Azure Pipeline to log the reason for cancellation rather than just "silently failing".
#151