Difference between revisions of "CSIT/Jobs"
From fd.io
< CSIT
(→VPP Jenkins Verify Jobs: Verify a VPP patch using an operational CSIT branch) |
(→CSIT Jenkins Periodic Jobs: Periodically verify VPP branch with ALL CSIT tests) |
||
| Line 127: | Line 127: | ||
|} | |} | ||
| − | ==CSIT Jenkins Periodic Jobs: Periodically verify VPP branch | + | ==CSIT Jenkins Periodic Jobs: Periodically verify VPP branch and CSIT branch== |
| − | + | Because these jobs take many hours to run, they are only triggered periodically to prevent blocking per patch verification by tying up hardware resources. There are two types of Jenkins periodic jobs: | |
| + | |||
| + | 1. Jobs that verify VPP images using all CSIT tests. | ||
| + | |||
| + | 2. Jobs that verify CSIT branch with verified stable VPP build. | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 134: | Line 138: | ||
|- | |- | ||
|[https://jenkins.fd.io/view/csit/job/csit-vpp-verify-master-semiweekly/ csit-vpp-verify-master-semiweekly] | |[https://jenkins.fd.io/view/csit/job/csit-vpp-verify-master-semiweekly/ csit-vpp-verify-master-semiweekly] | ||
| − | |Verify VPP image | + | |Verify latest VPP image of 'master' from nexus.fd.io. If all tests pass, the "VPP_STABLE_VER" of 'master' image used to verify CSIT patches can be updated (by CSIT patch). |
| − | |Twice a week ( | + | |Twice a week (start at 4AM UTC every Tuesday and Saturday) |
|csit branch 'oper-<$DATE>' | |csit branch 'oper-<$DATE>' | ||
| − | |vpp branch 'master' | + | |vpp branch 'master' from nexus.fd.io |
| − | |WORKING | + | |WORKING (Console output of latest jenkins job shows this is downloading VPP 'stable/1606' - correction is ready with patch https://gerrit.fd.io/r/#/c/1892/) |
|- | |- | ||
|[https://jenkins.fd.io/view/csit/job/csit-vpp-verify-1606-semiweekly/ csit-vpp-verify-1606-semiweekly] | |[https://jenkins.fd.io/view/csit/job/csit-vpp-verify-1606-semiweekly/ csit-vpp-verify-1606-semiweekly] | ||
| − | |Verify VPP image | + | |Verify VPP image of 'stable/1606' from nexus.fd.io. If all tests pass, the "VPP_STABLE_VER" of 'stable/1606' image used to verify CSIT patches can be updated (by CSIT patch). |
| − | |Twice a week ( | + | |
| + | |Twice a week (start at 4AM UTC every Tuesday and Saturday) | ||
|csit branch 'oper-rls1606-<$DATE>' | |csit branch 'oper-rls1606-<$DATE>' | ||
| − | |vpp branch 'stable/1606' | + | |vpp branch 'stable/1606' from nexus.fd.io |
|WORKING | |WORKING | ||
|- | |- | ||
|[https://jenkins.fd.io/view/csit/job/csit-vpp-verify-master-weekly/ csit-vpp-verify-master-weekly] | |[https://jenkins.fd.io/view/csit/job/csit-vpp-verify-master-weekly/ csit-vpp-verify-master-weekly] | ||
| − | |Verify CSIT | + | |Verify CSIT 'master' HEAD image using "VPP_STABLE_VER" of 'master' branch. If all tests pass, create csit branch 'oper-<$DATE>' that can be used for VPP verify Jenkins jobs. |
| − | |Once a week ( | + | |Once a week (start at 4AM UTC every Sunday) |
|csit branch 'master' HEAD | |csit branch 'master' HEAD | ||
| − | |stable vpp branch 'master'image from nexus.fd.io | + | |stable vpp branch 'master' image from nexus.fd.io |
|WORKING | |WORKING | ||
|- | |- | ||
|[https://jenkins.fd.io/view/csit/job/csit-vpp-verify-1606-weekly/ csit-vpp-verify-1606-weekly] | |[https://jenkins.fd.io/view/csit/job/csit-vpp-verify-1606-weekly/ csit-vpp-verify-1606-weekly] | ||
| − | |Verify CSIT | + | |Verify CSIT 'master' HEAD image using "VPP_STABLE_VER" of ''stable/1606' branch. If all tests pass, create csit branch 'oper-rls1606-<$DATE>' that can be used for VPP verify Jenkins jobs. |
|As required | |As required | ||
|csit branch 'rls1606' HEAD | |csit branch 'rls1606' HEAD | ||
Revision as of 22:09, 8 July 2016
Contents
VPP Jenkins Verify Jobs: Verify a VPP patch using an operational CSIT branch
The following jenkins jobs verify VPP patches by running CSIT tests based on gerrit events for the VPP git repository or manual scheduling based on gerrit comment trigger keywords posted to a VPP patch in gerrit. The version of the CSIT tests which are executed is determined by a script that is checked into each VPP branch. See CSIT/Branching_Strategy for details.
| Jenkins Job | Description | Gerrit Comment Trigger | Event Triggers | VPP Code | Testbed | Status |
|---|---|---|---|---|---|---|
| vpp-csit-verify-virl-master | Verify VPP patches by running csit functional tests | recheck | gerrit patch commit, gerrit rebase, gerrit edit | vpp branch 'master' + gerrit patch | LF VIRL compute nodes | WORKING |
| vpp-csit-verify-hw-perf-master-short | Verify VPP patches by running csit short performance tests | verify-perf-short | none | vpp branch 'master' + gerrit patch | LF HW compute nodes | WORKING |
| vpp-csit-verify-hw-perf-master-long | Verify VPP patches by running csit long performance tests | verify-perf-long | none | vpp branch 'master' + gerrit patch | LF HW compute nodes | WORKING |
| vpp-csit-verify-hw-perf-master-all | Verify VPP patches by running all csit tests (func., short perf., long perf.) | verify-perf-all | none | vpp branch 'master' + gerrit patch | LF HW compute nodes | WORKING |
| vpp-csit-verify-virl-1606 | Verify VPP patches by running csit functional tests | recheck | gerrit patch commit, gerrit rebase, gerrit edit | vpp branch 'stable/1606' + gerrit patch | LF VIRL compute nodes | WORKING |
| vpp-csit-verify-hw-perf-1606-short | Verify VPP patches by running csit short performance tests | verify-perf-short | none | vpp branch 'stable/1606' + gerrit patch | LF HW compute nodes | WORKING |
| vpp-csit-verify-hw-perf-1606-long | Verify VPP patches by running csit long performance tests | verify-perf-long | none | vpp branch 'stable/1606' + gerrit patch | LF HW compute nodes | WORKING |
| vpp-csit-verify-hw-perf-1606-all | Verify VPP patches by running all csit tests (func., short perf., long perf.) | verify-perf-all | none | vpp branch 'stable/1606' + gerrit patch | LF HW compute nodes | WORKING |
CSIT Jenkins Verify Jobs: Verify a CSIT patch using a validated VPP image
The following jenkins jobs verify CSIT patches by running CSIT tests based on gerrit events for the CSIT git repository or manual scheduling based on gerrit comment trigger keywords posted to a CSIT patch in gerrit. The VPP images used to verify the CSIT patches is based on the latest VPP image that has been validated by the CSIT semi-weekly verify job.
| Jenkins Job | Description | Gerrit Comment Trigger | Event Triggers | CSIT Code | Testbed | Status |
|---|---|---|---|---|---|---|
| csit-vpp-functional-master-virl | Verify CSIT functional tests against a validated VPP 'master' image | recheck | gerrit patch commit, gerrit rebase, gerrit edit | csit branch 'master' + csit patch | LF VIRL compute nodes | WORKING |
| csit-vpp-perf-master-all | Verify CSIT code changes against VPP 'master' - all performance tests | verify-perf-all | none | csit branch 'master' + csit patch | LF HW compute nodes | WORKING |
| csit-vpp-perf-master-long | Verify CSIT code changes against VPP 'master' - long performance tests | verify-perf-long | none | csit branch 'master' + csit patch | LF HW compute nodes | WORKING |
| csit-vpp-functional-1606-virl | Verify CSIT functional tests against a validated VPP 'stable/1606' image | recheck | gerrit patch commit, gerrit rebase, gerrit edit | csit branch 'rls1606' + csit patch | LF VIRL compute nodes | WORKING |
| csit-vpp-perf-1606-all | Verify CSIT code against VPP 16.06 release 'stable/1606' - all performance tests | verify-perf-all | none | csit branch 'rls1606' + csit patch | LF HW compute nodes | WORKING |
| csit-vpp-perf-1606-long | Verify CSIT code against VPP 16.06 release 'stable/1606' - long performance tests | verify-perf-long | none | csit branch 'rls1606' + csit patch | LF HW compute nodes | WORKING |
CSIT Jenkins Periodic Jobs: Periodically verify VPP branch and CSIT branch
Because these jobs take many hours to run, they are only triggered periodically to prevent blocking per patch verification by tying up hardware resources. There are two types of Jenkins periodic jobs:
1. Jobs that verify VPP images using all CSIT tests.
2. Jobs that verify CSIT branch with verified stable VPP build.
| Jenkins Job | Description | Execution Period | CSIT Code | VPP Code | Status |
|---|---|---|---|---|---|
| csit-vpp-verify-master-semiweekly | Verify latest VPP image of 'master' from nexus.fd.io. If all tests pass, the "VPP_STABLE_VER" of 'master' image used to verify CSIT patches can be updated (by CSIT patch). | Twice a week (start at 4AM UTC every Tuesday and Saturday) | csit branch 'oper-<$DATE>' | vpp branch 'master' from nexus.fd.io | WORKING (Console output of latest jenkins job shows this is downloading VPP 'stable/1606' - correction is ready with patch https://gerrit.fd.io/r/#/c/1892/) |
| csit-vpp-verify-1606-semiweekly | Verify VPP image of 'stable/1606' from nexus.fd.io. If all tests pass, the "VPP_STABLE_VER" of 'stable/1606' image used to verify CSIT patches can be updated (by CSIT patch). | Twice a week (start at 4AM UTC every Tuesday and Saturday) | csit branch 'oper-rls1606-<$DATE>' | vpp branch 'stable/1606' from nexus.fd.io | WORKING |
| csit-vpp-verify-master-weekly | Verify CSIT 'master' HEAD image using "VPP_STABLE_VER" of 'master' branch. If all tests pass, create csit branch 'oper-<$DATE>' that can be used for VPP verify Jenkins jobs. | Once a week (start at 4AM UTC every Sunday) | csit branch 'master' HEAD | stable vpp branch 'master' image from nexus.fd.io | WORKING |
| csit-vpp-verify-1606-weekly | Verify CSIT 'master' HEAD image using "VPP_STABLE_VER" of stable/1606' branch. If all tests pass, create csit branch 'oper-rls1606-<$DATE>' that can be used for VPP verify Jenkins jobs. | As required | csit branch 'rls1606' HEAD | stable vpp branch 'stable/1606'image from nexus.fd.io | DOES NOT EXIST |
