Closed Bug 1861749 Opened 4 months ago Closed 3 months ago

nightly builds on try are not available through bouncer


(Release Engineering :: Release Automation: Uploading, enhancement)



(firefox122 fixed)

Tracking Status
firefox122 --- fixed


(Reporter: bhearsum, Assigned: bhearsum)



(1 file)

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, 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 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

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

For more information, please visit BugBot documentation.

Flags: needinfo?(hneiva)
Type: defect → enhancement
Severity: -- → N/A
Flags: needinfo?(hneiva)
Attachment #9361055 - Attachment description: Bug 1861749: nightly builds on try are not available through bouncer r?#releng-reviewers! → Bug 1861749: allow bouncer-locations to run on try r?jcristau!
Pushed by
allow bouncer-locations to run on try r=releng-reviewers,taskgraph-reviewers,jcristau
Closed: 3 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.