* chore: add utility method to get konfig from scripts tests
Local scripts specs should be be caught by the changing current
directory when loading `konfig.coffee` (which loads `cwd.coffee`,
which changes the cwd to `packages/server`). This was throwing
snapshot tests into saving into a wrong folder until I have noticed
this and fixed in
[v8.0.3](https://github.com/bahmutov/snap-shot-core/releases/tag/v8.0.3)
* linting
* add more comments
* use 'platform-arch' naming scheme for downloads
* do full builds for this branch
* Revert "do full builds for this branch"
This reverts commit 6d539513e7.
* update wrong comments
* chore: test upload getCDN functions
* linting js
* unit test refactored manifest
* linting
* appveyor build for this branch
* don't force install ffmpeg on windows
don't force install ffmpeg on windows
* derp
* fix
* build in appveyor
* oops
* delete using del
* use RMDIR instead of DEL
* only build 32-bit
* build for x64 and x86 windows
* separate win32 and win64
* require lodash
* make electron arch configurable
* cross-compile 32, only run in 64-bit
* force install ffmpeg if necessary
* it's all win10 x64, but we can force it to build for ia32 in x32 mode
* add windows util
* who's idea was it to make whitespace meaningful?
* pass arch to npm install, pass arch to uploader
* add TARGET_PLATFORM
* fun fact: appveyor titlecases env var names
fun fact: appveyor titlecases env var names
* fix: pass args
* use process
* cli: use arch package to send arch to server
* pass TARGET_ARCH to all npm installs
* run-all
* always call getUploadNameByOs
* use the precise version of node, enable both x64 and ia32 arch
* quotes
* uh wat
* move console logs to script because windows
* add yet another env var to install the right node arch
* use x86, not x32
* give ia32 a try, why not
* use platform env again
* and also try x86 again
* remove notion of target_arch since we're using the right node version with arch set correctly
* more comprehensive checks to ensure the arch is correct
* simplify building the binary, do not accept arch as options
* build the binary and test it on this branch
* remove arch, ensure that process.env.Platform is set to x86
* do build the binary unless this is a forked PR
* attempt to verify that this is a 32bit or 64bit windows binary
* remove unused dep
* consolidate commands
* don't install packages in windows - just build the binary
- this avoids needing to reinstall all node_modules and build-js twice
* build the binary on more branches
* cd up appveyor
* ugh
* right logic for whether or not this is a forked PR
* remove unused deps
* fix undefined var
* platformArch
* set in options
* turns out we do have to npm install before building the binary
* options.platformArch
* comment out appveyor build 32bit/64bit verification temporarily
Co-authored-by: Brian Mann <brian.mann86@gmail.com>
* build: print prod and dev dependencies in packages/server
* use npm v6 on Windows
* use only=production npm install flag
* use latest version of Node on AppVeyor
* add env with NODE_ENV=production
* pretty ms for npm install
* fix retry
* remove devDependencies from each file
* test binary build logic on Circle
* do not even run unit tests on circle
* form package json path
* cannot mapSeries twice
* pass package folder name
* fixed missing json to save
* uncomment circle tests
* update some comments, remove branches
* set set-next-ci-version script command
* use current package.json version when asking for next one
* showing actual error response from buildkite
* rename .aws-credentials.json to just aws-credentials.json file
* rename aws_credentials_json on appveyor
* run linter an all
* add NPM package CI job
* more steps for NPM package
* start upload NPM package
* more work on NPM package upload
* testing upload
* move purge cache to utils
* add unique binary build and upload from CI
* pass saved urls to test-binary job
* allow CYPRESS_BINARY_VERSION to be an url right away
* put uploaded urls into /tmp folder
* use explicit json filenames
* paths instead of path
* testing cypress npm and binary
* use NPM folder beta to store temp binary and package
* refactor utils
* set env vars and trigger other test projects
* only test NPM and binary on develop branch
* enable all jobs again
* try installing on Windows
* Handle windows setup
- no browser detection on windows yet, just placeholder code
- symlink types
* add appveyor file
* add appveyor windows build
* use execa to run server unit tests
* run server unit tests on appveyor
* ignore root install errors
* upgrade rebuild-node-sass
and work on Json unit test that fails on Windows
* print npm version
before installing, commented out caching node modules in the root
* a few small tweaks for windows support
* fix bin-up in launcher project
use bin-up@1.1.0 for windows support, close#491
* cli: build script on Windows, close#492
* cli: build errors are fatal
* use cross-env in extension
Fixes environment variables on Windows in #490
* extension: fix 3 tests on Windows
1 more broken test remaining
* extension: use EOL before comparing text
* example: update test for Windows
* example: replace build.sh with build.js
Close#488
* remove trailing whitespace
* cli: build script again
* server: work on unit tests for windows
* binary: add windows as build platform
* windows: try building binary
started work on building on CI for windows
* binary: check platform, throw exception on mismatch
* binary: build script actually builds linux platform app
* zip from Mac both linux and darwin apps
* quiet npm installs during builds
