Skip to content

Conversation

@pjcollins
Copy link
Member

@pjcollins pjcollins commented Oct 13, 2021

The test stages that run in a given PR are selected dynamically after
checking which files have changed in the PR. This behavior relies on
the output variables Azure Pipelines feature. In order to access
the output variable containing test stage information in in other
stages, the step that sets it must use the name: key.

Fix output variable setting from the xaprepare yaml template by adding
an option name parameter.

@pjcollins pjcollins requested a review from jonpryor as a code owner October 13, 2021 15:54
@pjcollins pjcollins requested a review from jpobst October 13, 2021 15:54
The test stages that run in a given PR are selected dynamically after
checking which files have changed in the PR.  This behavior relies on
the [output variables][0] Azure Pipelines feature.  In order to access
the output variable in other stages, the step that sets it must use the
`name:` property.

Fix output variable setting from the xaprepare yaml template by adding
an option `name` parameter.

[0]: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#use-output-variables-from-tasks
Copy link
Contributor

@jpobst jpobst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If CI likes it, change looks good. Thanks for fixing this!

@jpobst jpobst merged commit fbbdc9f into dotnet:main Oct 13, 2021
@pjcollins pjcollins deleted the prepare-outputvar branch October 13, 2021 20:48
@github-actions github-actions bot locked and limited conversation to collaborators Jan 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants