mirrors/signal-desktop
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
signal-desktop/.travis.yml

29 lines
868 B
YAML
Raw Normal View History

Run tests on Sauce Labs * Issue #57
2014-11-23 03:36:52 +00:00
language: node_js
node_js:
Clean logs on start - and eslint/mocha with code coverage (#1945) * Clean logs on startup; install server-side testing/linting * Add eslint config, make all of app/ conform to its demands * Add Node.js testing and linting to CI * Lock project to Node.js 7.9.0, used by Electron 1.7.10 * New eslint error: trailing commas in function argumensts Node 7.9.0 doesn't like trailing commas, but Electron does * Move electron to devDependency, tell eslint it's built-in
2018-01-08 21:19:25 +00:00
- '7.9.0'
WIP Travis build // FREEBIE
2017-05-03 18:32:20 +00:00
os:
- linux
dist: trusty
Run tests on Sauce Labs * Issue #57
2014-11-23 03:36:52 +00:00
install:
WIP Travis build // FREEBIE
2017-05-03 18:32:20 +00:00
- yarn install
Run tests on Sauce Labs * Issue #57
2014-11-23 03:36:52 +00:00
script:
CI builds and uploads all targets // FREEBIE
2017-05-05 23:28:27 +00:00
- yarn run generate
Beta versions support: SxS support, in-app env/instance display (#1606) * Script for beta config; unique data dir, in-app env/type display To release a beta build, increment the version and add -beta-N to the end, then go through all the standard release activities. The prepare-build npm script then updates key bits of the package.json to ensure that the beta build can be installed alongside a production build. This includes a new name ('Signal Beta') and a different location for application data. Note: Beta builds can be installed alongside production builds. As part of this, a couple new bits of data are shown across the app: - Environment (development or test, not shown if production) - App Instance (disabled in production; used for multiple accounts) These are shown in: - The window title - both environment and app instance. You can tell beta builds because the app name, preceding these data bits, is different. - The about window - both environment and app instance. You can tell beta builds from the version number. - The header added to the debug log - just environment. The version number will tell us if it's a beta build, and app instance isn't helpful. * Turn on single-window mode in non-production modes Because it's really frightening when you see 'unable to read from db' errors in the console. * aply.sh: More instructions for initial setup and testing * Gruntfile: Get consistent with use of package.json datas * Linux: manually update desktop keys, since macros not available
2017-10-30 20:57:13 +00:00
- yarn prepare-build
Clean logs on start - and eslint/mocha with code coverage (#1945) * Clean logs on startup; install server-side testing/linting * Add eslint config, make all of app/ conform to its demands * Add Node.js testing and linting to CI * Lock project to Node.js 7.9.0, used by Electron 1.7.10 * New eslint error: trailing commas in function argumensts Node 7.9.0 doesn't like trailing commas, but Electron does * Move electron to devDependency, tell eslint it's built-in
2018-01-08 21:19:25 +00:00
- yarn eslint
- yarn test-server
Remove built assets from repo, updates to docs + GH templates (#1955) * Revamp issue and pull request templates, other docs tweaks `yarn test` now runs all of our tests. * Remove generated files from the repository * Update to new Signal support URL * Prevent the 'Test failed 2 == 1' from test-release in CI * Another attempt to fix grunt test-release on Appveyor * grunt test-release: Fail build if test fails * Lint fix, and move jshint earlier in CI process
2018-01-09 23:31:23 +00:00
- yarn lint
CI builds and uploads all targets // FREEBIE
2017-05-05 23:28:27 +00:00
- ./node_modules/.bin/build --em.environment=$SIGNAL_ENV --config.mac.bundleVersion='$TRAVIS_BUILD_NUMBER' --publish=never
Fix linux // FREEBIE
2017-05-06 06:16:07 +00:00
- ./travis.sh
Run tests on Sauce Labs * Issue #57
2014-11-23 03:36:52 +00: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-05 00:26:51 +00:00
- SIGNAL_ENV: production
Add secure environment vars for travis
2014-11-24 22:23:51 +00: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 23:05:13 +00: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 17:19:17 +00:00
notifications:
email: false
WIP Travis build // FREEBIE
2017-05-03 18:32:20 +00:00
addons:
artifacts:
paths:
CI builds and uploads all targets // FREEBIE
2017-05-05 23:28:27 +00:00
- $(ls ./dist/*.* | tr "\n" ":")
Reference in a new issue Copy permalink