[CI] Intermediate step to move the api scan out of the build. #21357
Conversation
This file contains 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
Due to the way that resource triggers are implemented in VSTS, we are triggering tests more than once. To solve the issue, we need to move the diff stages to different pipelines. This is the first step to allow use to get less stages in the build so that we can reduce the number of tests that are triggered.
rolfbjarne
approved these changes
Oct 2, 2024
mcumming
approved these changes
Oct 2, 2024
|
For all yml files that are attached to AzDo pipelines, can we add the link to the pipeline at the top of the yml file? |
I am going to be adding a wiki page with all the pipelines, yml files and dependencies. I'll be writing a CI prime as soon as things are working. Probably will be a README in the devops directory. |
This comment has been minimized.
This comment has been minimized.
stephen-hawley
approved these changes
Oct 2, 2024
haritha-mohan
approved these changes
Oct 3, 2024
dalexsoto
approved these changes
Oct 3, 2024
✅ API diff for current PR / commitNET (empty diffs)
✅ API diff vs stable.NET (No breaking changes)ℹ️ Generator diffGenerator Diff: vsdrops (html) vsdrops (raw diff) gist (raw diff) - Please review changes) Pipeline on Agent |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Due to the way that resource triggers are implemented in VSTS, we are triggering tests more than once. To solve the issue, we need to move the diff stages to different pipelines. This is the first step to allow use to get less stages in the build so that we can reduce the number of tests that are triggered.