Open Bug 1294831 Opened 4 years ago Updated 2 years ago

Provide a static link to latest unbranded CI build


(Release Engineering :: General, defect)

Not set


(Not tracked)


(Reporter: bill, Unassigned)



(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce:

For most Firefox release channels, a static link is made available which provides the latest release for that channel.



For the unbranded release, however, I can only find a link by visiting and clicking on the link under "Latest Release".  This will change upon every new release made.  A predictable static link makes it much easier to script tests with the latest unbranded release.

Actual results:

No static link is available for the latest unbranded release.

Expected results:

Please make available a static link for the latest unbranded release.
This is interfering with our CI process for the HTTPS Everywhere extension.  Since Firefox Stable (as of v. 48) no longer allows you to override extension signing, we're forced to test on the unbranded release channel.

Severity: normal → major
QA Whiteboard: [bugday-20160815]
Component: Untriaged → Releases
Product: Firefox → Release Engineering
QA Contact: rail
Component: Releases → Release Automation
These builds are CI-only, we don't "release" them similar to other builds. Morphing the title.

We can probably point to and friends.
No longer blocks: release-promotion
Component: Release Automation → General Automation
Ever confirmed: true
QA Contact: rail → catlee
Summary: Provide a static link to latest unbranded release → Provide a static link to latest unbranded CI build
As a possible work around you can use the attached example of how to generate links to the latest add-on-devel builds. I hope it helps.
I don't see any documentation on what the `add-on-devel` build actually consists of:

Is this intended to maintain version parity with Firefox Stable, as the `unbranded` release does?
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.