Closed Bug 1254540 Opened 9 years ago Closed 9 years ago

Use http://balrog/api as BALROG_API_ROOT for balrogVPNProxy enabled funsize jobs

Categories

(Release Engineering :: Release Automation: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

Attachments

(3 files)

https://tools.taskcluster.net/task-inspector/#-vamdM5qSAejDjX4jDaUTg/ failed to submit to https://aus4-admin.mozilla.org/api because we should use http://balrog/api which is special. The balrogVpnProxy feature in docker-worker sets up a proxy docker instance which uses VPN to the actual server, but we have to use http://balrog/api in our calls.
Attached file PR for releasetasks
More patches coming
Attachment #8727852 - Flags: review?(kmoir)
Attachment #8727854 - Flags: review?(kmoir) → review+
Attachment #8727855 - Flags: review?(kmoir) → review+
Attachment #8727852 - Flags: review?(kmoir) → review+
Attachment #8727852 - Flags: checked-in+
Comment on attachment 8727855 [details] MozReview Request: Bug 1254540 - Use separate Balrog API for production r=kmoir https://hg.mozilla.org/build/tools/rev/6d16b679118d
Attachment #8727855 - Flags: checked-in+
Comment on attachment 8727854 [details] MozReview Request: Bug 1254540 - Use separate Balrog API for production r=kmoir https://hg.mozilla.org/build/buildbot-configs/rev/ff40254797eb
Attachment #8727854 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: