summaryrefslogtreecommitdiffstats
path: root/jjb
AgeCommit message (Collapse)AuthorFilesLines
2018-04-10[yardstick] enable fraser dockerRoss Brattain2-2/+2
Change-Id: I47ae73da7240ee4c4e3902baa7320412a28ada6c Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-04-10[QTIP] Enable QTIP fraser docker build jobzhihui wu1-1/+3
- enable fraser docker build job - disable euphrates docker build job Change-Id: Ieeaec7ed36ee8d77a250c0f584ea9e5985a41c8f Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
2018-04-10[doctor] clean pep8 jobRyota MIBU1-88/+0
The global 'lint-all-code' job is already enabled for doctor repo, so there is no need to keep this verify job which only run pep8. JIRA: DOCTOR-120 Change-Id: I6eb95590b97c3bd2c2daa80a6ae3bcfe4a4119a4 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2018-04-10Merge "delete 'opnfv-build-ubuntu-defaults' parameters for doctor verify job"Serena Feng1-3/+3
2018-04-10delete 'opnfv-build-ubuntu-defaults' parameters for doctor verify jobdongwenjuan1-3/+3
Currently it will pass all the 'opnfv-build-ubuntu-defaults' parameters to the child jobs which include the node 'label', so all the doctor jobs will be running in the nodes with 'opnfv-build-ubuntu' label. Change-Id: If01f1f777c30c421f063c05fdd3c939f8758226c Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-04-10Merge "Create Stable Branch Jobs for container4nfv"Trevor Bramwell2-2/+13
2018-04-10Merge "[daisy] Enable functest daily jobs on zte-pod9 for stable/fraser branch"Trevor Bramwell1-0/+4
2018-04-10delete the 'node' parameter in 'doctor-slave-parameter' macrodongwenjuan1-11/+0
We define the 'node' parameter in job template: 'doctor-verify-{installer}-{inspector}-{arch}-{stream}', so we don't need to redefine them in the doctor parameter macro. It will schedule the fuel verify job to the default apex env. See: https://build.opnfv.org/ci/job/doctor-verify-fuel-sample-x86_64-master/1/console Change-Id: I49e6d26ca284f6548460312de0cb634bd033d3c1 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-04-10Merge "Create Dovetail Fraser Jobs"Serena Feng1-14/+14
2018-04-10[daisy] Enable functest daily jobs on zte-pod9 for stable/fraser branchZhijiang Hu1-0/+4
This PS is trying to solve errors like occured in [1]. [1] https://build.opnfv.org/ci/job/daisy-os-nosdn-nofeature-ha-baremetal-daily-fraser/5/console Change-Id: Ie4e023794d54cf0e236e9094fabf8362e17d9c8a Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2018-04-09create Stable Branch Jobs for nfvbenchagardner2-2/+7
Same for docker Change-Id: I48650881f5c0c8e7b4664b87b1b1a4a37c22cc8d Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-09Create Stable Branch Jobs for barometeragardner1-0/+4
Change-Id: I0def0f3566b8cc1231ea06bb8731f028c4e4aedd Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-09Create Stable Branch Jobs for calipsojenkins-ci1-0/+4
Change-Id: I2117807b8af3ee248b30747830e32b1661a23d6f Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
2018-04-09Merge "fix the default node label for doctor test"Trevor Bramwell1-2/+1
2018-04-09Merge "Add docker build job for clover"Trevor Bramwell1-1/+61
2018-04-09Merge "Create functest daily/weekly Fraser Jobs"Trevor Bramwell2-29/+19
2018-04-09Add docker build job for cloverYujun Zhang1-1/+61
Change-Id: I0167f223660d5b0edfac092a5d01fe165a91c2de
2018-04-09Merge "Split functest-kubernetes into smaller containers"Jose Lausuch2-22/+36
2018-04-09fix the default node label for doctor testdongwenjuan1-2/+1
There are no nodes with the label 'not-specified'. If the jobs which are not specified the node label will scheduled to the label 'not-specified' and they can not be runned. Change-Id: I7e7790be2517328fc07d02cdcdc23ee71c7df680 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-04-08Build stable/fraser tarballwutianwei1-1/+1
Change-Id: Ib2bef726f6fda5a54debbafa7b4ac383fef5cdbe Signed-off-by: wutianwei <wutianwei1@huawei.com>
2018-04-07Split functest-kubernetes into smaller containersCédric Ollivier2-22/+36
It conforms with the Docker slicing model proposed by Functest. See https://gerrit.opnfv.org/gerrit/#/c/55129/ Change-Id: Ic036034f043f995cba468fa0437e47a6129584b4 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-04-06Create functest daily/weekly Fraser JobsTrevor Bramwell2-29/+19
Though the stream was added it wasn't applied to any of the pod configurations which are expanded as part of the job names. Change-Id: I84af2e11033a40f314c8bc0c1f263002bc44bf60 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-06Create Dovetail Fraser JobsTrevor Bramwell1-14/+14
These are replacing the current Euphrates jobs. Change-Id: I6d7bf1490c1dd46f80ac5b14449abb6f287e5acf Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-06jjb: xci: Set XCI_PATH for bifrost jobsMarkos Chandras1-0/+3
The bifrost jobs are using some scripts from the releng-xci repository so we need to set the XCI_PATH variable appropriately. Change-Id: Ibfd139d2401029b2ea577c4797b68f29362356ec Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06Merge "Update clover daily job slot"Trevor Bramwell1-2/+2
2018-04-06Merge "Fix project name"Trevor Bramwell1-0/+5
2018-04-06Merge "Create Stable Branch Jobs for parser"Trevor Bramwell1-0/+4
2018-04-06Merge "Create Stable Branch Jobs for yardstick"Trevor Bramwell2-19/+20
2018-04-06Merge "Fix RabbitMQ service installation in Yardstick jobs"Trevor Bramwell1-10/+10
2018-04-06Merge "Apex: fix log uploading"Tim Rozet1-2/+3
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-06jjb: xci: Only set default scenario if no scenario is setMarkos Chandras1-7/+11
Previously, the code was already setting the default scenario if we had changes outside the xci/scenario directory. However, this is somewhat problematic since scenarios may touch other files which do not necessary affect other scenarios such as anything in xci/playbooks etc. As such, lets only set a default scenario if no scenario was set up to that point. However, since installers and scenarios need to match, we also need to consider installer changes because we fallback to the default scenario. Finally, since we are filtering results with 'uniq' we can simply drop the bash regexps prior to adding the scenario to the array. Change-Id: Ie961071b3e93d04a860bb6655513654208b1a9d4 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06jjb: xci: Fix functest exit codeMarkos Chandras1-5/+3
There is not reason to grep the logs for failures because we can simply preserve the functest exit code and use that to determine whether the job passed or not. Change-Id: I9f027960fd3d9d452d417b95e9dac66bbb314a47 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06Merge "jjb: xci: xci-set-scenario: Allow automatic detection of generic ↵Markos Chandras1-10/+10
scenarios"
2018-04-06Fix RabbitMQ service installation in Yardstick jobsRodolfo Alonso Hernandez1-10/+10
RabbitMQ commands need to be executed as root user. JIRA: YARDSTICK-1104 Change-Id: Ia6667cc3f7572f67a38fd4fd4bcf9fbb4309d36c Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-04-06jjb: xci: xci-set-scenario: Allow automatic detection of generic scenariosMarkos Chandras1-10/+10
The list of supported scenarios is hardcoded and this makes it difficult to test new scenarios. As such, lets determine the scenario and the installer based on the actual files that have been changed on every patchset. Change-Id: I4868a1da08d58cd6ff37347a0c0bc5c5e28b15bb Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-06Fix project nameTomi Juvonen1-0/+5
Not working currently: https://build.opnfv.org/ci/job/doctor-verify-sample-master/68/console Change-Id: I5fa065eda3f8e8eb8ae6b988ec593c1d37d0579a Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-04-05Merge "Fraser jobs for securedlab verification"Trevor Bramwell1-1/+1
2018-04-05Create Stable Branch Jobs for yardstickjenkins-ci2-19/+20
Change-Id: I5e59b6240b1e614fc6c06f918054813b7e5758cf Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org> Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-05Merge "Create daily Fraser jobs"Trevor Bramwell3-9/+18
2018-04-05Merge changes from topics 'storperf-docker-fraser-jobs', 'docker-arm-fraser'Trevor Bramwell2-10/+14
* changes: Create Fraser Docker Jobs for Storperf Add Fraser stream to Docker Arm Builds
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-05Create Fraser Docker Jobs for StorperfTrevor Bramwell2-10/+10
Change-Id: I5de7df11919f725264aa6b07d0f8d5e917f8a28c Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-05Add Fraser stream to Docker Arm BuildsTrevor Bramwell1-0/+4
This will allow changes to docker in stable/fraser branches to be built, when added to the associated project repository. Change-Id: Ib5d295f2845e519f4a5a65738e8af1a357f77c5e Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-05Merge "Switch Functest k8s docker builds to multijobs"Trevor Bramwell2-9/+174
2018-04-05Merge "Install RabbitMQ service in Yardstick functional tests"Trevor Bramwell1-2/+18
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 "Create Stable Branch Jobs for snaps"Trevor Bramwell1-0/+4
2018-04-05Merge "Create Stable Branch Jobs for clover"Trevor Bramwell1-2/+8
2018-04-05Install RabbitMQ service in Yardstick functional testsRodolfo Alonso Hernandez1-2/+18
Install and configure RabbitMQ service for Yardstick functional (Python 2.7 and Python 3) tests. JIRA: YARDSTICK-1104 Change-Id: I6b287def05c75dc67ab21727f72d4c384f8e2837 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>