Using Dynamic Matrix Config#31542
Conversation
|
/azp run js - pullrequest |
|
/azp run js - pullrequest |
|
/azp run js - pullrequest |
|
/azp run js - pullrequest |
… and no matter what I do AZDO is refusing to queue the build
|
/azp run js - matrix-pullrequest |
|
/azp run js - matrix-pullrequest |
1 similar comment
|
/azp run js - matrix-pullrequest |
| } | ||
|
|
||
| # if we know this is the matrix for our file, we should now see if there is a custom matrix config for the package | ||
| $matrixConfigList = GetValueSafelyFrom-Yaml $content @("extends", "parameters", "MatrixConfigs") |
There was a problem hiding this comment.
Does this also handle values behind devops template conditionals? e.g. https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/identity/tests.yml#L33
|
As I mentioned I was wondering if the generation complexity would be high, but the changes necessary are so small that I think it's very reasonable. I think if you add more examples on inline comments of an inputted matrix set to an outputted matrix set, with the actual package name additions then it will be very approachable to maintain/update going forwards. |
Executing! |
…akes 0 sense that it's returning an error. I hate powershell so much
…tually invoking the script
|
/azp run js - matrix-pullrequest |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
All the conversations in this PR ended up being commited in Azure/azure-sdk-tools#9281. Closing this PR in favor of #31420 in this repo. |
I've been thinking a lot about how we can abstract away both the package distribution as well as when specific packages have restrictions on what matrix they run.
This PR updates
generate-job-matrix.ymlwith a possible solution. (A lot of the powershell is not fully filled out as this is just a proto)We will:
This way we will be able to generate multiple platform matrixes while also allowing the custom selections from the users.