Hello,
we're running a Bamboo 9.2.4 and Bitbucket 8.13.0 installation with test licenses. Bitbucket and Bamboo are linked to each other.
We are facing an issue with triggering the plan with tag creation in Bitbucket.
We created a simple Bamboo project with a small build plan:
1. Stage just checks out a file from a Bitbucket Repo A, edit the same and checking it in again
2. Stage does the same, but with a file in Repo B
Both the repos are linked repos.
The plan shall be triggered by a tag creation in the repositories.
A build is triggered within a few seconds for repo B whenever the tag was created in a local repo and pushed to the origin. It does not work after creating the tag in Bitbucket GUI.
For repo A triggering the plan does never work: Neither creating the tag in a local repo and pushing it, nor creating it in Bitbucket triggers the plan.
I saw https://confluence.atlassian.com/bamkb/bamboo-repository-polling-trigger-does-not-start-the-build-immediately-1255451860.html, added the Java classes, but the mentioned log messages did not appear.
Why does a tag in repo B triggers the plan, whereas a tag in repo A does not?
Why does a tag creation in repo B via Bitbucket GUI doesn't trigger the plan?
Regards,
Chris
The issue you're encountering with Bamboo not triggering builds on tag creation in Bitbucket can be influenced by several factors. Given the discrepancy in behavior between Repo A and Repo B, along with the method of tag creation (local vs. Bitbucket GUI), here are some potential reasons and troubleshooting steps:
Next Steps
Given the inconsistencies and the troubleshooting steps above, I recommend:
This issue might involve nuanced configuration details specific to your setup, so these steps are intended to guide your investigation.
Wow! Thanks a lot for the detailed answer.
In our test installation we managed to get along with moving repo A's items into repo B and triggering by creating the tag locally.
The test installation was a kind of sandbox for project which is now scheduled for 2025.
Until then we don't have any further capacity to investigate using your answer. But I'll keep that in mind - for sure! As this is guides me to find the root cause, I accept the answer. In case find the reason, I'll update here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.