| commit | 5be29dda1d099e1d72636aec06bd3995f39ae4d8 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Mon Jun 22 18:52:45 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Mon Jun 22 18:52:45 2020 +0200 |
| tree | b93a249b2f9cda93a07847708bc81be26be3ad12 | |
| parent | dbfc638fa03704d274f78b31f508dde1e37502ee [diff] |
scripts/create_container: fix cockroachdb startup After moving the build container to --net=host this broke building //... (as sqlboiler touches a local crdb in order to generate SQL boilerplate...). This moves cockroachdb to also run with --net=host, and fixes the advertisement address in the same way as it's fixed in run_ci.sh. Test Plan: tested this locally :/ X-Origin-Diff: phab/D562 GitOrigin-RevId: 8b4dcc2b5c3f87c48824d6e0eb665bea44e84116
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.