We use PR builds and notifications pretty heavily, so that is a very useful feature for us. If you use the normal Multibranch features, you have to either write your own code (global library is what we did this before BBBS was available for Bitbucket Server) or use a plugin with a step. Another one is the 1 job per project rather the 1 job per repository which has reduced quite a bit of the overhead for each project. A nice value-add to further reduce needed configuration is auto-registration for the webhooks is currently open ( https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/21 ).
The plugin that you mentioned above does not support BBBS, and I'm not sure it ever will (see https://issues.jenkins-ci.org/browse/JENKINS-33507?focusedCommentId=260944&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-260944 and https://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/issues/171 ) which is one of the reasons we have almost completely switched We were (and still are) a bit cautious about about the newer Bitbucket plugin ( https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview ) but it has worked really well for us. Overall, we have found switching from the Multibranch to BBBS has been a great decision and very valuable. On Tue, Nov 15, 2016 at 11:51 AM Tim Webster <tim.webs...@gmail.com> wrote: Hi, Bear with me here - I'm not too worried about PRs right now (although I may in the future), but doesn't the 'regular' multibranch pipeline plugin already give you automatic branch indexing/builds? What does BBBS give you that it doesn't (or is it just the PR stuff)? I would like to choose a solution that is supported and works properly - the Blue Ocean support is good because I like the looks of that. But right now getting something as simple as push notifications and build triggers working is turning out to be much trickier than I would expect. I have a feeling the double build thing might have to do with merges, as after I 'fixed' the problem by deleting build history for my jobs, it only occurred after that on merge builds. This looked similar (which is related to the issue you sent me earlier): https://issues.jenkins-ci.org/browse/JENKINS-33865 Thanks, Tim On Tue, Nov 15, 2016 at 3:36 PM, Michael Kobit <mko...@gmail.com> wrote: Sorry, I replied without understanding the full message entirely. We still use that plugin with the Multibranch job type in some places but have been transitioning to using https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+Branch+Source+Plugin . The Bitbucket plugin you previously mentioned does not work with the Bitbucket Branch Source Plugin, which is why we have been switching. BBBS helps in a few ways: - Automatic PR indexing/builds - Automatic PR notifications - Automatic branch indexing/builds - Integration with upcoming Blue Ocean <https://jenkins.io/projects/blueocean/> The new Bitbucket Server plugin that works with BBBS is https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview . In terms of why you are seeing double builds, I don't know why that is happening. On Mon, Nov 14, 2016 at 5:56 PM Tim Webster <tim.webs...@gmail.com> wrote: Hi Michael, Thanks for your reply. I don't actually have that plugin installed (Bitbucket Branch Source Plugin). Should I? To be honest I'm not sure what plugins (on both sides) I should be using. What I had seemed to work OK for a while - until now. Thanks, Tim On Mon, Nov 14, 2016 at 11:19 PM, Michael Kobit <mko...@gmail.com> wrote: Sorry for mobile link: https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-36283 That issue is for customizing what is built by the plugin. On Mon, Nov 14, 2016, 16:43 Tim Webster <tim.webs...@gmail.com> wrote: Hi, For some reason, my Bitbucket webhooks are triggering 2 Jenkins builds at once in multibranch pipeline projects. One build will have a commit notification as the trigger, while the other one will have 'branch indexing' as the trigger (at least I think it's the trigger). Nothing has changed on the Bitbucket side, and it all used to work fine which makes me think the problem is on the Jenkins side of things... The only changes I've made are upgrading some pipeline plugins and setting some job properties in the Jenkinsfile (for discard old builds plugin), but it's worked OK for the past few days. It also seems to happen on some projects, but not others. Does anyone know where I should start looking? I'm relatively new to both Jenkins and Bitbucket. I'm using: Jenkins v2.30 Bitbucket v4.8.4 and this Bitbucket Plugin: https://marketplace.atlassian.com/plugins/com.nerdwin15.stash-stash-webhook-jenkins/server/overview Thanks... -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CABrquLxuA6tYm_vR-wJpcy6V3m2QC%2B%2BYdBNfoY%3Di2wGW%3Dc%3DR5w%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CABrquLxuA6tYm_vR-wJpcy6V3m2QC%2B%2BYdBNfoY%3Di2wGW%3Dc%3DR5w%40mail.gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALELY9Gv5Z2Ai35wUkUCu0u%3D4LmB6rbYDox6vqcxa7xYDRVfWw%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CALELY9Gv5Z2Ai35wUkUCu0u%3D4LmB6rbYDox6vqcxa7xYDRVfWw%40mail.gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CABrquLwnd%3DpZnOGCjxo4XP7Yqh_fa37x0kD677umUikMw_mZVA%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CABrquLwnd%3DpZnOGCjxo4XP7Yqh_fa37x0kD677umUikMw_mZVA%40mail.gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALELY9EZP4gcHkRUskFQ_nCOgMF-ndFcvwjj4ZSpGtTPm%2BGJ9g%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CALELY9EZP4gcHkRUskFQ_nCOgMF-ndFcvwjj4ZSpGtTPm%2BGJ9g%40mail.gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CABrquLyLPV6Bo-1aNNTUfAPsV999yhmpmoegeG7O74rCyc99gg%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CABrquLyLPV6Bo-1aNNTUfAPsV999yhmpmoegeG7O74rCyc99gg%40mail.gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALELY9G0i5L3mJyAfNcmDv3AuiUaM0gchXu1YXW-K7Xx5E0GaA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
