Age | Commit message (Collapse) | Author | Files | Lines |
|
currently only master job is enabled.
Change-Id: I7da6a1a3a8e8faf08cde34d9a20219346070151b
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
|
|
|
|
|
|
We only set default scenario if there is not one set already so we
need to check if the array is empty.
Change-Id: Ic5019fb68349adaf52d669aed43574bc5eaeddc3
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Change-Id: I9576417cd2c47fd10153d841dddb334cb47c666e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ibd6a523aa9da3aa6c2622a5f183102ffdbc3ccb8
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
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>
|
|
Change-Id: I761ec6f28ab4b2d7dc47250d49730dbe302221e0
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
|
|
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>
|
|
|
|
|
|
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>
|
|
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>
|
|
Change-Id: I6b35a5b36b1cc7b8ce2298388b9bb5caf9e44fc9
|
|
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>
|
|
|
|
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>
|
|
|
|
|
|
Change-Id: Ie7bd0d3299fbbb8bc3e865612026ad479c48392d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
Change-Id: I47ae73da7240ee4c4e3902baa7320412a28ada6c
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
- enable fraser docker build job
- disable euphrates docker build job
Change-Id: Ieeaec7ed36ee8d77a250c0f584ea9e5985a41c8f
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
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>
|
|
|
|
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>
|
|
|
|
|
|
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>
|
|
|
|
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>
|
|
Same for docker
Change-Id: I48650881f5c0c8e7b4664b87b1b1a4a37c22cc8d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I0def0f3566b8cc1231ea06bb8731f028c4e4aedd
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I2117807b8af3ee248b30747830e32b1661a23d6f
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
|
|
|
|
|
|
|
|
Change-Id: I0167f223660d5b0edfac092a5d01fe165a91c2de
|
|
|
|
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>
|
|
Change-Id: Ib2bef726f6fda5a54debbafa7b4ac383fef5cdbe
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
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>
|
|
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>
|