2017-05-03 21:43:04 +00:00
|
|
|
platform:
|
|
|
|
|
- x64
|
|
|
|
|
|
|
|
|
|
cache:
|
|
|
|
|
- '%LOCALAPPDATA%\electron\Cache'
|
2017-06-14 19:40:29 +00:00
|
|
|
- node_modules -> package.json
|
2017-05-03 21:43:04 +00:00
|
|
|
|
|
|
|
|
install:
|
2017-07-07 16:41:09 +00:00
|
|
|
- systeminfo | findstr /C:"OS"
|
2017-05-03 21:43:04 +00:00
|
|
|
- set PATH=C:\Ruby23-x64\bin;%PATH%
|
|
|
|
|
- ps: Install-Product node 6 x64
|
|
|
|
|
- yarn install
|
|
|
|
|
|
2017-05-05 23:28:27 +00:00
|
|
|
build_script:
|
2017-06-20 21:47:33 +00:00
|
|
|
- yarn run icon-gen
|
2017-09-14 23:05:31 +00:00
|
|
|
- node build\grunt.js
|
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
|
2017-05-16 22:49:29 +00:00
|
|
|
- node_modules\.bin\build --em.environment=%SIGNAL_ENV% --publish=never
|
2017-05-05 23:28:27 +00:00
|
|
|
|
2017-05-03 21:43:04 +00:00
|
|
|
test_script:
|
2017-09-14 23:05:31 +00:00
|
|
|
- node build\grunt.js test-release:win
|
|
|
|
|
- node build\grunt.js test
|
2017-05-03 21:43:04 +00:00
|
|
|
|
2017-05-05 00:26:51 +00:00
|
|
|
environment:
|
|
|
|
|
SIGNAL_ENV: production
|