| commit | 40fe63dc04b90d4a60b931b41da0abda321e73c7 | [log] [tgz] |
|---|---|---|
| author | Nasser Grainawi <nasser.grainawi@linaro.org> | Fri May 17 16:34:09 2024 -0600 |
| committer | Nasser Grainawi <nasser.grainawi@linaro.org> | Fri May 17 16:34:09 2024 -0600 |
| tree | ec8a374dc796fb2ccc904bb72ef3383a5ca6f473 | |
| parent | 07d08b6204c54d5e0e785ccaa9a1f40fb62420e5 [diff] |
Bump NodeJS version to 20.9.0 This brings in support for NodeJS 20.9.0 in the same way as done by Gerrit core change I610f0063fa70f36ead170d3bc85cc9f1928f924c. We are using rules_nodejs 5.8 release line that stopped becoming NodeJS version updates. Patch `private/node_versions.bzl` from rules_nodejs in place to consume new NodeJS versions. As pointed out in this feature request: [1], currently used rules_nodesjs 5.x release line will not become any new updates. The way forward is to migrate to rules_nodejs 6.x or to rules_js. [1] https://github.com/bazelbuild/rules_nodejs/issues/3703 Change-Id: Iee1b3d6fe60592369ea656cdefb700959f879f62 Release-Notes: skip
These build rules are used for building Gerrit Code Review plugins with Bazel. Plugins are compiled as .jar files containing plugin code and dependencies.
To be able to use the Gerrit rules, you must provide bindings for the plugin API jars. The easiest way to do so is to add the following to your WORKSPACE file, which will give you default versions for Gerrit plugin API.
git_repository( name = "com_googlesource_gerrit_bazlets", remote = "https://gerrit.googlesource.com/bazlets", commit = "928c928345646ae958b946e9bbdb462f58dd1384", ) load("@com_googlesource_gerrit_bazlets//:gerrit_api.bzl", "gerrit_api") gerrit_api()
The version parameter allows to override the default API. For release version numbers, make sure to also provide artifacts' SHA1 sums via the plugin_api_sha1 and acceptance_framework_sha1 parameters:
load("@com_googlesource_gerrit_bazlets//:gerrit_api.bzl", "gerrit_api") gerrit_api(version = "3.2.1", plugin_api_sha1 = "47019cf43ef7e6e8d2d5c0aeba0407d23c93699c", acceptance_framework_sha1 = "6252cab6d1f76202e57858fcffb428424e90b128")
If the version ends in -SNAPSHOT, the jars are consumed from the local Maven repository (~/.m2) per default assumed to be and the SHA1 sums can be omitted:
load("@com_googlesource_gerrit_bazlets//:gerrit_api.bzl", "gerrit_api") gerrit_api(version = "3.3.0-SNAPSHOT")
Suppose you have the following directory structure for a simple plugin:
[workspace]/ ├── src │ └── main │ ├── java │ └── resources ├── BUILD └── WORKSPACE
To build this plugin, your BUILD can look like this:
load("//tools/bzl:plugin.bzl", "gerrit_plugin") gerrit_plugin( name = "reviewers", srcs = glob(["src/main/java/**/*.java"]), manifest_entries = [ "Gerrit-PluginName: reviewers", "Gerrit-Module: com.googlesource.gerrit.plugins.reviewers.Module", ], resources = glob(["src/main/**/*"]), )
Now, you can build the Gerrit plugin by running bazel build <plugin>.
For a real world example, see the reviewers plugin.
gerrit_plugin(name, srcs, resources, deps, manifest_entries):
<name>.jar: library containing built plugin jar