87b049b72d
adding cd to after_deploy to ensure we're in the correct directory
2017-04-19 23:26:28 -05:00
36e4b74c13
added -force to after_deploy
2017-04-19 20:32:22 -05:00
bf5d9773e2
fixed after_deploy syntax for .travis.yml
2017-04-19 20:23:07 -05:00
af3de7b7df
azure is awfully particular for certain strings
2017-04-19 19:36:16 -05:00
e0208f48ba
added after_deploy step to travis.yml; updated string generation yet again
2017-04-19 19:29:36 -05:00
048ab5a774
renamed folder; updated deployment script; prompt for additional variables
2017-04-19 17:59:56 -05:00
3ce7a2499a
add execute permissions to deploy.sh file
2017-04-19 10:59:21 -05:00
d8131c2d5e
cleanup; permitted topic branch
2017-04-19 10:51:07 -05:00
ca65fe31ce
disabling travis deployment on master short-term
2017-04-19 10:46:54 -05:00
bbdb2cef53
removed branch restrictions on deploy
2017-04-19 10:28:11 -05:00
601735b873
updated .travis.yml to read branches prefixed with topic-
2017-04-18 19:10:41 -05:00
8d9e3e1b80
added deploy script, updated travis.yml to build topic- branches
2017-04-18 19:09:15 -05:00
b7f8ae542a
added directory to build matrix
2017-04-18 18:44:06 -05:00
4febc170b7
updated travis.yml for builds on terraform examples
2017-04-18 18:37:39 -05:00
96617b609b
remove consul tests from travis runs
...
they have timing out too often
2017-03-24 12:14:05 -04:00
420383cd53
set GOMAXPROCS to 4 in travis
...
The travis containers have 2 cores, up the GOMAXPROCS to 4 to give the
runtime a little more flexibility with our tests.
2017-03-15 12:05:44 -04:00
86f711f6fc
Make consul backend tests opt-in
...
This way we don't require contributers to have consul installed to run
make test.
2017-03-14 14:44:03 -04:00
d46d93c85f
try trusty
2017-03-14 13:12:07 -04:00
54224eb41e
fetch consul binary for tests
2017-03-13 18:07:10 -04:00
1c50c53da3
check vendor status in travis
2017-02-24 15:06:32 -05:00
ae6d82fea8
build: change to start using Go 1.8 ( #12022 )
2017-02-16 23:13:42 +02:00
c01680b7a9
build: Update travis to go1.7.5 and go1.8rc3 and Vagrantfile to go1.7.5 ( #11490 )
...
* Update travis to go1.7.5 and go1.8rc3
* Update Vagrantfile to go1.7.5
2017-01-29 19:39:07 +00:00
f3c48ec00c
disable vendor-status in travis for now
2017-01-25 14:47:14 -05:00
60e4cfd285
Merge pull request #11308 from hashicorp/jbardin/vendor-fix
...
Fix vendored packages
2017-01-20 12:49:37 -05:00
1aef515aba
Add vendor-status check to travis
2017-01-20 12:01:40 -05:00
651b0bf7c7
Update travis for go1.8rc2 ( #11297 )
2017-01-20 11:13:38 +00:00
a866da4938
Update travis for go1.8rc1 ( #11229 )
2017-01-17 11:38:23 +00:00
ce0fa85405
just us GOOS
2017-01-11 08:53:28 -06:00
f4f9af3bee
build on windows
2017-01-11 08:32:16 -06:00
4000d224e5
Update Travis to Go 1.8beta2
2016-12-15 13:50:14 -08:00
b75b839b2c
Update .travis.yml
2016-12-06 15:55:08 -08:00
9afa5d0f07
Update Travis and Vagrant to go 1.7.4
2016-12-01 13:37:34 -08:00
785cc7b78a
terraform: default new graphs on, old graphs behind -Xlegacy-graph
...
This turns the new graphs on by default and puts the old graphs behind a
flag `-Xlegacy-graph`. This effectively inverts the current 0.7.x
behavior with the new graphs.
We've incubated most of these for a few weeks now. We've found issues
and we've fixed them and we've been using these graphs internally for
awhile without any major issue. Its time to default them on and get them
part of a beta.
2016-11-10 21:53:20 -08:00
14cff93b67
Merge pull request #9388 from hashicorp/f-apply-builder
...
terraform: new apply graph builder based on the "diff"
2016-10-20 15:13:29 -07:00
2f92c4fb57
travis: Update to Go 1.7.3
2016-10-20 00:45:46 -07:00
ec15783f24
-Xnew-apply to enable the new apply graph
2016-10-19 13:39:28 -07:00
15ad398030
Update Travis to Go 1.7.1
2016-10-14 14:16:15 -07:00
58e4a58099
Update to Go 1.7 on travis
2016-08-16 17:57:35 -07:00
d38ee00039
travis: switch to unencrypted cookie
...
Otherwise rate limiting fix does not work for PRs from forks
2016-03-21 13:35:53 -05:00
39b5bd0efb
travis: add git cookie to get higher rate limits for `go get`
...
Should fix messages like this from the Travis builds:
```
Daily bandwidth rate limit exceeded for IP 52.0.240.122.
```
Refs https://github.com/golang/go/issues/12933
2016-03-21 08:36:18 -05:00
904c5ae576
Update Travis to use Go 1.6
2016-02-17 14:29:53 -08:00
fdf9a35490
Run `go vet` taget on Travis CI builds.
2016-02-17 13:37:56 -08:00
6fe2703665
Vendor all dependencies w/ Godep
...
* Remove `make updatedeps` from Travis build. We'll follow up with more
specific plans around dependency updating in subsequent PRs.
* Update all `make` targets to set `GO15VENDOREXPERIMENT=1` and to
filter out `/vendor/` from `./...` where appropriate.
* Temporarily remove `vet` from the `make test` target until we can
figure out how to get it to not vet `vendor/`. (Initial
experimentation failed to yield the proper incantation.)
Everything is pinned to current master, with the exception of:
* Azure/azure-sdk-for-go which is pinned before the breaking change today
* aws/aws-sdk-go which is pinned to the most recent tag
The documentation still needs to be updated, which we can do in a follow
up PR. The goal here is to unblock release.
2016-01-29 15:08:48 -06:00
d8022645ba
travis: remove go tip builds
...
I don't really see a good reason for running a build against Go tip.
This probably made more sense in the earlier days of Golang, but now
IMHO it's just wasting cycles for not much benefit.
/cc @jen20 @mitchellh
2015-12-07 11:45:53 -06:00
359c087a3a
Build using `make test` on Travis CI
2015-11-10 17:11:39 -05:00
89cc98934b
travis: build with go 1.5 now
2015-10-28 12:21:49 -04:00
028a8ac8c5
travis: run `go vet` on every build
2015-03-05 14:59:51 -06:00
b901f31645
Post to IRC
2015-01-22 16:02:03 -05:00
a61c409fd2
Only test the master branch (and PRs)
2015-01-22 15:57:01 -05:00
100270378b
Run on the new Travis Docker infrastructure
2015-01-22 15:56:32 -05:00
afc67ba426
Just test GO 1.4
2015-01-10 15:54:49 -08:00
40bd1580e4
Travis file should be unix line endings
2014-08-05 10:16:53 -07:00
9105ec8cc9
Travis
2014-08-05 10:16:27 -07:00
Scott Nowicki