commit | 73e7122a7e030bcff95058e7b1460f4d7a0d5e46 | [log] [tgz] |
---|---|---|
author | Antoine Musso <hashar@free.fr> | Thu Oct 13 16:46:25 2022 +0200 |
committer | Antoine Musso <hashar@free.fr> | Fri Oct 14 13:31:42 2022 +0200 |
tree | 8cd62fa904d5f76fc6d5c34990b19567dbaed609 | |
parent | 4989f742e0ad4398e8bafbbbe5b0636a16b7894c [diff] |
Refactor eclipse/project.py to make it testable Move all the logic of tools/eclipse/project.py so it can be tested and add a few tests. Add a py_test target so one can run the tests from bazel using: bazel test --test_output=streamed //tools/eclipse:test Add a bunch of tests and a helper to generate a coverage report. The resulting coverage report can be checked by opening `tools/eclipse/htmlcov/project_py.html`. Change-Id: I03582d70a5ec28117ab6d3b4c098d84e12e3d8dc
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