diff options
| author | Sjors Provoost <sjors@sprovoost.nl> | 2019-01-05 20:20:42 +0100 |
|---|---|---|
| committer | Sjors Provoost <sjors@sprovoost.nl> | 2020-02-11 21:46:21 +0100 |
| commit | 8b1460dbd1b732f06d4cebe1fa6844286c7a0056 (patch) | |
| tree | 5d2fba3358e417a1caaed230d79d51a635856e7c /ci/README.md | |
| parent | ae379cf7d12943fc192d58176673bcfe7d53da53 (diff) | |
[tests] check v0.17.1 and v0.18.1 backwards compatibility
Diffstat (limited to 'ci/README.md')
| -rw-r--r-- | ci/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ci/README.md b/ci/README.md index 880e49b459..d2ea255b4b 100644 --- a/ci/README.md +++ b/ci/README.md @@ -13,7 +13,7 @@ If the repository is not a fresh git clone, you might have to clean files from p The ci needs to perform various sysadmin tasks such as installing packages or writing to the user's home directory. While most of the actions are done inside a docker container, this is not possible for all. Thus, cache directories, -such as the depends cache or ccache, are mounted as read-write into the docker container. While it should be fine to run +such as the depends cache, previous release binaries, or ccache, are mounted as read-write into the docker container. While it should be fine to run the ci system locally on you development box, the ci scripts can generally be assumed to have received less review and testing compared to other parts of the codebase. If you want to keep the work tree clean, you might want to run the ci system in a virtual machine with a Linux operating system of your choice. |