summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-06-04jjb/releng: fix compass-container $DOCKERFILEYibo Cai1-1/+0
Use default $DOCKERFILE setting from downstream projects. Change-Id: I0bfee5dcaef9a9eb7601548a1e5da5a5f8d51bb5 Signed-off-by: Yibo Cai <yibo.cai@arm.com>
2018-06-02Merge "jjb/releng: fix compass container build error"Trevor Bramwell1-10/+16
2018-06-01Apex: Only use admin network for snapshot createTim Rozet1-3/+1
CSIT only uses admin network, so only collect that virsh def. Change-Id: I2bce08f004ca673cc8a9ecffd09e44f45b04eb76 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-06-01jjb/releng: fix compass container build errorYibo Cai1-10/+16
Error log: https://build.opnfv.org/ci/job/compass-tasks-base-build-arm64-master/1/console Change-Id: I47ef2ede64d63fb3e9a500dc48cdd510ee9ff235 Signed-off-by: Yibo Cai <yibo.cai@arm.com>
2018-05-31Merge "Auto: Setup Ci Jobs for Auto project"Trevor Bramwell3-4/+133
2018-05-31Merge "updated commit for Auto 6.1.1"Trevor Bramwell1-0/+4
2018-05-31Apex: Parameterize functest suite/testcaseTim Rozet3-2/+12
This patch parameterizes the functest variables for the apex-virtual job so that we can indicate which tests to run when calling the apex-virtual (which in turn runs deploy and functest). Change-Id: Ic628c7711aca2d3ac0520d34150a3242d8d9891d Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-30Merge "jjb/releng: support multi arch compass images"mei mei1-10/+89
2018-05-29updated commit for Auto 6.1.1Gerard Damm1-0/+4
Cherry-picked 3 changes from latest master, to stable/fraser merged these 3 changes into stable/fraser new commit ID: 0f43563624832c5908e6fc00eb0a4bbc6cc82c33 will need to be tagged as 6.1.1 patch#2: removed trailing spaces Change-Id: I934dedb6c0b1efde2404f550cbd1a58e618ffc1a Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
2018-05-29Apex: Changes default verify scenario to nosdnTim Rozet2-4/+4
Basically we are getting blocked on merging patches due to ODL breaking and these patches have nothing to do with ODL. So we are changing the default sceanrio to just be nosdn, and then if the change is relatd to ODL we can include an ODL gate run. Change-Id: I61ec224e62e6f3cb6ee40696326bf243788c27d6 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-29[fuel] Schedule odl-ovs-noha scenarioMichael Polenchuk1-0/+16
Change-Id: I2946684b8e5941201865c123793b7f5800b5421b Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2018-05-26Projects did not fill out their releases/fraser/Aric Gardner14-0/+48
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>
2018-05-26Merge "updated auto.yaml with 6.1.0 commit"Aric Gardner1-0/+4
2018-05-26updated auto.yaml with 6.1.0 commitGerard Damm1-0/+4
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>
2018-05-26Merge "Doctor Fraser opnfv-6.1.0"Aric Gardner1-0/+4
2018-05-26Merge "Tagging IPv6 stable/fraser branch for Fraser 6.1.0"Aric Gardner1-0/+5
2018-05-26Merge "Tagging SampleVNF stable/fraser branch for Fraser 6.1.0"Aric Gardner1-0/+3
2018-05-26Merge "Publish Functest opnfv-6.1.0 tags"Aric Gardner1-0/+6
2018-05-26Merge "Prepare for 6.1.0"Aric Gardner1-0/+4
2018-05-26Merge "Apex: Ready for Fraser SR1"Aric Gardner1-0/+12
2018-05-26Merge "modified for fraser 6.1.0 release"Aric Gardner1-0/+4
2018-05-26Merge "Prepare for Clover 6.1.0"Aric Gardner1-0/+3
2018-05-26Merge "[yardstick] fraser opnfv-6.1.0 release tag"Aric Gardner1-0/+3
2018-05-26Merge "tagging compass4nfv Fraser 6.1 release"Aric Gardner1-0/+7
2018-05-26Revert "Remove noop for tag creation."Aric Gardner1-1/+1
This reverts commit dc4b9d1ad316e9055ccb3767c4572ad22cbe43a5. Change-Id: I3bec4ef84dcb7e56d80b4df78b487f7caa931f3e
2018-05-26Remove noop for tag creation.Aric Gardner1-1/+1
This script is tested, and should now be allowed to create tags. Change-Id: Ia87341c9cb6397700442a11c38d502fed8dd4743 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2018-05-26[release] Fuel, Armband: Release opnfv-6.1.0Alexandru Avadanii2-0/+6
Change-Id: I7ec0b1d9b40d12500eaf0f82e2e8035c488d1437 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-05-26Merge "Verify and Create Tags from Release File"Aric Gardner6-32/+178
2018-05-25Verify and Create Tags from Release FileTrevor Bramwell6-32/+178
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>
2018-05-26tagging compass4nfv Fraser 6.1 releasechigang1-0/+7
JIRA:- fix 3 neutron trunk testcases failure in functest Change-Id: Ie3cd55c3aac1b6e1104054b3ab666056efa83b5b Signed-off-by: chigang <chigang@huawei.com>
2018-05-25Prepare for Clover 6.1.0Stephen Wong1-0/+3
Change-Id: I885f40ca8ac1c076b8443f03ca99a975d4edc82e Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
2018-05-25modified for fraser 6.1.0 releaseNarinder Gupta1-0/+4
Change-Id: Ibdb9bba605fd7deccf184010085cb14cc2805b59
2018-05-25[yardstick] fraser opnfv-6.1.0 release tagRoss Brattain1-0/+3
Change-Id: Ife8ee87db45381678c44ebd80adf08658bd697f5 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2018-05-25Apex: Ready for Fraser SR1Tim Rozet1-0/+12
Change-Id: Ib59491210da3996fe59885635481b22fd84d1af2 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-25Apex: More CSIT promotion fixesTim Rozet3-7/+14
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>
2018-05-25Prepare for 6.1.0Manuel Buil1-0/+4
Change-Id: I1282caa29b6c2a1fe67ec80f090a0acc1d4f24ce Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-05-25Merge "Apex: Fix blocking on promote and artifact ver"Trevor Bramwell3-6/+9
2018-05-25Merge "Fix armband functest job suite name"Trevor Bramwell1-1/+1
2018-05-25Apex: Fix blocking on promote and artifact verTim Rozet3-6/+9
Change-Id: I274dba9398ef549d20fa106eda88abebfbf48c9e Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-25Apex: migrate promote jobs to use virtual deploy jobTim Rozet2-42/+8
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>
2018-05-25Tagging SampleVNF stable/fraser branch for Fraser 6.1.0Deepak S1-0/+3
Change-Id: I6312e57c689519bdf65a562db85acfb343ac7b68 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-05-25Fix armband functest job suite nameDelia Popescu1-1/+1
Change-Id: Iea3269a25e88790d335456508ad0de904ed4706e Signed-off-by: Delia Popescu <delia.popescu@enea.com>
2018-05-24Merge "Cleanup functest jobs"Trevor Bramwell1-29/+0
2018-05-24Tagging IPv6 stable/fraser branch for Fraser 6.1.0Bin Hu1-0/+5
Change-Id: I5212e57c689519bdf65a562db85acfb343ac7b68 Signed-off-by: Bin Hu <bh526r@att.com>
2018-05-24Apex: Always build RPM in build jobTim Rozet1-2/+2
Change-Id: Ie2d0a730801bc7f5bb784ee90e60e8e30562ef47 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-24Apex: Fix scenario name for promote jobsTim Rozet2-10/+16
Promotion name for master OS should just be nofeature. Change-Id: I60086e94bbef87a1754f4f2cc00d096454668ded Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-05-24Apex: fix unbound variable in artifact dlTim Rozet1-3/+2
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>
2018-05-23Fix docs build errorsTrevor Bramwell4-3/+27
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>
2018-05-23Publish Functest opnfv-6.1.0 tagsCédric Ollivier1-0/+6
Change-Id: If1f9d8c961d976e21c5fd6354a712027a6591e96 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-05-23Doctor Fraser opnfv-6.1.0Tomi Juvonen1-0/+4
Change-Id: Ib09b9b919ca046532931fed551d7a6f7aa1857c1 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>