Loop over rust test apps, building them. (#29)

e2e-setup-action/action.yaml

@@ -1,3 +1,20 @@
+# e2e-actions
+#
+# When adding new e2e apps that require compilation (such as a new Rust test app) you have to add
+# the building step here.
+#
+# For Rust apps, we have a little script (see # Build Rust test apps) that loops through the
+# existing directories doing a `cargo build`.
+#
+# Be very careful when adding new build steps, as they have an impact on every other PR in 
+# the `mirrord` repo.
+#
+# If you add a new build step, say to compile a Go program, but the code for this program is only
+# in your PR, then all other PRs will start failing, as they lack yours.
+#
+# The best way to add new build steps here is to either do something similar to what's being done
+# for Rust, or to do it as a conditional build, first checking if the directory/code exists before
+# calling a compiler.
 name: 'Setup mirrord e2e environment'
 description: 'Install all required dependencies for mirrord e2e tests'
 inputs:
@@ -46,21 +63,13 @@ runs:
     - run: | # Build Go test apps.
         ./scripts/build_go_apps.sh 20
       shell: bash
-    - run: |
-        cd tests/rust-e2e-fileops
-        cargo build
-      shell: bash
-    - run: |
-        cd tests/rust-unix-socket-client
-        cargo build
-      shell: bash
-    - run: |
-        cd tests/rust-bypassed-unix-socket
-        cargo build
-      shell: bash
-    - run: |
-        cd tests/issue1317
-        cargo build
+    - run: | # Build Rust test apps.
+        for cargo_dir in $(find tests -name Cargo.toml -printf '%h\n'); do
+            echo "Building test app in: $cargo_dir"
+            pushd "$cargo_dir"
+            cargo build
+            popd
+        done
       shell: bash
     # start last thing, to have previous steps faster (no cpu in background)
     - name: start minikube