Non zero exit code from a custom command building install step in jitpack.yml is ignored

[vorburger]

Inspired by #3129,

I'm working on published my https://bazel.build -based project on JitPack in enola-dev/enola#970,

and found what to me appears to be a (minor) but in JitPack's error handling of Non zero exit code from a custom command building install step:

Given this jitpack.yml,

which make JitPack invoke this script,

causes https://.io/com/github/enola-dev/enola/d9fcbc02fb/build.log, copy/pasted here for preservation:

Running install command:
tools/maven/install.bash
+ bazelisk build //java/dev/enola
tools/maven/install.bash: line 22: bazelisk: command not found
Build tool exit code: 0
Looking for artifacts...
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
Looking for pom.xml in build directory and ~/.m2
Found artifact: dev.enola:enola:1.0.0-SNAPSHOT
2024-12-29T18:40:38.167527864Z
Exit code: 0

That doesn't sound right, to me... if bazelisk: command not found, then it wasn't (should be) exit code: 0... agreed?

PS: I'm only filing this issue to report a sub-optimal error handling. I'll separately fix the actual issue of installing the missing https://github.com/bazelbuild/bazelisk.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[jitpack-io]

Thank you for reporting!
We have rolled out a fix for this issue