Skip to content
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

[pipeline] migrate some functions from auto_release to sdk generation pipeline #40175

Closed
msyyc opened this issue Mar 21, 2025 · 0 comments · Fixed by #40177
Closed

[pipeline] migrate some functions from auto_release to sdk generation pipeline #40175

msyyc opened this issue Mar 21, 2025 · 0 comments · Fixed by #40177
Assignees
Labels
Mgmt-EngSys Engineering System (Management Plane Specific)

Comments

@msyyc
Copy link
Member

msyyc commented Mar 21, 2025

For self-service, service team may use new pipeline https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4642206&view=results to generate SDK PR.

New pipeline calls script used in SDK generation pipeline. Compared with auto_release, scripts of SDK generation pipeline lacks some functions. Without these functions, service team may need more manual work in the generated code. To make new pipeline more convenient, we had better migrate some functions from auto_release to the scripts used by SDK generation pipeline.

@msyyc msyyc self-assigned this Mar 21, 2025
@msyyc msyyc added the Mgmt-EngSys Engineering System (Management Plane Specific) label Mar 21, 2025
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 21, 2025
@xiangyan99 xiangyan99 removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mgmt-EngSys Engineering System (Management Plane Specific)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants