ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/.travis.yml

55 lines
1.4 KiB
YAML
Raw Normal View History

.travis.yml reverted back to hashicorp's master .travis.yml
2017-05-02 21:33:52 +02:00
dist: trusty
make: Add website + website-test targets
2018-05-02 13:43:14 +02:00
sudo: required
services:
- docker
.travis.yml reverted back to hashicorp's master .travis.yml
2017-05-02 21:33:52 +02:00
language: go
go:
Bump travis to 1.11
2018-09-09 19:39:36 +02:00
- "1.11"
early prep for CI of examples (#7) * early prep for CI of examples * added note to prevent moving upstream
2017-04-27 18:40:53 +02:00
.travis.yml reverted back to hashicorp's master .travis.yml
2017-05-02 21:33:52 +02:00
# add TF_CONSUL_TEST=1 to run consul tests
# they were causing timouts in travis
Add a note about running the 'etcdv3' tests.
2017-09-09 09:17:56 +02:00
# add TF_ETCDV3_TEST=1 to run etcdv3 tests
# if added, TF_ETCDV3_ENDPOINTS must be set to a comma-separated list of (insecure) etcd endpoints against which to test
fetch consul binary for tests
2017-03-13 23:07:10 +01:00
env:
build: Update most things for Go 1.11 modules We're still using vendoring for now until we get _all_ of our tooling updated, so the main idea here is to force use of the vendor directory when running tests and building for development so we can quickly find situations where we forget to run "go mod vendor". We also setting GO111MODULE=off for installation of tools. Right now this is the best way to install a tool in GOBIN without also interfering with go.mod and go.sum, until a better pattern for managing tool dependencies is devised by the Go team. Finally, we run "go mod download" before launching "gox" in the main build process, to prime the local module cache once so that the concurrent "go build" processes won't race to populate it redundantly. This means that we'll be producing final builds from the module cache rather than from vendor as with everything else -- there's currently no way to tell gox to use -mod=vendor -- but that should be fine in practice since our go.sum file will ensure that we get the exact sources we expect in the module cache before building.
2018-11-17 03:54:33 +01:00
- CONSUL_VERSION=0.7.5 GOMAXPROCS=4 GO111MODULE=on
fetch consul binary for tests
2017-03-13 23:07:10 +01:00
.travis.yml reverted back to hashicorp's master .travis.yml
2017-05-02 21:33:52 +02:00
# Fetch consul for the backend and provider tests
before_install:
- curl -sLo consul.zip https://releases.hashicorp.com/consul/${CONSUL_VERSION}/consul_${CONSUL_VERSION}_linux_amd64.zip
- unzip consul.zip
fix travis for unit tests
2017-07-13 19:19:24 +02:00
- mkdir -p ~/bin
.travis.yml reverted back to hashicorp's master .travis.yml
2017-05-02 21:33:52 +02:00
- mv consul ~/bin
- export PATH="~/bin:$PATH"
install:
# This script is used by the Travis build to install a cookie for
# go.googlesource.com so rate limits are higher when using `go get` to fetch
# packages that live there.
# See: https://github.com/golang/go/issues/12933
- bash scripts/gogetcookie.sh
build: Take protoc out of the "go generate" path Since protoc is not go-gettable, and most development tasks in Terraform won't involve recompiling protoc files anyway, we'll use a separate mechanism for these. This way "go generate" only depends on things we can "go get" in the "make tools" target. In a later commit we should also in some way specify a particular version of protoc to use so that we don't get "flapping" regenerations as developers work with different versions, but the priority here is just to make "make generate" minimally usable again to restore the dev workflow documented in the README. This also includes some updates that resulted from running "make generate" and "make protobuf" after those Makefile changes were in place.
2018-10-18 18:27:48 +02:00
- make tools
force git to use https
2017-10-30 19:04:25 +01:00
before_script:
- git config --global url.https://github.com/.insteadOf ssh://git@github.com/
.travis.yml reverted back to hashicorp's master .travis.yml
2017-05-02 21:33:52 +02:00
script:
update travis to catch vet failures
2017-05-19 15:12:56 +02:00
- make test
build: run end-to-end tests during Travis run We don't usually run "acceptance tests" during a Travis run, but this particular suite doesn't require any special credentials since it just accesses releases.hashicorp.com to download plugins, so therefore it's safe to run in Travis at the expense of adding a few more seconds to the runtime. Running it in Travis can therefore give us some extra confidence for pull requests that may inadvertently break certain details of the workflow, as well as ensuring that these tests are kept up-to-date as the system changes.
2017-09-19 21:00:26 +02:00
- make e2etest
build: Travis-CI build should use vendor directory when building for Windows
2018-11-20 20:59:48 +01:00
- GOOS=windows go build -mod=vendor
build: Temporarily disable the website tests for Travis-CI There are some known broken links right now because this repository has been updated ahead of some necessary changes in the terraform-website repository. We'll need to wait until the end of the v0.12 release process to re-enable this because the terraform-website repository is currently set up for the v0.11 content and will continue to be until v0.12.0 final is ready for release.
2018-11-17 03:58:50 +01:00
# website-test is temporarily disabled while we get the website build back in shape after the v0.12 reorganization
#- make website-test
make: Add website + website-test targets
2018-05-02 13:43:14 +02:00
Only test the master branch (and PRs)
2015-01-22 21:57:01 +01:00
branches:
only:
updated .travis.yml to read branches prefixed with topic-
2017-04-19 02:10:41 +02:00
- master
.travis.yml reverted back to hashicorp's master .travis.yml
2017-05-02 21:33:52 +02:00
notifications:
irc:
channels:
- irc.freenode.org#terraform-tool
skip_join: true
use_notice: true
matrix:
fast_finish: true
allow_failures:
update travis to catch vet failures
2017-05-19 15:12:56 +02:00
- go: tip