| commit | 3ff5af330857b2aadcdae9d9e6ca37b7e5d2c56e | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Wed Jun 24 16:34:11 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Wed Jun 24 16:34:11 2020 +0200 |
| tree | 9792637a9babc59ab73baaafbd370c5ba8a5bd5a | |
| parent | e50ec399203fa409bfb405169e19f86141d71336 [diff] |
Expand launch infrastructure and make dependencies use it Adds support for launching MicroVMs and networking multiple machines to the launch infrastructure and its consumers. Also makes use of our own qboot. Also converts ktests to that infra and and fixes the issue making it succeed if the VM couldn't be started. Test Plan: E2E tests & ktests still pass X-Origin-Diff: phab/D571 GitOrigin-RevId: 0f317f6d8a06e4a3da343b4a7ff5c87918401426
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.