30 We attempt to limit persistent state to this directory. Even when |
30 We attempt to limit persistent state to this directory. Even when |
31 performing tasks that may have side-effects, we try to limit those |
31 performing tasks that may have side-effects, we try to limit those |
32 side-effects so they don't impact the local system. e.g. when we SSH |
32 side-effects so they don't impact the local system. e.g. when we SSH |
33 into a remote machine, we create a temporary directory for the SSH |
33 into a remote machine, we create a temporary directory for the SSH |
34 config so the user's known hosts file isn't updated. |
34 config so the user's known hosts file isn't updated. |
|
35 |
|
36 Try Server |
|
37 ========== |
|
38 |
|
39 There exists a *Try Server* which allows automation to run against |
|
40 an arbitrary Mercurial changeset and displays results via the web. |
|
41 |
|
42 .. note:: |
|
43 |
|
44 The *Try Server* is still experimental infrastructure. |
|
45 |
|
46 To use the *Try Server*:: |
|
47 |
|
48 $ ./automation.py try |
|
49 |
|
50 With a custom AWS profile:: |
|
51 |
|
52 $ AWS_PROFILE=hg contrib/automation/automation.py try |
|
53 |
|
54 By default, the ``.`` revision is submitted. **Any uncommitted changes |
|
55 are not submitted.** |
|
56 |
|
57 To switch which revision is used:: |
|
58 |
|
59 $ ./automation.py try -r abcdef |
|
60 |
|
61 Access to the *Try Server* requires access to a special AWS account. |
|
62 This account is currently run by Gregory Szorc. Here is the procedure |
|
63 for accessing the *Try Server*: |
|
64 |
|
65 1. Email Gregory Szorc at gregory.szorc@gmail.com and request a |
|
66 username. This username will be stored in the public domain. |
|
67 2. Wait for an email reply containing your temporary AWS credentials. |
|
68 3. Log in at https://gregoryszorc-hg.signin.aws.amazon.com/console |
|
69 and set a new, secure password. |
|
70 4. Go to https://console.aws.amazon.com/iam/home?region=us-west-2#/security_credentials |
|
71 5. Under ``Access keys for CLI, SDK, & API access``, click the |
|
72 ``Create access key`` button. |
|
73 6. See the ``AWS Integration`` section for instructions on |
|
74 configuring your local client to use the generated credentials. |
35 |
75 |
36 AWS Integration |
76 AWS Integration |
37 =============== |
77 =============== |
38 |
78 |
39 Various automation tasks integrate with AWS to provide access to |
79 Various automation tasks integrate with AWS to provide access to |