| commit | da5cfaaf46e534220a52d9cf315ffe0a8c79c05d | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Mon Feb 24 10:07:10 2020 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Mon Feb 24 10:07:10 2020 +0100 |
| tree | 2b329e15589b360f430b615cfc50f212a7ce5ed8 | |
| parent | 1a5a667667849db21b533405245239445947b7fb [diff] |
Share Go pkg cache in CI This will decrease build times for scripts/gazelle.sh invocations, which will otherwise re-download all modules every time. There's likely a small risk of corrupting the shared cache, at which point it would have to cleaned manually. According to this GitHub issue, what we're doing is supported: https://github.com/golang/go/issues/26794 Due to the lockfile, this also serializes builds that need to download new packages. If this ever becomes an issue, we can create a per-working copy cache like we do for Bazel. Test Plan: Re-ran CI build multiple times, packages were not re-downloaded. Build time decreased by ~5-7s. X-Origin-Diff: phab/D374 GitOrigin-RevId: ec2f347d791f2915c5ecc04d9b67029de386aae9
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora 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.