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.

Sign up for GitHub

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

Jump to bottom

azure-sdk-for-net PR check in azure-rest-api-specs fails with "permission denied" #3162

Closed
mikekistler opened this issue Apr 18, 2022 · 3 comments
Closed

azure-sdk-for-net PR check in azure-rest-api-specs fails with "permission denied" #3162

mikekistler opened this issue Apr 18, 2022 · 3 comments
Assignees
@fengzhou-msft
Labels
SDK Automation Issues related to sdk automation

Comments

@mikekistler
Copy link
Member

The azure-sdk-for net PR check is failing in several PRs in the azure-rest-api-specs repo, e.g.

image
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 18, 2022
@mikekistler mikekistler added Spec PR Tools Tooling that runs in azure-rest-api-specs repo. and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Apr 18, 2022
@akning-ms
Copy link

@fengzhou-msft is working on disable .net SDK track1 generation as there is most of failure caused by SDK testing failure and it will be replaced by .net SDK track 2 generation soon.

@akning-ms akning-ms added SDK Automation Issues related to sdk automation and removed Spec PR Tools Tooling that runs in azure-rest-api-specs repo. labels Apr 27, 2022
@fengzhou-msft
Copy link
Member

@fengzhou-msft is working on disable .net SDK track1 generation as there is most of failure caused by SDK testing failure and it will be replaced by .net SDK track 2 generation soon.

The first batch is done with Azure/azure-rest-api-specs#18996

The plan is that we will no longer support Track 1 SDK automation from swagger repo once it shipped a corresponding beta/GA version of Track 2 SDK. Service Team can still generate the Track 1 SDK within the azure-sdk-for-net repo and request exception if they want to release a track 1 SDK.

@fengzhou-msft
Copy link
Member

Track 1 SDK generation failure is resolved by downgrading CI agent to Ubuntu 18.04. A long term solution nis tracked by Azure/azure-sdk-for-net#31839

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fengzhou-msft fengzhou-msft

Labels
SDK Automation Issues related to sdk automation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fengzhou-msft @akning-ms @mikekistler