equal
deleted
inserted
replaced
179 |
179 |
180 Various dependencies to run the Mercurial test harness are also required. |
180 Various dependencies to run the Mercurial test harness are also required. |
181 Documenting them is beyond the scope of this document. Various tests |
181 Documenting them is beyond the scope of this document. Various tests |
182 also require other optional dependencies and missing dependencies will |
182 also require other optional dependencies and missing dependencies will |
183 be printed by the test runner when a test is skipped. |
183 be printed by the test runner when a test is skipped. |
|
184 |
|
185 Releasing Windows Artifacts |
|
186 =========================== |
|
187 |
|
188 The `automation.py` script can be used to automate the release of Windows |
|
189 artifacts:: |
|
190 |
|
191 $ ./automation.py build-all-windows-packages --revision 5.1.1 |
|
192 $ ./automation.py publish-windows-artifacts 5.1.1 |
|
193 |
|
194 The first command will launch an EC2 instance to build all Windows packages |
|
195 and copy them into the `dist` directory relative to the repository root. The |
|
196 second command will then attempt to upload these files to PyPI (via `twine`) |
|
197 and to `mercurial-scm.org` (via SSH). |
|
198 |
|
199 Uploading to PyPI requires a PyPI account with write access to the `Mercurial` |
|
200 package. You can skip PyPI uploading by passing `--no-pypi`. |
|
201 |
|
202 Uploading to `mercurial-scm.org` requires an SSH account on that server |
|
203 with `windows` group membership and for the SSH key for that account to be the |
|
204 default SSH key (e.g. `~/.ssh/id_rsa`) or in a running SSH agent. You can |
|
205 skip `mercurial-scm.org` uploading by passing `--no-mercurial-scm-org`. |