This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Use .asArray/.asString syntax for scenarios and helixQueues #22173
Conversation
This file contains 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
RussKeldorph
approved these changes
Jan 24, 2019
|
@vtbassmatt @chcosta Matt Chris can you please confirm that there is no better way of doing this? What I need is a function like |
|
I opened issue microsoft/azure-pipelines-yaml#90 asking this question a month ago - but not sure if was a right repo for asking though |
|
I don't think we have anything that'll do it right now. Implicit casting might get you part of the way there (and even that, I'm not sure about) but it would include a bunch of quotation marks and brackets that you don't want. |
sbomer
approved these changes
Jan 24, 2019
jashook
approved these changes
Jan 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As far as I know, there is no way in Yaml to convert between comma-separated strings and arrays (i.e. neither
String.Join(",", items)norstr.Split(',')are available). As an unfortunate workaround, I propose to use the .asString/.as Array syntax for properties that are needed in both formats.As an example, right now we are using scenarios and helixQueues* properties only as an MSBuild input (i.e. comma-separated string passed as MSBuild properties).
For the purpose of enabling test publishing to Azure DevOps using officially supported task we would need to iterate over Helix queues and scenarios to call the task multiple times so we would those to be array values.