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,298,766
Community Members
 
Community Events
165
Community Groups

Bamboo tag trigger delay

Hi all,

 

I have a plan that is triggered by tag.

When I push the tag to the repo is takes quite some amount of time (in minutes like 3 to 5 I would say) before the plan is actually started.

Is that normal or I am missing something in my configuration.

My assumption was that it should be just like with the commit, almost imminent once the tag is pushed and visible in BitBucket.

What I am experiencing looks more like bamboo pooling for tags.

If so, can I increase the frequency (my users are complaining)?

 

best

Mariusz

1 answer

1 accepted

0 votes
Answer accepted

Hello @Mariusz Dullak,

Bamboo tag detection follows the branch detection interval which is 5 minutes by default and adds a time 50% delay to that time so it won't compete with the branch check activities, meaning that tag detection will be running every 300 seconds with a delay of 150 seconds.

E.g.

09:05:00 -> Branch detection
09:07:30 -> Tag detection
09:10:00 -> Branch detection
09:12:30 -> Tag detection
(...)

To adjust the branch detection period, go to:

  • Bamboo Administration -> General Configuration -> Branch and tag detection interval

 

Regards,

Eduardo Alvarenga
Atlassian Support APAC

Thanks Eduardo. That is exactly the option I was looking for.

Like Eduardo Alvarenga likes this

Hi again,

 

Seems that on some branches my tag triggers work and on some (of the same repo and plan) they do not (plan branch configuration is identical and does not contain anything plan branch and git branch specific).

In application-data folder/logs/atlassian-bamboo.log I can see execution of plan when tag was found. Where can I see that the detection was run and that no new tags were found?

Last but not least, are tagged that have been already build stored somewhere? How does bamboo knows which tags should trigger builds - which ones are new?

 

thanks in advance

Hello @Mariusz Dullak, Good to work with you again!

Bamboo will keep track of all tags from a VCS repository and store them on the VCS_TAG table in the database. When Bamboo scans for tags it compares with the data already present on that table and if there is a match, no triggers are actioned as it understands the tag is already present and was "already triggered" in the past.

If the tag entry is removed from the database, Bamboo will treat it as it was a new tag.

You can configure regular expressions that will be matched and trigger a Plan, so Bamboo will only consider those matched strings as a trigger:

You can add some extra DEBUG flags to Bamboo to follow the Tag detection process:

You might be interested on adding the following log levels:

  • com.atlassian.bamboo.plugins.git=ALL
  • com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager=DEBUG
  • com.atlassian.bamboo.plan.branch.BranchDetectionServiceImpl=DEBUG

WARNING: DEBUG logs may be very verbose!

 

Regards,

Eduardo Alvarenga
Atlassian Support APAC

Awesome thanks.

 

I cleaned some garbage (people having typos in tagging script) and looks like it is working as expected now.

Like # people like this

Hey @Mariusz Dullak Good news!

Happy to help!

Kind regards,

Eduardo Alvarenga
Atlassian Support APAC

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo Data Center on Kubernetes

Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...

963 views 3 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you