Move Azure build pipelines to OneBranch #1877
Open
+362
−1
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
…f other signed binaries
mikebattista
reviewed
Apr 1, 2024
| packageType: sdk | ||
| useGlobalJson: true | ||
|
|
||
| # TODO - this no longer sets an Azure Devops pipeline build number, OneBranch has a different way of doing that |
There was a problem hiding this comment.
Is this TODO still pending?
There was a problem hiding this comment.
It is, this Azure Devops pipeline name doesn't get properly set right now
There was a problem hiding this comment.
The current release pipeline uses the pipeline build number so I don't think we can merge this until this is resolved.
|
Does it make sense to migrate the pipeline to GitHub Actions and call out to a backend for signing? |
|
No. It looks like we still have access to the existing pipelines, though, so I plan to push out a release this week. |
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.
As part of compliance with updated security requirements, production pipelines must run in a 1ES environment. To do this, pipelines are converting to use OneBranch pipeline templates.
This changes how artifacts are published and the build environment is slightly different, resulting in some small changes to the build files.
As a backup plan, the existing azure pipeline scripts are left in place. These will be removed in the future.