CodeBuild: each buildspec command runs in its own shell, cd does not persist

CodeBuild: each buildspec command runs in its own shell, cd does not persist

TL;DR

In a CodeBuild buildspec, never rely on cd from a previous command line; chain commands with && in a single line. And remember post_build runs even on failure, so guard any notify-or-publish step on the build status variable. Context: From a community AWS CI/CD guide.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Each command in a CodeBuild buildspec runs in its own shell, so a cd in one command does not persist to the next. Chaining with && or putting the work in one command block is the fix. The same guide notes postbuild runs even when the build phase failed (guard on CODEBUILDBUILD_SUCCEEDING), and that a missing artifacts block means later stages never see your output.

Source: From a community AWS CI/CD guide. Each command in a CodeBuild buildspec runs in its own shell, so a cd in one command does not persist to the next. Chaining with && or putting the work in one command block is the fix. The same guide notes postbuild runs even when the build phase failed (guard on CODEBUILDBUILD_SUCCEEDING), and that a missing artifacts block means later stages never see your output.

Verified resolution: In a CodeBuild buildspec, never rely on cd from a previous command line; chain commands with && in a single line. And remember post_build runs even on failure, so guard any notify-or-publish step on the build status variable.

Source URL: https://github.com/sreen98/prephub/blob/HEAD/src/content/devops/aws-cicd-guide.md