Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
|
|
Liniting is broken, last fix forgot to run linting concurrent
FATAL: The project is configured to NOT run builds concurrent, but the
node parameter [SLAVE_NAME] is configured to trigger new builds
concurrent!
Change-Id: I1eb4bf7279c7af4e01950b89c515e183fbc57b2d
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Linting was broken by this patch
https://gerrit.opnfv.org/gerrit/#/c/50737/
Also added sudo to pip installs, as they are not in a venv
Patch forgot to put linting on build server
so it defaulted to master.
Change-Id: Iba8c1f633fad6d5f3d097f4911f45100c3b43e30
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I310c4f2e46a26b35eeafef2dfc8670d70ace0575
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
Only Danube still uses this param, newer branches rely on IDF.
Going forward, the `-B` deploy arg will be deprecated in Fuel.
Do not yet remove BRIDGE slave params from non-CI PODs, as
other installers (or custom Danube jobs?) might still use them.
Change-Id: I6d259299d1e13e8a5da732aca60b1f56b8472af6
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
OPNFV has common coding style [1]. So, all repos shall be checked by
one generic checker builder/job, eventually.
This patch adds lint wrapper builder 'lint-all-code', and also
refactors all exisiting lint and syntax check builders, following
'lint-yaml-code' builder approach, which only checks modified files.
This approach is nice as it won't require immediate fixes of violations
in whole repo code right after the lint checker job is enabled.
Note that lint jobs are still configured to run against some project
repo, in order to seperate discussion; wheter we should apply this
lint job to all OPNFV repo or not immediately.
[1] https://wiki.opnfv.org/display/DEV/Contribution+Guidelines
Change-Id: Ib4ab3ba5dc08845f3016b8be772f4ed119f11b2d
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Current doctor verify jobs need to be run on relevant pods which are
specified by slave-label. But, after multijob introduced, the parameter
is not passed to children jobs. Also, 'phase' of project is misleading,
as it isn't multijob's phase.
This patch makes sure each doctor job run on correct pod by updating
node label rule for doctor pod to 'doctor-{installer}-{arch}'.
This patch also merges doctor slave parameter definitions into one,
and deletes unnecessary setting where default are set.
Change-Id: Ic9bf218ae7fb4f9866b510efd1e0ccd19277b78e
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
|
|
GERRIT_REFSPEC is always passed by the gerrit-trigger plugin when a job
is triggered by Gerrit. Because it is not explicily defined, there is no
way to manually trigger jobs, as the git clone looks up the list of refs
by GERRIT_REFSPEC.
Being able to manually trigger jobs (with node parameters so they can be
restricted) is very helpful in debugging CI issues.
Change-Id: I8a1d9ea380902fc95f30482e5acb616347709ab1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I3ca61f015c07cbf3bd67acd7972d9a1e0011f21d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
1. add macro for report the provision result of installers
and try it in daisy
2. update according to TestAPI interface
Change-Id: Ic041744c917c37fcd84a12a92e927e39106cf18f
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
|
|
Change-Id: I5193285493926fcf82779f12d491a118bc83baa7
Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
|
|
In the initial formation of projects we found it easy to copy job
definitions to provide project a baseline job config to work off. This
has led to a lot of duplication and misalignment with the gerrit
triggers and default build server tag to be used.
Collapsing these jobs into a job-group containing the stream and a
verify job per-stream, should help reduce this duplication.
Change-Id: Icb366487590a145be4cbfc0637a8d86a6d9b7cec
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Facilitates the creation of docker images from tags pushed to Gerrit,
which should remove the need to manually trigger 'tagged' builds.
Fixes a typo in the 'gerrit-trigger-tag-created' macro,
replaces 'RELEASE_VERSION' with 'GERRIT_REFNAME', and adds the
tag-trigger to docker builds.
Change-Id: I6d8f8f34b1c51d74bb98211dfae21c37cf9356fa
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This change takes xci-verify-jobs as base and adjusts osa-periodic
jobs to ensure they do what they are supposed to.
The structure of periodic jobs is pretty similar to xci-verify-jobs and the
differences comparing to them are
- OPENSTACK_OSA_VERSION is set to master.
- SCM type changed to git-scm from gerrit
- Voting is removed.
- Triggering will be done using pollscm to ensure we only run jobs when something
changes upstream. Triggers are not enabled yet until the basics are verified
working.
This change requires https://gerrit.opnfv.org/gerrit/#/c/49275/ in order for
periodic jobs to work as expected.
Further changes are needed to finalize the structure.
Change-Id: I8f6519ccce93e6b8b65509638294419459fd36e8
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|