Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy servo-gecko-try #619

Closed
Manishearth opened this issue Mar 14, 2017 · 6 comments
Closed

Deploy servo-gecko-try #619

Manishearth opened this issue Mar 14, 2017 · 6 comments
Assignees

Comments

@Manishearth
Copy link
Member

@Manishearth Manishearth commented Mar 14, 2017

https://github.com/Manishearth/servo-gecko-try

Needs a similar setup as the intermittents tracker as far as flask is concerned

The setup is a bit trickier. You need a servo clone, and hg clones of https://hg.mozilla.org/mozilla-central/ and https://hg.mozilla.org/integration/autoland/ somewhere (preferably as child dirs). Additionally, you need a clone of http://hg.mozilla.org/hgcustom/version-control-tools/ somewhere, probably in ~/.mozbuild/version-control-tools. We need a public/private keypair that's tied to L1 managed by salt somewhere too (bug filed for getting the key and username: https://bugzilla.mozilla.org/show_bug.cgi?id=1347259).

Either the global hgrc (~/.hgrc) or each of the local hgrcs (.hg/hgrc) in the two firefox clones need to have these lines in them:

[extensions]
mq =
push-to-try = ~/.mozbuild/version-control-tools/hgext/push-to-try

[ui]
username = Bors <whatever@whatever.com>
ssh = ssh -l 'borsusername@bors.com' -i '/path/to/key.pub'

The config file should point to all the clones. host should probably be 127.0.0.1 if this service will be talked to by homu (and not open to the web).

cc @edunham

@larsbergstrom
Copy link
Contributor

@larsbergstrom larsbergstrom commented Apr 29, 2017

I suspect that we would like this to live on a server that is not the one with Homu on it, as that machine will be pretty locked-down, relative to the rest of Servo's infrastructure.

@edunham edunham self-assigned this May 31, 2017
edunham added a commit to edunham/servo-gecko-try that referenced this issue Jun 5, 2017
edunham added a commit to edunham/servo-gecko-try that referenced this issue Jun 5, 2017
@edunham
Copy link
Contributor

@edunham edunham commented Jun 5, 2017

@Manishearth does the [ui] section of that .hgrc ever do anything? Specifically, should we point it at some usually-ignored @servo.org email in case anything we care about would get annoyed at the mail bouncing?

@Manishearth
Copy link
Member Author

@Manishearth Manishearth commented Jun 5, 2017

The username exists for commit authoring. The ssh is there for the right pubkey and username to be used.

@edunham
Copy link
Contributor

@edunham edunham commented Jun 14, 2017

initial work at #700 which will probably break and need some fixups.

@aneeshusa
Copy link
Member

@aneeshusa aneeshusa commented Oct 4, 2017

See also Manishearth/servo-gecko-try#3 for some things I'd like to see done before putting this into production. Some of the upcoming changes should make this easier to deploy on the Salt side (app does all repo juggling by itself, publishing to PyPi instead of using git dependency, etc.)

@edunham
Copy link
Contributor

@edunham edunham commented May 3, 2018

VCS sync is no longer.

@edunham edunham closed this May 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.