If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

make tc builds generate firefox.{tar.bz2,zip} rather than target.{tar.bz2,zip} for user-friendliness

NEW
Unassigned

Status

Taskcluster
Task Configuration
5 months ago
5 months ago

People

(Reporter: froydnj, Unassigned)

Tracking

Details

(Reporter)

Description

5 months ago
Earlier today, I asked somebody to do something that required downloading a build from try to examine the packaged contents.  They responded that they had looked for a download link, but couldn't find anything in the artifact list.  That seemed kind of odd, so I took a look at their try push.  I didn't see anything obvious, either, but eventually guessed that "target.tar.bz2" must be the thing that they were probably looking for.  And indeed it was.

I realize that for the release pipeline, the exact package name probably doesn't matter; presumably there's taskcluster metadata associated with it and somesuch.  But for downloading builds off of try, something that contributors do with decent frequency and often ask bug reporters or commenters to do so those folks can test potential fixes, it's yet another hurdle to jump across, particular if the contributor asks but doesn't realize (or remember) that our infrastructure has this odd naming scheme, so there has to be a round trip or more of sorting things out.

My recollection is that we used to generate firefox-FOO.tar.bz2.  I'm ambivalent about the version number in the context, but firefox.tar.bz2 is way better than target.tar.bz2.  Can we change target.tar.bz2 to something more evocative please?
I wouldn't mind changing "target' to "firefox".  I think that should be a fairly straightforward change, and could be tested in try.  I'm not sure what the implications are for the release automation, but a r? could probably suss that out.
Component: General → Task Configuration
You need to log in before you can comment on or make changes to this bug.