(Re-)introduce release builds with Azure Pipelines #2176
Merged
+1,044
−860
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
Allow a caller of pack.sh and layout.sh to specify the location of the payload and symbols. Signed-off-by: Matthew John Cheetham <[email protected]>
Translate the layout.sh and pack.sh Bash scripts to PowerShell scripts. We are now building the .NET tool NuGet packages on Windows. Signed-off-by: Matthew John Cheetham <[email protected]>
Signed-off-by: Matthew John Cheetham <[email protected]>
Apply linter recommendations to the codesign.sh script used on macOS. Also always pass the absolute path of the entitlements file to the codesign command as using relative paths can sometimes fail. Signed-off-by: Matthew John Cheetham <[email protected]>
Add specific Windows pool information for SDL source tasks. These tasks only run on Windows. Signed-off-by: Matthew John Cheetham <[email protected]>
Signed-off-by: Matthew John Cheetham <[email protected]>
Add Windows release build definitions on Azure Pipelines. Signed-off-by: Matthew John Cheetham <[email protected]>
Add macOS release build definitions on Azure Pipelines. Signed-off-by: Matthew John Cheetham <[email protected]>
Add Linux release build definitions on Azure Pipelines. Signed-off-by: Matthew John Cheetham <[email protected]>
Add a release pipeline for the .NET Tool using Azure Pipelines. Signed-off-by: Matthew John Cheetham <[email protected]>
Add a new stage (after build) to publish the assets to GitHub and NuGet.org. Each target (GitHub and NuGet.org) need to run in separate jobs due to restrictions of the 1ES pipeline templates: - Publishing a NuGet package requires us to use template `outputs` - `type: releaseJob` cannot specify outputs - `type: releaseJob` is required to use the `GitHubRelease` task Signed-off-by: Matthew John Cheetham <[email protected]>
Remove the GitHub Actions-based release workflow files. We are using Azure Pipelines instead now. Signed-off-by: Matthew John Cheetham <[email protected]>
Default enable ESRP code signing, as well as publishing to GitHub and NuGet.org. Signed-off-by: Matthew John Cheetham <[email protected]>
Contributor
Author
|
For Microsoft employees, here's a link to the test release build showcasing this pipeline: |
dscho
approved these changes
Nov 13, 2025
Contributor
dscho
left a comment
dscho
left a comment
There was a problem hiding this comment.
Wow, what a bunch of work. Looks good to me, and I cannot wait to finally release a GCM version after that long of a hiatus!
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.
Since stewardship of the project has transitioned back to Microsoft from GitHub, we're moving the official release builds from GitHub Actions to Azure Pipelines. This is mainly a requirement to enable Microsoft code-signing of executables, packages, etc.
The release pipeline will also publish a GitHub release and the .NET Tool packages to NuGet.org.
The GitHub Actions release workflow is no longer in use (it also required access to approve releases from internal GitHub code-signing systems, which we no longer have access to).