Automate release plan create#44137
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
|
|
||
| High-level lifecycle: | ||
|
|
||
| 1. A spec PR merges into `main` in `Azure/azure-rest-api-specs` or `Azure/azure-rest-api-specs-pr`. |
There was a problem hiding this comment.
Shall we only target merge spec PR only in Azure/azure-rest-api-specs repo? We could not release SDK from the spec private repo.
There was a problem hiding this comment.
SDK stage will not run for private repo. It is only to create private preview release plan for KPI completion.
| @@ -0,0 +1,181 @@ | |||
| # Release Plan Auto-Generation | |||
|
|
|||
| This document explains how release plans are automatically discovered or created by the `eng/tools/release-plan` tool and the `eng/pipelines/release-plan.yml` pipeline. | |||
There was a problem hiding this comment.
Could you help to describe the problem you plan to solve? What are the challenges we are facing today?
There was a problem hiding this comment.
Currently release plan needs to be created using the agent. This can lead to agent nondeterministic behavior and also costs tokens when this can be automated without using agent at all. So, a service team does not have to worry about creating a release plan or missing release plan for their spec. Every auto generated SDK pull requests will have a release plan linked to it.
There was a problem hiding this comment.
I can add SDK generation as the second stage of this pipeline so SDK pull request will be auto generated after a release plan is created once API spec is merged. Currently one of the concerns from a few service teams is that they need to run these steps manually using the agent. This will also ensure SDK PR has a release plan.
|
Successful test run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6494683&view=results |
mikeharder
left a comment
mikeharder
left a comment
There was a problem hiding this comment.
approved, but a few remaining small fixes
Co-authored-by: Mike Harder <mharder@microsoft.com>
4 participants
Create a release plan automatically when API spec PR merges and if that API spec PR adds a new api version.