[WIP] Auto-deploy to NPM and S3 using Travis CI

[jankeromnes]

This is a follow-up to #30. As discussed in #30 (comment), we'd like to automate the deployments to NPM and S3.

This commit is a work-in-progress Travis CI configuration to achieve this.

TODO for NPM:

• use travis encrypt to encrypt NPM's email and api_key fields (after getting a token from https://npmjs.com, simply replace all secure: TODO by secure: theoutputoftravisencrypt) (split out into Auto-deploy to NPM using Travis CI #32)

TODO for S3:

• same for S3's access_key_id and secret_access_key credentials (might have to ask security first though)
• figure out how to configure the other S3 options/commands in deploy.sh:
  • --profile code.cdn.mozilla.net
  • s3 cp
  • --acl public-read
  • --cache-control max-age=86400
  • --content-type application/json
  • devices.json
  • s3://code-origin-cdn-mozilla-net/devices/devices.json

[martinbalfanz]

@jankeromnes maybe an addition: can we make sure that deployment only happens if all tests succeed?

[jankeromnes]

maybe an addition: can we make sure that deployment only happens if all tests succeed?

By default, Travis CI runs npm test (i.e. node test.js) first, and only deploys if the first step succeeds. Additionally, I've also set it up to only try to deploy new Git tags, instead of every commit, so you have to manually npm version patch && git push --tags origin master to even attempt a release, and then node test.js needs to succeed for it to work.

We could confirm that assumption by purposefully breaking the tests and trying to deploy. I can help with that if you'd like.

[martinbalfanz]

Thanks, that sounds good! I can also test this once we get there. Thanks for helping with the setup!

[samoyemen]

Good