[Build] Skip build jobs in the CreateInstaller stage during Image Validation pipeline runs #6001
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.
In an Agg PR pipeline run that is validating:
This change on average reduces the work in the Createinstaller stage by a half in a test OS image validation pipeline run, saving time and resources.
Currently, we are yet not skipping a build job completely, but most steps in the job are no-op'ed.
A related PR against the internal Aggregator repo disables BinSkim in CreateInstaller jobs iff we are validating a test OS image, to avoid a warning.
I see that two x64 test jobs failed. These 2 test jobs failed the same way in other PRs w/o my changes.
--
A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.