Age | Commit message (Collapse) | Author | Files | Lines |
|
From the failure log of doctor verify ci, project parameter is
not passed to other jobs.
see: https://build.opnfv.org/ci/job/doctor-verify-sample-master/33/console
Change-Id: I6a53cd609a261d90cdc0e1e10a3d7b05a515349e
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
|
|
We only want to specify slave-label, not sure why we are specifyign node
here and in jjb for Apex.
Change-Id: I184df37836039887f47e7d6141c89f8dd9cd014f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
apex-verify job calls apex-virtual to deploy and run functest. Apex has
2 virtual slaves attached to the apex-virtual-master label. When 2
verify jobs are triggered at the same time, apex-verify job is scheduled
on each slave correctly. However, when the mulitjob triggers
apex-virtual jobs, it only schedules both of them to a single slave.
This happens even though apex-virtual job has the same slave label and
node parameters are not passed from verify job. This patch changes the
node to be passed to apex-virtual from apex-verify. That way 2 nodes
will be scheduled on, but this is still not ideal scheduling as more
than 1 verify can run per node (but not more than one virtual job).
Change-Id: I155351c9037f70df2c5dba11bb5592423849e760
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
CentOS jobs started failing which requires troubleshooting.
In order not to block things, the voting is disabled for CentOS jobs.
Change-Id: Idc14b00cf09f0ee75bac17e993dc9f7724a1ad88
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
In [1], there are two IP addresses of daisy VM in the arp table.
Select the first one.
[1]: https://build.opnfv.org/ci/job/functest-daisy-zte-pod9-daily-master/2/
Change-Id: Ic071d718004bf9ed215b7e53c56568f7f018051a
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
|
|
|
|
Change-Id: I99da14477ab785475e425475fedca90a69eed8eb
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: If5569d01012b0f94976d26dfb4cd81692a40c83d
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
Change-Id: Ia9bc336d43fe9ed47368f9aada0c6d9244a71683
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
Change-Id: Icbdbe5a44660f498503ac84b323fd2a140ec3bbe
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
It follows the change "Move push_results_to_db to TestCase" [1] which
stopped duplicating TEST_DB_URL in config and in env.
[1] https://gerrit.opnfv.org/gerrit/#/c/49757/
Change-Id: If860492c40b1d0ed4082a4dbe385686020697f37
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
The default builder in Jenkins is '/bin/sh -ex'. Because of this lint
jobs are failing that we assume won't as everywhere else we've used
/bin/bash and explitily set options when needed.
Explicitly setting these jobs to use /bin/bash should keep Jenkins from
failing builds without reporting the lint results.
Change-Id: Ibe6cad979d6dcf30e7991873c9ac446ae3bf3a8b
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
Delete Fuel Euphrates CI job on zte-pod1
Change-Id: I93d5ed7b8aa40715fe8e7541d810ab0ee9a89f28
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Change-Id: I216d1877cba73272bbb37bf84c74dbf77dc2952d
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
|
|
Check jinja voting will keep bad configs out of our currently
pristine repo.
Also, Alex's schema valiadator is now running.
Change-Id: I12f38127b82583ef9cb2cc47ef4cfc5a8d051b87
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I3be5a3b6a0b7752f2b13df30944fca7645ee664d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I8e88ab0598f43be8d0c9c4ad199dba91c1561f13
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: Ib97cee06438d4ac240c55b0b504338f435a68259
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
|
|
Change-Id: I2a91409fb3a650e9d9cacd3f6ffe4b17bc394950
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
Change-Id: I39ed2ff1baedf5521f2fe1448350c0c91b1c4f61
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
CentOS is now supported by os-nosdn-nofeature scenario and it is
time to enable voting for it. For scenarios that do not support
CentOS yet, the jobs will skip running real stuff by exit 0 in
order not to fail the patch.
Change-Id: I86c9e1bb4d66ea84ccfc864186a7ca7c696f8663
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
Change-Id: I41aef4c9df47a076f8245cc1b466ff4297de0ae8
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
JIRA: COMPASS-579
Add a job to collect log and upload. what the job do
1. run collect-log.sh to get log from rsyslog container
2. copy log.tar.gz from compass-tasks to jumphost
3. upload the log.tar.gz to artifact
Change-Id: Ic2244e33e7ae4b7aa71e15af741191c850982053
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
|
|
Change-Id: Iebd8a9b558486927c25735d266d3557f91e26a15
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Now that vPDF support landed in Pharos and Fuel repos, disable the
'virtual_kvm' generic override, so we can load POD-specific PDF/IDF.
JIRA: FUEL-322
Change-Id: I0964220a25d6fe30afcbeb3ad1f020ae76d38e5a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Liniting is broken, last fix forgot to run linting concurrent
FATAL: The project is configured to NOT run builds concurrent, but the
node parameter [SLAVE_NAME] is configured to trigger new builds
concurrent!
Change-Id: I1eb4bf7279c7af4e01950b89c515e183fbc57b2d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Linting was broken by this patch
https://gerrit.opnfv.org/gerrit/#/c/50737/
Also added sudo to pip installs, as they are not in a venv
Patch forgot to put linting on build server
so it defaulted to master.
Change-Id: Iba8c1f633fad6d5f3d097f4911f45100c3b43e30
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: Ib61cb40b04eed23ad276f261645d83ce7cf00629
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Change-Id: I310c4f2e46a26b35eeafef2dfc8670d70ace0575
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
Only Danube still uses this param, newer branches rely on IDF.
Going forward, the `-B` deploy arg will be deprecated in Fuel.
Do not yet remove BRIDGE slave params from non-CI PODs, as
other installers (or custom Danube jobs?) might still use them.
Change-Id: I6d259299d1e13e8a5da732aca60b1f56b8472af6
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|