Bamboo - After failed deployment SSH tasks throw permission errors

Todd Ellner

We have a deployment task for moving .wars and service configuration from Bamboo builds to tomcat test servers.

1. Clean working directory
2. Artifact download
3. SCP Task- Copy war to server
4. SSH - Clean next folder
5. SSH - Explode war
6. SSH - Explode serverconfig
7. SSH - restart server

If the process is interrupted or times out the next deployment fails on step 4 ( rm -rf /opt/acton/tomcat/releases/theapp-next ) with a flood of "permission denied".

The user and ssh key in those steps have access to the directories. When I log in with them I can clear out theapp-next by hand and subsequent deployments succeed.

Does anyone know what causes this behavior and how to work around it?

rsperafico

Hello Todd,

Thank you for your question.

At this stage is difficult to say what is going on as it would be better having the build log to verify the tasks you are running and their output. Would be possible to provide those information, please?

Also, I would suggest you on running the same commands from Terminal using the same user running Bamboo just to narrow this issue down and determine if the issue is related to Bamboo or the tasks you are running, please.

—

Kind regards,
Rafael P. Sperafico
Atlassian Support