CodeBuild keeps running commands after one fails: add fail-fast yourself
Shows how to fix codeBuild keeps running commands after one fails: add fail-fast yourself. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
If you want fail-fast behavior, add set -e at the top of a script or chain commands with && so a failure aborts the rest. Check the build logs per command to see which one actually failed rather than trusting the final phase status alone.
Steps
- [Stack Overflow q46584324]: in AWS CodeBuild, if a command in the build phase exits non-zero, CodeBuild marks the build failed but continues executing the remaining commands in that phase. If you want fail-fast behavior, add set -e at the top of a script or chain commands with && so a failure aborts the rest. Check the build logs per command to see which one actually failed rather than trusting the final phase status alone.
When to use
You are seeing this: [Stack Overflow q46584324]: in AWS CodeBuild, if a command in the build phase exits non-zero, CodeBuild marks the build failed but continues executing the remaining commands in that phase. Use this skill when you run into "CodeBuild keeps running commands after one fails: add fail-fast yourself".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.