akovalenko/lnd.xprv
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
ba3c65bfd6
lnd.xprv/.travis.yml

75 lines
2.1 KiB
YAML
Raw Normal View History

Initial travis yml file
2016-06-09 01:12:13 +03:00
language: go
travis: enable caches This commit sets the GOCACHE environment variable, and enables caching on travis. GOCACHE will tell the compiler (only go 1.10+) where to store build and test artifacts. Caching this directory will significantly speed up succeeding builds and test runs. We also cache vendor/ as this will speed up the call to 'make dep'. A few dependencies in the GOPATH are cached, as calls to 'go get' for these will be sped up. Note that we don't cache the lnd directory, as it will conflict with the changes in the PR being built.
2018-10-11 11:31:05 +03:00
cache:
directories:
build: bump travis bitcoind version to v0.19.1
2020-03-13 21:03:00 +03:00
- ~/bitcoin/bitcoin-0.19.1/bin
make+travis: verify compiled protos on travis
2019-05-23 01:24:40 +03:00
- $DOWNLOAD_CACHE
travis: enable caches This commit sets the GOCACHE environment variable, and enables caching on travis. GOCACHE will tell the compiler (only go 1.10+) where to store build and test artifacts. Caching this directory will significantly speed up succeeding builds and test runs. We also cache vendor/ as this will speed up the call to 'make dep'. A few dependencies in the GOPATH are cached, as calls to 'go get' for these will be sped up. Note that we don't cache the lnd directory, as it will conflict with the changes in the PR being built.
2018-10-11 11:31:05 +03:00
- $GOCACHE
travis: force go modules support in $GOPATH, cache modules directory
2018-11-29 04:18:21 +03:00
- $GOPATH/pkg/mod
travis: enable caches This commit sets the GOCACHE environment variable, and enables caching on travis. GOCACHE will tell the compiler (only go 1.10+) where to store build and test artifacts. Caching this directory will significantly speed up succeeding builds and test runs. We also cache vendor/ as this will speed up the call to 'make dep'. A few dependencies in the GOPATH are cached, as calls to 'go get' for these will be sped up. Note that we don't cache the lnd directory, as it will conflict with the changes in the PR being built.
2018-10-11 11:31:05 +03:00
- $GOPATH/src/github.com/btcsuite
- $GOPATH/src/github.com/golang
make+travis: verify compiled protos on travis
2019-05-23 01:24:40 +03:00
- $GOPATH/src/github.com/grpc-ecosystem
travis: enable caches This commit sets the GOCACHE environment variable, and enables caching on travis. GOCACHE will tell the compiler (only go 1.10+) where to store build and test artifacts. Caching this directory will significantly speed up succeeding builds and test runs. We also cache vendor/ as this will speed up the call to 'make dep'. A few dependencies in the GOPATH are cached, as calls to 'go get' for these will be sped up. Note that we don't cache the lnd directory, as it will conflict with the changes in the PR being built.
2018-10-11 11:31:05 +03:00
- $GOPATH/src/gopkg.in/alecthomas
make+travis: verify compiled protos on travis
2019-05-23 01:24:40 +03:00
- $GOPATH/src/google.golang.org
travis: enable caches This commit sets the GOCACHE environment variable, and enables caching on travis. GOCACHE will tell the compiler (only go 1.10+) where to store build and test artifacts. Caching this directory will significantly speed up succeeding builds and test runs. We also cache vendor/ as this will speed up the call to 'make dep'. A few dependencies in the GOPATH are cached, as calls to 'go get' for these will be sped up. Note that we don't cache the lnd directory, as it will conflict with the changes in the PR being built.
2018-10-11 11:31:05 +03:00
travis: remove git clone depth limitation to fix linter By default, Travis-CI does `git clone --depth=50` which limits the repo to the last 50 commits. Because we do linting against an old commit, it cannot be found any more. We remove the limit completely to not run into this problem again.
2020-02-20 22:18:43 +03:00
# Remove Travis' default flag --depth=50 from the git clone command to make sure
# we have the whole git history, including the commit we lint against.
git:
depth: false
travis: split up into 3 builds This commit distributes the CI tests into 3 independend builds, by splitting the integration test run and unit test coverage. To better handle the extra cases, we define a build matrix with the three build types (RACE and LINT, ITEST, COVER).
2018-11-16 13:08:16 +03:00
go:
build: update travis to build against go 1.14
2020-02-26 21:33:53 +03:00
- "1.14.x"
travis: split up into 3 builds This commit distributes the CI tests into 3 independend builds, by splitting the integration test run and unit test coverage. To better handle the extra cases, we define a build matrix with the three build types (RACE and LINT, ITEST, COVER).
2018-11-16 13:08:16 +03:00
env:
travis: enable caches This commit sets the GOCACHE environment variable, and enables caching on travis. GOCACHE will tell the compiler (only go 1.10+) where to store build and test artifacts. Caching this directory will significantly speed up succeeding builds and test runs. We also cache vendor/ as this will speed up the call to 'make dep'. A few dependencies in the GOPATH are cached, as calls to 'go get' for these will be sped up. Note that we don't cache the lnd directory, as it will conflict with the changes in the PR being built.
2018-10-11 11:31:05 +03:00
global:
- GOCACHE=$HOME/.go-build
make+travis: verify compiled protos on travis
2019-05-23 01:24:40 +03:00
- DOWNLOAD_CACHE=$HOME/download_cache
travis: remove unnecessary export PATH This is done automatically by travis as part of the go setup.
2018-10-11 11:31:05 +03:00
Travis: fix sudo required and apt-get update command
2018-01-17 19:07:31 +03:00
sudo: required
travis: remove unnecessary export PATH This is done automatically by travis as part of the go setup.
2018-10-11 11:31:05 +03:00
travis: staged travis builds This PR introduces staging to our travis pipeline. Currently all instances perform: - compilation of lnd - linting - compilation and installation of btcd binaries - installation of bitcoind binaries In total this adds about 3 minutes to each of our 5 instances, resulting in roughly 12 minutes of redundant execution time. Additionally, if if a build fails to compile or lint we detect this 5 separate times, consuming precious instances from other builds. We alleviate this by adding an initial Build phase, which runs a single instance performing the actions above. This has the benefit of quickly sanity checking the pr before moving on to the more expensive unit or integration test suites, and failing faster for common mistakes. It also warms up the build caches for the Test stage in one fell swoop. For instance, if 5 people push changes at the same time, they can all get immediate feedback regarding compilation or linting issues, and potentially save hours waiting for other people's test to finish or fail before finding out they had a spelling error. This doesn't alleviate all possible issues, e.g. the 5 instances may already be consumed by test suites, but it does make a sizable step towards minimizing time-to-failure in common scenarios.
2019-12-05 06:53:20 +03:00
jobs:
include:
travis: add sanity check stage
2020-07-29 10:50:37 +03:00
- stage: Sanity Check
name: Lint and compile
before_script:
# Install the RPC tools as a before step so Travis collapses the output
# after it's done.
- ./scripts/install_travis_proto.sh
script:
# Step 1: Make sure no diff is produced when compiling with the correct
# version.
- make rpc-check
# Step 2: Make sure the unit tests compile, but don't run them. They run
# in a GitHub Workflow.
- make unit pkg=... case=_NONE_
# Step 3: Lint go code. Limit to 1 worker to reduce memory usage.
- make lint workers=1
github+travis: split CI tasks between Travis and GitHub To free up build in Travis, we decided to run the non-flaky parts of the CI pipeline in GitHub Workflows/Actions only. The integration tests on the other hand are removed from GitHub because individual actions cannot be restarted there which caused us to restart the whole workflow if one test was flaky. This split should give us the best of both worlds: Fast run of small checks, linting and unit tests with an easy overview of what failed in the PR directly. And more free build slots on Travis to do more advanced integration tests on other architectures and/or operating systems. And the option to restart a single flaky integration test on Travis.
2020-07-23 16:06:05 +03:00
- stage: Integration Test
travis: staged travis builds This PR introduces staging to our travis pipeline. Currently all instances perform: - compilation of lnd - linting - compilation and installation of btcd binaries - installation of bitcoind binaries In total this adds about 3 minutes to each of our 5 instances, resulting in roughly 12 minutes of redundant execution time. Additionally, if if a build fails to compile or lint we detect this 5 separate times, consuming precious instances from other builds. We alleviate this by adding an initial Build phase, which runs a single instance performing the actions above. This has the benefit of quickly sanity checking the pr before moving on to the more expensive unit or integration test suites, and failing faster for common mistakes. It also warms up the build caches for the Test stage in one fell swoop. For instance, if 5 people push changes at the same time, they can all get immediate feedback regarding compilation or linting issues, and potentially save hours waiting for other people's test to finish or fail before finding out they had a spelling error. This doesn't alleviate all possible issues, e.g. the 5 instances may already be consumed by test suites, but it does make a sizable step towards minimizing time-to-failure in common scenarios.
2019-12-05 06:53:20 +03:00
name: Btcd Integration
github+travis: split CI tasks between Travis and GitHub To free up build in Travis, we decided to run the non-flaky parts of the CI pipeline in GitHub Workflows/Actions only. The integration tests on the other hand are removed from GitHub because individual actions cannot be restarted there which caused us to restart the whole workflow if one test was flaky. This split should give us the best of both worlds: Fast run of small checks, linting and unit tests with an easy overview of what failed in the PR directly. And more free build slots on Travis to do more advanced integration tests on other architectures and/or operating systems. And the option to restart a single flaky integration test on Travis.
2020-07-23 16:06:05 +03:00
script:
- make itest
- name: Bitcoind Integration
script:
- bash ./scripts/install_bitcoind.sh
- make itest backend=bitcoind
- name: Neutrino Integration
script:
- make itest backend=neutrino
travis: add integration test on ARMv7 (32bit)
2020-07-22 16:40:02 +03:00
- name: Btcd Integration ARM
script:
- GOARM=7 GOARCH=arm GOOS=linux CGO_ENABLED=0 make btcd build-itest
- file lnd-itest
- GOARM=7 GOARCH=arm GOOS=linux CGO_ENABLED=0 make itest-only
arch: arm64
travis: remove unnecessary export PATH This is done automatically by travis as part of the go setup.
2018-10-11 11:31:05 +03:00
test: add upload of integration logs from TravisCI builds This commit adds adds: - Functionality to `gotest.sh` to log the output of `lnd` instances used for integration testing to file. - Uploading of those log files to [termbin.com ](http://www.termbin.com) from TravisCI integration builds. As an example of a build with this enabled, you can look at [this build](https://travis-ci.org/samvrlewis/lnd/builds/286942025), which is a build from my `ci_logging_test` branch. That branch has the same diff as my `ci_logging` branch but with a small inclusion to allow TravisCI builds to work (as I described in [my comment](https://github.com/lightningnetwork/lnd/issues/302#issuecomment-335133834) the other day). If you scroll to the end of the job logs where `RACE=false` you'll see a `after_script` section with an output like this: ``` output0.log uploaded to http://termbin.com/aloqr output1.log uploaded to http://termbin.com/3ggh output2.log uploaded to http://termbin.com/abb9 output3.log uploaded to http://termbin.com/rk9j output4.log uploaded to http://termbin.com/956p output5.log uploaded to http://termbin.com/iwwt ``` Fixes #302.
2017-10-18 01:42:22 +03:00
after_script:
travis: fix log upload regression after itest move
2019-06-05 00:51:25 +03:00
- LOG_FILES=./lntest/itest/*.log
- echo "Uploading to termbin.com..." && find $LOG_FILES | xargs -I{} sh -c "cat {} | nc termbin.com 9999 | xargs -r0 printf '{} uploaded to %s'"
- echo "Uploading to file.io..." && tar -zcvO $LOG_FILES | curl -s -F 'file=@-;filename=logs.tar.gz' https://file.io | xargs -r0 printf 'logs.tar.gz uploaded to %s\n'
Reference in New Issue Copy Permalink