2.1 KiB
Overview
This doc shows some common problems and resolution in CI.
Broken links
Add the broken links into eng/ignore-links.txt file to bypass this verification or you could update the broken links to valid ones, see example PR here.
Check spelling (cspell)
For new service the error usually happens, fix spelling in code or in markdown at file .vscode/cspell.json. See an example in devcenter PR.
Push failure\
Spawn pwsh ENOENT
Install Powershell. Make sure pwsh command works at this step (If you follow the above link, pwsh is typically added to the system environment variables by default.)
Authorization issue
If you are from service team, External to azure-sdk, you can follow these steps:
-
To request write access, join an appropriate team from this list(same list on MS OpenSource portal) that corresponds with the product or org that you work in. Be sure to join only one team.
-
If you don't see your team in the list? Contact Scott Kurtzeborn : scotk@microsoft.com to create a new one for your service team.
For more details, join a partner write team
Note
For merge permissions to main branches, you must be a member of an azure-sdk-push team. These permissions are assigned on case-by-case basis only. Reach out to Scott Kurtzeborn : scotk@microsoft.com if you think that your team needs that permission.