Rebase the installer build jobs on the global build job template #100110
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
jkoritzinsky
force-pushed
the
installer-job-global
branch
from
40f075d to
471f0eb
Compare
…ed in global-build-job jobs.
jkoritzinsky
force-pushed
the
installer-job-global
branch
from
ab65443 to
33e159c
Compare
This was referenced Mar 22, 2024
elinor-fung
reviewed
Mar 26, 2024
…an calculate a global build job name when we have a platform.
elinor-fung
approved these changes
Apr 4, 2024
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
3 tasks
|
/ba-g Slow mac timeouts |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Reimplement the installer build + test job on top of the global build job template.
Reimplement the build-linux-packages step on top of the global build step template now that all the usages of it are through the global build job template.
This allows us to further centralize our YAML into a smaller set of job templates, making it easier to maintain.