aboutsummaryrefslogtreecommitdiff
path: root/.travis.yml
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2020-06-06 21:52:46 -0400
committerMarcoFalke <falke.marco@gmail.com>2020-06-19 10:44:00 -0400
commitfad67208914e5a74b64f4cc018368902ef3a2e9b (patch)
treec0658ce966b55d9a25ae380b619f1f85d1e5ef97 /.travis.yml
parentfa880773b425fcd292ed7669d237ee3151a15bc6 (diff)
doc: move doc to ci readme
Diffstat (limited to '.travis.yml')
-rw-r--r--.travis.yml16
1 files changed, 1 insertions, 15 deletions
diff --git a/.travis.yml b/.travis.yml
index 864405dfc9..5b71619a45 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,18 +1,4 @@
-# The test build matrix (stage: test) is constructed to test a wide range of
-# configurations, rather than a single pass/fail. This helps to catch build
-# failures and logic errors that present on platforms other than the ones the
-# author has tested.
-#
-# Some builders use the dependency-generator in `./depends`, rather than using
-# apt-get to install build dependencies. This guarantees that the tester is
-# using the same versions as Gitian, so the build results are nearly identical
-# to what would be found in a final release.
-#
-# In order to avoid rebuilding all dependencies for each build, the binaries
-# are cached and re-used when possible. Changes in the dependency-generator
-# will trigger cache-invalidation and rebuilds as necessary.
-#
-# These caches can be manually removed if necessary. This is one of the very
+# Travis caches can be manually removed if necessary. This is one of the very
# few manual operations that is possible with Travis, and it can be done by a
# Bitcoin Core GitHub member via the Travis web interface [0].
#