Age | Commit message (Collapse) | Author | Files | Lines |
|
Includes logging more warning to help debug when things fail.
Change-Id: I25e9afc6b9f413d33368613291e718cf8ccd6335
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I43142004c2d44914baa8cfe79dd245c3613f465c
Signed-off-by: Bin Hu <bh526r@att.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>
|