Closed
Bug 780902
Opened 13 years ago
Closed 13 years ago
serve buildjson from https://secure.pub.build.mozilla.org , too
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
http://builddata.pub.build.mozilla.org/buildjson/ is great for TBPL, apparently, but causes mixed content warnings. So let's serve the same data via https, too, at
https://secure.pub.build.mozilla.org/builddata/buildjson
Assignee | ||
Updated•13 years ago
|
Assignee: server-ops-releng → dustin
Assignee | ||
Comment 1•13 years ago
|
||
Up on the old cluster (so you can start using these, philor):
https://secure.pub.build.mozilla.org/builddata/buildjson/
https://secure.pub.build.mozilla.org/builddata/reports/
Assignee | ||
Comment 2•13 years ago
|
||
And it's now working on the new cluster, too, so it will keep working when we switch to that cluster.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 3•13 years ago
|
||
Unfortunately, https://secure.pub.build.mozilla.org/builddata/buildjson/ requires authentication, which isn't going to work out for tbpl (it should still display for people without an LDAP account, and the server-side part doesn't actually have an account of its own to fetch https://secure.pub.build.mozilla.org/builddata/buildjson/builds-4hr.js.gz)
Assignee | ||
Comment 4•13 years ago
|
||
Hm, we could certainly adjust that.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 5•13 years ago
|
||
Fixed on both clusters.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Blocks: b2g-reftest
Updated•12 years ago
|
No longer blocks: b2g-reftest
Updated•12 years ago
|
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•