summaryrefslogtreecommitdiffstats
path: root/jjb/apex
AgeCommit message (Collapse)AuthorFilesLines
2018-05-24Apex: Fix scenario name for promote jobsTim Rozet2-10/+16
Promotion name for master OS should just be nofeature. Change-Id: I60086e94bbef87a1754f4f2cc00d096454668ded Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-24Apex: fix unbound variable in artifact dlTim Rozet1-3/+2
We still need VERSION_EXTENSION var to figure out which RPM files to remove on the slave. Change-Id: I03cc9c3318edec9860c8f3ffc01db52517a644b4 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-22Apex: enable RPM build on master verifyTim Rozet3-9/+14
Now that we only build apex python rpm in master, we can afford to build RPM everytime and ensure it builds correctly. Change-Id: Ica1efe1cc2c3db0dfe1c5677b5ab47df121c0966 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-21Apex: Updates daily master scenario namesTim Rozet2-4/+26
Change-Id: I881634a57f1d28cfcc3346476dc095873c014a22 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-16Rename files under jjb from 'yml' to 'yaml'Trevor Bramwell5-2/+2
global-jjb only supports the .yaml file ending for jjb jobs. Instead of waiting for a release we're going to rename the files. Change-Id: Icf3339eacd2320c583333e02250998cf6b1881f7 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-05-02Apex: Fix resources/images directory usage with deployTim Rozet1-3/+2
Change-Id: If50ad310049edca687da8e0acf412a7e1eacd2b6 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-02Apex: disable iso verify for master branchTim Rozet1-0/+5
Change-Id: I46753983e1fb37300df70700c474c3dda3532ffa Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-02Apex: Update for master upstream deploymentsTim Rozet5-57/+99
Change-Id: I92635178ddc354dd7773cd372a34d46f5ee0bf2a Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-18Ensure PATH has /usr/sbin/ for Apex Unit TestsTrevor Bramwell1-0/+2
Due to python-iptables calling out to ldconfig, we need to ensure /usr/sbin is available when running the Apex unit tests. Change-Id: I77fd4dedd6e7ad3c3831a1d181a5406d53a0e76e Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-17APEX: Add log collection to daily baremetal deployFeng Pan2-32/+22
Change-Id: I17c1aad45f8b965543a9c7d769ff94f59b9381d5 Signed-off-by: Feng Pan <fpan@redhat.com>
2018-04-17APEX: Fix gate detection regexFeng Pan1-1/+1
Change-Id: I41926856b129eb7dd99c5db8765961acd241eb55 Signed-off-by: Feng Pan <fpan@redhat.com>
2018-04-13Apex: remove non-released scenarios for FraserTim Rozet1-3/+0
We will not support RT KVM and IPv6 scenario. Change-Id: Iabd52f3ff803488e1ac68e8946001a7c04f5ca7f Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-13APEX: Fix missing bash command in verify jobFeng Pan1-1/+1
Change-Id: I055ec261368b341c5dd9f2ab5082c8ced15ad6e5 Signed-off-by: Feng Pan <fpan@redhat.com>
2018-04-12APEX: Fix gate check scenario detectionFeng Pan3-39/+11
- Change scenario parsing to allow k8s scenarios in gate jobs. - Remove scenario detection in shell scripts. Also changes network setting file for fd.io scenarios as we don't use separate config files any more. Change-Id: Icbcc6cb7b6b66c7cc43f5d6c58dd97730e41ea5f Signed-off-by: Feng Pan <fpan@redhat.com>
2018-04-11Apex: Fix log collection for daily jobTim Rozet2-2/+2
The wrong job name was being triggered so no job was running to collect logs. Change-Id: Ib58b030ac24920fc7906bff92a481407587a39bf Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-10Apex: Update master daily scenariosTim Rozet2-204/+6
As part of our new XCI effort, we only enable upstream ODL scenarios initially. Change-Id: I737bbffce14b6c5c69dfbbb653659c7e693cb4fb Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-10Enable Apex Fraser Jobsagardner2-2/+2
Change-Id: Ie7bd0d3299fbbb8bc3e865612026ad479c48392d Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-06Apex: fix log uploadingTim Rozet1-2/+3
Logs were owned by root, so jenkins-ci could not upload them. Also prints exact links for each file so it is easier to directly view logs from jenkins output. Change-Id: I919bf38c87561a696ae96683c56ad5f96c8d795e Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-05Apex: Fix conditions for multijobTim Rozet3-8/+5
condition actually affects *next* phase execution and not conditional on previous phase. This change fixes the condition so that fetch logs always runs. Change-Id: I50c3f9f9412682ea591c47116d406b5ed81ee2b5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-05Apex: add missing fetch-logs to jobs listTim Rozet2-2/+2
Change-Id: I28e4b613d92c43d32e95f8e1b4f4a4e2db102bc5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-05Merge "Apex: Enable overcloud log collection"Tim Rozet4-2/+164
2018-04-05Apex: Fix slave used by unit testTim Rozet1-1/+1
We were using 'stream' as part of the slave label to run unit tests on. However, we typically just use master label for everything to avoid having to update labels on slaves. Changing the unit test to follow the same method. Change-Id: I6a182c3f28d541109c8a9d94ea1dae2a80f2b835 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-05Apex: Enable overcloud log collectionTim Rozet4-2/+164
With this commit: https://gerrit.opnfv.org/gerrit/#/c/47875/ We can now gather logs from after at the end of a deploy/test job and upload them to artifacts. This patch enables that behavior on verify and daily jobs. Change-Id: If7af4cf1363e4bbcee78d98850af7c0e20250f3f Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-04-03Create Stable Branch Jobs for apexjenkins-ci5-0/+248
Change-Id: I7f6072121c4d88192c828e2e3cf2beb5d6c22c37 Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org> Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-03-28Apex: Updates promotion jobsTim Rozet3-37/+21
Change-Id: I37c7b8b6e4bd19ef94b9b42fe2e5e89cc3e2da21 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-03-28Apex: Adds parsing scenario on artifact downloadTim Rozet1-0/+20
Download was not properly being skipped on upstream scenarios because the scenario was not being detected and was set as "gate". Change-Id: I38533ad8140be48726aa2cb1c106d7ef6ca9afd5 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-03-19Make Apex JJB Renderer ImportableTrevor Bramwell1-21/+29
Wrapping the script into a function will make it importable from other python code. Calling the file directly will still work as it did before. Change-Id: I8336d34b05687fa650ce1c123bb37fa311ce2978 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-03-15Merge "change dovetail CI jobs on Apex"Tim Rozet2-4/+34
2018-03-15Apex: add support for deploying upstream onlyTim Rozet2-2/+12
Scenario names with 'upstream' in them will not download any artifacts and deploy from upstream. For now, this even applies to the apex python RPM for daily deployments. We will only use git repo for daily until after Fraser. Change-Id: I0da16dfde117ba6c1e7597294d8e4afc8501dd53 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-03-13change dovetail CI jobs on Apexxudan2-4/+34
1. Run test suite ovp.1.0.0 on Apex with even 'BUILD_NUMBER' for scenario nosdn-nofeature and bgpvpn. 2. Run test suite proposed_tests on Apex with odd 'BUILD_NUMBER' for scenario nosdn-nofeature and bgpvpn. JIRA: DOVETAIL-611 Change-Id: I5d4a86242d633eb83ddb0939dff5cf617c971c3b Signed-off-by: xudan <xudan16@huawei.com>
2018-03-08Add functest multijobs back to apex.agardner2-94/+96
fingers crossed Change-Id: I220a36ec8a6a0d95e847a5672c4d8e5c0d34c5ac Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-03-08Functest jobs are not showing upagardner2-94/+92
Remove and then re-add to see if we can get jjb merge to work Change-Id: Iff380b38bbc5a69e2850cd91a99267b6d5b1128f Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-03-08Nothing change to apex job to kick it into workingagardner2-2/+2
Change-Id: I88f33b7dcdf8f4d0a3aa3f8d46a07f10c62e6ae9 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-02-13Apex: Fixes concurrent apex-virtual jobsTim Rozet2-2/+4
We were missing concurrent on this job which was preventing parallel execution. Change-Id: I4d1ea62aef2a321220799cebee008f494490886c Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-02-13Apex: Attempt to fix apex-virtual parallel executionTim Rozet3-1/+3
Remove passing node params and enable global queue scanning. Hopefully this will allow 2 apex-virtual jobs to run at the same time (1 per each slave). Change-Id: I310dbc477e267c302d50599bab2a933ce988dba7 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-02-13Apex: Updates daily scenarios for FraserTim Rozet2-42/+20
Scenario list for Fraser: https://wiki.opnfv.org/display/SWREL/Fraser+Scenario+Status Change-Id: I083dc5b0b9cea9f91d7a9568a05df5865aeafa05 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-02-08Apex: Cleanup slave/slave-label configurationTim Rozet3-16/+2
Changes Include: - Remove defining 'node:' per job template and use slave-params defaults - Gate job was using daily/build slave, when it should be using virtual slave Change-Id: Iec2321801daef1b1fa40724a244bf2f6edf36c6e Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-02-07Apex: Fixes scheduling with apex verifyTim Rozet1-1/+1
apex-verify job calls apex-virtual to deploy and run functest. Apex has 2 virtual slaves attached to the apex-virtual-master label. When 2 verify jobs are triggered at the same time, apex-verify job is scheduled on each slave correctly. However, when the mulitjob triggers apex-virtual jobs, it only schedules both of them to a single slave. This happens even though apex-virtual job has the same slave label and node parameters are not passed from verify job. This patch changes the node to be passed to apex-virtual from apex-verify. That way 2 nodes will be scheduled on, but this is still not ideal scheduling as more than 1 verify can run per node (but not more than one virtual job). Change-Id: I155351c9037f70df2c5dba11bb5592423849e760 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-01-23Add GERRIT_REFSPEC to 'project-parameter' MacroTrevor Bramwell1-4/+0
GERRIT_REFSPEC is always passed by the gerrit-trigger plugin when a job is triggered by Gerrit. Because it is not explicily defined, there is no way to manually trigger jobs, as the git clone looks up the list of refs by GERRIT_REFSPEC. Being able to manually trigger jobs (with node parameters so they can be restricted) is very helpful in debugging CI issues. Change-Id: I8a1d9ea380902fc95f30482e5acb616347709ab1 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-01-04Apex: Adds os-odl-bgpvpn-noha to dailyTim Rozet2-0/+11
Change-Id: I92b3c2fce51dad5e0e00b836a41af40f845e701e Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-01-02Apex: disable Euphrates dailyTim Rozet2-2/+2
Change-Id: I7b10ac19a8844832886e6a54d065ee79dde026d0 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-12-20Apex: Enables verify trigger for ci directoryTim Rozet1-0/+2
We were missing triggering on the ci/ path in our Apex repo. This contains some code and a file we use to trigger verify jobs for dependent patches. Change-Id: I54f2826f8a16a1d0219d6ecc6ef8d257840b6399 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-12-06enable dovetail to run on APEX bgpvpn scenarioxudan2-2/+2
Since only APEX has the bgpvpn scenario in Euphrates, enable run dovetail on Apex euphrates scenario os-odl-bgpvpn-ha to test sdnvpn test cases. JIRA: DOVETAIL-568 Change-Id: Ic7c880a5ef911fac17807e19484f937bdaa53e21 Signed-off-by: xudan <xudan16@huawei.com>
2017-11-28Apex: enables daily master every other dayTim Rozet2-6/+6
Change-Id: I2f6e54badddf234fb781adc49b8395ac0144da06 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-11-27Remove ODL+FDIO scenarios in Euphrates dailyTim Rozet2-44/+0
These scenarios will not be part of 5.1 release. Change-Id: Ied91df7379705414850cda504842ecef2b3c7e0b Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-11-17Exposes GERRIT_REFSPEC parameter to buildTim Rozet1-0/+4
This value is usually passed by parent jobs (daily, verify, etc), but exposing it as parameter should allow us to build from JJB GUI. Change-Id: I294fbcd200ff5d8bbfca77681296c6e59d7f0063 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-11-17Fixes load-balancing jobs for virtual verifyTim Rozet3-1/+5
Issue where apex-virtual-master label node was being passed from verify job to deploy/functest. We allow multiple verify jobs to kick off on virtual slaves, but then passing the host down to the deploy/functest jobs causes the deploy/functest only run 1 job at a time on the same node, rather than running 2 jobs at a time, one on each slave. Change-Id: I1648eb6b84f17a2b08db4d161effe977c7952d63 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-11-15Apex: fix slave for verify jobsTim Rozet1-1/+1
We use apex-virtual-master label for slaves that will deploy and run functest. Build and unit test will not use this label and will use apex-build-master. Change-Id: Ibf266bd37813ea8ef38fc8060f73f83462275cfd Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-11-02Move Apex Verify Jobs to apex-verify-jobs fileTrevor Bramwell3-670/+364
JIRA: RELENG-287 Change-Id: Ie50fdddc47b47764d3e3064904f19015d5d39341 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-10-10Final Yamllint FixesTrevor Bramwell2-2/+2
Fixes some final yamllint issues introduced by recent patchsets in apex and armband. JIRA: RELENG-254 Change-Id: I26b45d737f06c215413e29c92031d14e23967506 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>