build: run nightly builds against selenium snapshot #2384
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asolntsev
requested review from
SrinivasanTarget,
mykola-mokhnach,
saikrishna321 and
valfirst
as code owners
asolntsev
force-pushed
the
run-nightly-builds-against-selenium-snapshot
branch
6 times, most recently
from
a0a6557 to
8b78518
Compare
Now GA build contains two steps: 1. Build with Selenium 4.41.0-SNAPSHOT (the latest nightly build) 2. Build with Selenium 4.40.0 (currently stable version) It will help to detect compatibility problems with the latest Selenium changes on an early stage.
asolntsev
force-pushed
the
run-nightly-builds-against-selenium-snapshot
branch
from
8b78518 to
73ea421
Compare
4 tasks
asolntsev
changed the title
valfirst
reviewed
Jan 27, 2026
| # echo ">>> $latest_snapshot" | ||
| # echo "latest_snapshot=$latest_snapshot" >> "$GITHUB_ENV" | ||
| # ./gradlew clean build -PisCI -Pselenium.version=$latest_snapshot | ||
| - name: Build with Gradle against Selenium nightly build |
Collaborator
There was a problem hiding this comment.
I think it's not "nightly" here
Contributor
Author
There was a problem hiding this comment.
I think it's not "nightly" here
Yes, it's an incorrect name for the PR. :)
So we have to choose one of two strategies:
- Run every build against two Selenium versions (like now)
- Run a separate nightly build from main branch against nightly Selenium build
@valfirst Which one do you prefer?
mykola-mokhnach
approved these changes
Jan 27, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change list
Try to build the project with the latest Selenium x.y.z-SNAPSHOT version (nightly build).
It would help to detect compatibility issues with the latest Selenium changes on an early stage.
The snapshot version is taken from https://raw.githubusercontent.com/SeleniumHQ/selenium/refs/heads/trunk/java/version.bzl
Alternatives
Another approach (probably better) is to create a separate GitHub Action script that will be executed nightly (independently from PRs).
In Selenide, we run such a job at 6:06 every night: https://github.com/selenide/selenide/blob/main/.github/workflows/test-with-selenium-nightly-build.yml
Types of changes
It would help to avoid issues like this: #2383
@valfirst @mykola-mokhnach