1861749 - nightly builds on try are not available through bouncer

Status: RESOLVED FIXED

(Release Engineering :: Release Automation, enhancement)

Description

[[e-mail] (:bhearsum)]

I think there's two issues here:

1. bouncer-locations refuses to run on Try at all because of its run-on-releases configuration. (try pushes can never have a release_type set other than for staging releases AFAICT)
2. On try, we upload nightly builds to http://ftp.stage.mozaws.net/pub/firefox/nightly/latest-try/, I believe due to the beetmover manifest pointing at latest-${branch}. However, even once we get Bouncer submission going, it would submit entries that point at latest-mozilla-central. (I'm double checking this in https://treeherder.mozilla.org/jobs?repo=try&revision=d17f5cb56402e92e72a090878dbfc50dceac8c56...but I don't see anything in bouncerscript that seems as if it could push to latest-try).

In order to fully close the testing loop for bug 1819405, we ought to make Nightlies on try downloadable through Bouncer & Bedrock. I suggest that we:

• Find a way to allow bouncer-locations to run
• Publish "nightly" builds on try to latest-mozilla-central (we already publish candidates/releases to directories named the same as production -- I think latest-try is an historical artifact dating back to when try builds were uploaded to archive.mozilla.org)

Comment 1

[[e-mail] (:bhearsum)]

Attachment: Bug 1861749: allow bouncer-locations to run on try r?jcristau!

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:hneiva, could you have a look please?

For more information, please visit BugBot documentation.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/cb2d73366c34
allow bouncer-locations to run on try r=releng-reviewers,taskgraph-reviewers,jcristau

Comment 4

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/cb2d73366c34