Description
Issue Summary
Tag trigger is used to schedule Bamboo to run a build automatically whenever a selected tag appears in the repository.
Bamboo does not take into account the state of the Tag trigger in the event that the trigger never never caused a build.
- One of the possible cause of not triggering build for new tags is, the situation where another plan trigger (not tag trigger ) starts a build and the plan which has concurrent builds disabled or no remote agent to build.
- Bamboo loss communication with remote repository
Workaround
- Allow about 6 minutes of delay before adding tags to repository.
- A use case can be to create a build plan which uses other triggers (Plan-A), and a separate plan with the Tag trigger (Plan-B), and both with sane default branch. In the plan with Tag trigger (Plan-B), the Trigger conditions option to make Tag trigger depend on the plan with other trigger (Plan-A). This will create a condition where Tag trigger on Plan-B when the build in Plan-A are successful.
Note
The performance and resource limits of Bamboo server should be considered before opting for option 2