Age | Commit message (Collapse) | Author | Files | Lines |
|
* Update docs/submodules/releng from branch 'master'
- [fuel] Schedule odl-ovs-noha scenario
Change-Id: I2946684b8e5941201865c123793b7f5800b5421b
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Projects did not fill out their releases/fraser/
This is the patchset of projects that did not fill out their
releases fraser file.
I have done it for them.
some of the projects had no changes on the fraser branch
in this case I put the tag in the same place as the 6.0.0 tag
some project I am familliar with and I move the tag to the
head of fraser for them,
Ideally team leads will do this work in the future
We will update the tagging instructions accordingly.
Change-Id: I1b2c7a8b6e63bc857192757e25f2d103c2629319
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "updated auto.yaml with 6.1.0 commit"
- updated auto.yaml with 6.1.0 commit
master commit to use for 6.1.0:
b718a43380376d2b19222c4203c97a95ca849ae8
(note: opnfv-6.1.0 tag: 553ea71b7aa2eb7d9ff46316de367dff0844ce42)
(can/should a tag objet ID be used for a point release ?)
updated stable/fraser SHA1, to same SHA1 that was used for 6.0.0
(i.e. 3a957a75f99686767d13f45d74b5ca8463559b7b)
(I assume stable/fraser SHA1 should be the same as 6.0.0 SHA1 ?)
>The stable ref is the ref when the branch was created, it should not
>change
(cherry-picking for stable/fraser is not possible after 6.0.0 is
released)
>You can cherry pick as long as you want.
Change-Id: I887174801a56b374cae0197b31561673bc0435ea
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Doctor Fraser opnfv-6.1.0"
- Doctor Fraser opnfv-6.1.0
Change-Id: Ib09b9b919ca046532931fed551d7a6f7aa1857c1
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Tagging IPv6 stable/fraser branch for Fraser 6.1.0"
- Tagging IPv6 stable/fraser branch for Fraser 6.1.0
Change-Id: I5212e57c689519bdf65a562db85acfb343ac7b68
Signed-off-by: Bin Hu <bh526r@att.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Tagging SampleVNF stable/fraser branch for Fraser 6.1.0"
- Tagging SampleVNF stable/fraser branch for Fraser 6.1.0
Change-Id: I6312e57c689519bdf65a562db85acfb343ac7b68
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Publish Functest opnfv-6.1.0 tags"
- Publish Functest opnfv-6.1.0 tags
Change-Id: If1f9d8c961d976e21c5fd6354a712027a6591e96
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Prepare for 6.1.0"
- Prepare for 6.1.0
Change-Id: I1282caa29b6c2a1fe67ec80f090a0acc1d4f24ce
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Apex: Ready for Fraser SR1"
- Apex: Ready for Fraser SR1
Change-Id: Ib59491210da3996fe59885635481b22fd84d1af2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "modified for fraser 6.1.0 release"
- modified for fraser 6.1.0 release
Change-Id: Ibdb9bba605fd7deccf184010085cb14cc2805b59
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Prepare for Clover 6.1.0"
- Prepare for Clover 6.1.0
Change-Id: I885f40ca8ac1c076b8443f03ca99a975d4edc82e
Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[yardstick] fraser opnfv-6.1.0 release tag"
- [yardstick] fraser opnfv-6.1.0 release tag
Change-Id: Ife8ee87db45381678c44ebd80adf08658bd697f5
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "tagging compass4nfv Fraser 6.1 release"
- tagging compass4nfv Fraser 6.1 release
JIRA:-
fix 3 neutron trunk testcases failure in functest
Change-Id: Ie3cd55c3aac1b6e1104054b3ab666056efa83b5b
Signed-off-by: chigang <chigang@huawei.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Revert "Remove noop for tag creation."
This reverts commit dc4b9d1ad316e9055ccb3767c4572ad22cbe43a5.
Change-Id: I3bec4ef84dcb7e56d80b4df78b487f7caa931f3e
|
|
* Update docs/submodules/releng from branch 'master'
- Remove noop for tag creation.
This script is tested, and should now be allowed to create tags.
Change-Id: Ia87341c9cb6397700442a11c38d502fed8dd4743
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- [release] Fuel, Armband: Release opnfv-6.1.0
Change-Id: I7ec0b1d9b40d12500eaf0f82e2e8035c488d1437
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Verify and Create Tags from Release File"
- Verify and Create Tags from Release File
Updates the releases verify and merge jobs to check release files for
the following:
- commits exist
- commits are on stable-branch
If both of these criteria are met and the patch is merged, the repos
will be tagged at the specified commits and pushed.
If a repo has already been tagged but not on stable-branch the job will
not exit, but will warn that the commit doesn't exist on the correct
branch. This is because tags should never be removed.
This adds an additional script 'repos.py' that provides an quick
interface for pulling out information from release files, along with the
script 'release-status.sh' for checking the status of tags.
NOTE: The branch creation script has been disabled until it can be reworked.
Change-Id: I498bc74f20aa50d2bd321771f20a77905b246399
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: More CSIT promotion fixes
Changes-Include:
- Use 2 computes as required by ODL team
- Get rid of checking JOB_NAME var for csit, and simply check if
PROMOTE var is True
- Pass PROMOTE all the way from top-down into deploy job
- Use CSIT network settings file when deploying CSIT
Change-Id: I56d953516ce690749634b474e553baad3a762364
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Apex: Fix blocking on promote and artifact ver"
- Apex: Fix blocking on promote and artifact ver
Change-Id: I274dba9398ef549d20fa106eda88abebfbf48c9e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Fix armband functest job suite name"
- Fix armband functest job suite name
Change-Id: Iea3269a25e88790d335456508ad0de904ed4706e
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: migrate promote jobs to use virtual deploy job
This job already does deploy and test, so just use that rather than
triggering seperate jobs.
Change-Id: Ie62088f434de93ebb7638ba4d4ef8791ac01aa1f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Cleanup functest jobs"
- Cleanup functest jobs
Remove unnecessary arm-daily testsuite
arm-daily does not require special builder or parameter
changes
Increase job-timeout to fit both architectures
JIRA: FUNCTEST-917
Change-Id: Id31709740906fa9ea3918c8694d04fd88191f03f
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: Always build RPM in build job
Change-Id: Ie2d0a730801bc7f5bb784ee90e60e8e30562ef47
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: Fix scenario name for promote jobs
Promotion name for master OS should just be nofeature.
Change-Id: I60086e94bbef87a1754f4f2cc00d096454668ded
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: fix unbound variable in artifact dl
We still need VERSION_EXTENSION var to figure out which RPM files to
remove on the slave.
Change-Id: I03cc9c3318edec9860c8f3ffc01db52517a644b4
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Fix docs build errors
This fixes the two error types being output by a Sphinx docs build:
- numbered - This is already included in the root toctree
(docs/index.rst) and doesn't need to be repeated
- List spacing - Only in infra/jenkins/connect-to-jenkins.rst, the
enumerated list of steps was missing spaces after each item
Change-Id: I55555821a35a3d248f3a347e8e4d9c851254cf08
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: enable RPM build on master verify
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Apex: Updates daily master scenario names
Change-Id: I881634a57f1d28cfcc3346476dc095873c014a22
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "xci: Enable verification of changes coming to prototypes folder"
- xci: Enable verification of changes coming to prototypes folder
Change-Id: I62095327781153eaff81999f5f3fdddc652dc550
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Fix Manual Triggering of Docker Jobs
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Update Global-JJB to master
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>
|
|
* Update docs/submodules/releng from branch 'master'
- openci: bugfix: Fix var names and event headers
Change-Id: I449037e727abed363766ca47a26ea3d2bd6abf4e
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "openci: Add OPNFV scenario composition and test jobs for the demo"
- openci: Add OPNFV scenario composition and test jobs for the demo
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "openci: Further filter triggering events based on scenario for ODL and ONAP"
- openci: Further filter triggering events based on scenario for ODL and ONAP
Change-Id: If05f7922d5888775eff113877b8bdd319948956a
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Fix Docker Container Build Tagging"
- Fix Docker Container Build Tagging
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Disable Daisy Jobs"
- Disable Daisy Jobs
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>
|
|
* Update docs/submodules/releng from branch 'master'
- openci: Add event publisher to ODL and ONAP Autorelease jobs
Change-Id: I1efdff3dbcfdcc9b0820b43d982f686bbe1db4a7
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "[Dovetail] Changing the path of the ssh key in pod.yaml for yardstick"
- [Dovetail] Changing the path of the ssh key in pod.yaml for yardstick
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "openci: Add skeletons for ODL autorelease and promotion jobs"
- openci: Add skeletons for ODL autorelease and promotion jobs
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "openci: Add skeletons for ONAP autorelease and promotion jobs"
- openci: Add skeletons for ONAP autorelease and promotion jobs
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Remove reverify for opnfv-lint and gate-security
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Bump JJB Build Timeout to 60 Minutes
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Update postbuildscript syntax for JJB 2.0.3"
- Update postbuildscript syntax for JJB 2.0.3
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Update JJB to 2.0.3 and Global-JJB to 0.18.0"
- Update JJB to 2.0.3 and Global-JJB to 0.18.0
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Adding sysstat xmlstarlet and facter
Adding lf global jjb deps to ansible build server job
Change-Id: If71a9cf68c6011a6f6c283e2296a17f211255286
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
* Update docs/submodules/releng from branch 'master'
- xci: Fix scenario determination for changes coming to releng-xci
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "Combine generic and external scenario determination to one"
- Combine generic and external scenario determination to one
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Merge "jjb: xci: Do not check for the WORKSPACE variable"
- jjb: xci: Do not check for the WORKSPACE variable
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Rename files under jjb from 'yml' to 'yaml'
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>
|
|
* Update docs/submodules/releng from branch 'master'
- Use Global-JJB for Releng merge/verify Jobs
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>
|