Remove single-stage-pipeline-with-resources.yml, use only pipeline-with-resources.yml

[akoeplinger]

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

[ghost]

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.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[radical]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

[akoeplinger]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

Ah yes, thanks.

[akoeplinger]

The failures are unrelated.

[akoeplinger]

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

[ghost]

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.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[radical]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

[akoeplinger]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

Ah yes, thanks.

[akoeplinger]

The failures are unrelated.

[akoeplinger]

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

[ghost]

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.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[radical]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

[akoeplinger]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

Ah yes, thanks.

[akoeplinger]

The failures are unrelated.

[akoeplinger]

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

[ghost]

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.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[radical]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

[akoeplinger]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

Ah yes, thanks.

[akoeplinger]

The failures are unrelated.

[akoeplinger]

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

[ghost]

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.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[radical]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

[akoeplinger]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

Ah yes, thanks.

[akoeplinger]

The failures are unrelated.

[akoeplinger]

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

[ghost]

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.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[radical]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

[akoeplinger]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

Ah yes, thanks.

[akoeplinger]

The failures are unrelated.

[akoeplinger]

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

[ghost]

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.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[radical]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

[akoeplinger]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

Ah yes, thanks.

[akoeplinger]

The failures are unrelated.

[akoeplinger]

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

[ghost]

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.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This reduces nesting of the pipeline templates. We hit an issue on the internal AzDO where the runtime.yml ran into this error:

The 'stages' parameter is not a valid StageList.
/eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml: Maximum events exceeded while evaluating the template. This may indicate an infinite loop or too many nested loops.

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.

Author:	akoeplinger
Assignees:	akoeplinger
Labels:	area-Infrastructure
Milestone:	-

[radical]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

[akoeplinger]

Should eng/pipelines/common/templates/single-stage-pipeline-with-resources.yml be removed now?

Ah yes, thanks.

[akoeplinger]

The failures are unrelated.