tasckat action always exits with error code 0 about action-taskcat

[muktadadariya]

Can I use pipefail with "taskcat test clean "?

[ShahradR]

Can I use pipefail with "taskcat test clean "?

@muktadadariya I think that should work! The pipefail option controls which exit codes are returned in Bash pipelines – as long as taskcat returns a non-zero exit code, pipefail should be able to catch that.

For your specific example, we can run taskcat test clean ALL | echo "Hello World" in a scenario where taskcat returns an error (in my case, I enabled termination protection on the stack). When pipefail isn't set, we won't catch the error because echo "Hello World" runs last and always returns 0. Once set, taskcat's exit code of 1 is returned by the pipeline instead.

Running pipeline without the pipefail option set

Running pipeline with the pipefail option set

For more info on the subject, Tom Van Eyck's blog post details the pipefail option along with a bunch of other ones you can set to make your shell scripts more robust. You can also take a look at the "Pipelines" section of the Bash reference manual for information on Bash pipelines in general. Hope this helps!

[github-actions]

🎉 This issue has been resolved in version 1.0.0-develop.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 1.0.0-develop.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀