| commit | efb028fdc542dd2f19bf74a3be98506e7a15c7b7 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Tue Jul 28 17:04:49 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Tue Jul 28 17:04:49 2020 +0200 |
| tree | 778c7ccea019f423ca9f660125fe8898014aa9d8 | |
| parent | 8b0431a9d22b1f2bb8ab3e6eb66ffda5ca4a2ea9 [diff] |
Allow applying patches before BUILD file generation This adds support for patching Go dependencies before BUILD file generation and also plumbs that support into fietsje. No actual prepatching is done in this revision. Test Plan: This has been used successfully in code built on top of it. X-Origin-Diff: phab/D612 GitOrigin-RevId: 7013e5f98feb57ac64ff3dc79d1a9bb94e4152a8
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)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //core/cmd/dbg -- kubectl describe
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.