2bf2e02719
co-authorized by: jianquanye@microsoft.com Why I did it Now, checkout code step and KVM test job can't be cancelled even though the whole build is cancelled. That's because by using Azure Pipeline Conditions, we customized the running condition, and we need to react to the Cancel action explicitly by asserting 'succeeded' https://learn.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops#succeeded https://learn.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops&tabs=yaml#ive-got-a-conditional-step-that-runs-even-when-a-job-is-canceled-how-do-i-manage-to-cancel-all-jobs-at-once How I did it Assert 'succeeded' condition explicitly. How to verify it Verified by cancelling and rerunning the azure pipeline. |
||
|---|---|---|
| .. | ||
| azure-pipelines-build.yml | ||
| azure-pipelines-download-certificate.yml | ||
| azure-pipelines-image-template.yml | ||
| azure-pipelines-job-groups.yml | ||
| azure-pipelines-Official.yml | ||
| azure-pipelines-repd-build-variables.yml | ||
| azure-pipelines-UpgrateVersion.yml | ||
| build-commonlib.yml | ||
| build-template.yml | ||
| check-dirty-version.yml | ||
| cleanup.yml | ||
| docker-sonic-mgmt.yml | ||
| docker-sonic-slave-template.yml | ||
| docker-sonic-slave.yml | ||
| dpkg-cache-cleanup.yml | ||
| official-build-cache.yml | ||
| official-build-cisco-8000.yml | ||
| official-build-multi-asic.yml | ||
| official-build.yml | ||
| run-test-template.yml | ||
| template-clean-sonic-slave.yml | ||
| template-commonlib.yml | ||
| template-skipvstest.yml | ||
| template-variables.yml | ||
| trigger-publish-artifacts-build.yml | ||
| vstest-exclude | ||
| vstest-include | ||