-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Placeholder support for CYPRESS_INSTALL_BINARY #16976
Comments
|
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What would you like?
An easy way to configure and install cypress in corporate environment. It's nice that CYPRESS_INSTALL_BINARY options exists but it could be better.
To cover all scenarios we need to support windows, mac, and linux (for CI) and there is no nice way do this if you are sitting behind corporate firewall. Here is what I ended up doing and I believe it would work for quite a few others without having to mirror download site (we use artifactory and sadly cypress download site does not come out of the box, I also have limited rights to play with it so I'm also not aware of complete functionality).
So.... drums rolls....
in .npmrc I have this:
and in our postinstall hook I do this:
This is obviously workaround and I'll have to maintain it in the future, but it is definitely better than proposed alternatives I could find.
So for the solution, how about adding placeholders for cypress version, platform and architecture in CYPRESS_INSTALL_BINARY variable?
Thanks for an awesome tool!
Why is this needed?
To make it less painful to configure and use cypress across workstations and CI.
The text was updated successfully, but these errors were encountered: