Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.

travis-ci.txt 2.0KB

il y a 6 ans
  1. Support for using travis-ci has been added in order to automate pull-testing.
  2. See https://travis-ci.org/ for more info
  3. This procedure is different than the pull-tester that came before it in a few
  4. ways.
  5. There is nothing to administer. This is a major feature as it means
  6. that builds have no local state. Because there is no ability to login to the
  7. builders to install packages (tools, dependencies, etc), the entire build
  8. procedure must instead be controlled by a declarative script (.travis.yml).
  9. This script declares each build configuration, creates virtual machines as
  10. necessary, builds, then discards the virtual machines.
  11. A build matrix is constructed to test a wide range of configurations, rather
  12. than a single pass/fail. This helps to catch build failures and logic errors
  13. that present on platforms other than the ones the author has tested. This
  14. matrix is defined in the build script and can be changed at any time.
  15. All builders use the dependency-generator in the depends dir, rather than
  16. using apt-get to install build dependencies. This guarantees that the tester
  17. is using the same versions as Gitian, so the build results are nearly identical
  18. to what would be found in a final release. However, this also means that builds
  19. will fail if new dependencies are introduced without being added to the
  20. dependency generator.
  21. In order to avoid rebuilding all dependencies for each build, the binaries are
  22. cached and re-used when possible. Changes in the dependency-generator will
  23. trigger cache-invalidation and rebuilds as necessary.
  24. These caches can be manually removed if necessary. This is one of the the very few
  25. manual operations that is possible with Travis, and it can be done by the
  26. Bitcoin Core committer via the Travis web interface.
  27. In some cases, secure strings may be needed for hiding sensitive info such as
  28. private keys or URLs. The travis client may be used to create these strings:
  29. http://docs.travis-ci.com/user/encryption-keys/
  30. For the details of the build descriptor, see the official docs:
  31. http://docs.travis-ci.com/user/build-configuration/