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,074
Community Members
 
Community Events
176
Community Groups

ssh-task shows command not found while running on connected server

Edited

I am using ssh-task in deployment job, this ssh-task is connected to server with ubuntu user where kubectl command are running.

When I am running same command directly on server, it working but when I am running it using job its showing command not found.

Is this due to ssh-task?

 

1 answer

0 votes

Hi @kswati,

It is possible that your problem is not Bamboo related but a constraint on how an SSH command is run. 

A command running with SSH does not get the same environment variables as if it was run with a logged in user on terminal. The reason is that we have a non-interactive terminal instead of an interactive one.

You should see completely different results from

Env as and SSH command:

$ ssh user@localhost 'env'

Env from terminal:

$ env


Suggestion for troubleshooting

  1. Check if you are able to run the command you need without Bamboo, but sending it through an ssh command line as the command above for 'env'.
  2. If you experience the same problem the reason might be a missing environment variable. In this case you will need to source the variable in the SSH command or add the full path to executable.
  3. In case you don't reproduce the problem, please send us the SSH task details so we can check them,

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events