Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Update cypress docker images automatically on release
See original GitHub issueCurrent behavior:
Cypress docker images are behind the cypress release
See the tags for cypress/included: https://hub.docker.com/r/cypress/included/tags
Currently the latest is 3.7.0, but 3.8.0 was released yesterday
Desired behavior:
An automated build should be setup to build the new docker images as soon as a release is cut
Versions
3.8.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Run Cypress with a single Docker command
We create new images for every Cypress version released. The image is built on top of the cypress/base:12.1.0 image with Node 12.1.0 included....
Read more >Docker Images - sorry-cypress
The images are automatically updated on each release and tagged in accordance with GitHub releases.
Read more >Automatically run Cypress tests on every code push ... - Medium
The Cypress GitHub action supports Docker natively, and Cypress also has their official Docker images hosted on Docker Hub, so with one line...
Read more >Docker full circle: Continuous Integration (CI) with Cypress
Have CircleCI monitor your code base and automatically build your production-ready Docker images and run your unit and Cypress end-to-end ...
Read more >kiwicom/cypress-cli - dockerfiles - Docker Hub
The images are built automatically by Docker Hub for the :latest tag, with updates of the base image triggering rebuilds.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@alexbrazier I merged in the docker-images PR now. I fully agree and have been advocating automating this for the last few releases.
I am thinking a webhook registered with NPM that gets notified on a new release that opens a pull request with new included folder? But then when does it get built - on merge to master? and pushed? Have to figure out how to build an image but only the new one