You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the great project! I'll preface this with I'm a Rails/Ruby newb.
I'm curious if anyone has got this to run with parallelization using knapsack-pro-cypress? I'm guessing the answer is no, because knapsack-pro-cypress calls Cypress internally using node and cypress-rails calls node from within Ruby to build the commands plus bootstrap itself.
Based on this code from launches_cypress.rb, it takes Cypress CLI options in, so --parallel would work.
But using --parallel requires the Cypress dashboard from what I've understood. I'm not certain of this, the last place I used Cypress had another team handle setting up parallelization on a private cloud.
knapsack-pro-cypress accepts supported Cypress CLI options, so off hand, if we were able to pass in a different node module than cypress, i.e. knapsack-pro-cypress, I think this could work.
One thing that would likely work in your case is to not install cypress locally to the project (such that "node_modules/.bin/cypress") did not resolve, and then to put a custom script on your PATH named cypress that calls the thing you want.
I don't think I'd be eager to add an additional option for custom / non-cypress executables
Thanks for the great project! I'll preface this with I'm a Rails/Ruby newb.
I'm curious if anyone has got this to run with parallelization using knapsack-pro-cypress? I'm guessing the answer is no, because knapsack-pro-cypress calls Cypress internally using node and cypress-rails calls node from within Ruby to build the commands plus bootstrap itself.
Based on this code from launches_cypress.rb, it takes Cypress CLI options in, so
--parallel
would work.But using
--parallel
requires the Cypress dashboard from what I've understood. I'm not certain of this, the last place I used Cypress had another team handle setting up parallelization on a private cloud.knapsack-pro-cypress accepts supported Cypress CLI options, so off hand, if we were able to pass in a different node module than
cypress
, i.e.knapsack-pro-cypress
, I think this could work.I see in finds_bin.rb,
cypress
is hard-coded.If an optional node module name could be passed in as an argument (default = "cypress"), then I think this could all work together.
My question turned into solutioning lol. Anyways, thoughts?
For some more context, this is currently how I have us set up to run knapsack or just cypress.
and Ideally have it something like this
Also, I'm happy to contribute to any work this would involve.
The text was updated successfully, but these errors were encountered: