Commit Graph

120 Commits

Author SHA1 Message Date
Mitchell Hashimoto 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
Christoph Blecker 2f92c4fb57
travis: Update to Go 1.7.3 2016-10-20 00:45:46 -07:00
Mitchell Hashimoto ec15783f24
-Xnew-apply to enable the new apply graph 2016-10-19 13:39:28 -07:00
Christoph Blecker 15ad398030
Update Travis to Go 1.7.1 2016-10-14 14:16:15 -07:00
Mitchell Hashimoto 58e4a58099
Update to Go 1.7 on travis 2016-08-16 17:57:35 -07:00
Paul Hinze 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
Paul Hinze 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
James Nugent 904c5ae576 Update Travis to use Go 1.6 2016-02-17 14:29:53 -08:00
Trevor Pounds fdf9a35490 Run `go vet` taget on Travis CI builds. 2016-02-17 13:37:56 -08:00
Paul Hinze 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
Paul Hinze 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
James Nugent 359c087a3a Build using `make test` on Travis CI 2015-11-10 17:11:39 -05:00
Paul Hinze 89cc98934b travis: build with go 1.5 now 2015-10-28 12:21:49 -04:00
Paul Hinze 028a8ac8c5 travis: run `go vet` on every build 2015-03-05 14:59:51 -06:00
Seth Vargo b901f31645 Post to IRC 2015-01-22 16:02:03 -05:00
Seth Vargo a61c409fd2 Only test the master branch (and PRs) 2015-01-22 15:57:01 -05:00
Seth Vargo 100270378b Run on the new Travis Docker infrastructure 2015-01-22 15:56:32 -05:00
Mitchell Hashimoto afc67ba426 Just test GO 1.4 2015-01-10 15:54:49 -08:00
Mitchell Hashimoto 40bd1580e4 Travis file should be unix line endings 2014-08-05 10:16:53 -07:00
Mitchell Hashimoto 9105ec8cc9 Travis 2014-08-05 10:16:27 -07:00