Closed Bug 588029 Opened 9 years ago Closed 4 years ago

Create libraries to do common filename handling for release automation

Categories

(Release Engineering :: Release Automation: Other, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: catlee, Unassigned)

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2614] [automation])

There are many places in our release automation where we have to deal with various types of filenames.  Most of this code is duplicated and scattered all over the place.

We should create a core set of modules for each language (python, perl, etc.) to where all the filename processing is done.  Tests can then be written against these modules, and the rest of release automation can count on them to function properly.
We have a super tiny start to this in build/tools/lib with getPrettyVersion/GetPrettyVersion

I bet we could almost copy/paste fileInfo from http://hg.mozilla.org/build/tools/file/483d22dfacf8/release/signing/signing.py for the Python version.
Mass move of bugs to Release Automation component.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: hg-automation
Product: mozilla.org → Release Engineering
Whiteboard: [automation] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2614] [automation]
I don't think this will matter once release promotion is finished because it will be passing around references to taskcluster artifacts and/or s3 locations...
Status: NEW → RESOLVED
Closed: 4 years ago
QA Contact: bhearsum
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.