Closed
Bug 548549
Opened 15 years ago
Closed 8 years ago
unify release automation *_info.txt files with the ones generated by the build system
Categories
(Release Engineering :: Release Automation: Other, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
References
Details
(Whiteboard: [automation][triagefollowup])
In bug 474610 Ted added a txt file that contains a buildid that gets uploaded alongside the build. We already do something similar for releases, but it's done in a Buildbot factory. We should support the build system way. The cheap way of doing this is to adjust the path and filename of this file to what the automation expects when MOZ_PKG_PRETTYNAMES is set. Probably the better way is to make the automation support the filenames that the build system already uses.
Comment 1•15 years ago
|
||
Yeah, I'm not married to the filename I'm using, it's just the basename of the package file, since that was convenient to use.
Updated•13 years ago
|
Assignee: nobody → jhford
Updated•13 years ago
|
Blocks: hg-automation
Reporter | ||
Updated•13 years ago
|
No longer blocks: hg-automation
Reporter | ||
Comment 2•13 years ago
|
||
Mass move of bugs to Release Automation component.
Blocks: hg-automation
Component: Release Engineering → Release Engineering: Automation (Release Automation)
Reporter | ||
Updated•13 years ago
|
No longer blocks: hg-automation
Comment 3•13 years ago
|
||
Ben, do you know if we still want this?
Reporter | ||
Comment 4•13 years ago
|
||
It's a "nice to have" for me, I can't think of any reason why we want this other than avoiding duplication.
Comment 6•13 years ago
|
||
putting back in the pool
Assignee: jhford → nobody
Severity: normal → enhancement
Updated•13 years ago
|
Whiteboard: [automation] → [automation][triagefollowup]
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Reporter | ||
Comment 7•9 years ago
|
||
Are these still going to exist after we have release promotion? IIRC we talked about possibly passing the buildids via other means, and I don't think these files are used for anything else.
QA Contact: bhearsum
Comment 8•9 years ago
|
||
Looks like those are created in ReleaseBuildFactory, so we'll lose them by switching to mozharness. However we can parse files like
http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux64/1435312529/firefox-41.0a1.en-US.linux-x86_64.txt
instead, contents:
20150626025529
https://hg.mozilla.org/mozilla-central/rev/d45440221297
Comment 9•8 years ago
|
||
I believe this is fixed and we use info.txt files generated by the build system
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•