signal-desktop/.travis.yml

language: node_js
node_js:
  - 'node'
os:
  - linux
dist: trusty
install:
  - yarn install
script:
  - yarn run generate
  - ./node_modules/.bin/build --em.environment=$SIGNAL_ENV --config.mac.bundleVersion='$TRAVIS_BUILD_NUMBER' --publish=never
  - ./travis.sh
env:
  global:
    - SIGNAL_ENV: production
    - secure: LeXDynRSyeHXR9KdmhYuP/zsc8uFsnYoOWI3fqg8x5SLOilfDyQ766idkT9NTRrdSR8WY7wP4DPs3hrBWGmcVq7BhytI9Q34YSgGS/Sds0jlm5AzSpYfAHpSQ+9ufQXNKN6lgxTkupdsWlc2Em20wUd5EfluDSOoeWVMlqHmKrw=
    - secure: WzXjaiy6BmEyKI3uXeanjbAlmzadlwIWxJbC7Mff2duIl/nsaOTK6ElYu23IfeBCvK1DxXV8DVUfTIZXkeFeqHKPtgq2t3HcS12YiNnb7ToGpgOpzElYY4wAOPxRbqPE/ZcthbSxo1x/thgDeWNWxqK1X4XJ3qEIRoE+tPsGKG8=
sudo: false
notifications:
  email: false
addons:
  artifacts:
    paths:
      - $(ls ./dist/*.* | tr "\n" ":")
Run tests on Sauce Labs * Issue #57 2014-11-22 19:36:52 -08:00			`language: node_js`
			`node_js:`
WIP Travis build // FREEBIE 2017-05-03 11:32:20 -07:00			`- 'node'`
			`os:`
			`- linux`
			`dist: trusty`
Run tests on Sauce Labs * Issue #57 2014-11-22 19:36:52 -08:00			`install:`
WIP Travis build // FREEBIE 2017-05-03 11:32:20 -07:00			`- yarn install`
Run tests on Sauce Labs * Issue #57 2014-11-22 19:36:52 -08:00			`script:`
CI builds and uploads all targets // FREEBIE 2017-05-05 16:28:27 -07:00			`- yarn run generate`
			`- ./node_modules/.bin/build --em.environment=$SIGNAL_ENV --config.mac.bundleVersion='$TRAVIS_BUILD_NUMBER' --publish=never`
Fix linux // FREEBIE 2017-05-05 23:16:07 -07:00			`- ./travis.sh`
Run tests on Sauce Labs * Issue #57 2014-11-22 19:36:52 -08:00			`env:`
			`global:`
More release scripting in npm npm run icon-gen and grunt (run default task) can be grouped into one operation. Use SIGNAL_ENV instead of NODE_ENV since Setting NODE_ENV adversely affects yarn's install behavior, so we had to set it after the install and before the build. By using a custom variable instead, we can set it globally and eventually use it in a build matrix. Move mas build to its own npm script // FREEBIE 2017-05-04 17:26:51 -07:00			`- SIGNAL_ENV: production`
Add secure environment vars for travis 2014-11-24 14:23:51 -08:00			`- secure: LeXDynRSyeHXR9KdmhYuP/zsc8uFsnYoOWI3fqg8x5SLOilfDyQ766idkT9NTRrdSR8WY7wP4DPs3hrBWGmcVq7BhytI9Q34YSgGS/Sds0jlm5AzSpYfAHpSQ+9ufQXNKN6lgxTkupdsWlc2Em20wUd5EfluDSOoeWVMlqHmKrw=`
			`- secure: WzXjaiy6BmEyKI3uXeanjbAlmzadlwIWxJbC7Mff2duIl/nsaOTK6ElYu23IfeBCvK1DxXV8DVUfTIZXkeFeqHKPtgq2t3HcS12YiNnb7ToGpgOpzElYY4wAOPxRbqPE/ZcthbSxo1x/thgDeWNWxqK1X4XJ3qEIRoE+tPsGKG8=`
Migrate to new travis infrastructure http://docs.travis-ci.com/user/migrating-from-legacy 2015-07-28 16:05:13 -07:00			`sudo: false`
Travis doesn't respect the repo/organization email so turning off Turning off travis email notifications. Github does a fine job notifying us about the things we care about, otherwise we can always go there and see the results. FREEBIE 2017-08-15 10:19:17 -07:00			`notifications:`
			`email: false`
WIP Travis build // FREEBIE 2017-05-03 11:32:20 -07:00			`addons:`
			`artifacts:`
			`paths:`
CI builds and uploads all targets // FREEBIE 2017-05-05 16:28:27 -07:00			`- $(ls ./dist/. \| tr "\n" ":")`