Excuse me Daniel? Not actively maintained? Here I am trying to actively maintain https://github.com/jenkinsci/bitbucket-branch-source-plugin Which btw supports both Bitbucket Server and Bitbucket clouid.
At no point did you try and reach out. On Thursday, November 7, 2019 at 5:41:22 AM UTC+1, Daniel Kjellin wrote: > > Hello, > Yes indeed it is quite a mess. We are hoping to help clear this up a bit, > some of these plugins are not as actively maintained as they perhaps need > to be, and lack some features that we expect in modern plugins. > > regards > Daniel > On 6/11/19 5:09 pm, domi wrote: > > Thats great suggestion by Mark! > Please also make sure to clearly differentiate the “Bitbucket Server” > Plugin landscape form the “Bitbucket Cloud” landscape - its quite a mess > and hard to understand what is really needed for what and why. > e.g. there are plugins like > - https://plugins.jenkins.io/bitbucket > - https://plugins.jenkins.io/bitbucket-approve > - https://plugins.jenkins.io/cloudbees-bitbucket-branch-source > - https://plugins.jenkins.io/bitbucket-oauth > - “Bitbucket for Blue Ocean” > - https://plugins.jenkins.io/bitbucket-build-status-notifier > - https://plugins.jenkins.io/stashNotifier > - https://plugins.jenkins.io/violation-comments-to-stash > - https://plugins.jenkins.io/bitbucket-pullrequest-builder > - https://plugins.jenkins.io/bitbucket-approval-filter > - https://plugins.jenkins.io/bitbucket-filter-project-trait > - https://plugins.jenkins.io/bitbucket-push-and-pull-request > - https://plugins.jenkins.io/bitbucket-scm-filter-aged-refs > - https://plugins.jenkins.io/bitbucket-scm-filter-jira-validator > - https://plugins.jenkins.io/bitbucket-scm-trait-commit-skip > - https://plugins.jenkins.io/publish-to-bitbucket > ... > > Some do support “Server” AND “Cloud” others don’t. Some even do the > exact/nearly same thing. And most of the plugins probably do not use a > common configuration but have to be configured individually to have access > to the service. > > As I’m a user of "bitbucket cloud” my self, I think this clearly shows a > problem: there is no coordination of what kind of plugins are build and how > they should work together. I understand this is also the power of Jenkins: > something is missing and your free to build a plugin to solve the issue. > But with each plugin published, the confusion for users/admins gets bigger. > I’m sure this issue is not only about bitbucket, the same thing (probably > even bigger) might be with GitHub and other areas. > > It would be really great to have some kind of documentation for a > topics/area which highlights (and maybe coordinates) the most common use > cases one has around different topics. e.g. GitHub Integration, Bitbucket > Cloud Integration, Bitbucket Server Integration, Kubernetes Integration, > Docker Integration, … some of these might overlap or must work with each > other - but sure there are a lot of hidden gems and simplifications which > should get better attention. Providing a bigger picture on a specific topic > (not just a single plugin) in the context of the whole community, might > even help to coordinate plugin creation and feature placing in existing > plugins AND deprecation of existing/duplicated plugins. Sure, such an > initiative would need someone being responsible, in terms of Bitbucket, I > think the best would be if Atlassian could step in. > > Sorry for misusing this thread, but the topic just happened to raise this > issue for me again and I’m sure I’m not the only one feeling this way... > > /Domi > > > On 6 Nov 2019, at 05:24, Mark Waite <[email protected] <javascript:>> > wrote: > > We don't have a recommended install count, though I think that is a good > idea for discussion. > > Would you be willing to join me in a Jenkins Online Meetup > <https://www.meetup.com/Jenkins-online-meetup/> that can highlight the > new capabilities and the improvements provided by the Bitbucket Server > integration plugin? > > We hosted the next generation Warnings plugin in a Jenkins Online Meetup > <https://www.youtube.com/watch?v=0GcEqML8nys> and it helped users > understand the capabilities of the plugin and how it was improving the > experience compared to the previous plugin. If your'e available in mid > December (17, 18, or 19), I could host that session in the same fashion. > If that week in December does not work for you, we could host it in early > January. > > If you're attending DevOps World | Jenkins World 2019 in Lisbon Dec 2-5, > we could have you present a lightning talk in the community booth > describing the plugin and what it provides. > > It would also be very nice to add a "Bitbucket" use case section to the > jenkins.io site, similar to the "GitHub > <https://jenkins.io/solutions/github/>" use case section. The plugin > documentation seems like a good start for that use case section. > > You might also consider a blog post on the new plugin as another way to > encourage users to use it. > > Thanks, > Mark Waite > > On Tue, Nov 5, 2019 at 7:34 PM Daniel Kjellin <[email protected] > <javascript:>> wrote: > >> Thank you for the response. >> I totally understand, and yes it was released about a month ago. Do we >> have a recommended install count that should aim for before we consider the >> plugin? >> >> regards >> Daniel >> >> Thanks for asking. >> >> Recommended plugins tend to be widely used before they are added to the >> list. The Bitbucket server integration plugin looks very promising but >> seems too recent to be added to the recommended plugins. The plugins page >> reports that the first pre-release was in August 2019 with the 1.0 release >> a month ago. >> >> On Tue, Nov 5, 2019 at 5:41 PM Daniel Kjellin <[email protected] >> <javascript:>> wrote: >> >>> Hello, >>> I'm one of the developers behind the Atlassian Bitbucket server >>> integration. We were wondering what the process is to get this added to >>> the list of recommended plugins that users can install during the setup >>> of their Jenkins instance? >>> >>> The plugin in question is >>> https://plugins.jenkins.io/atlassian-bitbucket-server-integration >>> >>> >>> regards >>> Daniel >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/9a1575a8-5217-7779-38c1-f9bdbacf5d61%40atlassian.com >>> . >>> >> >> >> -- >> Thanks! >> Mark Waite >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEMZLyPx0zGa%3DZvfueb3%3D7iPdqFmR1Vi_BEoa1THiwOJw%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEMZLyPx0zGa%3DZvfueb3%3D7iPdqFmR1Vi_BEoa1THiwOJw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/43dcd793-e4c0-402e-325c-b1d1d4527cdc%40atlassian.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/43dcd793-e4c0-402e-325c-b1d1d4527cdc%40atlassian.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Thanks! > Mark Waite > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGn%2BWoZO6dbYwUkQsL9XitMt%2BajXzkmKc95LXOCpUYbnQ%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGn%2BWoZO6dbYwUkQsL9XitMt%2BajXzkmKc95LXOCpUYbnQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/9C71FFB9-1B04-40B1-A588-C9222199CEE2%40fortysix.ch > > <https://groups.google.com/d/msgid/jenkinsci-dev/9C71FFB9-1B04-40B1-A588-C9222199CEE2%40fortysix.ch?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5c7cc3d1-dca0-4342-a3e5-587d3cb43fa2%40googlegroups.com.
