Age | Commit message (Collapse) | Author | Files | Lines |
|
The last patch to add apex danube jobs on huawei-pod4 forget to add the
job-template to the jobs list.
Change-Id: I671faa2068bab517adc59ad8597e9c05330d528f
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
Run Dovetail proposed_test job against Apex Danube daily on
huawei_pod4.
Change-Id: I14f4f86caa2b1fb2802b5ea154edec47784209cc
Signed-off-by: Peng Liu <pliu@redhat.com>
|
|
Change-Id: I34a555697d963efc38064a7b53f25191d6bf1382
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Due to bug with forbidden file paths conflicting with file paths this
explicitly defines all the file paths in apex. This isn't the greatest
solution in the case where someone adds a new folder, but chances are
they will also modify one of the other files as well. Note it also
fixes a bug where unit tests woudl run twice because it would be
triggered as part of apex-verify-master and apex-unit-tests-master.
Change-Id: I6b10f8eb70c2cd7c8dd5c01363e06b7458c00127
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I19fff409b5e8335ff44f0d9ba8167d3e882a9ad5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ide3c39d508d26be40e73cec13cd00eace984b6cc
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
this should make forbidden-file-paths work
Change-Id: I18d63bffb92abd916eae54c7aafe9a8e1e98926f
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I360cd5ba894022cd30cf7237e8338ab2e213c940
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I0c6e54ce4caf0b6889bac62b25afcee2706ca75f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
If we make changes to apex/tests path it is only unit tests and we do
not want to trigger apex-verify-stream.
Change-Id: I42ef56330883ea6e9643f24567eaee3d5fa36071
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Change-Id: Ia48b95589e6365102fef54444a8e334a80301dd2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Since these jobs don't deal with scenarios they can safely be moved to
another file without the need to duplicate the scenario listings.
Fixes a bug with 'concurrent-builds' not being set due to missing
quotation marks.
JIRA: RELENG-287
Change-Id: Icce39620521c7d25476553115efbaa9063ca2e17
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I0bd9f2bac11b4161da4b6cdfa0a0c6d444020944
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I3f0119db7b7cade3ddd2dbeaa97e03e1fea58798
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I3e5a08996e896bcf7b88c97b503de414f7f3ee71
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This will limit how many simultaneous builds we can do at a time on
build server, but will stop the bug we are hitting where deploy (next
job) and functest (current job) start at the same time by blocking
parent jobs.
Change-Id: If23ce857d7ef043c408b0eb6a74357ce1278e4b9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
storperf has infinite loop:
https://build.opnfv.org/ci/job/storperf-apex-baremetal-daily-master/10/consoleFull
Change-Id: I526cddbda15c6262b4afd7c30b6d2681011f48a5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I3878f3e1a85b31ddba8d3f53e774a9e1d16f8afb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
We have blocking so that deploy wont run while another deploy or
functest is running. However there is an issue where after a deploy
completes, the next in line deploy starts at the same time as the
functest starts for the previous deploy. This patch adds a quiet period
to the deploy job of 30 seconds, which hopefully will offset the start
time between the two and resume correct blocking.
Change-Id: Id94d075f2d2e48952a5c2186eeb81d09bb68c49b
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I999640281d8e15132c9024e25e43122d2a12baf7
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
According to the multijob builder, condtion: "condition (str) – when to
trigger the other job". Other job in this case means the next job I
believe.
Change-Id: I084fffc80584ad683345f6040ec0081c16513c8d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
The groovy script is working, but it is changing the 'apex test suite'
phase to unstable and we really want it to change the 'scenario' job
result to unstable if deploy passed but tests failed. Therefore this
patch moves the groovy plugin to execute on the scenario job, and looks
for deploy successful before changing the build result.
Change-Id: I1b6907f4fb2647e644c4a627be6e481fff32f195
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Conditional plugin does not work for detecting current status in
mulitjob, but groovy publisher does. Shown to be working in sandbox
job:
https://sandbox.opnfv.org/view/All/job/test_groovy_publisher/17/
Change-Id: Ic0ed09885bb29254c4bfda24164c5358eda0d20a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: DOVETAIL-470
Bug log:
https://build.opnfv.org/ci/job/apex-testsuite-os-nosdn-nofeature-ha-baremetal-master/5/console
Can't evaluate expression, false is assumed: groovy.lang.MissingPropertyException:
No such property: DEPLOY_SCENARIO for class: Script1
Skipping dovetail-apex-baremetal-proposed_tests-master. Condition was evaluated to false.
Change-Id: I8295313a3096b603bd390fdb70d451274a5146bb
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: DOVETAIL-359
1)run againt scenarios:
os-nosdn-nofeature-ha os-nosdn-kvm-ha os-odl_l3-fdio-ha
2)stream: master
3)details see
https://wiki.opnfv.org/display/dovetail/Running+history+for+the+dovetail+tool
Change-Id: Ief6f85faa955b59c2229a5fdffd73f83480fc214
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
Change-Id: Ica77eb12fccfbb45479bbd75bbd8d3154f16a17b
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Breaks testing up into its own mulitjob, which allows us to condtionally
set status for the job due to failures, which will be set to unstable if
only test suites fail.
Change-Id: I5d886b98e437bf100b1d5546aebfcd046b0238cb
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ia155e3c60be35c0cdd31d6ddb0705dc5c3f6ad42
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I56002eea4b626fa9616d3a6dac7b230058121d96
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes Include:
- Functest in daily only executes on successful deployment
- os-odl-bgpvpn-ha added to daily master
- daily sub-job renamed to match CI evolution
Change-Id: If34d013416b6d6c7fdfb4d0cdff652222e02462e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Adding smoketest back, but it will not fail verify job.
Change-Id: I18743ceb529565b2afc26ad0983c18d911920bec
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I7ed790c9cd33029776b0c2551386d3f94eacc07e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Since job names changed during the migration to multijob, we need to
update the scripts which assume the the snapshot type is part of the job
name. Moving them to be jjb variables instead and not rely on job name.
Change-Id: I18f3bd5488c36b2f82a7bc7cb80045ab6807fa57
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ie3ca73a09cbea1aaf5c195fe319e5ec46e71f1bf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
apex-verify-*: we dont need blocking on this, since it can run on any
node, and blocking is handled at lower layer jobs
apex-build-{stream}: needs to block if apex-verify-iso-{stream} is
running since apex-verify-iso will use the build directory of
apex-build-stream to get the ISO from in daily
apex-verify-iso does not need to block other deploys
Change-Id: Icf69d23b7aeaf73f5ebc7103db24e309ab0e949f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
only master branch supports more than 1 build per node at a time
Change-Id: I4e4b105cda5ff4f870917abd62660c64a4b535ee
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
Builds can take a lot longer when running simultaneously and daily
builds upload many rpm and srpm artifacts which takes longer.
Change-Id: Ib8dd23e5bea1a552c10a6f5a5aa1ea158647f7d1
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I0f4325b8489edb18fb2e69ed987dd6ec7caeb3ea
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
|
|
Change-Id: I5431e1c86d9f56b5192880dc9e7eb6f2f0ab61ee
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
|
|
Functest is having problems running and logging failures, so we need to
temporarily disable it on verify jobs until that infra is fixed.
Change-Id: Ib2c41bb0f3c99517c98cfe1167fdc94e2313fb4f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I563b961286fe215c4e5381ccde30d787188f1e8e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I03cf0207075116de44ebde03429ab5b499db540b
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I0c85806e5fa04a890a130d8106d96c7fb812e691
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This reverts commit ec2e44c72271cb78a00bebd32ceb43487ad176b5.
Change-Id: I2f8db687df9cceaa50bf6a26de659ea70f70df45
|
|
Change-Id: Ifb1173a49066fd493c58f41ae22d4decc69e03f9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I0a8d51c7e0a586469cfe25d0610f078fd937c9ba
Signed-off-by: Tim Rozet <trozet@redhat.com>
|