зеркало из https://github.com/microsoft/BuildXL.git
e3f6f515d8
BuildXL Release pipeline currently contains two CloudTest tasks. Task Cf runs on CloudTest Int, while task Cg runs on CloudTest Prod. Due to limitations in CloudTest UI, this means the results of the Cg task are not populated in the `1ES Test` tab of Azure DevOps. To fix this, there were two approaches: either move Cf to Prod or move Cg to Int. Moving Cf to Prod is more complicated, since there are build pipeline certificates installed and used specifically by CloudTest Int environment, which are not available on Prod. We are taking the approach of moving Cg task to CloudTest Int. To do this, the SKU and Image used to run the Cg task needed to change, as the currently configured ones are not available on Int environment. Here's a successful run that uses this configuration on CloudTest Int environment: https://cloudtest.visualstudio.com/CloudTest/_build/results?buildId=57793&view=results This is part 1 of two changes required for this to work. After this PR completes, the release pipeline task and the CloudTest Validation(Gvfs) pipelines need to be edited to use the correct CloudTest configuration, which involves the following changes. - Use Int environment instead of Prod - Use wus2-default stamp - Use cloudtest tenant instead of BuildXL |
||
|---|---|---|
| .. | ||
| Gvfs | ||
| BuildXL.CloudTest.TestMap.xml | ||
| deployment.dsc | ||
| module.config.dsc | ||