pipelines/cargo: ability to override output-dir

Some projects exports the binaries to different paths so that we couldn't use the cargo/build pipeline properly. Signed-off-by: Dentrax <[email protected]>
chainguard-dev · Nov 19, 2024 · b526565 · b526565
1 parent 9b14cd2
commit b526565
Showing 1 changed file with 6 additions and 1 deletion.
diff --git a/pkg/build/pipelines/cargo/build.yaml b/pkg/build/pipelines/cargo/build.yaml
@@ -36,11 +36,16 @@ inputs:
       Directory where binaries will be installed
     default: bin
 
+  output-dir:
+    description: |
+      Directory where the binaris will be placed after building. Defaults to target/release
+    default: target/release
+
 pipeline:
   - runs: |
       # Installation directory should always be bin as we are producing a binary
       INSTALL_PATH="${{targets.contextdir}}/${{inputs.prefix}}/${{inputs.install-dir}}"
-      OUTPUT_PATH="target/release"
+      OUTPUT_PATH="${{inputs.output-dir}}"
 
       # Enter target package directory
       cd "${{inputs.modroot}}"