signal-desktop/appveyor.yml

platform:
  - x64

cache:
  - '%LOCALAPPDATA%\electron\Cache'
  - node_modules -> package.json

install:
  - systeminfo | findstr /C:"OS"
  - set PATH=C:\Ruby23-x64\bin;%PATH%
  - ps: Install-Product node 7.9.0 x64
  - yarn install

build_script:
  - yarn eslint
  - yarn test-server
  - yarn run icon-gen
  - node build\grunt.js
  - type package.json | findstr /v certificateSubjectName > temp.json
  - move temp.json package.json
  - yarn prepare-build
  - node_modules\.bin\build --em.environment=%SIGNAL_ENV% --publish=never

test_script:
  - node build\grunt.js test-release:win
  - node build\grunt.js test

environment:
  SIGNAL_ENV: production
Add appveyor 2017-05-03 21:43:04 +00:00			`platform:`
			`- x64`

			`cache:`
			`- '%LOCALAPPDATA%\electron\Cache'`
Make node_modules cache dependent on package.json FREEBIE 2017-06-14 19:40:29 +00:00			`- node_modules -> package.json`
Add appveyor 2017-05-03 21:43:04 +00:00
			`install:`
Appveyor: Add some logging to help track down flakiness FREEBIE 2017-07-07 16:41:09 +00:00			`- systeminfo \| findstr /C:"OS"`
Add appveyor 2017-05-03 21:43:04 +00:00			`- set PATH=C:\Ruby23-x64\bin;%PATH%`
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			`- ps: Install-Product node 7.9.0 x64`
Add appveyor 2017-05-03 21:43:04 +00:00			`- yarn install`

CI builds and uploads all targets // FREEBIE 2017-05-05 23:28:27 +00:00			`build_script:`
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`
AppVeyor - fix what appears to be a problem with '&& grunt' FREEBIE 2017-06-20 21:47:33 +00:00			`- yarn run icon-gen`
Bypass often-corrupt node_modules/.bin/grunt.cmd on windows (#1481) FREEBIE 2017-09-14 23:05:31 +00:00			`- node build\grunt.js`
Add certificate name for windows code-signing (#1513) * Add certificate name for windows code-signing electron-builder supports our extended validation code-signing cert, but only on windows. Our release process must now include a signing step on windows. FREEBIE * AppVeyor Remove certificateSubjectName to disable signing * Move code-signing disable package.json updates above build * AppVeyor: Use temporary holding file for package.json changes 2017-09-28 18:58:45 +00:00			`- type package.json \| findstr /v certificateSubjectName > temp.json`
			`- move temp.json package.json`
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`
Fixes for appveyor build: path formats, correct electron binary 2017-05-16 22:49:29 +00:00			`- node_modules\.bin\build --em.environment=%SIGNAL_ENV% --publish=never`
CI builds and uploads all targets // FREEBIE 2017-05-05 23:28:27 +00:00
Add appveyor 2017-05-03 21:43:04 +00:00			`test_script:`
Bypass often-corrupt node_modules/.bin/grunt.cmd on windows (#1481) FREEBIE 2017-09-14 23:05:31 +00:00			`- node build\grunt.js test-release:win`
			`- node build\grunt.js test`
Add appveyor 2017-05-03 21:43:04 +00:00
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			`environment:`
			`SIGNAL_ENV: production`