fleet/circle.yml

machine:
  pre:
    - sudo curl -L -o /usr/bin/docker 'https://s3-external-1.amazonaws.com/circle-downloads/docker-1.9.1-circleci'
    - sudo chmod 0755 /usr/bin/docker
  services:
    - docker

dependencies:
  pre:
    - docker info
    - docker login -e $DOCKER_HUB_EMAIL -u $DOCKER_HUB_USERNAME -p $DOCKER_HUB_PASSWORD
  override:
    - docker pull kolide/kolide-builder:1.7

test:
  override:
      - docker run -v $(pwd):/go/src/github.com/kolide/kolide-ose -v /home/ubuntu/.go_workspace/pkg:/go/pkg kolide/kolide-builder:1.7 -B

deployment:
  development:
    branch: /^((?!master).)*$/  # not the master branch
    commands:
      - make docker-build-circle
replace godep in favor of glide and using vendor directory update make deps step in Makefile update workflow for managing third party dependencies in README closes #24, #47 2016-08-13 21:49:19 +00:00			`machine:`
add build container for testing in ci (#89) build fails if container exit code fails. One step closer to #71 2016-08-20 00:05:24 +00:00			`pre:`
			`- sudo curl -L -o /usr/bin/docker 'https://s3-external-1.amazonaws.com/circle-downloads/docker-1.9.1-circleci'`
			`- sudo chmod 0755 /usr/bin/docker`
			`services:`
			`- docker`

React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. Note: Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications 2016-08-10 05:15:44 +00:00			`dependencies:`
add build container for testing in ci (#89) build fails if container exit code fails. One step closer to #71 2016-08-20 00:05:24 +00:00			`pre:`
			`- docker info`
			`- docker login -e $DOCKER_HUB_EMAIL -u $DOCKER_HUB_USERNAME -p $DOCKER_HUB_PASSWORD`
replace godep in favor of glide and using vendor directory update make deps step in Makefile update workflow for managing third party dependencies in README closes #24, #47 2016-08-13 21:49:19 +00:00			`override:`
Updating the docker image to go 1.7 (#104) 2016-09-04 15:55:26 +00:00			`- docker pull kolide/kolide-builder:1.7`
add build container for testing in ci (#89) build fails if container exit code fails. One step closer to #71 2016-08-20 00:05:24 +00:00
React Base (#61) * Add sensible React base to the app for frontend This PR attempts to "reactify" Kolide and provide a sane development environment that a front-end engineer would probably expect. This PR accomplishes by doing the following: 1. Reorganizes the app into a `server/` and `client/` folders to keep golang logic separated from react logic. 2. Adds an "asset pipeline" via webpack which knows how to build a js and css bundle. 3. Packages up all static assets in a go-bindata file so that the binary remains portable without external file dependencies. 1. Add a Makefile with several targets that will be common in everyday development. For example, we have `serve` target which spins up a nodejs reverse proxy on port 8081 which then watches for changed files, automatically rebuilds the app, and hot loads the new JS/CSS in. Note: Please use `make` to build the app, not `go build` as there are now several things that need to be orchestrated beyond the go code to build the app. * Create build if it doesn't exist, and use `go get` * Improve README to reflect new dev workflow * Document css vars and funcs and use alias paths * makefile and structure modifications 2016-08-10 05:15:44 +00:00			`test:`
Adding a circle config file (#52) 2016-08-09 03:42:24 +00:00			`override:`
Docker Push of new builds (#192) * wip * add build step * remove filter? * circle does not rebuild on force push * circle does not rebuild on force push * add branch filter * use build flag on builder * push * add circle env variable set * redeploy 2016-09-19 22:54:57 +00:00			`- docker run -v $(pwd):/go/src/github.com/kolide/kolide-ose -v /home/ubuntu/.go_workspace/pkg:/go/pkg kolide/kolide-builder:1.7 -B`

			`deployment:`
			`development:`
			`branch: /^((?!master).)*$/ # not the master branch`
			`commands:`
			`- make docker-build-circle`