summaryrefslogtreecommitdiffstats
path: root/releases
AgeCommit message (Collapse)AuthorFilesLines
2018-07-02Tagging FDS for Fraser 6.2.0Onong Tayeng1-0/+3
Change-Id: Idebf9d0d49ef9d57901615ddf15595545031f093 Signed-off-by: Onong Tayeng <otayeng@cisco.com>
2018-07-02Merge "Tagging Bottlenecks F release 6.2"Aric Gardner1-0/+3
2018-07-02Merge "Fraser Tagging: 6.2.0"Aric Gardner1-0/+3
2018-07-02Merge "[yardstick] fraser opnfv-6.2.1 release tag"Aric Gardner1-0/+3
2018-07-02Fraser Tagging: 6.2.0Sridhar K. N. Rao1-0/+3
vswitchperf tagging. Change-Id: I93a7d97e89d493b2ace9bf2c00b1932a89bab772 Signed-off-by: Sridhar K. N. Rao <sridhar.rao@spirent.com>
2018-07-02Tagging Bottlenecks F release 6.2Yang (Gabriel) Yu1-0/+3
Change-Id: I7df15a89379ce0e30eba0bd00ae9fbb76056970d Signed-off-by: Yang (Gabriel) Yu <Gabriel.yuyang@huawei.com>
2018-07-01[yardstick] fraser opnfv-6.2.1 release tagrexlee87761-0/+3
fix opnfv-6.2.0 bug: docker image build failed JIRA: YARDSTICK-1278 Change-Id: Ifac06060ffedf6c8300e371600f1af2ce928dd14 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-06-30Tagging opnfv-6.2.0 for CloverStephen Wong1-0/+4
Change-Id: I350cce402226444fa0dda75e64405cfcb20a3519 Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
2018-06-30update fraser 6.2.0 release tag for sdnvpnPeriyasamy Palanisamy1-0/+3
Change-Id: Id78fbfe1cb2e0ace44d2e6acf688e4115941a84a Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
2018-06-29Merge "Adds StorPerf 6.2.0"Trevor Bramwell1-0/+3
2018-06-29Merge "Update in release tag for sfc"Trevor Bramwell1-1/+3
2018-06-29Merge "Apex: update release tags for 6.2"Trevor Bramwell1-0/+12
2018-06-29Merge "Tag snaps-oo with 6.2 for fraser"Trevor Bramwell1-0/+3
2018-06-29Merge "[release] Fuel, Armband: Release opnfv-6.2.0"Trevor Bramwell2-0/+6
2018-06-29Merge "[yardstick] fraser opnfv-6.2.0 release tag"Trevor Bramwell1-0/+3
2018-06-29Merge "updated auto.yaml with 6.2.0 commit"Trevor Bramwell1-0/+4
2018-06-29Merge "Tagging opnfv-6.2.0 for IPv6"Trevor Bramwell1-0/+3
2018-06-29Merge "Tagging SampleVNF stable/fraser branch for Fraser 6.2.0"Trevor Bramwell1-0/+4
2018-06-29Apex: update release tags for 6.2Tim Rozet1-0/+12
Change-Id: I4d6e12a6975b5a3e49fc50eeca71514d118cf235 Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-06-29Adds StorPerf 6.2.0mbeierl1-0/+3
Change-Id: Iec76686129f9cd53603e6a73df45681979e4a695 Signed-off-by: mbeierl <mark.beierl@dell.com>
2018-06-29Update in release tag for sfcManuel Buil1-1/+3
Change-Id: I1e410851dc4e4dcbb2844af9c35cb0b5bb91ac94 Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-06-29Publish Functest 6.2.0 tagsCédric Ollivier1-0/+6
Change-Id: Ieef2d00e57af2c06f588f4f819b9eaf402830a07 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-06-29[yardstick] fraser opnfv-6.2.0 release tagrexlee87761-0/+3
merge after patch https://gerrit.opnfv.org/gerrit/#/c/59349/ Change-Id: Icf2a16659f2804eaef95c83ee7d959b7e73441eb Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2018-06-29[release] Fuel, Armband: Release opnfv-6.2.0Alexandru Avadanii2-0/+6
Change-Id: I704c09f22098023ad39b835a982a58159ac45ff0 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-06-29Tag snaps-oo with 6.2 for fraserspisarski1-0/+3
patch 2, selected wrong SHA earlier Change-Id: Ibf3176a048c6e9e882cd997f3bc74ae986d7bbf8 Signed-off-by: spisarski <s.pisarski@cablelabs.com>
2018-06-29Tagging SampleVNF stable/fraser branch for Fraser 6.2.0Deepak S1-0/+4
Change-Id: I6312e57c689519bdf65a562db85acfb443ac7b68 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-06-28updated auto.yaml with 6.2.0 commitGerard Damm1-0/+4
JIRA: AUTO-41 Change-Id: I6952b19687eef464040b47ccc116597f0cb9b397 Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
2018-06-28Tagging opnfv-6.2.0 for IPv6Bin Hu1-0/+3
Change-Id: Ic0d7b8976d91239bca61f01396fc0423e51ac578 Signed-off-by: Bin Hu <bh526r@att.com>
2018-06-28tagging compass4nfv Fraser 6.2 releaseHarry Huang1-0/+7
JIRA: - check ip_forward and set to 1 Change-Id: I23f8757339a0433d79d0973366be2db15c6760a3 Signed-off-by: Harry Huang <huangxiangyu5@huawei.com>
2018-06-28Fix the output of repo list to be 'repo, tag, ref'Trevor Bramwell1-1/+1
This was changed in a previous commit and causes calls to 'git branch' during the verification job to fail. Change-Id: I71c248abecf030658371b810d403e1f460933946 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-06-28Fix Typo in repos release scriptTrevor Bramwell1-1/+1
As the scripts are ran under Python 3, parenthesis are required around print statements. Adding these doesn't seem to cause in error in Python 2. Change-Id: Ic0ce623ded5f3e3f27c8117e2067566afc8d8c0b Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-06-28Merge "Doctor Fraser opnfv-6.2.0"Trevor Bramwell1-0/+4
2018-06-25Doctor Fraser opnfv-6.2.0Tomi Juvonen1-0/+4
Change-Id: I9f61914d3c07ca52e9b062110a2d0036090b3626 Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
2018-06-13Update the repo script to only list repos onceTrevor Bramwell2-6/+40
When projects have multiple releases (ex 6.0, 6.1) the repos would be listed multiple times when only wanting repo names. This change still supports listing the repos when they have multiple versions. Change-Id: I7b0c96649b5486d91b177f95cf175bebcb53815b Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
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-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-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-25Verify and Create Tags from Release FileTrevor Bramwell3-0/+85
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>