Closed
Bug 1298343
Opened 8 years ago
Closed 11 months ago
consider moving entire ship-it api.py from tools to shipitapi python package and have release runner use it
Categories
(Release Engineering :: Release Automation: Other, defect, P5)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mtabara, Unassigned)
References
Details
In bug 1288434 we needed to share the code from http://hg.mozilla.org/build/tools/file/tip/lib/python/kickoff/api.py in a mozharness script. We had three options: 1. to duplicate code in mozharness script 2. to use tools repo in the mozharness script 3. to extract the logic in a Pypi package and use it from there in both places (tools and mozharness). Eventually we went with the third option and https://pypi.python.org/pypi/shipitapi was born. For the moment it only contains the base API class and the Release one. TODOs: * consider adding the L10n and Releases classes as well in the shipitapi package * tweak release runner to use the shipitapi package instead of the api.py file from kickoff
Comment 1•8 years ago
|
||
You can do something similar to http://hg.mozilla.org/build/tools/rev/f7c95836d626 we did for retry. The basic idea is to copy the library into lib/python/vendor and adjust the usage. This way we would know that if we touch something in vendor, we would want to upstream the changes.
Updated•7 years ago
|
Priority: -- → P2
Updated•7 years ago
|
Assignee: mtabara → nobody
Priority: P2 → P5
Updated•11 months ago
|
Severity: normal → S3
Updated•11 months ago
|
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•