-
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.
[JENKINS-53080] Jenkins bitbucket plugin not building tags, if not other changes happened
Stephan Schultchen
created issue -
| Attachment | New: screenshot-1.png [ 46142 ] |
In my case, plugin resolved tags after scan multibranch but without building it - I must do it manually.
My configuration and job results:
| Attachment | New: screenshot-2.png [ 46143 ] |
| Environment |
Original:
jenkins 2.138 bitbucket plugin 1.1.8 |
New:
Jenkins ver. 2.150.3 Git plugin 4.0.0-rc Branch API Plugin 2.1.2 Credentials Plugin 2.1.18 Branch API Plugin 2.1.2 Bitbucket Plugin 1.1.8 Bitbucket Pullrequest Builder Plugin 1.4.29 Bitbucket Push and Pull Request Plugin 1.2 Bitbucket OAuth Plugin 0.9 Bitbucket Pipeline for Blue Ocean 1.11.1 |
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