aboutsummaryrefslogtreecommitdiff
path: root/ci
diff options
context:
space:
mode:
author721217.xyz <*~=`'#}+{/-|&$^_@721217.xyz>2023-02-10 17:08:05 +0100
committer721217.xyz <*~=`'#}+{/-|&$^_@721217.xyz>2023-02-10 17:05:39 +0100
commitfa8e92c022057adcb8b98647bde626ed9c054df2 (patch)
tree74ec5bde42de1819efe11317ac44c537770fc565 /ci
parent5fffff54e9fcf154c722dc421025a567fa0c5c97 (diff)
downloadbitcoin-fa8e92c022057adcb8b98647bde626ed9c054df2.tar.xz
doc: Update ci docs
Diffstat (limited to 'ci')
-rw-r--r--ci/README.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/ci/README.md b/ci/README.md
index 3c5f04c39e..de798607df 100644
--- a/ci/README.md
+++ b/ci/README.md
@@ -8,8 +8,7 @@ Be aware that the tests will be built and run in-place, so please run at your ow
If the repository is not a fresh git clone, you might have to clean files from previous builds or test runs first.
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, previous release binaries, or ccache, are mounted as read-write into the docker container. While it should be fine to run
+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.