Bitbucket "Pipe X failed"

A pipe: step exited non-zero. The pipe ran but its task failed - a missing required variable, a wrong pipe version, or an error from the service it calls (deploy target, cloud API). The real reason is in the pipe's own output above the failure line.

What this error means

The step ends with ✖ pipe failed naming the pipe. The lines above describe the actual problem - a missing variable, an auth error, or a downstream API error.

✖ Variable "S3_BUCKET" was not provided.
✖ pipe failed (atlassian/aws-s3-deploy:1.1.0)

Common causes

Missing or wrong pipe variable

Pipes declare required variables. Omitting one, or passing the wrong type, makes the pipe fail before it does its work.

Downstream error or wrong pipe version

The pipe may fail from the service it calls (access denied, not found) or from a pinned version with different inputs than you provided.

How to fix it

Provide the required variables and pin a known version

Pass every required variable and reference a valid pipe version.

- pipe: atlassian/aws-s3-deploy:1.1.0
  variables:
    AWS_DEFAULT_REGION: 'us-east-1'
    S3_BUCKET: 'my-bucket'
    LOCAL_PATH: 'dist'

Read the pipe output for the real error

1. Scroll above the pipe failed line to the pipe's own error message.
2. Fix the missing variable, auth, or downstream issue it reports.
3. Check the pipe README for the version's required variables.

How to prevent it

• Provide every required variable a pipe declares.
• Pin pipes to a known version and read its README.
• Check the pipe's own output for the underlying error.

Related guides