e848e3616f
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 Each step has its own signature of success or failure. Using the chain of responsibility pattern to manage all status. Modify the expected-state in each step.
122 lines
4.9 KiB
YAML
122 lines
4.9 KiB
YAML
parameters:
|
|
- name: TOPOLOGY
|
|
type: string
|
|
|
|
- name: POLL_INTERVAL
|
|
type: number
|
|
default: 10
|
|
|
|
- name: POLL_TIMEOUT
|
|
type: number
|
|
default: 36000
|
|
|
|
- name: MIN_WORKER
|
|
type: string
|
|
default: 1
|
|
|
|
- name: MAX_WORKER
|
|
type: string
|
|
default: 2
|
|
|
|
- name: TEST_SET
|
|
type: string
|
|
default: ""
|
|
|
|
- name: DEPLOY_MG_EXTRA_PARAMS
|
|
type: string
|
|
default: ""
|
|
|
|
- name: MGMT_BRANCH
|
|
type: string
|
|
default: master
|
|
|
|
- name: COMMON_EXTRA_PARAMS
|
|
type: string
|
|
default: ""
|
|
|
|
steps:
|
|
- script: |
|
|
set -ex
|
|
# always use the test plan script from master branch.
|
|
wget -O ./.azure-pipelines/test_plan.py https://raw.githubusercontent.com/sonic-net/sonic-mgmt/master/.azure-pipelines/test_plan.py
|
|
wget -O ./.azure-pipelines/pr_test_scripts.yaml https://raw.githubusercontent.com/sonic-net/sonic-mgmt/${{ parameters.MGMT_BRANCH }}/.azure-pipelines/pr_test_scripts.yaml
|
|
displayName: Download TestbedV2 scripts
|
|
|
|
- script: |
|
|
set -ex
|
|
pip install PyYAML
|
|
rm -f new_test_plan_id.txt
|
|
python ./.azure-pipelines/test_plan.py create -t ${{ parameters.TOPOLOGY }} -o new_test_plan_id.txt --min-worker ${{ parameters.MIN_WORKER }} --max-worker ${{ parameters.MAX_WORKER }} \
|
|
--test-set ${{ parameters.TEST_SET }} --kvm-build-id $(KVM_BUILD_ID) --deploy-mg-extra-params "${{ parameters.DEPLOY_MG_EXTRA_PARAMS }}" --mgmt-branch ${{ parameters.MGMT_BRANCH }} \
|
|
--common-extra-params "${{ parameters.COMMON_EXTRA_PARAMS }}"
|
|
TEST_PLAN_ID=`cat new_test_plan_id.txt`
|
|
|
|
echo "Created test plan $TEST_PLAN_ID"
|
|
echo "Check https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID for test plan status"
|
|
echo "##vso[task.setvariable variable=TEST_PLAN_ID]$TEST_PLAN_ID"
|
|
env:
|
|
TESTBED_TOOLS_URL: $(TESTBED_TOOLS_URL)
|
|
TENANT_ID: $(TESTBED_TOOLS_MSAL_TENANT_ID)
|
|
CLIENT_ID: $(TESTBED_TOOLS_MSAL_CLIENT_ID)
|
|
CLIENT_SECRET: $(TESTBED_TOOLS_MSAL_CLIENT_SECRET)
|
|
displayName: Trigger test
|
|
|
|
- script: |
|
|
set -ex
|
|
echo "Lock testbed"
|
|
echo "TestbedV2 is just online and might not be stable enough, for any issue, please send email to sonictestbedtools@microsoft.com"
|
|
echo "Runtime detailed progress at https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID"
|
|
# When "LOCK_TESTBED" finish, it changes into "PREPARE_TESTBED"
|
|
python ./.azure-pipelines/test_plan.py poll -i "$(TEST_PLAN_ID)" --expected-state LOCK_TESTBED
|
|
env:
|
|
TESTBED_TOOLS_URL: $(TESTBED_TOOLS_URL)
|
|
displayName: Lock testbed
|
|
|
|
- script: |
|
|
set -ex
|
|
echo "Prepare testbed"
|
|
echo "Preparing the testbed(add-topo, deploy-mg) may take 15-30 minutes. Before the testbed is ready, the progress of the test plan keeps displayed as 0, please be patient(We will improve the indication in a short time)"
|
|
echo "If the progress keeps as 0 for more than 1 hour, please cancel and retry this pipeline"
|
|
echo "TestbedV2 is just online and might not be stable enough, for any issue, please send email to sonictestbedtools@microsoft.com"
|
|
echo "Runtime detailed progress at https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID"
|
|
# When "PREPARE_TESTBED" finish, it changes into "EXECUTING"
|
|
python ./.azure-pipelines/test_plan.py poll -i "$(TEST_PLAN_ID)" --expected-state PREPARE_TESTBED
|
|
env:
|
|
TESTBED_TOOLS_URL: $(TESTBED_TOOLS_URL)
|
|
displayName: Prepare testbed
|
|
|
|
- script: |
|
|
set -ex
|
|
echo "Run test"
|
|
echo "TestbedV2 is just online and might not be stable enough, for any issue, please send email to sonictestbedtools@microsoft.com"
|
|
echo "Runtime detailed progress at https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID"
|
|
# When "EXECUTING" finish, it changes into "KVMDUMP", "FAILED", "CANCELLED" or "FINISHED"
|
|
python ./.azure-pipelines/test_plan.py poll -i "$(TEST_PLAN_ID)" --expected-state EXECUTING
|
|
env:
|
|
TESTBED_TOOLS_URL: $(TESTBED_TOOLS_URL)
|
|
displayName: Run test
|
|
|
|
- script: |
|
|
set -ex
|
|
echo "KVM dump"
|
|
echo "TestbedV2 is just online and might not be stable enough, for any issue, please send email to sonictestbedtools@microsoft.com"
|
|
echo "Runtime detailed progress at https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID"
|
|
# When "KVMDUMP" finish, it changes into "FAILED", "CANCELLED" or "FINISHED"
|
|
python ./.azure-pipelines/test_plan.py poll -i "$(TEST_PLAN_ID)" --expected-state KVMDUMP
|
|
condition: succeededOrFailed()
|
|
env:
|
|
TESTBED_TOOLS_URL: $(TESTBED_TOOLS_URL)
|
|
displayName: KVM dump
|
|
|
|
- script: |
|
|
set -ex
|
|
echo "Try to cancel test plan $TEST_PLAN_ID, cancelling finished test plan has no effect."
|
|
python ./.azure-pipelines/test_plan.py cancel -i "$(TEST_PLAN_ID)"
|
|
condition: always()
|
|
env:
|
|
TESTBED_TOOLS_URL: $(TESTBED_TOOLS_URL)
|
|
TENANT_ID: $(TESTBED_TOOLS_MSAL_TENANT_ID)
|
|
CLIENT_ID: $(TESTBED_TOOLS_MSAL_CLIENT_ID)
|
|
CLIENT_SECRET: $(TESTBED_TOOLS_MSAL_CLIENT_SECRET)
|
|
displayName: Finalize running test plan
|