Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Docker builds are currently timing out when multiple builds are running
on the same node. Builds start in parallel but Docker only allows one
to run at a time. By throttling builds to 1 per-node Docker builds will
run sequentially, as they are currently, but not timeout.
JIRA: RELENG-315
Change-Id: Ib64252f9449cccdc35856debafd3bcb8796f1100
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
As JOID do not have access to any other POD so changing from
master to E release for E release build.
Change-Id: I1ba9b92be0c3056023eac0e5869de041cf429344
Signed-off-by: Narinder Gupta <narinder.gupta@canonical.com>
|
|
|
|
Change-Id: I745287911eab7414adccd99e9e2385bf5b7438f7
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
The XCI script now uses more accurate VM names, so replace
the VM name in the destroy job as well.
Change-Id: Ia4c8ea204ecaa6ae765ce67aff3923dabab6d5f0
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Since Jenkins job builder doesn't support unicode yet, any non-ascii
character will break the releng-merge-jjb job.
Change-Id: Idc50c258c9c00c8d594717364907e701d9fee385
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Per Idec0fc06c82435adc1a4d569b8e578616998de5f it's now possible
to use a clean virtual machine to verify XCI so lets make use of
it. Moreover this patch updates the distro parameter to use more
accurate names and bring it inline with what dib expects.
Change-Id: I18c88637819884fef07d0bfa0dc2c1077a26c2f1
Signed-off-by: Markos Chandras <mchandras@suse.de>
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Change-Id: I40e00a1abfc383bb5f13a8ec140294d3a67e5cbf
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
And add debug information for the suite jobs
Change-Id: I478a09c689b54f82246a72c19726576ff5aeaffd
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
Also, improve suite job with alpine images.
Change-Id: I1367dea6b09361641c38ef91652acec5be4fbebb
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: I68e3caede7b209a7d1afe9ea46e49686daf83147
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
JIRA: QTIP-273
Change-Id: I8d192c70b881cc826fa37d15eec7eb4173a51e35
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
There is a bug where if there are multiple builds queued and daily build
completes, the following iso verify job will try to use the workspace of
the completed daily build to get the iso file. However, if another
build job has already started it may clean and overwrite the workspace
of the daily build job, and the iso verify job will fail because the
file is now gone. This makes the build job copy the iso to a tmp
directory for apex iso verify to consume.
This should be safe since only one daily can run at a time on the host
and daily jobs build and iso verify have to always execute on the same
node.
Change-Id: Ie8e32c4abefbc311e505688d6da2b26ae08ed98f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
Change-Id: I23ea156d9bbfa42c7bbf8dada344ded96b41e2e4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
|
|
|
|
Change-Id: I8c0c088c5b6879033e1d369488b589271e741a68
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Enable the security gating check to run on all machines labled
'opnfv-build'. This will allow the job to run as long as one of these
machines are online.
JIRA: RELENG-313
Change-Id: Icc792f7732c6cc3ca49bd8db32027fc146f8b1cd
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Setting this to allow all users to read/write the permissions enable the
container to write to the volume mounted reports directory even though
it is owned by the Jenkins user.
JIRA: RELENG-313
Change-Id: Ib26e9b98cd17607c98a180888593c42376458f7f
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I5a8f02944e346319d6c5d4fca10ddc54503e82d7
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Updated all the jobs that use functest-suite.
For single test cases, we need to know to which docker image
the test belongs to.
Change-Id: If7db231ccc891233423f2f2bc3aa5b95d048b30a
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
|
|
|
|
Change-Id: Ic5b88c7581879dbf0b72eaf6dbe3ad9c86b17f3c
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
To build apline images for euphrates
Change-Id: I63d77c99306aed263e220c2a0cd27ee2cca1ecb9
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Compass will use huawei-pod7 to run all danube jobs.
Dovetail add this pod.
Change-Id: Id184d33665e19a8469e600df04759b43005df157
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: RELENG-254
Change-Id: Iaf0c4a23f5d9b6117ec7a455ee1650e68893f4b3
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- drop obsolete file pattern matching.
- drop duplicate check-jinja2.sh from releng, use securedlab script;
While at it, s/danube/euphrates/ to enable stable/E verify.
Depends-on: I9d6807f3d24cee8d9a03955112a8c179d9ea7d14
Change-Id: Ia88140d872f2b64ff013f22ef0f43bd2cb31bd4f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Id47f61c950e1cc036e32e8efe2e2b55193e7c49e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
The old time is "0 12 * * *", need to set it to "0 1 * * *".
Change-Id: Id568dcb638202612ef8d7a9464d71952a95bffe8
Signed-off-by: xudan <xudan16@huawei.com>
|
|
So far we had 2 approaches:
* return Functest CI status: can be OK even if tests are FAIL
* return Functest Test status: can be FAIL even if all Functest tests are OK
(Fail in onboaraded tests)
A 3rd way is possible thanks to [1].
We consider only Functest status and Functest tests for the return statement
the return will be FAIL only if
* error in the framework
* error in Functest Tests
So concretely, if promise, Doctor can be FAIL, if Functest tests are OK, the
return will be PASS
[1]: https://gerrit.opnfv.org/gerrit/#/c/42245/
Change-Id: I6c7fbe99d888e43700ddb2dfc9bfd6cc9bfbaed6
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
Change-Id: I418f4f2b5f4b28acb9ed39f4f512dc59a4a6f012
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Change-Id: I9e4aab444490b7a85d2fd24344045452a62a0bcc
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
Change-Id: I8a138d6cdcfa055260fc25fa909b28d192d5c98f
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Adds stable/euphrates branch for StorPerf ARM jobs that were
enabled for existing master
Change-Id: I4f16097575367e8921e1f25201e57c3af5cd9d19
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
|
|
Change-Id: I01eb67919aa489c47d34976f9587f3187059d2b3
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
|
|
Previously we had apex-verify-master running multiple instances on
virtual-slaves. Apex-verify-master would kick off a build on our build
server, and then apex-verify-master would execute deploy multijob and
then functest multijob. However we found a bug where jenkins build
blocker would see that a deploy finished on the virtual slave, and then
execute functest multijob as well as deploy multijob (for the next
verify job) at the same time.
This patch adds a parent job apex-virtual-{stream} which calls deploy
and functest multijob and will block correctly. It also renables having
more than 1 apex-verify job running at a time on the virtual slaves.
Change-Id: Id15b2415407fc3318f333e3dfc59076d04db4ffb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|