Exits with status=0 when signing fails

[salomvary]

• Version: 19.55.3

• Target: macOS

When dist or release fails due to misconfigured code signing certificates the process exits with zero status after printing out the errors. Expected: exit status should be non-zero, signaling a failure.

Example output: https://travis-ci.org/salomvary/soundcleod/builds/335354664

[develar]

Set forceCodeSigning to true.

[salomvary]

Set forceCodeSigning to true.

Maybe print this note after the giant red stack trace that follows failure? :)

[salomvary]

Actually, it does not seem to build anything (note the absence of "• building ..." lines in the output).

[salomvary]

@develar So I have forceCodeSigning set to true and the exit status is still zero despite signing fails die to untrusted certificate. See the output here.

Btw. is there any way to force accepting self-signed certificates on CI? While I can manually set it trusted locally with Keychain Access, not sure what the equivalent of that is in on a CI.