lnd.xprv/.travis.yml

language: go
matrix:
  include:
  - go: "1.11.x"
    env: RACE=TRUE USE_LINT=TRUE
  - go: "1.11.x"
    env: RACE=FALSE USE_LINT=TRUE
  - go: "1.10.x"
    env: RACE=TRUE USE_LINT=FALSE
  - go: "1.10.x"
    env: RACE=FALSE USE_LINT=FALSE
sudo: required
install:
  - sudo add-apt-repository -y ppa:bitcoin/bitcoin -y
  - sudo apt-get update -q
  - sudo apt-get install bitcoind -y
  - export PATH=$PATH:$PWD/linux-amd64/
script:
  - export PATH=$PATH:$GOPATH/bin
  - make travis
after_script:
  - echo "Uploading to termbin.com..." && find *.log | xargs -I{} sh -c "cat {} | nc termbin.com 9999 | xargs -r0 printf '{} uploaded to %s'"
  - echo "Uploading to file.io..." && tar -zcvO *.log | curl -s -F 'file=@-;filename=logs.tar.gz' https://file.io | xargs -r0 printf 'logs.tar.gz uploaded to %s\n'
Initial travis yml file 2016-06-09 01:12:13 +03:00			`language: go`
build: update build file to exclude go 1.10 from linting In this commit, we modify our build file to only lint under go 1.11. We do this as there's been a breaking change in gofmt between go 1.10 and go 1.11 that causes files which pass the linter under go 1.10, to fail the linter under go 1.11. In the end, we only really need to lint using one version of go. In order to achieve this, we "unroll" the build matrix to enumerate each version and the environment variables that it should be run with. We then modify the Makefile to only include the lint directive if the particular env variable is set ($(USE_LINT)). With these two changes, we'll now only lint under go 1.11. 2018-10-07 07:59:29 +03:00			`matrix:`
			`include:`
build: bump Go versions, use '.x' to always get latest patch versions 2018-10-31 06:15:42 +03:00			`- go: "1.11.x"`
travis: correctly set RACE=TRUE in build matrix 2018-10-10 12:03:24 +03:00			`env: RACE=TRUE USE_LINT=TRUE`
build: bump Go versions, use '.x' to always get latest patch versions 2018-10-31 06:15:42 +03:00			`- go: "1.11.x"`
build: update build file to exclude go 1.10 from linting In this commit, we modify our build file to only lint under go 1.11. We do this as there's been a breaking change in gofmt between go 1.10 and go 1.11 that causes files which pass the linter under go 1.10, to fail the linter under go 1.11. In the end, we only really need to lint using one version of go. In order to achieve this, we "unroll" the build matrix to enumerate each version and the environment variables that it should be run with. We then modify the Makefile to only include the lint directive if the particular env variable is set ($(USE_LINT)). With these two changes, we'll now only lint under go 1.11. 2018-10-07 07:59:29 +03:00			`env: RACE=FALSE USE_LINT=TRUE`
build: bump Go versions, use '.x' to always get latest patch versions 2018-10-31 06:15:42 +03:00			`- go: "1.10.x"`
build: update build file to exclude go 1.10 from linting In this commit, we modify our build file to only lint under go 1.11. We do this as there's been a breaking change in gofmt between go 1.10 and go 1.11 that causes files which pass the linter under go 1.10, to fail the linter under go 1.11. In the end, we only really need to lint using one version of go. In order to achieve this, we "unroll" the build matrix to enumerate each version and the environment variables that it should be run with. We then modify the Makefile to only include the lint directive if the particular env variable is set ($(USE_LINT)). With these two changes, we'll now only lint under go 1.11. 2018-10-07 07:59:29 +03:00			`env: RACE=TRUE USE_LINT=FALSE`
build: bump Go versions, use '.x' to always get latest patch versions 2018-10-31 06:15:42 +03:00			`- go: "1.10.x"`
build: update build file to exclude go 1.10 from linting In this commit, we modify our build file to only lint under go 1.11. We do this as there's been a breaking change in gofmt between go 1.10 and go 1.11 that causes files which pass the linter under go 1.10, to fail the linter under go 1.11. In the end, we only really need to lint using one version of go. In order to achieve this, we "unroll" the build matrix to enumerate each version and the environment variables that it should be run with. We then modify the Makefile to only include the lint directive if the particular env variable is set ($(USE_LINT)). With these two changes, we'll now only lint under go 1.11. 2018-10-07 07:59:29 +03:00			`env: RACE=FALSE USE_LINT=FALSE`
Travis: fix sudo required and apt-get update command 2018-01-17 19:07:31 +03:00			`sudo: required`
build: update travis CI config This commit updates the previous travis CI config to pin against the two latest golang versions, and perform installation via Glide. Additionally, this should allow lnwallet’s integration tests to build properly as the btcd binary will be available in the build process’ PATH. 2016-07-26 02:39:22 +03:00			`install:`
Travis: fix sudo required and apt-get update command 2018-01-17 19:07:31 +03:00			`- sudo add-apt-repository -y ppa:bitcoin/bitcoin -y`
			`- sudo apt-get update -q`
			`- sudo apt-get install bitcoind -y`
travis: use glide install of btcd In order to have more stable builds we should use use glide install directly, instead of "go get". 2017-06-21 17:12:53 +03:00			`- export PATH=$PATH:$PWD/linux-amd64/`
build: update travis CI config This commit updates the previous travis CI config to pin against the two latest golang versions, and perform installation via Glide. Additionally, this should allow lnwallet’s integration tests to build properly as the btcd binary will be available in the build process’ PATH. 2016-07-26 02:39:22 +03:00			`script:`
travis: update to use `make travis` 2018-03-30 04:49:39 +03:00			`- export PATH=$PATH:$GOPATH/bin`
			`- make travis`
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:`
test: upload integration test logs from TravisCI to file.io 2018-04-27 12:58:21 +03:00			`- echo "Uploading to termbin.com..." && find *.log \| xargs -I{} sh -c "cat {} \| nc termbin.com 9999 \| xargs -r0 printf '{} uploaded to %s'"`
			`- echo "Uploading to file.io..." && tar -zcvO *.log \| curl -s -F 'file=@-;filename=logs.tar.gz' https://file.io \| xargs -r0 printf 'logs.tar.gz uploaded to %s\n'`