| commit | 96b72a12e288a15df54552f37707738de5e230a3 | [log] [tgz] |
|---|---|---|
| author | Han-Wen Nienhuys <hanwen@google.com> | Tue May 14 09:41:16 2019 +0200 |
| committer | Han-Wen Nienhuys <hanwen@google.com> | Tue May 14 09:41:16 2019 +0200 |
| tree | 14f9bf045a9a29b91fcf07427961c6d7ce36f667 | |
| parent | 5036795734c1059905de382f9233e5c5be4a4d68 [diff] |
build-deploy: make google-java-format.jar +x
This is a style verifier intended to be used with the Gerrit checks plugin.
go install github.com/bazelbuild/buildtools/buildifier curl -o google-java-format.jar https://github.com/google/google-java-format/releases/download/google-java-format-1.7/google-java-format-1.7-all-deps.jar
Obtain an HTTP password, and put it in testsite-auth. The format is username:secret.
Register a checker
go run ./cmd/checker -auth_file=testsite-auth --gerrit http://localhost:8080 \ --language go --repo gerrit --register
go run ./cmd/checker -auth_file=testsite-auth --gerrit http://localhost:8080 \ --list
go run ./cmd/checker -auth_file=testsite-auth --gerrit http://localhost:8080
For simplicity of deployment, gerritfmt checker is stateless. All the necessary data is encoded in the checker UUID
handle file types (symlink) and deletions
more formatters: clang-format, typescript, jsformat, ... ?
isolate each formatter to run with a separate gvisor/docker container.
tests: the only way to test this reliably is to spin up a gerrit server, and create changes against the server.
Update the list of checkers periodically.
This currently runs the formatters without sandboxing. Critical bugs (heap overflow, buffer overflow) in formatters can be escalated to obtain the OAuth2 token used for authentication.
The currently supported formatters are written in Java and Go, so this should not be an issue.
This is not an official Google product