Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
|
|
|
|
|
|
substitue docker-compose.template with string description,
so that user can wget deploy.py and execute directly.
Change-Id: I9703a1c8dfbdc46470561d54c6663e3728540162
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
1. In the original design, if the auto-job starts soon after
the watchdog starts, the auto update might be mingled with
connectivity check, which may lead to update failure. so instead,
the connectivity is checked first, if failed and module is not in deploying,
restart module.
2. only automate-docker-deploy job will impact the container status during
auto-job, so substitue auto-job status check with automate-docker-deploy's
3. the watchdog is not only for testapi, but also for reporting, and
all docker container server deployed in testresults.opnfv.org, so move it under
utils/test/opts, which is leveraged to store tool-sets employed for testing tools.
Change-Id: I766f3a534a3d510ce7509d4e742150150ccd8f54
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
To build apline images for euphrates
Change-Id: I63d77c99306aed263e220c2a0cd27ee2cca1ecb9
Signed-off-by: Linda Wang <wangwulin@huawei.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>
|
|
leverage docker compose to deploy testresults set
testapi/reporting/mongo
usage:
python one_click_deploy.sh -tp 8082 -rp 8084 -tl http://host_ip:8082
Change-Id: I8dfb868637749b82ec86e58220376b03ad50664d
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
|
|
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: 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>
|
|
|
|
|
|
|
|
|
|
Adds stable/euphrates branch for StorPerf jobs that were
enabled for existing master
Change-Id: Id11c4958c40cf8b8db49d545face4bd6ddbf31d3
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
Change-Id: Ia4523a185708a9d29243b522894b38fd1f047682
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
1. Jobs to deploy Apex danube has been merged.
This job will deploy Apex and then run Dovetail.
2. So Dovetail don't need to run test on huawei-pod4,
because it will be triggered by Apex deploy job.
JIRA: DOVETAIL-503
Change-Id: I49850a6c45e977ee3e5e8ad246b90a3dbd16884c
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Change-Id: I536d3182ef7f4b598f734502cc0880201487d968
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change switches jobs to euphrates and removes danube jobs.
Change-Id: I9e53c595886b6214927c10c380a898e3c7510c7b
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
|
|
Change-Id: Ia705bd9c16ca934bc781e558b27feafa89b3bff0
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
create job for euphrates
Change-Id: Ibabe87a6ba2e8c49356b33ed0b7ce7e93ab46df8
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
We dont have other pods so no reason to make extra labels
Change-Id: Ib701ae25d6cd08035930773219f691c7dc1b156e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I2f6dbe545c1c1adaa0a7020440f17f6f0cf37973
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: RELENG-254
Change-Id: I1c658e0af40d2973301b33f760d7fd420e80f253
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This change switches jobs to euphrates and removes danube jobs.
Change-Id: I421b3927e05712a62409e768b1b6a2e36c462537
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
|
|
|
|
|