| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Since: [1] Bazel changed the list of resource file locations.
Adapt to that list and move `%workspace%/tools/bazelrc` to
`%workspace%/.bazelrc`. See: [2], [3] for more details.
[1] https://github.com/bazelbuild/bazel/commit/ec83598
[2] https://github.com/bazelbuild/bazel/issues/4502
[3] https://github.com/bazelbuild/bazel/issues/5756
Change-Id: Ia13c71bcff7036e2f5541618b28713d9b0d77040
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
.bazelrc is for user settings that are specific to the workspace, it is
not supposed to be checked in the code repository. The correct path for
the checked in version should be tools/bazel.rc
TEST PLAN:
Verify that workspace status command still works:
$ bazel build :gen_version
Reported-by: Damien Martin-guillerez <dmarting@google.com>
Change-Id: I91d3859b6bacd3b0c96c52324cd2bbdf2705197b
|
|
|
|
|
| |
Reported-by: Damien Martin-guillerez <dmarting@google.com>
Change-Id: I1a688a9c737129e0bb280b984ed16d09bd84bdf7
|
|
|
|
|
|
|
|
|
| |
bazel: generate the workspace version from the volatile status.
To work across bazel 0.3.1 and 0.3.2, we should grep both volatile and
stable status files for the magic version string.
Change-Id: I48361374a8d9cda1e7a5b5db4e147bc49b4452a3
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel 0.3.2 introduced regression: [1] workspace_status_command seems to
be ignored. That broke Bazel build. Revert this change and re-consider to
re-apply it, when the problem is fixed upstream.
* [1] https://github.com/bazelbuild/bazel/issues/1976
This reverts commit 214171ddda6c173e528affee625aa65db8dcc360.
Change-Id: I729ffaf6ae1bff5fb858d78de2a6915058c9e651
|
|
|
|
|
|
|
|
|
|
| |
This generates a version file that looks correct, but doesn't rebuild
correctly. Correct rebuilds will be provided by a version of
bazel containing
https://github.com/bazelbuild/bazel/commit/a2897bff4c16c07793279f425d2627ce7bf3e232
Change-Id: I5101d7f2643d464cf32c8281a28ec6c3fc4fa2cf
|
|
To run the tests:
bazel test //...
To build the Gerrit plugin API, run:
bazel build gerrit-plugin-api:plugin-api_deploy.jar
To build the Gerrit extension API, run:
bazel build gerrit-extension-api:extension-api_deploy.jar
TODOs:
Licenses
Reduce visibility (all public for now)
Generate HTML Documentation
Core plugins
gerrit_plugin() rule to build plugins in tree and standalone modes
GWT UI (only gwt_module() skylark rule is provided, no gwt_binary())
PolyGerrit UI
WAR
Publish artifacts to Maven Central
Ask Bazel team to add Gerrit to their CI on ci.bazel.io
Contributed-By: Han-Wen Nienhuys <hanwen@google.com>
Change-Id: I9a86e670882a44a5c966579cdeb8ed79b1590de3
|