Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upDeploy servo-gecko-try #619
Comments
|
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. |
from servo/saltfs#619
from servo/saltfs#619
|
@Manishearth does the |
|
The username exists for commit authoring. The |
|
initial work at #700 which will probably break and need some fixups. |
|
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.) |
|
VCS sync is no longer. |
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:The config file should point to all the clones.
hostshould probably be 127.0.0.1 if this service will be talked to by homu (and not open to the web).cc @edunham