Bamboo build tasks not triggering Deployment plan where it is configured correctly.

Devendar Gangapuram
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2024

Hi Team,


We have below 2 tasks in "BUILD plan" in Bamboo 9.2.10 , and after this build execution, it has to pass "release number" to "deployment plan". But on Build plan execution, it is gong to queue for longer time because it is trying to connect a bitbucket "" , which is not past of the build tasks execution. 


Task(1):create a properties file:-

echo pom.releaseVersion=${} > ""
echo pom.artefactId=hello-world-service >> ""
echo AppZ_anypoint_mule_version=3.8.4 >> ""


Task(2): Inject for deploy plan

Path to properties file(required)
Relative to the build's working directory.
Namespace is used to avoid name conflicts with existing variables.
Scope of the variables
Variables will only be available in this job.



But while build is executing , it is going to Queue for longer time , and in logs I found below error.


process for build 'Retail Transformation - hello-world-service-uat - Default Job #27 (RT-HEW1UAT-JOB1-27)'\n ... running command line: \n/anw/bamboo/application-data/temp/\n ... in: /anw/bamboo/application-data/local-working-dir/3145729/RT-HEW1UAT-JOB1\n
2024-02-20 07:25:20,562 INFO [NavLink RestCapabilitiesClient:thread-1] [RetryExec] I/O exception ( caught when processing request to {s}-> Connection reset
2024-02-20 07:25:20,562 INFO [NavLink RestCapabilitiesClient:thread-1] [RetryExec] Retrying request to {s}->
2024-02-20 07:27:18,451 INFO [RemoteEvents CapabilitiesCacheLoader:thread-1] [RetryExec] I/O exception ( caught when processing request to {s}-> Connection reset
2024-02-20 07:27:18,451 INFO [RemoteEvents CapabilitiesCacheLoader:thread-1] [RetryExec] Retrying request to {s}->
2024-02-20 07:27:39,124 INFO [18-BAM::CD Agent::Agent:pool-31-thread-1] [BuildAgentControllerImpl] Agent 17006593 checking build queue for executables...


Please help me how to resolve this error. 




Thank you,

Dev G


1 answer

0 votes
Khushboo Gupta
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 20, 2024

Hello @Devendar Gangapuram


From your description, it seems like you're having issues with your Bamboo build plan getting stuck in the queue for a long time. This is happening because it's trying to connect to a Bitbucket server at ``, which isn't part of your build tasks execution. From the logs that you have provided, it seems that a service is trying to connect to a Bitbucket repository located at ``

We looked at the script you sent, and it appears you used more command to display the content of the file. I think this is because the "more" command is executing the script task repeatedly. Kindly see whether using the "cat" command solves the problem.



Are the error logs you sent from the same build as well? If yes please follow below : 

  • Please check you Bamboo configuration as well as Bamboo plan configuration to make sure there are no tasks or dependencies that require access to the Bitbucket server. 
  • Check Web-hooks in Bitbucket: Bitbucket can use web-hooks to notify Bamboo about changes, which can then trigger builds. 

Or if you are connecting to another Bitbucket server you need to manually update your repositories in Bamboo to get the new SSH Base URL. If you have too many repositories to manually update, you can use the workaround on the below feature request to update them in bulk via a SQL query on your Bamboo database:



Khushboo Gupta

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events