938402edba
bad syntax
2017-04-24 13:43:38 -05:00
441b86ac86
explicit build dirs
2017-04-24 13:40:07 -05:00
679aa2e014
run script in wrong dir
2017-04-24 13:30:03 -05:00
fcffe2d82b
easier to export in before_deploy block
2017-04-24 13:27:00 -05:00
d4ea91a029
removal of extra cd
2017-04-24 13:14:02 -05:00
d0e8c2816c
fixed travis cfg
2017-04-24 13:09:53 -05:00
986b0682ea
travis syntax changes
2017-04-24 12:50:47 -05:00
ccfdc3c6c3
branch restrictions
2017-04-24 12:17:22 -05:00
02952cac6f
cleanup/reorg
2017-04-24 12:14:07 -05:00
3e498199e9
fixed broken syntax for travis
2017-04-24 12:02:06 -05:00
9a7e42459b
cleanup; sane defaults
2017-04-24 11:45:24 -05:00
6c3c85d05f
simplified deploy.sh, fixed after_deploy delete via cli
2017-04-20 19:46:42 -05:00
20d8a07ad0
azure cli after_deploy step working properly; cleanup
2017-04-20 15:45:05 -05:00
10f48d565e
cleaned up argument passing;removed quotes from container args
2017-04-20 14:10:54 -05:00
f04718040c
env vars need quotes
2017-04-20 13:57:49 -05:00
3a1adfc3e1
simplified travis.yml and deploy.sh
2017-04-20 13:44:23 -05:00
60b20817b4
service docker required, despite docker already running
2017-04-20 12:52:12 -05:00
8ed7e81255
invalid path for travis
2017-04-20 12:49:23 -05:00
017b469ee6
mount pwd to container for terraform
2017-04-20 12:46:43 -05:00
3f9d6a2111
no need to pull images
2017-04-20 12:38:00 -05:00
602559f3f7
updated travis file to use docker for pre_deploy/deploy/after_deploy
2017-04-20 12:34:32 -05:00
f117f1de26
trying terraform 0.9.2 for destroy bug; fixed interpolation issue with sshCommand
2017-04-20 00:43:32 -05:00
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
8d9e3e1b80
added deploy script, updated travis.yml to build topic- branches
2017-04-18 19:09:15 -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
Scott Nowicki