Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
The gerrit variable for the git SHA is GERRIT_PATCHSET_REVISION instead
of GERRIT_CHANGE_ID. We also need to export the XCI_ANSIBLE_PARAMS
variable.
Change-Id: I206820f1155a4876fb7d87cc0b5ae1b8afb06bd6
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Since there is only one CI pod available for armband at the moment,
we instruct CI to run only one job per day. Four jobs for master
branch and 3 for stable branch.
Change-Id: I645a98d922c00b2237cb5aeeb280d00ecdf0e288
Signed-off-by: Charalampos Kominos <Charalampos.Kominos@enea.com>
|
|
|
|
That's mainly because of that
1. The owner of all results files are root:root
2. Sometimes there are some files that can only be read by root
3. User jenkins failed to upload these files
Solutions:
1. Change the owner to be jenkins:jenkins
2. Remove these files which are useless for users
Change-Id: I0b5e72e8d5045c7e0d64e32a13ba559612460a84
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Pass scenario information using the new override mechanism.
This patch depends on the matching releng-xci change
https://gerrit.opnfv.org/gerrit/#/c/56643/
Change-Id: Ib8473249e424f259f5757ebdaed7d73fa4b0adce
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
|
|
|
|
|
|
Functest VNF tests are not adapted for aarch64.
The tests can be reactivated when they are adapted to execute
on aarch64.
JIRA: FUNCTEST-964
Change-Id: I2413a6eff831c8dd2751b7bc73ad583f55a00dcf
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
|
|
With this change releng/jjb/* now passes on:
Jenkins Job Builder version: 2.0.1 and 1.6.2
Error:
TypeError: write() argument must be str, not list
Explanation:
in jjb 1.6.2 it would allow the list in and then the job would convert
the list into a literal string of "['var1', 'var2']"
- 'compass-{scenario}-{pod}-daily-{stream}'
Can have scenario passed, {scenario} is part of the job name
so it knows which scenario to add.
- 'compass-deploy-{pod}-daily-{stream}'
cannot have scenario passed, there is not one job generated per scenario
so its tryting to add "['senario1', 'scenario2', 'etc']" into the {scenario}
value, which is not allowed.
This worked on jjb 1.6.2 becasue we overwrite the scenario
information later:
- trigger-builds:
- project: 'compass-deploy-{pod}-daily-{stream}'
predefined-parameters: |
DEPLOY_SCENARIO={scenario}
jjb/armband/armband-ci-jobs.yml is very simillar to this job
and passes a default, which works, so that is what I have done here:
- string:
name: DEPLOY_SCENARIO
default: 'os-odl-nofeature-ha'
addendum:
removed scenario: '{scenario}' from
'compass-{scenario}-{pod}-daily-{stream}'
even though it is valid, Trevor rightly pointed out that there is
nothing to consume this value.
Change-Id: I134b2bd5888dcdfa5b768a7db2bdc98ad32ec28e
Signed-off-by: agardner <agardner@linuxfoundation.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: If50ad310049edca687da8e0acf412a7e1eacd2b6
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I46753983e1fb37300df70700c474c3dda3532ffa
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I92635178ddc354dd7773cd372a34d46f5ee0bf2a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I4d6c4015ca36f743dadbb6524a1ca8d5619ce3d6
Signed-off-by: Yang Yu <Gabriel.yuyang@huawei.com>
|
|
According to this https://issues.jenkins-ci.org/browse/JENKINS-47566,
the failure seems to be caused by the permission problem.
Change the owner of all files in 'results' directory to be jenkins.
Change-Id: I0ed30018354259601c39016fc1950ea7db867e78
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
As master is currently disabled, it doesn't make sense for this to be
enabled.
Change-Id: Ie5966e22ffdff7a585781673259775c4e6150acf
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
|
|
Bottlenecks ping test case could exhaust the system.
As a result, tests runned after this one probably get failed.
So this patch is to move this test at the bottom of tests list
Change-Id: Ief8af01c6dc7b6f5cb60e568d6239ee7901ad89c
Signed-off-by: Yang Yu <Gabriel.yuyang@huawei.com>
|
|
Dovetail does not currently support AArch64 properly (e.g. it tries
to load x86 images), so limit its runs to weekend days until full
support is implemented.
Change-Id: I83347286490344912593a122fc47013d5fcf7125
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
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>
|