Skip to content

Commit 0a8ee99

Browse files
Revise release steps for MSBuildLocator (#365)
* Revise release steps for MSBuildLocator Updated the release process for MSBuildLocator to reflect changes in the pipeline build and release steps. * Remove GitHub release job from pipeline * Fix typo in pipeline build instruction
1 parent a42e012 commit 0a8ee99

2 files changed

Lines changed: 4 additions & 15 deletions

File tree

Releasing_MSBuildLocator.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@ These instructions can only be followed by Microsoft-internal MSBuild maintainer
55
1. Create a PR in https://github.com/microsoft/MSBuildLocator
66
2. Have it reviewed.
77
3. Once approved, merge it.
8-
4. It will automatically start a pipeline build [here](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=11881).
9-
5. Once it succeeds, proceed to [our release page](https://dev.azure.com/devdiv/DevDiv/_release?_a=releases&view=mine&definitionId=408) and create a release (top-right). Specify the build that succeeded.
10-
6. At some point, it will stop to request permission to continue. If you want to publish to NuGet, do so, clicking Approve. It will make a little more progress and push to NuGet! It will then give you the option to "resume" (or cancel) twice. Do so.
11-
8+
4. Start a pipeline build [here](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=11881) for the commited changes.
9+
5. Once it succeeds, proceed to [our release pipeline](https://dev.azure.com/devdiv/DevDiv/_build?definitionId=27492) and queue release. Specify the build that succeeded.
10+
6. On Public NuGet release stage it will stop to request permission to continue. If you want to publish to NuGet, do so, clicking Approve.
11+
1212
### Releasing a non-preview version of MSBuildLocator
1313

1414
The above steps will push a package to NuGet.org, but it is a preview version. To make a final release branded version, merge the latest changes into a release branch like `release/1.5`. Follow the steps as above, and it will publish a release package to NuGet.org.

release-pipeline.yml

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -79,14 +79,3 @@ stages:
7979
https://microsoft.sharepoint.com/teams/toolsforeng/_layouts/OneNote.aspx?id=%2Fteams%2Ftoolsforeng%2FOne%20Note%2FToolsForSoftwareEngineers&wd=target%28Build%20Tools%2FMSBuild%2FGitHub.one%7CFF6DC598-65EC-43D5-AB29-DB38FEB82BC8%2FMyGet%20Feed%7CFAFC6258-899D-48D4-8DB4-892396202C9C%2F%29
8080
onenote:https://microsoft.sharepoint.com/teams/toolsforeng/One%20Note/ToolsForSoftwareEngineers/Build%20Tools/MSBuild/GitHub.one#MyGet%20Feed&section-id={FF6DC598-65EC-43D5-AB29-DB38FEB82BC8}&page-id={FAFC6258-89
8181
onTimeout: 'reject'
82-
83-
- job: GitHubRelease
84-
displayName: 'GitHub release'
85-
dependsOn: PublicNuGetRelease
86-
pool: server
87-
steps:
88-
- task: ManualValidation@0
89-
displayName: 'Create GitHub release'
90-
inputs:
91-
instructions: 'Create the GitHub release manually'
92-
onTimeout: 'reject'

0 commit comments

Comments
 (0)