Split build/test and publish stages into separate templates #1652
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is needed for https://github.com/dotnet/dotnet-docker-internal/issues/7413, because we need to call the publish stage separately from the build/test stages. I took the simplest approach, which is just making the build and publish stages their own templates, with their own inputs.
build-test-publish-repo.yml
still contains some important default values, so the next step would probably be to push the default values down into the sub-templates. We can also pull the giant nested conditional out ofpublish.yml
back up intobuild-test-publish-repo.yml
, because that logic assumes that you aren't running the publish stage by itself.