* all browser tests run in one suite
* remove separate headless test - just use the bazel flag for any browser
* move fsutil command for short names on windows to bazel
* maybe unit tests need to be single threaded for windows
* Update pinned browser versions
* [rb] Enabling passing test
* [java] Fixing testShouldDoNothingIfThereIsNothingToGoBackTo
* Fixing more tests
* Running test only for Chrome and Edge
* Executing NetworkInterceptorRestTest in GH runners
* Skipping test for FF beta for now
* Adjusting workflows
---------
Co-authored-by: Selenium CI Bot <selenium-ci@users.noreply.github.com>
Co-authored-by: Diego Molina <diemol@users.noreply.github.com>
Co-authored-by: Diego Molina <diemol@gmail.com>
If it's there, then `bazel query "attr(tags, 'remote', tests(//java/...))`
would also return non-remote targets. This happens because Bazel queries
for partial match in attribute ("selenium-remote" contains "remote").
This commit introduces few major changes to the Selenium CI, overhauling
the current implementation to make it a bit more usable and maintainable.
1. Introduces high-level orchestrating "CI" workflow that is run on
every push to the main branch, every 12 hours, every pull request,
and manually. This workflow checks which bindings are affected by the
pushed changes and calls individual CI workflows, presenting all of
the results on a single page -
https://github.com/SeleniumHQ/selenium/actions/workflows/ci.yml.
2. Reworks every "CI - <Bindings>" workflow to be callable from other
workflows or run manually. The former is important for the "CI" workflow,
the latter is matter of convenience so that individual bindings CI
workflow can be run.
3. Individual bindings CI workflow are also implemented in a similar
manner with the following pipeline:
Build -> Documentation / Lint / Unit Tests -> Integration Tests
This allows to better balance the load across the CI runners queue,
preventing an immediate burst of queued runs.
4. Almost every CI pipeline step is implemented via a callable
bazel.yml workflow. It is responsible for setting up the whole
environment (browsers, Bazel caches) and greatly simplifies the
individual bindings workflow. The only exceptions not using it are
few JavaScript/Python tasks not migrated to Bazel and Rust pipeline.
6. Removes unnecessary installation of JDK because it's already taken
care of by Bazel.
7. Allows to start interacting SSH session inside CI upon failure. This
can be done by re-running a failed build with "Enable debug logging"
on.
8. Allows to force-run CI on pull requests if the title includes
[<bindings>] text. We could also fetch commits on this PR, but it
needs extra code and can be done later.
It provides cross-platform configuration of Bazel and fine-grained
caching for bazelisk, disk_cache, repository_cache and external
repositories resulting in faster CI builds.
This commit lands a support for public read-only remote Bazel cache
stored on Google Cloud Storage at
https://storage.googleapis.com/seleniumhq-bazel-remote-cache. The
storage bucket is public so anyone on the internet can use it to speed
up building Selenium locally.
The cache is written on the trunk CI builds by specifying
--remote_upload_local_results=true in CI .bazelrc. Likewise, Selenium
committers can write to the cache by getting the JSON key and adding
the following to the .bazelrc.local:
build --remote_upload_local_results=true --google_credentials=<path-to-json-key>
For now, the bucket is stored in @p0deje personal Google cloud and we
should eventually move it SeleniumHQ account if/once we have it.
