{CI} Migrate azure cli pipelines #24201
Conversation
ghost
added
ghost
requested review from
|
Migrate cli pipelines |
|
/azp where |
|
Azure DevOps orgs getting events for this repository: |
|
CI/CD Pipelines for this repository: |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
| @@ -187,7 +187,7 @@ msbuild /t:rebuild /p:Configuration=Release %REPO_ROOT%\build_scripts\windows\az | |||
|
|
|||
| if %errorlevel% neq 0 goto ERROR | |||
|
|
|||
| start %OUTPUT_DIR% | |||
| echo %OUTPUT_DIR% | |||
There was a problem hiding this comment.
Using start command in 1ES agent pool gets stuck, replace with echo command.
| python /mnt/vss/_work/1/s/scripts/live_test/monitor.py "$(DB_PWD)" "$(GITHUB_TOKEN)" |
There was a problem hiding this comment.
After using the 1ES agent pool, the pipeline working directory has changed, need to change /home/vsts/work to /mnt/vss/_work
There was a problem hiding this comment.
Is it possible to use predefined variables instead of hardcoding it to /mnt/vss/_work/1/s?
There was a problem hiding this comment.
The building DEB pipeline uses BUILD_SOURCESDIRECTORY as /home/vsts/work/1/s:
| @@ -17,7 +17,7 @@ | |||
|
|
|||
|
|
|||
| def main(): | |||
| env = Environment(loader=FileSystemLoader('/home/vsts/work/1/s/scripts/live_test/')) | |||
| env = Environment(loader=FileSystemLoader('/mnt/vss/_work/1/s/scripts/live_test/')) | |||
There was a problem hiding this comment.
There is a variable Pipeline.Workspace has the value /home/vsts/work/1, but we still need to hardcode /home/vsts, /home/vsts/work and /home/vsts/work/1/s and etc.
Considering it's a one-time job, can we keep using the hardcoding?
| testRunTitle: 'Azure CLI live test results of $(Target)' | ||
| # mergeTestResults: true | ||
| # testResultsFormat: 'JUnit' | ||
| - task: PublishBuildArtifacts@1 | ||
| condition: succeededOrFailed() | ||
| inputs: | ||
| PathtoPublish: '/home/vsts/work/1/$(Target).report.json' | ||
| PathtoPublish: '/mnt/vss/_work/1/$(Target).report.json' |
There was a problem hiding this comment.
/home/vsts/work/1 is available as Pipeline.Workspace.
| @@ -59,20 +62,20 @@ jobs: | |||
| - task: PublishTestResults@2 | |||
| condition: succeededOrFailed() | |||
| inputs: | |||
| testResultsFiles: '/home/vsts/.azdev/env_config/home/vsts/work/1/env/test_results.xml' | |||
| testResultsFiles: '/mnt/vss/.azdev/env_config/mnt/vss/_work/1/env/test_results.xml' | |||
There was a problem hiding this comment.
azdev saves its config to ~/.azdev:
so /mnt/vss should be available as ~ or $HOME.
There was a problem hiding this comment.
/home/vsts: Not found
/home/vsts/work: Not found
/home/vsts/work/1: Pipeline.Workspace or Agent.BuildDirectory
/home/vsts/work/1/a: Build.ArtifactStagingDirectory
/home/vsts/work/1/b: Build.BinariesDirectory
/home/vsts/work/1/s: System.DefaultWorkingDirectory or Build.SourcesDirectory
/home/vsts/work/1/TestResults: Common.TestResultsDirectory
/home/cloudtest: ~
/usr/local/vss-agent/2.214.1: Agent.HomeDirectory
* update agent pool * Update azure-pipelines.yml * update * Update build.cmd * Update azure-pipelines.yml * update * Update azure-pipelines.yml * update
Migrate azure cli pipelines to https://dev.azure.com/azclitools
Azure.azure-cli
Azure.azure-cli Full Test
Aladdin Document Parser
Azure CLI ARM64
Azure CLI Build SAW MSI
Azure CLI installation benchmark
Azure CLI Live Test Monitor
Azure CLI Live Test
Azure CLI Regression Test
CLI installation time
Azure CLI beta Release
Azure CLI Release
Prepare for Release Build
Azure CLI Edge Release