Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue where apex-virtual-master label node was being passed from verify
job to deploy/functest. We allow multiple verify jobs to kick off on
virtual slaves, but then passing the host down to the deploy/functest
jobs causes the deploy/functest only run 1 job at a time on the same
node, rather than running 2 jobs at a time, one on each slave.
Change-Id: I1648eb6b84f17a2b08db4d161effe977c7952d63
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
We use apex-virtual-master label for slaves that will deploy and run
functest. Build and unit test will not use this label and will use
apex-build-master.
Change-Id: Ibf266bd37813ea8ef38fc8060f73f83462275cfd
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: RELENG-287
Change-Id: Ie50fdddc47b47764d3e3064904f19015d5d39341
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Fixes some final yamllint issues introduced by recent patchsets in apex
and armband.
JIRA: RELENG-254
Change-Id: I26b45d737f06c215413e29c92031d14e23967506
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Dovetail danube jobs don't need to be triggerred every day now.
Disable the timed trigger.
If need, they can be triggered manually.
Change-Id: I2f114cd17fcd27d0e34be0824be3fc0d072dbae9
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: RELENG-254
Change-Id: I354d7064c560d4b23e361d556b7fe269d7fb5d26
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I1e4237fd9716e92eec7633006c54240284f312c6
Signed-off-by: Ilia Abashin <abashinos@gmail.com>
|
|
Change-Id: I1d01d9d4a72946b4998437972ae12083675e7e79
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Even with a timed trigger that shouldn't execute more than once a year,
the apex-daily-master job is still triggering every day or so. Using an
explicit disable to disable the job.
Change-Id: I3b014c0d0899dba617fcb7cfee17ca758b291f9f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
There is a bug where if there are multiple builds queued and daily build
completes, the following iso verify job will try to use the workspace of
the completed daily build to get the iso file. However, if another
build job has already started it may clean and overwrite the workspace
of the daily build job, and the iso verify job will fail because the
file is now gone. This makes the build job copy the iso to a tmp
directory for apex iso verify to consume.
This should be safe since only one daily can run at a time on the host
and daily jobs build and iso verify have to always execute on the same
node.
Change-Id: Ie8e32c4abefbc311e505688d6da2b26ae08ed98f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Updated all the jobs that use functest-suite.
For single test cases, we need to know to which docker image
the test belongs to.
Change-Id: If7db231ccc891233423f2f2bc3aa5b95d048b30a
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
The old time is "0 12 * * *", need to set it to "0 1 * * *".
Change-Id: Id568dcb638202612ef8d7a9464d71952a95bffe8
Signed-off-by: xudan <xudan16@huawei.com>
|
|
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>
|
|
Change-Id: Ia4523a185708a9d29243b522894b38fd1f047682
Signed-off-by: Tim Rozet <trozet@redhat.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>
|
|
|
|
Change-Id: I2f4a8c57bf056fcc266a0757b291309671ecc151
Signed-off-by: Peng Liu <pliu@redhat.com>
|
|
The tmp directory no longer holds large files, and removing this while
other jobs are running can cause build failures.
Change-Id: I504d06e2e114dd1be4fe3790fcefaf97c724552c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Disables master daily. Just uses master labels for Euphrates jobs as
well.
Change-Id: I65b0eed528518c07d3ef4194a021004deabe2ed0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Change-Id: I2b7ee35500da4523a6cb872f89225fad6dd8af7f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Merged 'apex-daily-master' and 'apex-daily-danube' into
'apex-daily-{stream}'
Change-Id: I2b1e9e3dd0869b6a1f2b1b6415b364a2d9f151d2
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
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: I3246aa7d7b26b2d79ba9bd23aba4f305eb47fd94
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I503250b2152686cb1c9168aeaa6a11f614b0e954
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Since we do not install the package for build process we need to ensure
the PYTHONPATH is set to WORKSPACE so that build.py can find the libs it
needs in Apex.
Change-Id: I4e7f28ce5220206c7f4a8244199b00f762d72648
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Icac677ac9e17b4b4ae4e7fc82139587cc201bcb6
Signed-off-by: Tim Rozet <trozet@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: 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>
|