548549 - unify release automation *_info.txt files with the ones generated by the build system

Status: RESOLVED FIXED

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

Description

[[e-mail] (:bhearsum)]

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

[(not currently active) Ted Mielczarek]

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.

Comment 2

[[e-mail] (:bhearsum)]

Mass move of bugs to Release Automation component.

Comment 3

[John Ford [:jhford] CET/CEST Berlin Time]

Ben, do you know if we still want this?

Comment 4

[[e-mail] (:bhearsum)]

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

[John Ford [:jhford] CET/CEST Berlin Time]

putting back in the pool

Comment 7

[[e-mail] (:bhearsum)]

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.

Comment 8

[Nick Thomas [:nthomas] (UTC+12)]

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

[Rail Aliiev [:rail]]

I believe this is fixed and we use info.txt files generated by the build system