Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I1541a0e277891b526a671953bf33daab842b524e
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
Moves the jjb-version configuration from globals to releng CI jobs. This
was not being pulled into the '{project-name}-ci-jobs' configuration and
kept our JJB version at 2.2.1.
Change-Id: I33a62e639bbca6d519957515af591615543d27b7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
apex-virtual-{stream} is not being blocked and running at the same time
while csit tests are running. This should stop it from running until the
promotion job is finished.
Change-Id: Ie164bbee08253a7e79892d36780b66fe0ad2cf97
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
|
|
|
|
We need the fix:
'Allow running only on one of nodes with label parameter'
https://review.openstack.org/#/c/590356/
This fix is present in 2.5.0
Change-Id: Iff9e9e6357573db382d94b688b7cfe7d42d4023c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Has been offline for > 1 week
https://build.opnfv.org/ci/job/functest-core-docker-build-arm64-gambia/
is showing
There are no nodes with the label ‘Job triggered without a valid online
node, given where: arm-build6’)
Change-Id: Ia00281f9c05fac9b16bd914063ccffeca3fb135b
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
With changes to deploy scenario files for gambia, we still need the
logic to pull in the right csit-env. That logic broke as it depended on
DEPLOY_SCENARIO with the changes to scenario names. This patch fixes it
to check openstack version (OS_VERSION) instead.
Change-Id: Ie130efd0fc3cb7f09a3fa4e896ad461d24394777
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
In Apex, some random jobs are queueing to intel-pod11 which does not
exist anymore. The problem is, when these jobs queue they are blocking
apex daily functest, as it looks like the job is only set to allow 1 job
globally at a time. This change bumps the max concurrent global jobs to
10.
Change-Id: I62d458a92abfa35bb0d1c459ccf4ffedfd51e66d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
Change-Id: I36b2f245aa2044ebcdab5122d3b30ae1d9fb1788
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
Since CSIT does not pass on HA, but we still want to promote some
snapshots for HA, reduce the CSIT suites to L2 and L3 only.
Change-Id: Iaf739f972211c1e94de781a006065d7130ddf1c3
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Now that Gambia branch is used for queens promotion, scenario files use
nofeature instead of using branch name.
Change-Id: I76e8f851bc6ef337301d1367dcafd798b212bb38
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I2c9c1f042b4b13af58526e23a44680304313cee9
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
|
|
A change to the NodeLabelParameter config in JJB caused any jobs using
the plugin to possibly have their jobs triggered on builders which
weren't online.
This in turn caused the queue to backup and newer jobs are blocked
waiting for older ones to complete, which never happens as they're never
queued on an online builder.
The 'all-nodes' parameter ensure jobs that are set to run concurrently
don't trigger across all available nodes at once, as this will include
offline nodes as well. As this is the default of the plugin, projects
which need it can enable it individually.
Change-Id: Ia690eef078209b6b056dad85613dda6868b18271
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Missed a check where we install packages based on old package
convention.
Change-Id: If1da8db9b10b81ea5825b7548509be29e08e6f91
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ibe83eb4131d8ff553aa81e343cfe5ae8c19b4cf6
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Change-Id: I4cecaf7302fa1f39aa1e8b2c3e34f11ee49b4359
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Global JJB now has non-JJB YAML configuration and requires action on the
ci-management repo when upgrading to this version of Global JJB to
prevent JJB from picking up these YAMLs as config. Follow the
instructions below BEFORE upgrading globall-jjb:
cd <git-root>
git mv jjb/global-jjb global-jjb
mkdir jjb/global-jjb
ln -s ../../global-jjb/shell jjb/global-jjb/shell
ln -s ../../global-jjb/jjb jjb/global-jjb/jjb
git add jjb/global-jjb
git commit -sm "Prepare repo for global-jjb v0.25.0"
Git diff confirms no changes.
diff -bur . /tmp/releng/job_output/
Change-Id: I6d7239b8bab8ef08368f833d9a64cd94a824b158
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
From the release notes:
Upgrade to global-jjb v0.24.6 before performing this upgrade. This
ensures that jjb-verify job pulls in a regex fix that will allow it to
verify the v0.25.0 upgrade.
Change-Id: I48335de599b46b7e6c70f8bb77fb8c254cfe85f4
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
Change-Id: I89040a4f7ac493efe8a11a268ce891c156e53c18
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
|
|
jjb/lf-ci-jobs.yaml has jjb-version: 2.2.1 as a minimum
change block-level to blocking-level:
https://review.openstack.org/#/c/608092/
We will need to change this back once we move past
jenkins-job-builder>2.5.0
Change-Id: I12d0f55ee3c2dad20340ebf0fa8428ee1ad8484c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Change-Id: I388d5b46d206655990f3fb2723a90e8ed4397c89
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
|
|
Push OPNFV docker builds for clover-ns-modsecurity-crs image
Change-Id: I134108d78d84de8a04bb7372c49314d0491a1248
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adds the gambia stable branch stream.
Change-Id: Ic1afb65b580396f11c00488a7f135e0e5cdc96cd
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
This node has permissions for Google Storage to upload the archive while
master does not.
Also adds myself to list of recipients so I'll get notified when the job
fails.
Change-Id: I07a13dcc72c59854222f6e5ace9d1e18c24e6479
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
The dockerfile path is relative to the dockerdir, not the root of the
cloned repository.
Change-Id: I7836abf8f15d4d9f14cb8d39bc951ec9341d39ba
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Removing the cperf docker image in clean just adds more overhead to the
next cperf run, because the entire docker image has to be re-downloaded.
Docker pull will automatically download the difference between the old
image and the new image (less bandwidth) so there is no reason to remove
the image.
Change-Id: I79ba2af20e3bdacfedc28d468fb629e040d7098f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I7baab0712ee5531b12ac15af5c36672778a8c6d4
Signed-off-by: Qiaowei Ren <qiaowei.ren@intel.com>
|
|
Change-Id: I0f5f8225c38f535241ecd78aa93aee28782cbc4f
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|