-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[🚀 Feature]: add nightly build #1712
Comments
We do want to have something like that in the near future, like offering a weekly build or so, but so far it is an issue of time, we do not have enough people to do something like this for now. |
@diemol, if we pick up binary selenium nightly to build and release images nightly, which tag name is suitable to tag those images? |
I would use |
Nightly images delivered via https://github.com/SeleniumHQ/docker-selenium/releases/tag/nightly |
Great, thank you @VietND96! This should be mentioned in the readme. |
Yes, I updated a short description in README for both docker and chart https://github.com/SeleniumHQ/docker-selenium?tab=readme-ov-file#nightly-images |
Looks good. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature and motivation
It would be helpful to have an image containing a nightly build of selenium (with the current latest stable browser version).
Many of us may be able to run such an image in our CI infrastructure and help to discover bugs and issues with selenium before a release is tagged if this we’re available.
Usage example
In our case we typically run the
selenium/standalone-chrome:latest
andselenium/standalone-firefox:latest
images, and we are currently planning to add additional builds for the beta tags of these images in the coming weeks. The hope is that this will help us discover any issues with those browsers, or their respective drivers ahead of time.We would also like to add similar builds for a nightly build of Selenium itself so that we can be more proactive in reporting any issues we encounter as a result prior to the release of that version so that fewer people are impacted by any issues.
The text was updated successfully, but these errors were encountered: