-
Bug
-
Resolution: Unresolved
-
Minor
-
None
the first time i create a tag on a hash, jenkins will happily trigger a build of matching jobs. but if i create another tag on the same hash, jenkins will not trigger a build.
i guess this is a feature right now, since the wiki says: "If the job's SCM (git) detects that the remote repository has changes, THEN A full build of the job will be queued"
i would suggest to add an option to skip this check, since otherwise creating tags is not correctly working.
my current workaround is do delete the workspace at the end of the build.
This is not a defect. By design the plugin does not trigger build if has already built the hash code. Moreover by default (of the branch-ap plugin) a build is not trigger on tag events unless you get a specific plugin that implements a new default logic.
https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/139#issuecomment-433684917