Adding Atlassian Bitbucket server integration to recommended plugins

299 views
Skip to first unread message

Daniel Kjellin

unread,
Nov 5, 2019, 7:41:26 PM11/5/19
to Jenkins Developers
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

Mark Waite

unread,
Nov 5, 2019, 8:08:20 PM11/5/19
to jenkinsci-dev
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.

--
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 jenkinsci-de...@googlegroups.com.
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

Daniel Kjellin

unread,
Nov 5, 2019, 9:34:24 PM11/5/19
to jenkin...@googlegroups.com
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

Mark Waite

unread,
Nov 5, 2019, 11:24:37 PM11/5/19
to jenkinsci-dev
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 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 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" 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

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/43dcd793-e4c0-402e-325c-b1d1d4527cdc%40atlassian.com.


--
Thanks!
Mark Waite

domi

unread,
Nov 6, 2019, 1:09:55 AM11/6/19
to Jenkins Developers
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 
- “Bitbucket for Blue Ocean”
...

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


Mark Waite

unread,
Nov 6, 2019, 1:21:05 PM11/6/19
to jenkinsci-dev
I have a document where I'm outlining where specific git use cases should be described in the documentation.

We would love to have more contributors and more contributions to the documentation.  Pull requests are welcomed!

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9C71FFB9-1B04-40B1-A588-C9222199CEE2%40fortysix.ch.


--
Thanks!
Mark Waite

Daniel Kjellin

unread,
Nov 6, 2019, 11:38:49 PM11/6/19
to jenkin...@googlegroups.com

Thank you all for your responses.

Would you be willing to join me in a Jenkins Online Meetup that can highlight the new capabilities and the improvements provided by the Bitbucket Server integration plugin?

Yes, if is indeed online and timezones permit, we would be happy to.

It would also be very nice to add a "Bitbucket" use case section to the jenkins.io site, similar to the "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.

We would love to do that! How do we go about that? Do we open a PR somewhere? or provide the content to someone?

regards
Daniel

Daniel Kjellin

unread,
Nov 6, 2019, 11:41:22 PM11/6/19
to jenkin...@googlegroups.com

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

Mark Waite

unread,
Nov 6, 2019, 11:55:39 PM11/6/19
to jenkinsci-dev
The jenkins.io site is maintained with pull requests to  https://github.com/jenkins-infra/jenkins.io .  Fork the repository, review the contributing guidelines, and submit pull requests.

Blog posts and documentation on that site are both submitted as pull requests.

Regarding time zones, we've generally preferred to overlap with San Francisco working hours where possible, but we're open to scheduling at other times and allowing those in the U.S. to view the recording on YouTube.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e8744cda-1871-9cb1-43f8-16210a33e662%40atlassian.com.


--
Thanks!
Mark Waite

Joseph P

unread,
Nov 10, 2019, 4:51:01 AM11/10/19
to Jenkins Developers
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.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.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 jenkin...@googlegroups.com.

--
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 jenkin...@googlegroups.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 jenkin...@googlegroups.com.
--
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 jenkin...@googlegroups.com.

Daniel Kjellin

unread,
Nov 10, 2019, 3:26:48 PM11/10/19
to jenkin...@googlegroups.com

I'm sorry I did not mean to imply that every plugin is not actively maintained.

I did say _some_ we did look at a number of plugins, and some of them are actively stating that they're looking for new maintainers, others have very little activity. Your branch source plugin is not one of those as it is actively maintained and many users use it and are very happy with it.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5c7cc3d1-dca0-4342-a3e5-587d3cb43fa2%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages