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
Remove mention of Heroku CI support #324
Comments
Hey @Pro777, yeah, I tried updating the stack to
I don't think that Heroku CI should be removed, as I don't see why xvfb wouldn't work in Or, cypress-io/cypress#832 would make Cypress compatible with Chrome Headless, and no xvfb would be needed. |
correct @bahmutov, Electron still needs a display manager to run, so we still need |
I will disable our CI Heroku project, because it just keeps failing, breaking our status checks, but I will keep this issue open, because once we remove Electron we should enable it back |
Ok interesting, I was fighting with heroku and not understunding why i had this SIGILL Error since i was folowing all the steps. I had the project detected in cypress dashboard (but no info about it). So this is due to this deprecated build of chrome. So @bahmutov do we have a roadmap of when electron will be removed? |
You can follow the issue about removing Electron from Cypress core here: cypress-io/cypress#3899 |
Cedar-14 stack EOL has been delayed until November 2, 2020 due to COVID-19. |
I am currently writing a bunch of cypress test right now and we use Heroku CLI, will this not work if we want to make it part of the pipeline? |
Unfortunately because of Heroku limitations I don't think Cypress can run on it unless we make it fully headless so it does not need xvfb. I would suggest trying another CI that could even be triggered after Heroku finishes the deploy |
I would like to use cypress on the heroku ci. Is there no other way to make it work? |
I'm sorry this issue got re-opened, but it looks like there is some hope with this issue/pr |
Heroku's cedar-14 stack is now EOL.
The heroku buildpack required for Cypress to function is not compatible with newer stacks, so can references to compatibility with Heroku CI be removed?
The text was updated successfully, but these errors were encountered: