Closed Bug 1248870 Opened 6 years ago Closed 6 years ago

Set up a temporary balrog instance for build promotion

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

Attachments

(1 file, 1 obsolete file)

The current dev instance is behind VPN and it's not accessible from TC (I have vague memories using it from heroku though). TC's balrogVPNProxy feature is available only for the production balrog instance.

As a workaround we can set up an EC2 instance and run balrog in docker (with https://github.com/mozilla/balrog/pull/52), probably using elastic IP.

It should accept any auth credentials (this is how the dev setup works in docker).
Also need to create date-* rules and aliases
Attached patch balrog.diff (obsolete) — Splinter Review
this is an ubuntu 15.10 instance with `docker-compose up` running in tmux. Since tmux is better than screen, this is a great improvement! :D
Assignee: nobody → rail
Attachment #8720154 - Flags: review?
Added rules and aliases.
Attached patch balrog.diffSplinter Review
better port :) No https though
Attachment #8720154 - Attachment is obsolete: true
Attachment #8720154 - Flags: review?
Attachment #8720158 - Flags: review?
Comment on attachment 8720158 [details] [diff] [review]
balrog.diff

Don't forget to add permissions for whatever username you end up submitting as.

Will you be using any in-house machines for anything that submits to Balrog? If so, can they route to this?
Attachment #8720158 - Flags: review? → review+
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Blocks: 1249680
You need to log in before you can comment on or make changes to this bug.