Blame: WORKSPACE - SeleniumHQ/selenium

A browser automation framework and ecosystem.

0 0 1275 Java

[bazel] Remove WORKSPACE mode in favor of bzlmod 2024-03-29 14:30:22 -07:00			`workspace(name = "selenium")`
[bazel]: Compile JS rules 2018-11-25 13:21:40 +00:00
Setting up bazel build rules for javascript stuff. I've covered most of the major stuff (excluding selenium-core). The closure bazel build rules are really strict and our code has hundreds of errors, so I've configured everything to suppress warnings; we can clean up later. There's one exception in selenium-atoms/text.js, where the build caught a reference to a variable that doesn't exist anymore - since I happened to notice that warning in particular, I went ahead and fixed it. With this change, I can `bazel build //javascript/...` using: $ bazel version Starting local Bazel server and connecting to it... Build label: 0.24.1 Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar Build time: Tue Apr 2 16:29:26 2019 (1554222566) Build timestamp: 1554222566 Build timestamp as int: 1554222566 2019-04-30 11:18:59 -07:00			`load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")`

[bazel] Remove WORKSPACE mode in favor of bzlmod 2024-03-29 14:30:22 -07:00			`# rules_closure are not published to BCR.`
[js] //javascript/node/selenium-webdriver now builds + tests with bazel 2019-05-05 14:49:34 -07:00
Fixing Bazel WORKSPACE python rule imports to work with Windows The python build rules were initially added in the WORKSPACE file using git_repository(); however, that workspace rule relies on bash commands, like `rf -rm`, which are not available on Windows. Changing the ruleset download to use http_archive() instead resolves the issue. 2019-08-19 16:07:45 -07:00			`http_archive(`
[bazel] Upgrade closure rules to 0.11.0 2020-11-10 12:28:55 +00:00			`name = "io_bazel_rules_closure",`
[bazel] Add integrity hash to closure rules to remove warning from console 2025-03-06 10:29:02 +00:00			`integrity = "sha256-lJjlc2jvuCuYXbHtQmp2fL8boDmP167WMvw5CGVOGx4=",`
[bazel] Switch to rules_closure 0.12.0 (#14895) 2024-12-12 13:40:50 +00:00			`strip_prefix = "rules_closure-0.12.0",`
			`url = "https://github.com/bazelbuild/rules_closure/archive/refs/tags/0.12.0.tar.gz",`
[bazel] Switch to rules_python for python rules 2019-08-07 14:55:51 +03:00			`)`

[bazel] Upgrade closure rules to 0.11.0 2020-11-10 12:28:55 +00:00			`load("@io_bazel_rules_closure//closure:repositories.bzl", "rules_closure_dependencies", "rules_closure_toolchains")`
Run buildifier over BUILD and WORKSPACE files 2019-11-12 14:41:19 +00:00
Ensure rules_proto comes from the module file (#13879) 2024-04-26 12:41:58 +10:00			`rules_closure_dependencies(`
			`omit_rules_java = True,`
			`omit_rules_proto = True,`
			`omit_rules_python = True,`
			`)`
[bazel] Switch to rules_python for python rules 2019-08-07 14:55:51 +03:00
[bazel] Upgrade closure rules to 0.11.0 2020-11-10 12:28:55 +00:00			`rules_closure_toolchains()`