| commit | fc5dbc6646c6e332f5cbb88f6a68b6fbcffebe77 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Thu May 28 12:18:07 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Thu May 28 12:18:07 2020 +0200 |
| tree | 4ea7cb93b2f0abfca9f547ee1401d39b73a79f5d | |
| parent | 140bddcbe1aac46b168f6fc2178eb9c3870a434c [diff] |
Add E2E tests for basic functionality and port launching to Go This adds a new E2E test suite replacing the old log-parsing based one. It also moves launching and controlling Smalltown VMs into a Go package and command and exposes the '//:launch' alias. The new E2E test suite covers basic conditions (IP assigned, Data available) and Kubernetes Node, Deployment and StatefulSet tests. Test Plan: This consists of E2E tests X-Origin-Diff: phab/D544 GitOrigin-RevId: 7c624c667c849068bafa544a3a6c635d6d406e1c
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.