Age | Commit message (Collapse) | Author | Files | Lines |
|
otherwise the insecure key will be left in server
Change-Id: I2bae0c16e8da05d68d53cb5624a6660053c80756
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Parameter BRANCH is not correct in danube daily job[1]: expected `stable/danube`, actual `danube`
The following corrections are made as an attempt to fix this issue
- enable CI_DEBUG for additional information
- inline qtip-common-parameters
[1]: https://build.opnfv.org/ci/view/qtip/job/qtip-daily-fuel-zte-pod3-danube/7/parameters/
Change-Id: Ia892371925ffdb817d663c134d16e4568c07dff7
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
|
|
|
|
|
|
Change-Id: Ie45900e1724d761d6f547b159f5ec276d705326b
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This patch
- creates job skeletongs based on the structure of other OPNFV jobs
upstream job per scenario triggering and controlling the downstream jobs
downstream jobs to run provisioning, deployment and functest
- renames infra directory to xci
Change-Id: I9a7ac3590d660f4270ab387598586e4270787ecb
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This patch includes resource allocation/time-slots for kvmfornfv
os-nosdn-kvm_ovs_dpdk-ha, os-nosdn-kvm_ovs_dpdk_bar-ha,
os-nosdn-kvm_ovs_dpdk-noha and os-nosdn-kvm_ovs_dpdk_bar-noha
scenarios on Danube branch.
Change-Id: Ib8250075a43dec60be398ce9ee4152b97b7c6796
Signed-off-by: Navya Bathula <navyax.bathula@intel.com>
|
|
Change-Id: I5c93950a12c284d5e560e813891283aaf3638fd4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I93339884bd604da2314e32dfe7cbf25b21c67537
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
- since zte pod2 is used for daisy, move qtip job to zte pod1
- add danube trigger
Change-Id: Id0bdc5e791d3ed33a4f48d46b51823672794d2dc
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Change-Id: I52bc5bc4c8207b71ebad038c584874adebad3ec5
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
|
|
|
|
|
|
Change-Id: Ia6cbcf2b4014f456916fc4971050e8a244b25e81
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I45353b59bb13b49e8c81eb3e372672767d27d1d0
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I298b09f654dfe5efa64df9dc287fd586fcdf131d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
For the first time the daily build is ran, the properties file
for the latest ISO built is not present.
JIRA: FUEL-262
Change-Id: I842668bfde4c84cd3ba31571df274633ae238a90
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
Change-Id: I8375e4bc2c43e5a7b1c537da409de69609229c9d
Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
|
|
|
|
Change-Id: I622eb6677423581ab842a169480d91e21965b265
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
|
|
arm-pod3-2 is an aarch64 jenkins slave for the same POD as the existing
x86 jenkins slave arm-pod3. This commit adds jobs so we can deploy the
POD and run functest from the aarch64 jenkins slave.
These jobs are non-ci
JIRA: ARMBAND-241
Change-Id: Ie3b808a641e44649c02f3b75c83d79119217fdfe
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
|
|
Change-Id: I486c94bd85574140069b4854e93f7a458a8c6885
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: I57c7a06f8a0d89c6238d1d25908786466fa1bff2
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
|
|
Commit f6bba721fd13 ("jjb: infra: bifrost-cleanup-job: Do not trigger on
patchset creation") changed the job to not trigger on new patchsets but
this does not work as expected because it seems that the default value
for this option is 'true'. Set 'patchset-uploaded-event' to 'false' in
order to really disable that trigger.
Fixes: f6bba721fd13 ("jjb: infra: bifrost-cleanup-job: Do not trigger on patchset creation")
Change-Id: Id19474511f37ebd13d1933f5d13f185dc5c8e3c9
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Previously, if an upstream patchset contained a change for a file
listed in 'forbidden-file-paths' the job would not be triggered. This
is not desirable since such a patchset may contain important changes so
we enable the 'disable-strict-forbidden-file-verification' option which
triggers the job unless the patchset only contains changes for the
files listed in 'forbidden-file-paths'.
Note: The diff was generated using the following script:
for i in $(grep -l -r forbidden-file-paths *);do sed -i "s/\(^.*\)forbidden-file-paths/\1disable-strict-forbidden-file-verification: \'true\'\n&/" $i; done
Please double check that the changes look sensible for each team's project.
Change-Id: Ifa86d3a39b36375b2fd52b449e29c8dc757499b4
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
This should be the same as docs merge
Change-Id: Ib65e4dca130369e8372cfda433d4158393e67d3f
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
This commit rebalances the nr of runs between master and danube branch
for CI jobs
JIRA: ARMBAND-238
Change-Id: I541ddf3974680096d503829b279cb26ab76577bc
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Change-Id: I8b1a4291cd1e0167aad3e9341bb95c42f338caeb
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
|
|
VSPERF VERIFY and MERGE jobs should be executed at opnfv-build-ubuntu.
Only daily job should be executed at intel-pod12. Configuration of
Danube jobs was fixed to use the same executors as master branch.
Change-Id: I95a12c7d828eb840c177d3e8114ed81b342b9427
Signed-off-by: Martin Klozik <martinx.klozik@intel.com>
Reviewed-by: Aric Gardner <agardner@linuxfoundation.org>
Reviewed-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: If21b82c06ff38a52f70e502b49aa08dae8c2aad5
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Change-Id: Ia414071cccafe3f255d09555d83a04bc6600ffcd
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
|
|
Here are the projects that were branched:
I will double check against this list that these changes make sense
and that no one is missing as I go forward.
wiki page of participating projects, and their jobs:
https://wiki.opnfv.org/display/SWREL/Milestone+Compliance+for+Danube
apex - already enabled
armband - done
availability - already enabled
barometer - done
bottlenecks - already enabled
compass4nfv - done
copper - already enabled
daisy - (not participating -- keep jobs disabled?)
doctor - already enabled
domino - already enabled
fds - N/A
fuel - done
functest - already enabled
ipv6 - already enabled
joid - done
kvmfornfv - already enabled
models - already enabled
multisite - done
netready - NOT DONE
opera - NOT DONE
opnfvdocs - done
orchestra - Not participating
onosfw - done
ovsnfv - done
parser - N/A
promise - already enabled
qtip - already enabled
sdnvpn - N/A
snaps - done
securityscanning - N/A
sfc - N/A
storperf - done
ves - already enabled
vswitchperf - already enabled
yardstick - already enabled
Change-Id: I803662faf05c8554cfe7fa5f85da9521f72b03ff
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Change-Id: Ife9dae40246558b3219b4e194680e7428270df14
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
'RELEASE_VERSION: unbound variable' popped up when building stable docker image
Change-Id: I5d4582aea2f154e0bc34cdccdd05b9df64032ed2
Signed-off-by: helenyao <yaohelan@huawei.com>
|
|
|
|
- Execute compute qpi in qtip daily job.
- delete unuse parameter
- add CI_DEBUG parameter
Change-Id: I0e429703b7d1ac8cc7fda2ec888de789b57a5e50
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
|
|
Also adds odl_l3-fdio-noha to daily job for Apex
Change-Id: I4732f8b905d0908124c2c65cd2ad3af92262d4b5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
When building an aarch64 docker image an Dockerfile.aarch64 file is
expected to exist. With this patch we may create it from the x86
Dockerfile by applying an aarch64 patch
This feature can be used with qtip, via
https://gerrit.opnfv.org/gerrit/#/c/30185/
JIRA: ARMBAND-219
Change-Id: I71e1e1852e31f92fb1f1947542f7f397b996541f
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Enable danube verify/validate job for qtip.
Change-Id: I9a9403ed19e17f88c01a33fda5991984a8fd5166
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Use commit message: 'check k8', 'verify k8', 'check kubernetes' or
'verify kubernetes' to trigger k8s patchset verify.
Previous patch bug appearance:
https://gerrit.opnfv.org/gerrit/#/c/29471/
Change-Id: I14b52e253fd6ceae601d661568e86c449ae544fa
Signed-off-by: QiLiang <liangqi1@huawei.com>
|
|
|
|
Use commit message: check-k8, verify-k8, check-k8s, verify-k8s,
check-kubernetes or verify-kubernetes, to trigger k8s patchset
verify.
Change-Id: I89c471f603846d6d3a7ff6b73562ee52fb2e93e8
Signed-off-by: QiLiang <liangqi1@huawei.com>
|