Test Windows build on CircleCI

[bahmutov]

• Closes CircleCI can test Win 64 builds #48
• Added Windows CircleCI build
• Shows currently failing pipe from dest.end error crash during run exit on GitLab CI / Windows cypress#2181
• Once a fix is implemented can be merged
• moved early halt logic into a Node script because the bash syntax was not working on Windows

[flotwig]

@bahmutov This is unblocked now that Cypress can run in Windows CircleCI, right?

[bahmutov]

Are the tests passing on circle windows ? It should be I think

…

Sent from my iPhone

On Dec 26, 2019, at 13:06, Zach Bloomquist ***@***.***> wrote:  @bahmutov This is unblocked now that Cypress can run in Windows CircleCI, right? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[flotwig]

Not passing yet, but it seems to be a failure in copying artifacts, not in Cypress itself

[bahmutov]

Windows paths shenanigans?

…

Sent from my iPhone

On Dec 26, 2019, at 13:08, Zach Bloomquist ***@***.***> wrote:  Not passing yet, but it seems to be a failure in copying artifacts, not in Cypress itself — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[bahmutov]

@flotwig I have updated the dependency ok-file that was checking files - it was getting single-quoted argument on Windows, breaking it. Now Circle is happy again and AppVeyor failures are because it is AppVeyor and fails sometimes to pass env variables!

Literally this is stupid https://ci.appveyor.com/project/cypress-io/cypress-test-tiny-fitqm/builds/29766710

node_modules\.bin\run-if npm run cypress:verify
Platform win32 is allowed
Arch ia32 is allowed
> cypress-test-tiny@1.0.0 cypress:verify C:\projects\cypress-test-tiny-fitqm
> cypress verify
[21:21:54]  Verifying Cypress can run C:\Users\appveyor\AppData\Local\Cypress\Cache\3.8.1\Cypress [started]
[21:21:56]  Verifying Cypress can run C:\Users\appveyor\AppData\Local\Cypress\Cache\3.8.1\Cypress [completed]
node_modules\.bin\run-if npm run cypress:run -- --record
Platform win32 is allowed
Arch ia32 is allowed
> cypress-test-tiny@1.0.0 cypress:run C:\projects\cypress-test-tiny-fitqm
> cypress run "--record"
You passed the --record flag but this project has not been setup to record.
This project is missing the 'projectId' inside of 'cypress.json'.
We cannot uniquely identify this project without this id.
You need to setup this project to record. This will generate a unique 'projectId'.
Alternatively if you omit the --record flag this project will run without recording.
https://on.cypress.io/recording-project-runs
npm ERR! code ELIFECYCLE
npm ERR! errno 1

The record key and project id are set as environment variables on AppVeyor for this project.

[flotwig]

Appveyor has been failing since 2f2b827 in this branch with the same error, also, that job doesn't seem to exist for any of the commits before that 2f2b827. I looked at the changes but don't really understand how they could be causing Appveyor to run when it didn't before.

[bahmutov]

ok, I removed recording on AppVeyor, enough is enough

[flotwig]

nice!

[bahmutov]

yeah, it is ok to remove hardcoded version