Pipeline(E2E): move ModelKitArtifacts ref conditional into top-level …#833
Merged
Conversation
…variable
Azure Pipelines does not allow ${{ if }} / ${{ else }} template expressions in the YAML key position inside a
esources.repositories entry. PR #823 used that pattern to switch the artifact repo's
ef between Build.SourceBranch and main, which caused the pipeline parser to fail with:
A template expression is not allowed in this context (Line 61/63)
Move the conditional into a top-level compile-time �ariables block (which does support ${{ if }}: value: ... / ${{ else }}: value: ...) and reference the resulting �rtifactsRef from
esources.repositories.ModelKitArtifacts.ref as a plain value-position template expression — which is the pattern explicitly enabled by ADO Sprint 212.
timenick
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…variable
Azure Pipelines does not allow ${{ if }} / ${{ else }} template expressions in the YAML key position inside a
esources.repositories entry. PR #823 used that pattern to switch the artifact repo's
ef between Build.SourceBranch and main, which caused the pipeline parser to fail with:
A template expression is not allowed in this context (Line 61/63)
Move the conditional into a top-level compile-time �ariables block (which does support ${{ if }}: value: ... / ${{ else }}: value: ...) and reference the resulting �rtifactsRef from
esources.repositories.ModelKitArtifacts.ref as a plain value-position template expression — which is the pattern explicitly enabled by ADO Sprint 212.