Issue Summary

If Plan repository tag is detected using Tag trigger, and such tag does not cause a build execution, subsequent detection of the tag will not cause build execution.

Bamboo does not take into account the state of the Tag trigger in the event that the tag detection did caused a build to run.

In a case where Bamboo does not run a build for this tag, two Causes identified are

1. there was no agent to pickup the Tag build (Bamboo concurrency is disabled)
2. the tag build failed, this can not be rerun with Tag trigger

Steps to Reproduce

1. Create a plan with with Bitbucket repository triggers and Tag trigger
2. Commit a change in repository, and Bitbucket repository trigger cause build to run
3. When the build completes add Tag to the repository

Expected Results

Detect the tag and run a build

[TagDetectionServiceImpl] Found following tags in repository: (v1.1.1: dd065c9a...)

Actual Results

Tag is detected as a known tag, and Bamboo does not fire build for know tags.

 [TagDetectionServiceImpl] Found following known tags: (v1.1.1: dd065c9a...)

Workaround

Cause 1

1. allow about 6 minutes of delay before adding tags to repository

Cause 2

1. use customized build and type a tag as Revision
2. go to the failed build result and use Re-run build