Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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>
|
|
Change-Id: I1a506b327c125d61088277d8e92b5b6ce08f4e87
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
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>
|
|
|
|
Fix the location to be the git commit and not Gerrit change-id.
Change-Id: Idd02beb4881a66accd55299e879799b2ec6626a0
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
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>
|
|
|
|
|
|
|
|
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>
|
|
These are replacing the current Euphrates jobs.
Change-Id: I6d7bf1490c1dd46f80ac5b14449abb6f287e5acf
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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>
|
|
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>
|
|
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>
|
|
scenarios"
|
|
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>
|
|
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>
|
|
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>
|
|
|
|
Change-Id: I5e59b6240b1e614fc6c06f918054813b7e5758cf
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
* changes:
Create Fraser Docker Jobs for Storperf
Add Fraser stream to Docker Arm Builds
|
|
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>
|
|
Change-Id: I5de7df11919f725264aa6b07d0f8d5e917f8a28c
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
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>
|
|
|
|
Missed changing the branch name when copying over the release file.
Change-Id: I25105253911f19dbfa621b29c2a812df4a8af01d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
Change-Id: I28e4b613d92c43d32e95f8e1b4f4a4e2db102bc5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|