1294831 - Provide a static link to latest unbranded CI build

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[William Budington]

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.

Examples:

Stable: https://download.mozilla.org/?product=firefox-latest&os=linux64&lang=en_US
Dev: https://download.mozilla.org/?product=firefox-aurora-latest-ssl&os=linux64&lang=en-US
ESR: https://download.mozilla.org/?product=firefox-esr-latest&os=linux64&lang=en_US

For the unbranded release, however, I can only find a link by visiting https://wiki.mozilla.org/Add-ons/Extension_Signing 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.

Comment 1

[William Budington]

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.

See: https://github.com/EFForg/https-everywhere-docker-base/issues/1

Comment 2

[Rail Aliiev [:rail]]

These builds are CI-only, we don't "release" them similar to other builds. Morphing the title.

We can probably point to https://tools.taskcluster.net/index/#gecko.v2.mozilla-release.latest.firefox/gecko.v2.mozilla-release.latest.firefox.win64-add-on-devel and friends.

Comment 3

[Rail Aliiev [:rail]]

Attachment: get_latest_addon_devel_build.py

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.

Comment 4

[William Budington]

I don't see any documentation on what the `add-on-devel` build actually consists of:

https://encrypted.google.com/search?hl=en&q=add-on-devel#hl=en&q=add-on-devel+firefox

Is this intended to maintain version parity with Firefox Stable, as the `unbranded` release does?

Comment 5

[Aki Sasaki (not active)]

+1, the add-on-devel builds are there for developers to be able to test against them with unsigned or test-signed add-ons.

Each appears to have an index associated, e.g. linux64-add-on-devel, which means a link like target.tar.bz2 will work until we change artifact compression formats or the like.