Age | Commit message (Collapse) | Author | Files | Lines |
|
We will try to reuse the job template
for deploying from armband project.
Change-Id: I76a783094ce5be1b4aa93585a6b90898d909ca13
Signed-off-by: pava <Paul.Vaduva@enea.com>
|
|
Now that we only build apex python rpm in master, we can afford to build
RPM everytime and ensure it builds correctly.
Change-Id: Ica1efe1cc2c3db0dfe1c5677b5ab47df121c0966
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I881634a57f1d28cfcc3346476dc095873c014a22
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
When manually triggering a docker job (or even through timed builds),
GERRIT_EVENT_TYPE will not get set. This does gets set when the job is
triggered by a Gerrit event (ex: ref-updated, comment-added).
Specifying the variable lookup to default to nothing (ex: "${FOO:-}")
should allow non-Gerrit triggered jobs to complete successfully.
Change-Id: Ic1ba8ebef0967b0f20a2d6385ce0e0b4876901dc
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This is a temporary update until a new release of Global-JJB comes out.
Updating Global-JJB to a commit on master past 0.19.2 which allows
jjb jobs to run on the same builder without tripping over each other.
The related Gerrit change for the current tip of master can be seen
here: https://gerrit.linuxfoundation.org/infra/#/c/10717/
Change-Id: I4205fc74d8af805ac29ac93d4c5b033c145a00b9
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I62095327781153eaff81999f5f3fdddc652dc550
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I449037e727abed363766ca47a26ea3d2bd6abf4e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
and ONAP"
|
|
|
|
The flow is
- OPNFV compose job gets triggered by the ArtifactPublishedEvents published by
ODL and ONAP autorelease jobs, composing the corresponding scenarios. At the
end, CompositionDefinedEvent is published for the composed scenario.
- OPNFV test job gets triggered by the CompositionDefinedEvents published by
OPNFV compose jobs, deploying and testing the composed scenario. At the end,
ConfidenceLevelModifiedEvent is published for the tested scenario which can
be consumed by ODL and/or ONAP Jenkinses, doing further promotion.
Change-Id: Ice1736d65f3f2b26e849302fec2bb0c579da4a1c
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
All ZTE Pods are offline so there is nowhere for these to run. Disabling
until resources are available again.
Change-Id: Ic57d9d690622ad6e019fa90c512bf3f1a4992fc6
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: If05f7922d5888775eff113877b8bdd319948956a
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I1efdff3dbcfdcc9b0820b43d982f686bbe1db4a7
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
|
|
Builds triggered by tags have a typo in the extraction of the tag name.
This change includes a method for retriggering a tag build with the
comment "retag TAG_NAME".
Change-Id: Ie035e0922f8c073d3e360917ea7ccd6fa76d7b20
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
The jjb will be proposed to ONAP Releng once it is verified on OPNFV
Jenkins.
The flow is
- ONAP autorelease job publishes an ArtifactPublishedEvent to make the
availability of a new version that is tested known to the world
- ONAP promote job gets triggered by a ConfidenceLevelModifiedEvent
published by OPNFV CI to promote autorelease artifact further.
The prototype doing realistic stuff will be built on top of these jobs
and
- parse the triggering event to find the location of autorelease
artifact
- download the artifact for composing ONAP scenario
- run the deployment and testing of ONAP scenario
Please note that this change just adds the basic structure for the jobs
to share the idea. Further changes will add triggering, message
costruction, and publishing.
Change-Id: Ib8939ab44d664ff71f472db66a0e2171ed7b56c5
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
The jjb will be proposed to ODL Releng once it is verified on OPNFV
Jenkins.
The flow is
- ODL autorelease job publishes an ArtifactPublishedEvent to make the
availability of a new version that is tested known to the world
- ODL promote job gets triggered by a ConfidenceLevelModifiedEvent
published by OPNFV CI to promote autorelease artifact further.
The prototype doing realistic stuff will be built on top of these jobs
and
- parse the triggering event to find the location of autorelease
artifact
- download the artifact for composing ODL scenario
- run the deployment and testing of ODL scenario
Please note that this change just adds the basic structure for the jobs
to share the idea. Further changes will add triggering, message
costruction, and publishing.
Change-Id: I51d7e0cfcb5f2552fcc9ac287ed12ed70f582895
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This is temporary, using reverify does not work in global-jjb
for for now remove surrounding jobs so that users dont think its working.
I've been told we can add reverify into global-jjb
after that is done, I will re-add these.
Change-Id: I533ff7c15d55d2630504ca18416583c167228c0d
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Without caching enable or when updating the JJB version all jobs get
reconfigured, which can take upwards of 30 minutes. Setting this to a
higher value should keep the build from being failed while still
running.
Change-Id: Ie2ed11da919ed9114700423591ebfaef94e61c88
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
Also updates global-jjb to 0.18.0 as it includes fixes to
Postbuildscript required by the update to JJB 2.0.3.
Link to Global-JJB 0.18.0 commit:
https://gerrit.linuxfoundation.org/infra/#/c/10101/
Change-Id: I246e60d6c63cf6ba40aeba30d2a7e3985e57d5ad
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Adding lf global jjb deps to ansible build server job
Change-Id: If71a9cf68c6011a6f6c283e2296a17f211255286
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
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>
|
|
The ssh key is already available in the userconfig directory mounted by
Dovetail inside the Yardstick container.
Change-Id: Ic72473e9e47b625fbf4a0f8a8fb140aaed72b69a
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>
|
|
Earlier change took the possibility of dynamically determining the default
scenario. This change puts part of it back which is based on the changed
installer and/or other changed files.
Change-Id: Ie6d9a9b0622ac4ae5ff0cf0e679fd26beed51747
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
Previously we were determining the impacted generic scenario by looking into
changeset in releng-xci. Since we moved the scenarios to releng-xci-scenarios,
this is not needed anymore and same function can be used for determining the
scenario.
Change-Id: I06a65599e03dff4016d0d9d78116e505d84b5061
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
The WORKSPACE variable is always set so we do not need to check it
in the script.
Change-Id: I33d2e17b9a4a7b262c781c7442cc69c2433f8729
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Change-Id: I9f6a287727d36266207fb2821127ac142952f67d
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
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>
|
|
Replaces the releng templates:
- releng-verify-jjb
- releng-merge-jjb
With the job group '{project-name}-ci-jobs' which includes:
- releng-jjb-verify
- releng-jjb-merge
- releng-jenkins-cfg-merge
- releng-jjb-deploy
JIRA: RELENG-397
Change-Id: If8160a67d8d665dcb8f86b6649288a710cc0fe13
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>
|
|
Since the commit submodule commit can't be set to an explicit tag,
please see this link[1] for verification that
90e4e825b3d0ac5959122c50e457419ad0cfe137 is v0.17.0.
[1] https://gerrit.linuxfoundation.org/infra/#/c/9386/
JIRA: RELENG-398
Change-Id: I9d4e90cc073c8b9cb741735a2ba582a2c7882087
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
We no longer have static inventory files per installer and flavor
so we need to switch to the dynamic inventory option.
Change-Id: I5b8bf800264b1b297b61d09d010552cd22636627
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
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>
|
|
|
|
|
|
The scenarios have been moved from the releng-xci to
releng-xci-scenarios repository so we should connect Jenkins
to that repo as well.
Change-Id: Ifcb4f02b8532dd94c8a622185328f7316e726c6b
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Change-Id: I380008fe2cadbce8f6b7b1f84c9f3bf720df485e
Signed-off-by: xudan <xudan16@huawei.com>
|
|
When passing a YAML variables file to Ansible, we need to prefix it
with '@'.
Change-Id: I884f4698a1033cca9ad55bf3592e1dd817273f81
Signed-off-by: Markos Chandras <mchandras@suse.de>
|