Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ic81f0a707b1a46c65b47251fedc51c8afc8e6d54
|
|
Change-Id: I94e981782dec65df6352d78ea79f4e389b9a2ea3
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
Change-Id: I087b16302226eca76d8842be0343781990345f45
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
|
|
|
|
|
|
on behalf of Tina Tsou PTL
Change-Id: Ib3779a67a09025b2433520566af060516ab6dc43
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
|
|
|
|
Includes logging more warning to help debug when things fail.
Change-Id: I25e9afc6b9f413d33368613291e718cf8ccd6335
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Id5431eca0a078926976d4c96287aee9eb271dbf0
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I43142004c2d44914baa8cfe79dd245c3613f465c
Signed-off-by: Bin Hu <bh526r@att.com>
|
|
add availability yaml for Fraser to create the stable branch
automatically
JIRA: HA-35
Change-Id: Ied9b760b16dbe93cee2d633a225b3596cb59ad22
Signed-off-by: fuqiao <fuqiao@chinamobile.com>
|
|
Change-Id: I89834b6662459cdaaecec506e247c5f60302a075
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
My testing was done using Python 2.7 but the build server running the
jobs is obviously running Python3.
These changes allow the create_branch.py release script to run against
both Python2 and Python3.
Change-Id: I02478986ef869ce82ece5b96dbb4b5ed548a2a55
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Ibe0e92b2b3772c53df66e10bf7059be4754d4646
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
|
|
Tracking releases through yaml file similar to the openstack/releases
project.
Includes a schema file to be for validation, jobs for creating gerrit
branches and stable branch jobs, and documentation for projects on
creating their releases.
Change-Id: Id1876482723e01806c0a6932126dff5ea314eae5
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
These files normally contain the start point of the stable/release branch,
but as this is the initial setup starting from the previous release,
they contain the tip of the stable branch.
When a project is ready to being the stable branch process, they will
copy their project's release file and modify the 'branches' mapping to
create their stable branch.
Change-Id: I0244da5eeb94c431d83f217ec07b08553fdf0639
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|