Disable CG task in PR pipelines#12426
Merged
Merged
Conversation
leqiao-1
approved these changes
Aug 3, 2022
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
2 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.
Description:
We have pull request pipelines, packaging pipelines and some other nightly pipelines.
This PR will disable the CG task in some pull request pipelines to unblock the patch release. The task is auto-injected and recently it is very fragile. We still need to use it for the bits we releases. While we'd better to run it in every pipeline, currently nobody watches the results from pull request pipelines. Therefore I will disable the task until someone wants to look the results.
While I should do it for all pull request pipelines instead of some, we have too many pipelines and I don't know what is missed. But once this is checked in, I can watch which pipeline still sends data there then I will know.
Motivation and Context