| commit | f64021170952839c39f25e13e8771d8e377af898 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Mon May 04 16:50:31 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Mon May 04 16:50:31 2020 +0200 |
| tree | 06b4841b976cba50dea2f567d300ae2a5b355a14 | |
| parent | bb7db92ee6e788b576e22ece70914e0321a785f7 [diff] |
Enable stamping and use correct variables In D487 stamping was introduced, but not actually enabled. This enables it. Kubernetes also uses "volatile" stamping variables for things that logic depends on. This is a terrible idea because you cannot unbreak a build since volatile stamps don't trigger a rebuild. The status variables which are not purely informational have been changed to "stable" variables (see https://docs.bazel.build/versions/master/user-manual.html#flag--workspace_status_command). Test Plan: By itself not really testable, but has been tested on an upcoming revision that actually depends on stamping behaving correctly. X-Origin-Diff: phab/D491 GitOrigin-RevId: 48dda066d56e29d10fb0f0a88a845d8caf527c98
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.