-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Remove single-stage-pipeline-with-resources.yml, use only pipeline-with-resources.yml #78968
Conversation
…th-resources.yml This reduces nesting of the pipeline templates.
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsThis reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:
We found out that when we remove one level of nesting through the single-stage-pipeline-with-resources.yml the pipeline works again. This required re-indending a lot of the .yml files though, so I suggest reviewing the PR with whitespace changes ignored. The interesting bit is that we don't hit this on the public AzDO instance, the current theory is that we have different AzDO templating limits applied there.
|
Should |
Ah yes, thanks. |
The failures are unrelated. |
This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:
We found out that when we remove one level of nesting through the single-stage-pipeline-with-resources.yml the pipeline works again. This required re-indending a lot of the .yml files though, so I suggest reviewing the PR with whitespace changes ignored.
The interesting bit is that we don't hit this on the public AzDO instance, the current theory is that we have different AzDO templating limits applied there.