Closed Bug 1385558 Opened 7 years ago Closed 7 years ago

Tinderbox builds isn't being updated

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mp3geek, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170726043022

Steps to reproduce:

Often manually download the latest Firefox builds from https://ftp.mozilla.org/pub/firefox/tinderbox-builds/mozilla-central-win64-pgo/




Actual results:

No updates since 26-Jul-2017 13:34  Also applicable for 32bit builds.


Expected results:

Would like the return of tinderbox builds
Component: Untriaged → General Automation
Product: Firefox → Release Engineering
QA Contact: catlee
Version: 56 Branch → ---
Not to push, but can we get a fix for the regular tinderbox builds?
Any update on this?
Plus unbranded builds are missing

https://queue.taskcluster.net/v1/task/PQysjCErReaYKGFbQxJQDw/artifacts/public/build/

and linux x86 unbranded builds too.

Both of these are important for extension testing and private testing (on stable n beta code)
(In reply to mdew from comment #0)
> Often manually download the latest Firefox builds from
> https://ftp.mozilla.org/pub/firefox/tinderbox-builds/mozilla-central-win64-
> pgo/

After migrating to Taskcluster, tinderbox-builds is no longer being updated with per-checkin builds.

The proper place to fetch per-checkin builds is from the Taskcluster index. e.g. https://tools.taskcluster.net/index/artifacts/gecko.v2.mozilla-central.latest.firefox/win64-pgo

(In reply to hulmelo from comment #3)
> Plus unbranded builds are missing
> 
> https://queue.taskcluster.net/v1/task/PQysjCErReaYKGFbQxJQDw/artifacts/
> public/build/
> 
> and linux x86 unbranded builds too.
> 
> Both of these are important for extension testing and private testing (on
> stable n beta code)

This is unrelated. Please see bugs 1391283 and 1393071.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Shouldn't this technically be marked "WONTFIX"?
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.