Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: I4d6e12a6975b5a3e49fc50eeca71514d118cf235
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Iec76686129f9cd53603e6a73df45681979e4a695
Signed-off-by: mbeierl <mark.beierl@dell.com>
|
|
Change-Id: I1e410851dc4e4dcbb2844af9c35cb0b5bb91ac94
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Change-Id: Ieef2d00e57af2c06f588f4f819b9eaf402830a07
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
merge after patch https://gerrit.opnfv.org/gerrit/#/c/59349/
Change-Id: Icf2a16659f2804eaef95c83ee7d959b7e73441eb
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
Change-Id: I704c09f22098023ad39b835a982a58159ac45ff0
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
patch 2, selected wrong SHA earlier
Change-Id: Ibf3176a048c6e9e882cd997f3bc74ae986d7bbf8
Signed-off-by: spisarski <s.pisarski@cablelabs.com>
|
|
Change-Id: I6312e57c689519bdf65a562db85acfb443ac7b68
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
JIRA: AUTO-41
Change-Id: I6952b19687eef464040b47ccc116597f0cb9b397
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
|
|
Change-Id: Ic0d7b8976d91239bca61f01396fc0423e51ac578
Signed-off-by: Bin Hu <bh526r@att.com>
|
|
JIRA: -
check ip_forward and set to 1
Change-Id: I23f8757339a0433d79d0973366be2db15c6760a3
Signed-off-by: Harry Huang <huangxiangyu5@huawei.com>
|
|
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>
|
|
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>
|
|
|
|
Change-Id: I9f61914d3c07ca52e9b062110a2d0036090b3626
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
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>
|
|
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>
|
|
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>
|
|
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: I7ec0b1d9b40d12500eaf0f82e2e8035c488d1437
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
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>
|
|
JIRA:-
fix 3 neutron trunk testcases failure in functest
Change-Id: Ie3cd55c3aac1b6e1104054b3ab666056efa83b5b
Signed-off-by: chigang <chigang@huawei.com>
|
|
Change-Id: I885f40ca8ac1c076b8443f03ca99a975d4edc82e
Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
|
|
Change-Id: Ibdb9bba605fd7deccf184010085cb14cc2805b59
|
|
Change-Id: Ife8ee87db45381678c44ebd80adf08658bd697f5
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
Change-Id: Ib59491210da3996fe59885635481b22fd84d1af2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I1282caa29b6c2a1fe67ec80f090a0acc1d4f24ce
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Change-Id: I6312e57c689519bdf65a562db85acfb343ac7b68
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I5212e57c689519bdf65a562db85acfb343ac7b68
Signed-off-by: Bin Hu <bh526r@att.com>
|
|
Change-Id: If1f9d8c961d976e21c5fd6354a712027a6591e96
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: Ib09b9b919ca046532931fed551d7a6f7aa1857c1
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
Change-Id: I0384563e5e663ea485626562df5ee49815b95817
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|