summaryrefslogtreecommitdiffstats
path: root/jjb/apex/apex.yml.j2
AgeCommit message (Collapse)AuthorFilesLines
2017-10-08Disable timed dovetail danube jobsxudan1-1/+1
Dovetail danube jobs don't need to be triggerred every day now. Disable the timed trigger. If need, they can be triggered manually. Change-Id: I2f114cd17fcd27d0e34be0824be3fc0d072dbae9 Signed-off-by: xudan <xudan16@huawei.com>
2017-10-04Fix Yamllint violations for jjb/apexTrevor Bramwell1-990/+1010
JIRA: RELENG-254 Change-Id: I354d7064c560d4b23e361d556b7fe269d7fb5d26 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-09-27Apex: disable daily job for masterTim Rozet1-1/+4
Even with a timed trigger that shouldn't execute more than once a year, the apex-daily-master job is still triggering every day or so. Using an explicit disable to disable the job. Change-Id: I3b014c0d0899dba617fcb7cfee17ca758b291f9f Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-23Apex: Fixes iso verify depending on previous build workspaceTim Rozet1-0/+5
There is a bug where if there are multiple builds queued and daily build completes, the following iso verify job will try to use the workspace of the completed daily build to get the iso file. However, if another build job has already started it may clean and overwrite the workspace of the daily build job, and the iso verify job will fail because the file is now gone. This makes the build job copy the iso to a tmp directory for apex iso verify to consume. This should be safe since only one daily can run at a time on the host and daily jobs build and iso verify have to always execute on the same node. Change-Id: Ie8e32c4abefbc311e505688d6da2b26ae08ed98f Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-21[Functest] Support functest-suite with Alpine containersJose Lausuch1-1/+2
Updated all the jobs that use functest-suite. For single test cases, we need to know to which docker image the test belongs to. Change-Id: If7db231ccc891233423f2f2bc3aa5b95d048b30a Signed-off-by: Jose Lausuch <jalausuch@suse.com>
2017-09-20Reset the trigger time of Apex danube job on huawei-pod4xudan1-1/+1
The old time is "0 12 * * *", need to set it to "0 1 * * *". Change-Id: Id568dcb638202612ef8d7a9464d71952a95bffe8 Signed-off-by: xudan <xudan16@huawei.com>
2017-09-19Apex: Renables async builds and fixes blocking bugTim Rozet1-24/+85
Previously we had apex-verify-master running multiple instances on virtual-slaves. Apex-verify-master would kick off a build on our build server, and then apex-verify-master would execute deploy multijob and then functest multijob. However we found a bug where jenkins build blocker would see that a deploy finished on the virtual slave, and then execute functest multijob as well as deploy multijob (for the next verify job) at the same time. This patch adds a parent job apex-virtual-{stream} which calls deploy and functest multijob and will block correctly. It also renables having more than 1 apex-verify job running at a time on the virtual slaves. Change-Id: Id15b2415407fc3318f333e3dfc59076d04db4ffb Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-19Apex: fixes gspathname for euphratesTim Rozet1-1/+1
Change-Id: Ia4523a185708a9d29243b522894b38fd1f047682 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-18Apex: Enables euphrates branch for daily CITim Rozet1-1/+12
Disables master daily. Just uses master labels for Euphrates jobs as well. Change-Id: I65b0eed528518c07d3ef4194a021004deabe2ed0 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-14Merge Apex Daily JobsTrevor Bramwell1-28/+32
Merged 'apex-daily-master' and 'apex-daily-danube' into 'apex-daily-{stream}' Change-Id: I2b1e9e3dd0869b6a1f2b1b6415b364a2d9f151d2 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-09-13Bugfix: Add job-template to jobsxudan1-0/+1
The last patch to add apex danube jobs on huawei-pod4 forget to add the job-template to the jobs list. Change-Id: I671faa2068bab517adc59ad8597e9c05330d528f Signed-off-by: xudan <xudan16@huawei.com>
2017-09-14Merge "Apex, Dovetail: run proposed_test against Apex on huawei_pod4"Jun Li1-0/+67
2017-09-13Apex, Dovetail: run proposed_test against Apex on huawei_pod4Peng Liu1-0/+67
Run Dovetail proposed_test job against Apex Danube daily on huawei_pod4. Change-Id: I14f4f86caa2b1fb2802b5ea154edec47784209cc Signed-off-by: Peng Liu <pliu@redhat.com>
2017-09-08installers: Use global macro 'clean-workspace'Alexandru Avadanii1-8/+1
Change-Id: I34a555697d963efc38064a7b53f25191d6bf1382 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-09-08Apex: Explicitly define file pathsTim Rozet1-1/+53
Due to bug with forbidden file paths conflicting with file paths this explicitly defines all the file paths in apex. This isn't the greatest solution in the case where someone adds a new folder, but chances are they will also modify one of the other files as well. Note it also fixes a bug where unit tests woudl run twice because it would be triggered as part of apex-verify-master and apex-unit-tests-master. Change-Id: I6b10f8eb70c2cd7c8dd5c01363e06b7458c00127 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-07Apex: adds daily flex jobTim Rozet1-5/+13
Change-Id: I19fff409b5e8335ff44f0d9ba8167d3e882a9ad5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-07Apex: Add daily flex jobTim Rozet1-0/+72
Change-Id: Ide3c39d508d26be40e73cec13cd00eace984b6cc Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-07Add file-paths **agardner1-1/+5
this should make forbidden-file-paths work Change-Id: I18d63bffb92abd916eae54c7aafe9a8e1e98926f Signed-off-by: agardner <agardner@linuxfoundation.org>
2017-09-07Apex: temporarily disable strict forbidden file pathTim Rozet1-1/+1
Change-Id: I360cd5ba894022cd30cf7237e8338ab2e213c940 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-06Apex: remove file-paths from triggers for verifyTim Rozet1-11/+2
Change-Id: I0c6e54ce4caf0b6889bac62b25afcee2706ca75f Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-06Apex: fixes verify with only unit test changesTim Rozet1-1/+4
If we make changes to apex/tests path it is only unit tests and we do not want to trigger apex-verify-stream. Change-Id: I42ef56330883ea6e9643f24567eaee3d5fa36071 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-05Merge "Move apex build jobs into 'apex-project-jobs' file"Tim Rozet1-107/+0
2017-09-02Apex: re-enable storperf on os-nosdn-nofeature-haTim Rozet1-12/+13
Change-Id: Ia48b95589e6365102fef54444a8e334a80301dd2 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-09-01Move apex build jobs into 'apex-project-jobs' fileTrevor Bramwell1-107/+0
Since these jobs don't deal with scenarios they can safely be moved to another file without the need to duplicate the scenario listings. Fixes a bug with 'concurrent-builds' not being set due to missing quotation marks. JIRA: RELENG-287 Change-Id: Icce39620521c7d25476553115efbaa9063ca2e17 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-08-30Apex: fixes trigger for gate jobTim Rozet1-0/+2
Change-Id: I0bd9f2bac11b4161da4b6cdfa0a0c6d444020944 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-30Apex: Detect deploy scenario for functest on gate jobTim Rozet1-1/+5
Change-Id: I3f0119db7b7cade3ddd2dbeaa97e03e1fea58798 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-28Apex: increase deploy timeout by 20 minTim Rozet1-1/+1
Change-Id: I3e5a08996e896bcf7b88c97b503de414f7f3ee71 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-28Apex: limits verify per node to 1Tim Rozet1-2/+12
This will limit how many simultaneous builds we can do at a time on build server, but will stop the bug we are hitting where deploy (next job) and functest (current job) start at the same time by blocking parent jobs. Change-Id: If23ce857d7ef043c408b0eb6a74357ce1278e4b9 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-28Apex: disable storperf in dailyTim Rozet1-12/+12
storperf has infinite loop: https://build.opnfv.org/ci/job/storperf-apex-baremetal-daily-master/10/consoleFull Change-Id: I526cddbda15c6262b4afd7c30b6d2681011f48a5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-27Apex: fix verify trigger pathsTim Rozet1-1/+3
Change-Id: I3878f3e1a85b31ddba8d3f53e774a9e1d16f8afb Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-24Apex: Fixes bug with blockingTim Rozet1-1/+1
We have blocking so that deploy wont run while another deploy or functest is running. However there is an issue where after a deploy completes, the next in line deploy starts at the same time as the functest starts for the previous deploy. This patch adds a quiet period to the deploy job of 30 seconds, which hopefully will offset the start time between the two and resume correct blocking. Change-Id: Id94d075f2d2e48952a5c2186eeb81d09bb68c49b Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-23storperf: Create daily job for storperfFatih Degirmenci1-0/+13
Change-Id: I999640281d8e15132c9024e25e43122d2a12baf7 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com> Signed-off-by: mbeierl <mark.beierl@dell.com>
2017-08-15Apex: fixes test suite always running even when deploy failsTim Rozet1-2/+1
According to the multijob builder, condtion: "condition (str) – when to trigger the other job". Other job in this case means the next job I believe. Change-Id: I084fffc80584ad683345f6040ec0081c16513c8d Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-08-02Apex: fix groovy build result updateTim Rozet1-12/+4
The groovy script is working, but it is changing the 'apex test suite' phase to unstable and we really want it to change the 'scenario' job result to unstable if deploy passed but tests failed. Therefore this patch moves the groovy plugin to execute on the scenario job, and looks for deploy successful before changing the build result. Change-Id: I1b6907f4fb2647e644c4a627be6e481fff32f195 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-07-27Apex: changes build result using groovy-postbuildTim Rozet1-0/+14
Conditional plugin does not work for detecting current status in mulitjob, but groovy publisher does. Shown to be working in sandbox job: https://sandbox.opnfv.org/view/All/job/test_groovy_publisher/17/ Change-Id: Ic0ed09885bb29254c4bfda24164c5358eda0d20a Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-07-24Bugfix: Add Apex jobs failed because of wrong regexxudan1-1/+1
JIRA: DOVETAIL-470 Bug log: https://build.opnfv.org/ci/job/apex-testsuite-os-nosdn-nofeature-ha-baremetal-master/5/console Can't evaluate expression, false is assumed: groovy.lang.MissingPropertyException: No such property: DEPLOY_SCENARIO for class: Script1 Skipping dovetail-apex-baremetal-proposed_tests-master. Condition was evaluated to false. Change-Id: I8295313a3096b603bd390fdb70d451274a5146bb Signed-off-by: xudan <xudan16@huawei.com>
2017-07-19dovetail: proposed_test run against apexMatthewLi1-0/+14
JIRA: DOVETAIL-359 1)run againt scenarios: os-nosdn-nofeature-ha os-nosdn-kvm-ha os-odl_l3-fdio-ha 2)stream: master 3)details see https://wiki.opnfv.org/display/dovetail/Running+history+for+the+dovetail+tool Change-Id: Ief6f85faa955b59c2229a5fdffd73f83480fc214 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-07-19Apex: fix missing job for testsuiteTim Rozet1-0/+1
Change-Id: Ica77eb12fccfbb45479bbd75bbd8d3154f16a17b Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-07-19Apex: Fixes daily result reportingTim Rozet1-1/+60
Breaks testing up into its own mulitjob, which allows us to condtionally set status for the job due to failures, which will be set to unstable if only test suites fail. Change-Id: I5d886b98e437bf100b1d5546aebfcd046b0238cb Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-07-19Apex: throttles scenario jobs to only 1 per nodeTim Rozet1-0/+5
Change-Id: Ia155e3c60be35c0cdd31d6ddb0705dc5c3f6ad42 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-07-19Apex: adds slave params to deploy jobTim Rozet1-0/+1
Change-Id: I56002eea4b626fa9616d3a6dac7b230058121d96 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-07-19Apex: updates for post-danubeTim Rozet1-25/+24
Changes Include: - Functest in daily only executes on successful deployment - os-odl-bgpvpn-ha added to daily master - daily sub-job renamed to match CI evolution Change-Id: If34d013416b6d6c7fdfb4d0cdff652222e02462e Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-07Apex: adds smoketest backTim Rozet1-34/+34
Adding smoketest back, but it will not fail verify job. Change-Id: I18743ceb529565b2afc26ad0983c18d911920bec Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-06Apex: fix gerrit comment passing for gate jobsTim Rozet1-0/+1
Change-Id: I7ed790c9cd33029776b0c2551386d3f94eacc07e Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-01Apex: fixes snapshot promotion be variablesTim Rozet1-4/+12
Since job names changed during the migration to multijob, we need to update the scripts which assume the the snapshot type is part of the job name. Moving them to be jjb variables instead and not rely on job name. Change-Id: I18f3bd5488c36b2f82a7bc7cb80045ab6807fa57 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-01Apex: fixes scenario name for netvirt+vppTim Rozet1-1/+1
Change-Id: Ie3ca73a09cbea1aaf5c195fe319e5ec46e71f1bf Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-27Apex: fixes blocking per node with daily, verifyTim Rozet1-19/+5
apex-verify-*: we dont need blocking on this, since it can run on any node, and blocking is handled at lower layer jobs apex-build-{stream}: needs to block if apex-verify-iso-{stream} is running since apex-verify-iso will use the build directory of apex-build-stream to get the ISO from in daily apex-verify-iso does not need to block other deploys Change-Id: Icf69d23b7aeaf73f5ebc7103db24e309ab0e949f Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-26Apex: variablize concurrent builds per nodeTim Rozet1-1/+3
only master branch supports more than 1 build per node at a time Change-Id: I4e4b105cda5ff4f870917abd62660c64a4b535ee Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-05-25Merge "Apex: increase build timeout"Tim Rozet1-1/+1
2017-05-25Merge "Trigger cperf not functest from apex-cperf-runner"Tim Rozet1-3/+5