How to add new recommended plugin? was Re: Jenkins 2.0 initial setup plugin selection

91 views
Skip to first unread message

Arnaud Héritier

unread,
May 30, 2016, 4:03:42 AM5/30/16
to jenkin...@googlegroups.com
Hi guys,

  What is the process to propose a new recommended plugin in the installation wizard ?

Cheers


On Tue, Mar 22, 2016 at 9:57 PM, Baptiste Mathus <m...@batmat.net> wrote:
Wondering if BuildTriggerBadge could/should make it in the "build features" part (disclaimer: my first plugin).

It lets you quickly know what triggered a build. Without the recent glitch in stats, it would have gone above 3k installs in the last month I think. 
It was judged useful by Praqma too apparently :).

I admit I'm certainly not the best person to judge it :), but really I know find it really hard to look at a builds list in the job page when it's not installed.
IIRC it's a bit below the threshold Daniel set, but I think it's quite general purposed, and somehow improves the UX w/o normally being a "risky" thing from any PoV I guess.

Live example on https://ci.jenkins-ci.org/job/jenkins_2.0/ for example.

WDYT?

2016-03-22 0:09 GMT+01:00 Daniel Beck <m...@beckweb.net>:
Hi everyone,

I hope by now most of you had the opportunity to check out alpha 3 or alpha 4. I'd like to know what you think of the default plugins selection. What do you think should be included?

As I've written before I tried to build a useful list for alpha 3 as a starting point, but didn't have the time to discuss it without delaying the alphas. But we have still the time to change things towards 2.0. And with a change I hope to get in shortly after 2.0, Jenkins will retrieve the list from the update site, so we can always tweak it, even for past releases[1].

If you're not able to try the setup wizard right now, you'll also find the lists of both the available and the recommended plugins in [2]. "Available" means users are able to select them during installation (which has been discussed here so far), and "recommended" is the set of plugins that are 'checked by default' if the user wants to customize, and will be installed if the user chooses to accept the defaults.

1: https://issues.jenkins-ci.org/browse/JENKINS-33299
2: https://github.com/jenkinsci/jenkins/blob/2.0/war/src/main/js/api/plugins.js

--
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/7CEC8F5E-D0CC-453A-B411-CC4ABE9721F4%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--
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/CANWgJS57VrApuAufgC7PH8SDQd5ctsYvBnLmQHqVPExT4c70bA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.



--
-----
Arnaud Héritier
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Arnaud Héritier

unread,
Jul 13, 2016, 6:13:29 AM7/13/16
to jenkin...@googlegroups.com
ping ?

Daniel Beck

unread,
Jul 13, 2016, 6:20:22 AM7/13/16
to jenkin...@googlegroups.com

> On 30.05.2016, at 10:03, Arnaud Héritier <aher...@gmail.com> wrote:
>
> What is the process to propose a new recommended plugin in the installation wizard ?

We don't really have one. For Jenkins 2.0 I wrote up https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog and we had the mailing list discussion.

I think for changes, it would be best to have them filed as PR, with an associated thread on the dev list explaining why it should be in the list and how it satisfies the criteria, each linking to the other.

What do others think about this?

> I have this one in mind : https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin

Is there a reason this isn't part of the aggregator?

Robert Sandell

unread,
Jul 13, 2016, 6:27:54 AM7/13/16
to jenkin...@googlegroups.com
It is a "separate" plugin maintained by me, not "the pipeline team" :)
 

--
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.

For more options, visit https://groups.google.com/d/optout.



--
Robert Sandell
Software Engineer
CloudBees Inc.

Arnaud Héritier

unread,
Jul 13, 2016, 6:43:15 AM7/13/16
to jenkin...@googlegroups.com
On Wed, Jul 13, 2016 at 12:20 PM, Daniel Beck <m...@beckweb.net> wrote:

> On 30.05.2016, at 10:03, Arnaud Héritier <aher...@gmail.com> wrote:
>
> What is the process to propose a new recommended plugin in the installation wizard ?

We don't really have one. For Jenkins 2.0 I wrote up https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog and we had the mailing list discussion.

Yes it is the page I found but always as draft and no detail about the submission process
 

I think for changes, it would be best to have them filed as PR, with an associated thread on the dev list explaining why it should be in the list and how it satisfies the criteria, each linking to the other.

I agree. PR on which file? I had in memory a plugins.js file but I don't find it anymore ..
 

What do others think about this?

> I have this one in mind : https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin

Is there a reason this isn't part of the aggregator?
--
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.

For more options, visit https://groups.google.com/d/optout.

Daniel Beck

unread,
Jul 13, 2016, 8:09:34 AM7/13/16
to jenkin...@googlegroups.com

> On 13.07.2016, at 12:42, Arnaud Héritier <aher...@gmail.com> wrote:
>
> I agree. PR on which file? I had in memory a plugins.js file but I don't find it anymore ..
>

Oleg changed how the bundled list works, and with that came a new path to the file. I suppose we could even switch to have it provided by the update site in the future, with this new foundation in place.

https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/install/platform-plugins.json

Reply all
Reply to author
Forward
0 new messages