Pipeline to validate PR without caching #2296
Merged
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
MichaelSimons
approved these changes
Oct 7, 2020
41 tasks
mthalman
added a commit
to mthalman/dotnet-docker
that referenced
this pull request
Oct 12, 2020
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.
Defines a new pipeline YAML file that is intended to be used to validate PRs without caching enabled. The pipeline should only build/test a subset of the images. Rather than defining that subset within the YAML, I felt it more appropriate to define it in the variables of the build definition in AzDO where it can be more easily adjusted as necessary. See #2247 (comment) for the suggested set of paths to use.
This pipeline is configured to be triggered only by changes to the eng and tests folders. A change to the src folder would likely end up causing a cache miss in the existing PR pipeline so this one wouldn't need to run in that case. The primary use case for this pipeline is to validate infrastructure changes in the eng folder.
Fixes #2247