Age | Commit message (Collapse) | Author | Files | Lines |
|
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: I59523b6233ca48c2eb2d4b4934263f0114d8e7a8
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>
|
|
We dont need to use the apex/ci directory anymore and the ci scripts
should be in releng. A follow up patch will remove the ci/clean script
usage.
Change-Id: Ib2c7bd3d2dfee360bb13b42852ff2010a691a018
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I75bd15be3e68fa630a59cd30a0da72b8f17b8b84
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
There should be no reason to clean as the unit tests should be local to
the code. This was deleting some of our undercloud vms in daily
deployment causing deployment to fail.
Change-Id: I22abc57ea1a3f10cb91451e7005aa23d9715acc5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I30bc270c1ae9c648ec184e446a712bd304ad1230
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
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>
|
|
Change-Id: I4a1da6ba1efe2b704f0109f63817021435d283b8
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>
|
|
Change-Id: I36066bf003b1504524a5b8143cceef7829b23ca8
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Iba1b2f47e8ace4fb4a9eed80342fcb8950e848f8
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I0455283ba94501119786ffbc3b1217bb71cc35c7
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>
|
|
Change-Id: I6bd33b0304127dbcac1ccc4320a2a34e8a837d00
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I900f9dc6e6dd3bf041fbecc5eab3216f5bd7f8bc
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I8433b84bc2e2c3acf7db67b8bf40aedddb727daa
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I0670eb1e0c698e2a57698ba0f11879a17a34c2ff
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
|
|
The script had double quotes which will try to interpret dollar sign as
a templated variable. Switching to literal string.
Change-Id: Ic8d09dc6c862b9db95bf9d1277f562e5bce02fc9
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>
|
|
Change-Id: I9d080558ac6943f53d657cbec6c25dd2e6c10ac5
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I959a46ed619d55df3a8c6bd3b3300bad4432b911
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
The following scenarios are added:
- os-nosdn-fdio-ha
- os-nosdn-fdio-noha
- os-odl-fdio-ha
- os-odl-fdio-noha
Change-Id: I7aa68cf3c673cd7f0026873cd3d6939887944117
Signed-off-by: Feng Pan <fpan@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>
|
|
Change-Id: I0399c414c5ae042fdc3d3ace1354414897f7d92b
Signed-off-by: Dan Radez <dradez@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>
|
|
|
|
Change-Id: Ib71936bec70951dea7478c1dcf657c5f2581fdf6
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>
|