Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,725
Community Members
 
Community Events
176
Community Groups

Why are my pipelines suddenly failing with "command not found" errors

My pipeline has randomly started failing. The first step reads:

- step:
  name: Build simulation
  script:
     - rsync -av --progress . dist --exclude dist
  artifacts:
     - dist/**

It's failing with the log:

+ rsync -av --progress . dist --exclude dist
bash: rsync: command not found
bash: lesspipe: command not found
bash: dircolors: command not found

First I thought it was an issue with rsync, but actually, whatever I have tried fails similarly, eg:

bash: ssh: command not found
bash: apt-get: command not found

Just to emphasis, it was initially working fine, and now it seems like the container doesn't have anything installed in it. Does anyone know what is going on here? Cheers.

1 answer

0 votes

Hey Jonathan,

Without being able to see your pipelines configuration, there is a possibility that you are using a variable named "PATH" somewhere in your workspace which is conflicting with the default "PATH" variable which is prepended/required for every command in pipelines and will cause this error for every command when a conflict is present.

We also have a public ticket highlighting the same - if this variable exists as a custom variable (either in deployment, repository or workspace variables), please remove or rename it and try to run the build again:
https://jira.atlassian.com/browse/BCLOUD-20162

If this is not the case, please let me know and we can open a ticket on your behalf.

Cheers!

- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events