-
Notifications
You must be signed in to change notification settings - Fork 227
Add a new script to mark package as released from release pipeline #11559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a new script to mark package as released from release pipeline #11559
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds automation to mark packages as released in Azure DevOps release plans after successful pipeline deployment. The script integrates with the release pipeline to automatically update work item status when packages are published.
- Adds a PowerShell script to identify and update release plan work items based on merged pull requests
- Implements helper functions to query Azure DevOps for release plans and update their status
- Provides automated tracking of package releases by linking Git commits to DevOps work items
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| eng/common/scripts/Mark-ReleasePlanCompletion.ps1 | Main script that finds merged PRs for a path and updates corresponding release plan work items |
| eng/common/scripts/Helpers/DevOps-WorkItem-Helpers.ps1 | Helper functions for Azure DevOps integration, language mapping, and work item updates |
|
The following pipelines have been queued for testing: |
Co-authored-by: Copilot <[email protected]>
|
The following pipelines have been queued for testing: |
|
The following pipelines have been queued for testing: |
weshaggard
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we chatted lets not use the PRs for this lets use the package name and PR status from the release plant
maririos
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as we talked offline, leaving the feedback here. but I will check once there is an update
|
The following pipelines have been queued for testing: |
weshaggard
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor suggestion but otherwise looks good.
|
The following pipelines have been queued for testing: |
Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#11559 See [eng/common workflow](https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/README.md#workflow) --------- Co-authored-by: Praveen Kuttappan <[email protected]> Co-authored-by: Praven Kuttappan <[email protected]> Co-authored-by: Copilot <[email protected]>
Sync eng/common directory with azure-sdk-tools for PR Azure/azure-sdk-tools#11559 See [eng/common workflow](https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/README.md#workflow) --------- Co-authored-by: Praveen Kuttappan <[email protected]> Co-authored-by: Praven Kuttappan <[email protected]> Co-authored-by: Copilot <[email protected]>
This script will be plugged in to the release stage of the pipeline post publishing steps to identify any release plans created for releasing this SDK and mark package release status as released in the release plan work item.