aaron stacy
frontend engineer
but we need to ship
we've got a lot of tools
that help us build
- browsers' dev tools
- module loaders
- css preprocessors
- how many mvc frameworks??!
the mysterious "tests" folder
n00bs
continuous integration
those things you do
when you release
- run tests
- minify
- concatenate
- compile
- deploy
except all the time,
every commit
we want to:
- run our tests on every commit
- receive an e-mail when something breaks
- not receive an e-mail when stuff doesn't break
- know if merging a pull request will cause problems
make grunt test work
add a .travis.yml to your repo:
language: node_js
node_js: ["0.10"]
before_script: npm install -g grunt-cli
script: grunt test
[docs]
[example]
we want to:
- run our tests on every commit
- receive an e-mail when something breaks
- not receive an e-mail when stuff doesn't break
- know if merging a pull request will cause problems
we want to:
- run our tests on every commit
- receive an e-mail when something breaks
- not receive an e-mail when stuff doesn't break
- know if merging a pull request will cause problems
we want to:
- run our tests on every commit
- receive an e-mail when something breaks
- not receive an e-mail when stuff doesn't break
- know if merging a pull request will cause problems
we want to:
- deploy our app on a successful build
make grunt deploy work
update your .travis.yml:
language: node_js
node_js: ["0.10"]
before_script: npm install -g grunt-cli
script: grunt test
[instructions]
[example]
update your .travis.yml:
language: node_js
node_js: ["0.10"]
before_script: npm install -g grunt-cli
script: grunt test
# additional info for automatic deployment
after_success: grunt deploy
env:
global:
- secure: GvrIQCbjeEB... # generated token
[instructions]
[example]
busy people ❤ this
teams ❤ this
everybody #winning