paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-10-31 12:03:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

tools: Rename tools/travis directory to tools/ci.

Browse Source
This commit is contained in:
Vishnu Ks
2018-12-10 12:35:16 +05:30
committed by Tim Abbott
parent a1d99adce7
commit a86faecff5
16 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/testing/travis.md
View File

@@ -29,14 +29,14 @@ The specific test suites we have are listed in the `matrix` section,
which has a matrix of Python versions and test suites (`$TEST_SUITE`).
We've configured it to use a few helper scripts for each job:
* `tools/travis/setup-$TEST_SUITE`: The script that sets up the test
* `tools/ci/setup-$TEST_SUITE`: The script that sets up the test
environment for that suite (E.g., installing dependencies).
* For the backend and frontend suites, this is a thin wrapper around
`tools/provision`, aka the development environment provision script.
* For the production suite, this is a more complicated process
because of all the packages Travis installs. See the comments in
`tools/travis/setup-production` for details.
* `tools/travis/$TEST_SUITE`: The script that runs the actual test
`tools/ci/setup-production` for details.
* `tools/ci/$TEST_SUITE`: The script that runs the actual test
suite.
The main purpose of the distinction between the two is that if the
@@ -111,6 +111,6 @@ build workers (e.g. several copies of Postgres, Java, MySQL, etc.).
In order to make Zulip's tests performance reasonably well, we
uninstall (or mark with `apt-mark hold`) many of these dependencies
that are irrelevant to Zulip in
[`tools/travis/setup-production`][setup-production].
[`tools/ci/setup-production`][setup-production].
[setup-production]: https://github.com/zulip/zulip/blob/master/tools/travis/setup-production
[setup-production]: https://github.com/zulip/zulip/blob/master/tools/ci/setup-production