I have 2 SSH and one SCP task in my deployment plan, all connecting to a server TJiraHost.ac.local on the local network using port 22.
These tasks seem to fail 99% of the time and then occasionally they succeed.
Whats even more interesting is that whilst this is failing, if I manually SSH using putty from the box on which the Bamboo server is running to TJiraHost.ac.local on port 22 (using the same login details) the putty connection succeeds - every time.
Therefore, I know the hostname, port, username and password are correct, but I cannot figure out why Bamboo fails whilst putty succeeds.
At first I thought it may be related to the keep alive so I set this to 5s for each task and still faced the same issue.
Just for completeness, TJiraHost is running CentOS and the Bamboo server is a Windows server.
This ended up being purely a network based error.
Essentially, the builds were occurring 99% of the time on a remote agent, from which the SSH connections would also then be attempted. However, this remote agent was not able to see the deployment server due to subnet issues.
The other 1% of the time the SSH connections were made on the local agent (the machine from which I successfully tried SSH using putty). This local agent was able to see the deployment server as it had visibility of both of our subnets. This meant in these 1% of deployments the SSH tasks passed without issue.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs