2022-10-19 00:33:17 -05:00
parameters :
- name : TOPOLOGY
type : string
- name : POLL_INTERVAL
type : number
default : 10
- name : POLL_TIMEOUT
type : number
default : 36000
- name : MIN_WORKER
2022-11-30 08:36:55 -06:00
type : string
2022-10-19 00:33:17 -05:00
default : 1
- name : MAX_WORKER
2022-11-30 08:36:55 -06:00
type : string
default : 1
2022-10-19 00:33:17 -05:00
- name : TEST_SET
type : string
default : ""
- name : DEPLOY_MG_EXTRA_PARAMS
type : string
default : ""
2022-11-07 05:48:06 -06:00
- name : COMMON_EXTRA_PARAMS
type : string
default : ""
2022-11-10 01:27:31 -06:00
- name : VM_TYPE
type : string
default : "ceos"
- name : SPECIFIED_PARAMS
type : string
default : "{}"
- name : MGMT_BRANCH
type : string
default : master
2022-11-10 20:54:37 -06:00
- name : NUM_ASIC
type : number
default : 1
2022-10-19 00:33:17 -05:00
steps :
- script : |
2023-03-29 05:35:08 -05:00
set -e
2022-10-19 00:33:17 -05:00
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/master/.azure-pipelines/pr_test_scripts.yaml
displayName : Download TestbedV2 scripts
- script : |
2023-03-29 05:35:08 -05:00
set -e
2022-10-19 00:33:17 -05:00
pip install PyYAML
rm -f new_test_plan_id.txt
2022-11-10 01:27:31 -06:00
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 }}" --common-extra-params "${{ parameters.COMMON_EXTRA_PARAMS }}" \
2022-11-10 20:54:37 -06:00
--mgmt-branch ${{ parameters.MGMT_BRANCH }} --vm-type ${{ parameters.VM_TYPE }} --specified-params "${{ parameters.SPECIFIED_PARAMS }}" \
--num-asic ${{ parameters.NUM_ASIC }}
2022-10-19 00:33:17 -05:00
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 : |
2023-03-29 05:35:08 -05:00
set -e
2022-10-19 00:33:17 -05:00
echo "Lock testbed"
echo "TestbedV2 is just online and might not be stable enough, for any issue, please send email to sonictestbedtools@microsoft.com"
2023-03-29 05:35:08 -05:00
echo "Runtime detailed progress at https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID "
2022-10-19 00:33:17 -05:00
# When "LOCK_TESTBED" finish, it changes into "PREPARE_TESTBED"
Improve the display of pipeline. (#13123)
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.
2023-01-08 20:10:17 -06:00
python ./.azure-pipelines/test_plan.py poll -i "$(TEST_PLAN_ID)" --expected-state LOCK_TESTBED
2022-10-19 00:33:17 -05:00
env :
TESTBED_TOOLS_URL : $(TESTBED_TOOLS_URL)
displayName : Lock testbed
- script : |
2023-03-29 05:35:08 -05:00
set -e
2022-10-19 00:33:17 -05:00
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"
2023-03-29 05:35:08 -05:00
echo "Runtime detailed progress at https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID "
2022-10-19 00:33:17 -05:00
# When "PREPARE_TESTBED" finish, it changes into "EXECUTING"
Improve the display of pipeline. (#13123)
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.
2023-01-08 20:10:17 -06:00
python ./.azure-pipelines/test_plan.py poll -i "$(TEST_PLAN_ID)" --expected-state PREPARE_TESTBED
2022-10-19 00:33:17 -05:00
env :
TESTBED_TOOLS_URL : $(TESTBED_TOOLS_URL)
displayName : Prepare testbed
- script : |
2023-03-29 05:35:08 -05:00
set -e
2022-10-19 00:33:17 -05:00
echo "Run test"
echo "TestbedV2 is just online and might not be stable enough, for any issue, please send email to sonictestbedtools@microsoft.com"
2023-03-29 05:35:08 -05:00
echo "Runtime detailed progress at https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID "
2022-10-19 00:33:17 -05:00
# When "EXECUTING" finish, it changes into "KVMDUMP", "FAILED", "CANCELLED" or "FINISHED"
Improve the display of pipeline. (#13123)
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.
2023-01-08 20:10:17 -06:00
python ./.azure-pipelines/test_plan.py poll -i "$(TEST_PLAN_ID)" --expected-state EXECUTING
2022-10-19 00:33:17 -05:00
env :
TESTBED_TOOLS_URL : $(TESTBED_TOOLS_URL)
displayName : Run test
- script : |
2023-03-29 05:35:08 -05:00
set -e
2022-10-19 00:33:17 -05:00
echo "KVM dump"
echo "TestbedV2 is just online and might not be stable enough, for any issue, please send email to sonictestbedtools@microsoft.com"
2023-03-29 05:35:08 -05:00
echo "Runtime detailed progress at https://www.testbed-tools.org/scheduler/testplan/$TEST_PLAN_ID "
2022-10-19 00:33:17 -05:00
# When "KVMDUMP" finish, it changes into "FAILED", "CANCELLED" or "FINISHED"
Improve the display of pipeline. (#13123)
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.
2023-01-08 20:10:17 -06:00
python ./.azure-pipelines/test_plan.py poll -i "$(TEST_PLAN_ID)" --expected-state KVMDUMP
2022-10-21 12:04:17 -05:00
condition : succeededOrFailed()
2022-10-19 00:33:17 -05:00
env :
TESTBED_TOOLS_URL : $(TESTBED_TOOLS_URL)
displayName : KVM dump
- script : |
2023-03-29 05:35:08 -05:00
set -e
2022-10-19 00:33:17 -05:00
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