dotnet
[release/7.0] Fix servicing failures when building coreclr nuget packages
Backport of #75884 to release/7.0
/cc @ViktorHofer
Customer Impact
Testing
Risk
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Tagging subscribers to this area: @hoyosjs See info in area-owners.md if you want to be subscribed.
Issue Details
Backport of #75884 to release/7.0
/cc @ViktorHofer
Customer Impact
Testing
Risk
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
| Author: | github-actions[bot] |
|---|---|
| Assignees: | - |
| Labels: |
|
| Milestone: | - |
@jeffschwMSFT this infrastructure change is necessary to successfully build 7.0.x servicing bits. This was already part of release/6.0 but was never forward ported into main. Please see the linked issue for more details.
I assume this is a tell-mode only change and can be merged without additional approvals?
I don't think so. Seems to be another AzDO flakiness/outage:
##[warning]Git fetch failed with exit code 128, back off 7.517 seconds before retry.
git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune --prune-tags --progress --no-recurse-submodules origin --depth=20 +1986e7a0aa0866dfc873111fe13f1907888f5ec4:refs/remotes/origin/1986e7a0aa0866dfc873111fe13f1907888f5ec4
fatal: unable to access 'https://github.com/dotnet/runtime/': The requested URL returned error: 429
##[error]Git fetch failed with exit code: 128