summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-04-11Remove euphrates jobsagardner1-4/+0
Change-Id: I63fdf2826d2077465f264f082dc1a15eafc2b05a Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-11Merge "Apex: Fix log collection for daily job"Tim Rozet2-2/+2
2018-04-11Merge "docker build -f should use relative path to PATH, not working directory"Aric Gardner1-8/+8
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-11Merge "jjb: xci: xci-set-scenario: Drop errexit option"Fatih Degirmenci1-1/+0
2018-04-11Merge "Create Xtesting stable/fraser"Fatih Degirmenci1-0/+3
2018-04-11Merge "Stop verifying Functest Euphrates"Fatih Degirmenci1-4/+0
2018-04-11jjb: xci: xci-run-functest.sh: Reload XCI environment for functestMarkos Chandras1-2/+3
We should reload the XCI environment before running functest in order to ensure that playbooks have the correct information from the XCI deployment. Change-Id: Ieadeca61d3ea3e504e21aa96945ad067f20d1489 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-11Merge "xci: Enable Functest Healthcheck for Kubernetes scenarios"Fatih Degirmenci1-6/+0
2018-04-11Merge "[QTIP] Enable QTIP fraser docker build job"Serena Feng1-1/+3
2018-04-11xci: Enable Functest Healthcheck for Kubernetes scenariosFatih Degirmenci1-6/+0
This change enables Functest for kubernetes scenarios but any change that impacts kubernetes scenarios will fail and block the change from merging until the prepare-functest playbook and role are fixed in releng-xci. Change-Id: I046e3a0fb9a211cf9d629899017922288d466b0c Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-04-11Create Xtesting stable/fraserCédric Ollivier1-0/+3
Xtesting is not directly part of Fraser but this stable branch could be required for bugfixes. stable/pike could have been selected instead but it would have raised side effects when syncing requirements or building containers. Change-Id: I407f651ba09e27a7c87cc76f7b8ccbd6c0784a48 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-04-11Stop verifying Functest EuphratesCédric Ollivier1-4/+0
Functest Euphrates is now EOL (jjobs creating containers has already been removed) Change-Id: I668137b2701d073ce95856fa20dc54135a6cc111 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-04-11docker build -f should use relative path to PATH, not working directoryYujun Zhang1-8/+8
Change-Id: I6b35a5b36b1cc7b8ce2298388b9bb5caf9e44fc9
2018-04-10jjb: xci: xci-set-scenario: Drop errexit optionMarkos Chandras1-1/+0
Commands may exit with non-zero exit code but this could be normal (for example grep does than when it doesn't match anything). As such, lets not fail on everything but rather capture such failures and handle them appropriately. Change-Id: Icc16d0ccd09fd6f262600ae514161bfdf0c593f1 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-04-10Merge "create Stable Branch Jobs for nfvbench"Aric Gardner2-2/+7
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-10Merge "[yardstick] enable fraser docker"Trevor Bramwell2-2/+2
2018-04-10Merge "Enable Apex Fraser Jobs"Tim Rozet2-2/+2
2018-04-10Enable Apex Fraser Jobsagardner2-2/+2
Change-Id: Ie7bd0d3299fbbb8bc3e865612026ad479c48392d Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-04-10Merge "Create Stable Branch Jobs for calipso"Aric Gardner1-0/+4
2018-04-10Merge "[opnfvdocs] Create stable/fraser Branch"Aric Gardner1-0/+9
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-09[opnfvdocs] Create stable/fraser BranchTrevor Bramwell1-0/+9
Change-Id: I1a506b327c125d61088277d8e92b5b6ce08f4e87 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-09Merge "Create Stable Branch Jobs for barometer"Aric Gardner1-0/+4
2018-04-09Merge "[stor4nfv] Create stable/fraser Branch"Trevor Bramwell1-1/+1
2018-04-09Merge "[container4nfv] Create stable/fraser branch"Trevor Bramwell1-1/+1
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 "[calipso] Create stable/fraser branch"Trevor Bramwell1-0/+9
2018-04-09[container4nfv] Create stable/fraser branchTrevor Bramwell1-1/+1
Fix the location to be the git commit and not Gerrit change-id. Change-Id: Idd02beb4881a66accd55299e879799b2ec6626a0 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-09[stor4nfv] Create stable/fraser BranchTrevor Bramwell1-1/+1
Set the stable/fraser branch location to the commit intead of the Change-ID. Change-Id: I3f3c4ba3465c399d001464c6922d4725cfd9a2df Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.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>