| commit | 60a85b669e05f788bc63663568102a23c78d6195 | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Sun Nov 17 19:12:41 2019 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Sun Nov 17 19:12:41 2019 +0100 |
| tree | f7dcac1fcabe86b8cd1afa317284e309d43916cf | |
| parent | d868d69320140863a1938bfa042ad0824cfa9500 [diff] |
Run go vet using nogo during build step See https://github.com/bazelbuild/rules_go/blob/master/go/nogo.rst These are correctness checks, not coding style linters, such that compilation will fail if they do not pass. They are also ran for external dependencies, with more or less fine-grained exclusions. Test Plan: Ran gazelle.sh and tests. Bug: T472 X-Origin-Diff: phab/D269 GitOrigin-RevId: f932555ec8cbb9d0c09f2a3c6a0df94a0f6724a8
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora 30 or 31 host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.