Command-Line Tools: Write Useful Exit Codes
A script prints an error but exits successfully, so CI treats failure as success. This guide gives you a small, testable way to approach the issue before changing a live system.
A practical workflow
- Return zero for success and a nonzero status for a failed operation.
- Test invalid input, missing files and interrupted work from a shell script.
What to check
Write diagnostic messages to standard error and avoid exposing secrets in logs. Compare the result with the original problem and record what changed. If a measurement or test does not support the change, revisit the assumption rather than adding more complexity.
Keep the experiment small enough to reverse. Document the starting state, the change and the result so another person can repeat the process. Product menus and versions can change, so check the current documentation for your environment.
Official reference: Read the documentation.