Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
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>
|
|
|
|
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>
|
|
Adds Gambia daily/verify jobs and prepares to migrate master queens
scenarios to rocky scenarios.
Change-Id: I7bfe6202e00fd62c1e668f3a6f9b481b9fbca99d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Icb84e4860021f5aa24de0d68542863da7fee4aff
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This is still far from a clean and secure approach, as `pip install`
should not be ran with `sudo`.
However, `-H` limits the area we touch and also fixes some incompat
between disto-provided pip and pip-provided pip.
Change-Id: I0e19dfeaf66f6f453e3868c71016305ae050f0c8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- cleanup deploy tooling for old-style artifacts (ISO-based);
- remove danube stream, related jobs and hacks required for them;
Change-Id: Ib2486173df1ec83f2dbc08a5e9faf950bffb4b06
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
This is a temporary fix until we can determine the full list of
requirements from each project needed for the opnfv-build-ubuntu labled
servers.
Previously these were building fine on ericsson-build4, so reassigning
them there should keep there builds green.
Change-Id: I767b6faa718cd6dd4b9fd17f83e7ee817cfb8c4d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I2d0a71fc40a4a6cd1f5b1e63ca429c5b83b7ad00
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
As these only affect jobs defined in global-jjb (no other jobs used
these variable names) they should be safe to define at the global level.
Change-Id: I646c3afc73757bff561cc84b80df064e13680080
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Create functest-k8 job for arm platform. It will be triggerd by
container4nfv jobs.
Add 2 arm pods to functest-daily pod list.
Change-Id: If8209574263b863f2a907cd962f9511cc3db74ea
Signed-off-by: Jingzhao Ni <jingzhao.ni@arm.com>
|
|
|
|
Change-Id: I24cc328cdefcd7ac5f34292f0cf1635f797f8f00
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I4db7c0cda5485dbc756a22b9cbde298612241274
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
As doctor run tox under root user, we need to clean
the workspace in the publisher, otherwise the tests
which come next will be fail when they operate in
the workspace with jenkins user.
Change-Id: I14fbabc7516153c6d93e53baf106067ff4194af6
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Ensures Fatih is still listed for the releng-xci repository.
Change-Id: I4e4d8f474ed35ec07d840e38151956d832fb5692
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
We will try to reuse the job template
for deploying from armband project.
Change-Id: I76a783094ce5be1b4aa93585a6b90898d909ca13
Signed-off-by: pava <Paul.Vaduva@enea.com>
|
|
JJB 2.0.3 changed the postbuildscript syntax a bit and requires
changes so that they work properly with version 2.x of PostBuildScript
plugin.
This patch requires that Jenkins also be updated to install the 2.x
release of PostBuildScript.
Change-Id: I65e52c8d9b2efa38a3d16193c176c65e87e704c1
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
|
|
global-jjb only supports the .yaml file ending for jjb jobs. Instead of
waiting for a release we're going to rename the files.
Change-Id: Icf3339eacd2320c583333e02250998cf6b1881f7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Needed for JJB verify and Merge to work.
These jobs are going away, but first we need to get a verified +1
from jenkins
Also remove releng-comment-jjb its unused
Change-Id: Ice2ad625f87f1d9c841979ede4bb1943110691c8
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Even with per-build-tag set to false, JJB 1.6.2 does not seem to remove
'Create tag for each build' from the git-scm settings. Though the option
is deprecated it is still supported, so setting both of these should
disable tagging when Jenkins clones a git repo.
Change-Id: I5977149ad581df67d938ce2b46794d47c5e06fe3
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Though these defaults match what Jenkins defaults to, we don't want to
get any surprises.
Change-Id: Ia1f49a30f8f14992c548d2cf71c64a9c7a2c91dd
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Removing archived projects from jjb
These project dont need any jobs associated with them
escalator
fastpathmetrics
inspector
lsoapi
movie
multisite
octopus
openretriever
prediction
Change-Id: Ibbe49e54ed326f502157c7892022b7a62173b72d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
These have been moved back into installer-params.yml and added to the
daisy jobs where 'testapi-parameters' is being used.
Including this in the list of parameters would cause duplication as most
installers already include 'DEPLOY_SCENARIO' as a parameter. The
'DEPLOY_SCENARIO' parameter is also sometimes defined through a macro,
which could cause second declaration of DEPLOY_SCENARIO (defaulting to
'os-nosdn-nofeature-ha') to always be used.
Documentation has been added to the parameter to explain the related
macros and how they should be used.
Change-Id: I9aef031dbcf523ae2db15695ce294bd85025530d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
We define the 'node' parameter in job template:
'doctor-verify-{installer}-{inspector}-{arch}-{stream}',
so we don't need to redefine them in the doctor parameter macro.
It will schedule the fuel verify job to the default apex env.
See: https://build.opnfv.org/ci/job/doctor-verify-fuel-sample-x86_64-master/1/console
Change-Id: I49e6d26ca284f6548460312de0cb634bd033d3c1
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
There are no nodes with the label 'not-specified'.
If the jobs which are not specified the node label will
scheduled to the label 'not-specified' and they can not be runned.
Change-Id: I7e7790be2517328fc07d02cdcdc23ee71c7df680
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Change-Id: I7f6072121c4d88192c828e2e3cf2beb5d6c22c37
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Most of these projects will not have a stable branch, but for those that
do follow the process they will need these jobs.
Change-Id: Id0e6cfa9716d72882c38b0fcb42b3ab420332a2e
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I54b4015b1da9a5961c2d3ee1f672b381a3f72914
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
In
https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170,
it indicates that:
only build parameters that have been explicitly defined in a job's
configuration will be available by default at build time. Any other
arbitrary parameters added to a build by plugins will not be
available by default.
It has been tested in sandbox.opnfv.org that only defined parameters can
be passed to the triggered jobs.
For parameters required by TESTAPI are common to all the projectes,
including installers, Functest, and Yardstick, it is convenient to
define a common macro and used by others.
Change-Id: Iac1da85445e1b5d75109ccd64b174f35151b9969
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
PostBuildScript plugin's result affects Jenkins pipeline, so we should
return the original job running status in the postbuildscript in the end
Update macros:
1. from $POD_NAME to $NODE_NAME
2. from $SCENARIO to $DEPLOY_SCENARIO
2. {installer} to $INSTALLER_TYPE for {installer} is not existed in
trigger job
3. add parameters definition for they can not be used in trigger jobs by
predefined-parameters
4. missing TIMESTAMP_END
Change-Id: I354be3d5ad02e53bb988995adc09b59e92a1640a
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
replace `include-raw-escape` with `include-raw` for no jjb macros in the
bash file.
Change-Id: I6125779f23a5aafd7fed0f5017c4280394624bcd
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
Report the provision result to TestAPI.
Change-Id: I05a3a870125c2b1e74b98da043b53684ea334683
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
|
|
|
|
I set -x in a test and then it did report.
not sure what's going on here,
I thought this was fixed.
May as well cat the violation log as we debug
Change-Id: I142fb3855ebc000ee90aa24e0ecb336bb9b313df
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Includes the name of the PTL but should be just the email.
Change-Id: If6ef3b7c15defd44c6f86a24d6250840c37dd24b
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Let the 'email-dovetail-ptl' macro reflect that Georg Kunz is the new
PTL of the dovetail project.
Change-Id: I3b3bd53a7c7f146105a719727fd627bf15054aca
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Julien has recently been promoted to PTL of the Pharos project and the
macro for emailing the Pharos PTL should reflect this change.
Change-Id: Id3f025cd87284d480da892fc999d7379af50ac95
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Changes Include:
- Remove defining 'node:' per job template and use slave-params
defaults
- Gate job was using daily/build slave, when it should be using virtual
slave
Change-Id: Iec2321801daef1b1fa40724a244bf2f6edf36c6e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
We only want to specify slave-label, not sure why we are specifyign node
here and in jjb for Apex.
Change-Id: I184df37836039887f47e7d6141c89f8dd9cd014f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
The char "/" was included in $msg.
It will have issue
"sed: -e expression #1, char 7: unknown option to `s'"
We can substitute '/' with '#' in sed command to solve this issue
Signed-off-by: wutianwei <wutianwei1@huawei.com>
Change-Id: I1308e9b1b2111f0033df119e4465df4dda27eac0
|
|
when we want to trigger the scipt only when previous builders fail, we
should also set the other macro 'script-only-if-succeeded' to false, the
default value is true.
script-only-if-succeeded: false
script-only-if-failed: true
Change-Id: Ifdca24ea8d076dd4e16ef466705e0167b97cf1df
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
The default builder in Jenkins is '/bin/sh -ex'. Because of this lint
jobs are failing that we assume won't as everywhere else we've used
/bin/bash and explitily set options when needed.
Explicitly setting these jobs to use /bin/bash should keep Jenkins from
failing builds without reporting the lint results.
Change-Id: Ibe6cad979d6dcf30e7991873c9ac446ae3bf3a8b
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|