Closed Bug 780902 Opened 8 years ago Closed 8 years ago

serve buildjson from https://secure.pub.build.mozilla.org, too

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set
normal

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: server-ops-releng → dustin
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: 8 years ago
Resolution: --- → FIXED
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)
Blocks: 686263
Hm, we could certainly adjust that.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Fixed on both clusters.
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
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.