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

"After successful build plan" deployment trigger not working

David Gard September 26, 2019

I have added a "after successful build plan" trigger to a deployment plan, but it does not seem to be working.

The wording states the following...

When a deployment is automatically triggered, a new release is created from the latest successful build result of the linked plan.

However, this does not seem to be the case, as 15 minutes after a successful build, no release has been created, and thus nothing has been deployed.

The build plan has only one stage, and all jobs completed successfully; the build is not waiting for manual intervention.

I'm running Bamboo version 6.9.1.


1 answer

0 votes
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 1, 2019

Hi @David Gard

According to your description, the build deployment should be triggered after the build.

Would you mind double-checking the plan and selected branch by going to Deployment configuration >> Edit build plan >> Linked build?

Other checks to help troubleshooting this:

  • Do you have other plans where a similar configuration is working?
  • Did this plan work in the past with this configuration?
  • Are you building the same branch configured in the deployment build plan configuration?
  • Have you checked the server logs at <Bamboo_Home>/logs/atlassian-bamboo.log ?

I hope the above will helps us to narrow down what is causing this issue.

David Gard October 2, 2019

Thanks for your reply,

With regards to the build plan - yes, the correct plan is linked. I can manually create a release and deploy it.

In answer to your other questions -

  • No.
  • N/A
  • I'm building the branch specified in the deployment trigger.
  • I've tried, but there is so much in there it's impossible to know if any of it is relevant to me.
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 7, 2019

Hi @David Gard

Things I would try to move forward:

  1. Create a new plan and new deployment for this plan. Add the trigger and check if this will fail as well.
    This will allow us to see if this issue is only present in the build/deployment you already have.
  2. Reproduce the problem and share the logs:
    1. Run the build
    2. Check what time the build finishes with success
    3. Get the log entries from that time and the next 1min
    4. Check if there are any errors in them
    5. If you don't find anything that you consider a problem, please send this piece of logs to us.
      Please verify if there is any private information that needs to be anonymised first.
  3. Try to share the set of steps you run to configure this. It might help us to reproduce the issue locally.

Please let me know your thoughts and comments.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events