mirror of
https://github.com/dashpay/dash.git
synced 2024-12-27 04:52:59 +01:00
207b1c5877
c456145b2c65f580683df03bf10cd39000cf24d5 [test] add 0.19 backwards compatibility tests (Sjors Provoost) b769cd142deda74fe46e231cc7b687a86514f2f1 [test] add v0.17.1 wallet upgrade test (Sjors Provoost) 9d9390dab716f07057c94e8e21f3c7dd06192f35 [tests] add wallet backwards compatility tests (Sjors Provoost) c7ca6308968b29a0e0edc485cd06e68e5edb7c7d [scripts] support release candidates of earlier releases (Sjors Provoost) 8b1460dbd1b732f06d4cebe1fa6844286c7a0056 [tests] check v0.17.1 and v0.18.1 backwards compatibility (Sjors Provoost) ae379cf7d12943fc192d58176673bcfe7d53da53 [scripts] build earlier releases (Sjors Provoost) Pull request description: This PR adds binaries for 0.17, 0.18 and 0.19 to Travis and runs a basic block propagation test. Includes test for upgrading v0.17.1 wallets and opening master wallets with older versions. Usage: ```sh contrib/devtools/previous_release.sh -f -b v0.19.0.1 v0.18.1 v0.17.1 test/functional/backwards_compatibility.py ``` Travis caches these earlier releases, so it should be able to run these tests with little performance impact. Additional scenarios where it might be useful to run tests against earlier releases: * creating a wallet with #11403's segwit implementation, copying it to an older node and making sure the user didn't lose any funds (although this PR doesn't support `v0.15.1`) * future consensus changes * P2P changes (e.g. to make sure we don't accidentally ban old nodes) ACKs for top commit: MarcoFalke: ACK c456145b2c65f580683df03bf10cd39000cf24d5 🔨 Tree-SHA512: 360bd870603f95b14dc0cd629532cc147344f632b808617c18e1b585dfb1f082b401e5d493a48196b719e0aeaee533ae0a773dfc9f217f704aae898576c19232
39 lines
1.7 KiB
Markdown
39 lines
1.7 KiB
Markdown
## ci scripts
|
|
|
|
This directory contains scripts for each build step in each build stage.
|
|
|
|
Currently three stages `lint`, `extended_lint` and `test` are defined. Each stage has its own lifecycle, similar to the
|
|
[Travis CI lifecycle](https://docs.travis-ci.com/user/job-lifecycle#the-job-lifecycle). Every script in here is named
|
|
and numbered according to which stage and lifecycle step it belongs to.
|
|
|
|
### Running a stage locally
|
|
|
|
Be aware that the tests will be built and run in-place, so please run at your own risk.
|
|
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
|
|
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.
|
|
|
|
To allow for a wide range of tested environments, but also ensure reproducibility to some extent, the test stage
|
|
requires `docker` to be installed. To install all requirements on Ubuntu, run
|
|
|
|
```
|
|
sudo apt install docker.io bash
|
|
```
|
|
|
|
To run the default test stage,
|
|
|
|
```
|
|
./ci/test_run_all.sh
|
|
```
|
|
|
|
To run the test stage with a specific configuration,
|
|
|
|
```
|
|
FILE_ENV="./ci/test/00_setup_env_arm.sh" ./ci/test_run_all.sh
|
|
```
|