|
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.
On 10/11/19 8:51 pm, Joseph P wrote:
Excuse me Daniel?
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
- “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
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
--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGn%2BWoZO6dbYwUkQsL9XitMt%2BajXzkmKc95LXOCpUYbnQ%40mail.gmail.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9C71FFB9-1B04-40B1-A588-C9222199CEE2%40fortysix.ch.
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.
--
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/adf30b41-7bde-2f14-b850-bc8a5ede6130%40atlassian.com.
|
