24758dfe0a
The display of azure pipeline is not specific now, such as when the step Run test fails, the display of itself shows successful, but the display of step Kvmdump shows fails, but actually, the step Kvmdump doesn't fail. I improve the display of azure pipeline in this pr, each step has its own success or failure, and is shown in azure pipeline. Why I did it The display of azure pipeline is not specific now, such as when the step Run test fails, the display of itself shows successful, but the display of step Kvmdump shows fails, but actually, the step Kvmdump doesn't fail. I improve the display of azure pipeline in this pr, each step has its own success or failure, and is shown in azure pipeline. How I did it 1. Each step has its own signature of success or failure. 2. Using the chain of responsibility pattern to manage all status. 3. Modify the expected-state in each step. |
||
---|---|---|
.. | ||
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.yml | ||
run-test-scheduler-template.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 |