1167497 - Create dynamic redirect URL for latest EME-disabled build

Status: RESOLVED WONTFIX

(Release Engineering :: Release Automation, defect, P1)

Description

[Lawrence Mandel [:lmandel] (use needinfo)]

As of Firefox 38.0 we are now shipping a build that has EME disabled. At this point the primary link for this build is in a Mozilla blog post. 

https://blog.mozilla.org/blog/2015/05/12/update-on-digital-rights-management-and-firefox/

This post was pointing at 38.0 and needed to be updated when 38.0.1 was released. Rather than continue to update the link in the post (as we want to direct people to the latest release build) I'd like to request that we create a URL that redirects to the latest EME-disabled release build like we currently have for Dev Edition. https://download.mozilla.org/?product=firefox-aurora-latest-ssl&os=osx&lang=en-US. To keep it simple, we can just point the URL at the directory rather than trying to determine the correct platform to link directly to the binary.

Comment 1

[Rail Aliiev [:rail]]

We may want to publish the build to the releases directory as well.

Comment 2

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

We get /pub/mozilla.org/firefox/releases/<version>/win32-EME-free/ from bug 1164094, in the same style as we used to use for EUBallot. This bug boils down to adding a bouncer product & one location for each release build, and updating an alias in post-release. See bug 1112966 for patches to reverse and morph.

Once we have that it doesn't seem like that much more work to create an all.html to point the blog post and release notes to.

Comment 3

[Rail Aliiev [:rail]]

Should be as easy as adding something similar to https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/releases/bouncer_firefox_release.py#50-93

Comment 4

[Simon Fraser [:sfraser] ⌚️GMT]

Attachment: Proposed EME-free config

Similar to this attachment? Should it be a new product in bouncer_firefox_release.py?

Comment 5

[Rail Aliiev [:rail]]

Comment on attachment 8796203 [details]
Proposed EME-free config

(In reply to Simon Fraser [:sfraser] from comment #4)
> Created attachment 8796203 [details]
> Proposed EME-free config
> 
> Similar to this attachment? Should it be a new product in
> bouncer_firefox_release.py?

Yes.

Something to consider:

* you may want to add an alias, something like "Firefox-EME-free-latest", so we can use this on the website. There are examples in the same config file. If you add an alias, check_uptake would be required, otherwise I'd say set it to False, so we don't hit the same issue as in bug 1300060.

* "add-locales" uses in-tree shipped-locaes file with a list of locales added to bouncer, which may differ from https://github.com/mozilla-partners/mozilla-EME-free/blob/master/desktop/mozilla-EME-free/repack.cfg#L6 (they may be out of sync, see bug 1254939). I don't recall the logic used in bouncer for uptake checks, but it may be using the list of locales. If they are out of sync, you may never get enough uptake. It'd be safer to set it to False, so this way bouncer uses the hard coded locale.

Comment 6

[Mihai Tabara [:mtabara]⌚️GMT]

I think this bug outlived its usefulness. Please reopen if I'm wrong.