opendev
/
jeepyb
Code Issues Proposed changes
Gerrit Project Builder Tools
437 Commits 1 Branch 0 Tags 3.6 MiB
Python 100%
Go to file
Clark Boylan 5b68b2227f Handle newer gerrit in update blueprint script 
Newer gerrit provides the project name and the branch the change is
proposed against as well as the change id itself in the --change
argument to patchset created hooks. This is a behavior change that we
have to handle as old gerrit passed only the change id.

We do this by going to the old behavior of the script by splitting off
the change id from the new string and using only that. Note that this
may not be strictly correct as multiple changes can share a change id
(likely why gerrit made this change in the first place). We can worry
about properly correct behavior in future updates.

Change-Id: Idef56e98ed6c753a58b766024295b2f5147e3aea
 		2017-09-23 12:21:13 -07:00
jeepyb Handle newer gerrit in update blueprint script 2017-09-23 12:21:13 -07:00
.gitignore Add .idea to .gitignore 2013-07-22 13:10:38 +04:00
.gitreview Updated .gitreview location 2012-12-16 20:31:45 +00:00
.mailmap Add gerritx project infrastructure. 2012-11-22 09:41:44 -08:00
CONTRIBUTING.md Workflow documentation is now in infra-manual 2015-02-03 18:40:17 +00:00
MANIFEST.in Renamed to jeepyb. 2012-11-28 09:39:39 -08:00
README.rst Switched documentation to point to storyboard. 2014-11-11 15:17:23 -08:00
requirements.txt Remove argparse from requirements 2016-01-20 19:32:12 +01:00
setup.cfg Split track-upstream from manage-projects 2017-02-14 12:20:07 -06:00
setup.py Updated from global requirements 2015-11-13 11:12:07 +11:00
test-requirements.txt Updated from global requirements 2015-11-13 11:12:07 +11:00
tox.ini Ignore E125 and H flake8 violations. 2013-12-03 10:19:04 -08:00

README.rst

Tools to Manage Gerrit Projects

jeepyb is a collection of tools which make managing a gerrit easier. Specifically, management of gerrit projects and their associated upstream integration with things like github, launchpad, and storyboard.