| commit | 581b0bd6386a077e29107710e008983b62233ccf | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Thu Mar 12 13:36:43 2020 +0100 |
| committer | Serge Bazanski <serge@nexantic.com> | Thu Mar 12 13:36:43 2020 +0100 |
| tree | 85cf721d9711e7adc88c744c55ee12a96ee7114d | |
| parent | 79d7a625709242204993cffbd99ed734dc1c50a5 [diff] |
init: remount to tmpfs runsc needs to be able to pivot_root. According to @lorenz this does not work from initramfs. This introduces a temporary fix to re-mount and re-exec into a new root based on tmpfs. A proper fix would be to use a real filesystem instead of initramfs (like squashfs), but this will do for now. We also use this opportunity to use devtmpfs instead of manually managing /dev. This collides with the storage manager that tries to create all storage nodes - we just remove that. Test Plan: shouldn't change behaviour X-Origin-Diff: phab/D433 GitOrigin-RevId: aa59fec6551bab1b1b9c2fe037dce410e550981b
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.