Jenkins 2.0 initial setup plugin selection

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
64 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

Jenkins 2.0 initial setup plugin selection

Daniel Beck
Hi everyone,

For Jenkins 2.0, we're aiming for a much better 'getting started' experience, aimed for users new to Jenkins.

We already talked about this last year[1], but the discussion didn't really have a great result, so I'd like to start over by defining a list of guidelines on what kind of plugins qualify for inclusion first. My initial proposal is in the wiki[2]. Please take a look and provide feedback in this thread.

Specific selection of plugins would be the next step.

Daniel

1: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
2: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

ogondza
How about some criteria for testing? Requiring X% for code coverage is clearly wrong. But how about the plugin needs to have _some_ tests? What I believe we should do is having a CI that verifies the plugin selection against the core version. Not sure we should use ATH or plugin-compat-tester or both.

--
oliver

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/07f5637d-bd73-4a03-96ba-c9baa790ff6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Daniel Beck

On 22.01.2016, at 14:14, ogondza <[hidden email]> wrote:

> How about some criteria for testing? Requiring X% for code coverage is clearly wrong. But how about the plugin needs to have _some_ tests? What I believe we should do is having a CI that verifies the plugin selection against the core version. Not sure we should use ATH or plugin-compat-tester or both.

Looks like a reasonable requirement. Any idea how we could incorporate that?

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/74A77A96-3E33-4011-BA3D-E259EF2EE246%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Daniel Beck
In reply to this post by Daniel Beck
Hi everyone,

I added two additional criteria to the wiki: The plugin shouldn't require a restart to work (otherwise it's not exactly a great getting started experience), and it shouldn't be just a UI/theming plugins that replaces part of the Jenkins UI (as including them in a list of suggested/recommended plugins would just be weird).

Based on these criteria I tried to build a list of plugins to feature in the initial setup wizard.

A reminder: All plugins are still available in the plugin manager. But with 1100+ plugins now, it'd be great if we could provide a curated subset to get new users started. This also means that particularly complex plugins, that require knowledge of Jenkins internals, even though they may be useful, are basically excluded by default.

To approximate popularity, I used the previous install count multiplied by the growth in the previous year (as neither alone is a sufficient indicator of popularity). Then I sorted by this value, and went through the list, being mildly judgmental. This is the result:

https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit#gid=0

This is the list of plugins I came up with for the initial setup dialog. If a plugin wouldn't be used, the reason is stated. Regarding 'Unsafe': Wearing my security officer hat, I consider every plugin with Groovy scripting that is not using the Groovy Sandbox to be unsafe, even if it implements security measures.

Please review the list, and let me know what you think.


On 21.01.2016, at 19:56, Daniel Beck <[hidden email]> wrote:

> Hi everyone,
>
> For Jenkins 2.0, we're aiming for a much better 'getting started' experience, aimed for users new to Jenkins.
>
> We already talked about this last year[1], but the discussion didn't really have a great result, so I'd like to start over by defining a list of guidelines on what kind of plugins qualify for inclusion first. My initial proposal is in the wiki[2]. Please take a look and provide feedback in this thread.
>
> Specific selection of plugins would be the next step.
>
> Daniel
>
> 1: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
> 2: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/73110AB5-7D59-4858-8A12-F20F64180CA9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Arnaud Héritier
#19 
maven-plugin100810126144157844No: We don’t really want people to use this

LOL, even if I agree, all Maven users will install it ....
Evil but highly used :(

On Tue, Feb 23, 2016 at 11:20 PM, Daniel Beck <[hidden email]> wrote:
Hi everyone,

I added two additional criteria to the wiki: The plugin shouldn't require a restart to work (otherwise it's not exactly a great getting started experience), and it shouldn't be just a UI/theming plugins that replaces part of the Jenkins UI (as including them in a list of suggested/recommended plugins would just be weird).

Based on these criteria I tried to build a list of plugins to feature in the initial setup wizard.

A reminder: All plugins are still available in the plugin manager. But with 1100+ plugins now, it'd be great if we could provide a curated subset to get new users started. This also means that particularly complex plugins, that require knowledge of Jenkins internals, even though they may be useful, are basically excluded by default.

To approximate popularity, I used the previous install count multiplied by the growth in the previous year (as neither alone is a sufficient indicator of popularity). Then I sorted by this value, and went through the list, being mildly judgmental. This is the result:

https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit#gid=0

This is the list of plugins I came up with for the initial setup dialog. If a plugin wouldn't be used, the reason is stated. Regarding 'Unsafe': Wearing my security officer hat, I consider every plugin with Groovy scripting that is not using the Groovy Sandbox to be unsafe, even if it implements security measures.

Please review the list, and let me know what you think.


On 21.01.2016, at 19:56, Daniel Beck <[hidden email]> wrote:

> Hi everyone,
>
> For Jenkins 2.0, we're aiming for a much better 'getting started' experience, aimed for users new to Jenkins.
>
> We already talked about this last year[1], but the discussion didn't really have a great result, so I'd like to start over by defining a list of guidelines on what kind of plugins qualify for inclusion first. My initial proposal is in the wiki[2]. Please take a look and provide feedback in this thread.
>
> Specific selection of plugins would be the next step.
>
> Daniel
>
> 1: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
> 2: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/73110AB5-7D59-4858-8A12-F20F64180CA9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.



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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8pFthuD3%2BNjMTfVca0sJph6-5uZtYNqjJ%2Bs056xtGwgA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Daniel Beck

On 23.02.2016, at 23:38, Arnaud Héritier <[hidden email]> wrote:

> LOL, even if I agree, all Maven users will install it ....
> Evil but highly used :(

The idea is to not steer them towards it. The maven build step in core is functional, and it should be an actual decision to use it.

It's kind of weird that we today bundle a feature with Jenkins that, whenever someone comes to the mailing lists and asks about a problem with it, we call it the 'evil' job type and link to Stephen's blog post on it.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/65C64DDE-7E0C-426D-99D0-BAED29361F8B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Manfred Moser-2
In reply to this post by Arnaud Héritier
At least it will easily be possible to have it NOT available so unknowing users dont get into trouble. I strongly believe that a lot of people only use this because they dont even know about the Maven build step.

Maybe we should change the job type title to include something like "deprecated" or "legacy" or so.

I for one will be glad once its gone. We even have a script we run to find any jobs and alert on it. Then we tell people to change the job ... 

manfred 



On Tue, Feb 23, 2016 at 2:38 PM, Arnaud Héritier <[hidden email]> wrote:
#19 
maven-plugin100810126144157844No: We don’t really want people to use this

LOL, even if I agree, all Maven users will install it ....
Evil but highly used :(

On Tue, Feb 23, 2016 at 11:20 PM, Daniel Beck <[hidden email]> wrote:
Hi everyone,

I added two additional criteria to the wiki: The plugin shouldn't require a restart to work (otherwise it's not exactly a great getting started experience), and it shouldn't be just a UI/theming plugins that replaces part of the Jenkins UI (as including them in a list of suggested/recommended plugins would just be weird).

Based on these criteria I tried to build a list of plugins to feature in the initial setup wizard.

A reminder: All plugins are still available in the plugin manager. But with 1100+ plugins now, it'd be great if we could provide a curated subset to get new users started. This also means that particularly complex plugins, that require knowledge of Jenkins internals, even though they may be useful, are basically excluded by default.

To approximate popularity, I used the previous install count multiplied by the growth in the previous year (as neither alone is a sufficient indicator of popularity). Then I sorted by this value, and went through the list, being mildly judgmental. This is the result:

https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit#gid=0

This is the list of plugins I came up with for the initial setup dialog. If a plugin wouldn't be used, the reason is stated. Regarding 'Unsafe': Wearing my security officer hat, I consider every plugin with Groovy scripting that is not using the Groovy Sandbox to be unsafe, even if it implements security measures.

Please review the list, and let me know what you think.


On 21.01.2016, at 19:56, Daniel Beck <[hidden email]> wrote:

> Hi everyone,
>
> For Jenkins 2.0, we're aiming for a much better 'getting started' experience, aimed for users new to Jenkins.
>
> We already talked about this last year[1], but the discussion didn't really have a great result, so I'd like to start over by defining a list of guidelines on what kind of plugins qualify for inclusion first. My initial proposal is in the wiki[2]. Please take a look and provide feedback in this thread.
>
> Specific selection of plugins would be the next step.
>
> Daniel
>
> 1: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
> 2: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/73110AB5-7D59-4858-8A12-F20F64180CA9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.



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

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8pFthuD3%2BNjMTfVca0sJph6-5uZtYNqjJ%2Bs056xtGwgA%40mail.gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CABffhO4JAnPed4OSpM_yi7C648uojOBAZ1jJ0Q%3D8nW4QiAXmHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

ogondza
In reply to this post by Daniel Beck
On 02/23/2016 07:08 PM, Daniel Beck wrote:
>
> On 22.01.2016, at 14:14, ogondza <[hidden email]> wrote:
>
>> How about some criteria for testing? Requiring X% for code coverage is clearly wrong. But how about the plugin needs to have _some_ tests? What I believe we should do is having a CI that verifies the plugin selection against the core version. Not sure we should use ATH or plugin-compat-tester or both.
>
> Looks like a reasonable requirement. Any idea how we could incorporate that?

For the plugin test coverage we can add a requirement to the wiki the
plugin must have test coverage. It should not be a hard criteria but at
least stating that we take testing seriously on default plugin selection
is useful IMO.

Ad ATH, there is a way to provide a list of HPIs to be installed for
every tests executed - that is a great way to make sure installing
recommended plugins is not going to break some other feature in core or
reasonably popular plugin. Perhaps we can go a step further and install
all recommended plugins for all tests by default.

--
oliver

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/56CD56F7.7020200%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Robert Sandell-2
So what defines UI/Theme plugins?

I see for example that extra-columns and sidebar-link made the cut?

/B

On Wed, Feb 24, 2016 at 8:08 AM, Oliver Gondža <[hidden email]> wrote:
On 02/23/2016 07:08 PM, Daniel Beck wrote:

On 22.01.2016, at 14:14, ogondza <[hidden email]> wrote:

How about some criteria for testing? Requiring X% for code coverage is clearly wrong. But how about the plugin needs to have _some_ tests? What I believe we should do is having a CI that verifies the plugin selection against the core version. Not sure we should use ATH or plugin-compat-tester or both.

Looks like a reasonable requirement. Any idea how we could incorporate that?

For the plugin test coverage we can add a requirement to the wiki the plugin must have test coverage. It should not be a hard criteria but at least stating that we take testing seriously on default plugin selection is useful IMO.

Ad ATH, there is a way to provide a list of HPIs to be installed for every tests executed - that is a great way to make sure installing recommended plugins is not going to break some other feature in core or reasonably popular plugin. Perhaps we can go a step further and install all recommended plugins for all tests by default.

--
oliver

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/56CD56F7.7020200%40gmail.com.

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



--
Robert Sandell
Software Engineer
CloudBees Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3MdMwgvRR%3DvnUyyZyVnqsY%2B%2Be3tQg-4LrpeFuAnmV8cw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Robert Sandell-2
... and gravatar.

And I believe docker-commons is just an API plugin.

/B

On Wed, Feb 24, 2016 at 11:44 AM, Robert Sandell <[hidden email]> wrote:
So what defines UI/Theme plugins?

I see for example that extra-columns and sidebar-link made the cut?

/B

On Wed, Feb 24, 2016 at 8:08 AM, Oliver Gondža <[hidden email]> wrote:
On 02/23/2016 07:08 PM, Daniel Beck wrote:

On 22.01.2016, at 14:14, ogondza <[hidden email]> wrote:

How about some criteria for testing? Requiring X% for code coverage is clearly wrong. But how about the plugin needs to have _some_ tests? What I believe we should do is having a CI that verifies the plugin selection against the core version. Not sure we should use ATH or plugin-compat-tester or both.

Looks like a reasonable requirement. Any idea how we could incorporate that?

For the plugin test coverage we can add a requirement to the wiki the plugin must have test coverage. It should not be a hard criteria but at least stating that we take testing seriously on default plugin selection is useful IMO.

Ad ATH, there is a way to provide a list of HPIs to be installed for every tests executed - that is a great way to make sure installing recommended plugins is not going to break some other feature in core or reasonably popular plugin. Perhaps we can go a step further and install all recommended plugins for all tests by default.

--
oliver

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/56CD56F7.7020200%40gmail.com.

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



--
Robert Sandell
Software Engineer
CloudBees Inc.



--
Robert Sandell
Software Engineer
CloudBees Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS26t%3D8%2B6yadDtDiURP%2B0kC0DDqLWp%2BzBAuVbOa1CkYzfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Victor Martinez
What about docker plugin? It might be a good candidate as part of the plugin selection as it's widely used and might alienate the concept of reproducibility and configuration, which are nowadays quite trendy, with Jenkins.

Mercurial and Perforce are not part of that list, although their usage are not massive compare to Git or SVN, but might be also important to have them as part of the SCM category. That's my point of view and sorry if I said something which it was already said previously.

Cheers

On Wednesday, 24 February 2016 10:47:44 UTC, Robert Sandell wrote:
... and gravatar.

And I believe docker-commons is just an API plugin.

/B

On Wed, Feb 24, 2016 at 11:44 AM, Robert Sandell <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="n-EctxkeEgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">rsan...@...> wrote:
So what defines UI/Theme plugins?

I see for example that extra-columns and sidebar-link made the cut?

/B

On Wed, Feb 24, 2016 at 8:08 AM, Oliver Gondža <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="n-EctxkeEgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ogo...@...> wrote:
On 02/23/2016 07:08 PM, Daniel Beck wrote:

On 22.01.2016, at 14:14, ogondza <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="n-EctxkeEgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ogo...@...> wrote:

How about some criteria for testing? Requiring X% for code coverage is clearly wrong. But how about the plugin needs to have _some_ tests? What I believe we should do is having a CI that verifies the plugin selection against the core version. Not sure we should use ATH or plugin-compat-tester or both.

Looks like a reasonable requirement. Any idea how we could incorporate that?

For the plugin test coverage we can add a requirement to the wiki the plugin must have test coverage. It should not be a hard criteria but at least stating that we take testing seriously on default plugin selection is useful IMO.

Ad ATH, there is a way to provide a list of HPIs to be installed for every tests executed - that is a great way to make sure installing recommended plugins is not going to break some other feature in core or reasonably popular plugin. Perhaps we can go a step further and install all recommended plugins for all tests by default.

--
oliver

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="n-EctxkeEgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/56CD56F7.7020200%40gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/56CD56F7.7020200%40gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/56CD56F7.7020200%40gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/56CD56F7.7020200%40gmail.com.

For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



--
Robert Sandell
Software Engineer
CloudBees Inc.



--
Robert Sandell
Software Engineer
CloudBees Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e9004e7f-9af0-43a3-aa62-408527666bd7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Daniel Beck

On 24.02.2016, at 13:05, Victor Martinez <[hidden email]> wrote:

> And I believe docker-commons is just an API plugin.

My apologies for the spreadsheet not being clear enough -- Plugins to be part of the initial setup are those with "YES" in the Inclusion column. I stopped around 14k projected installs to not overload the dialog. Any plugins without that "YES" would not appear as entries.

We can always go further down the list if we determine the initial setup could/should have more stuff in it.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/42867520-E58B-4447-87AC-D276D69E2F55%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Daniel Beck
In reply to this post by Victor Martinez

On 24.02.2016, at 13:05, Victor Martinez <[hidden email]> wrote:

> Mercurial and Perforce are not part of that list, although their usage are not massive compare to Git or SVN, but might be also important to have them as part of the SCM category. That's my point of view and sorry if I said something which it was already said previously.

Good point. As I wrote on the wiki, SCM plugins are special (nothing much going on in Jenkins without them), so I recommend we're more accepting in that category. My current list of SCMs to include are (with approx. install count):

https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin - 76k
https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin - 123k
https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+Plugin - 1500
https://wiki.jenkins-ci.org/display/JENKINS/CVS+Plugin - 120k
https://wiki.jenkins-ci.org/display/JENKINS/GitBucket+Plugin - 1200
https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin - 20k
https://wiki.jenkins-ci.org/display/JENKINS/Gitlab+Merge+Request+Builder+Plugin - 2000
https://wiki.jenkins-ci.org/display/JENKINS/GitLab+Plugin - 5800
https://wiki.jenkins-ci.org/display/JENKINS/Mercurial+Plugin - 6500
https://wiki.jenkins-ci.org/display/JENKINS/P4+Plugin - 1500
https://wiki.jenkins-ci.org/display/JENKINS/Repo+Plugin - 1300
https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin - 1000
https://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin - 2900

While Perforce Plugin has more installs than P4, it stagnates, and its wiki page recommends use of P4, which is rapidly growing.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D05C72E9-6127-4260-A8FD-0FC3D2E77E3D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Daniel Beck
In reply to this post by Victor Martinez

On 24.02.2016, at 13:05, Victor Martinez <[hidden email]> wrote:

> What about docker plugin? It might be a good candidate as part of the plugin selection as it's widely used and might alienate the concept of reproducibility and configuration, which are nowadays quite trendy, with Jenkins.

This is an interesting question, and one I wanted to explore once the initial plugins selection is defined:

Could we actually manage to curate a more opinionated list?

Given how the initial discussion last year went, I had my doubts -- hence this reboot that started out with a set of rules/guidelines, rather than a proposed list of plugins. I think the result could be much better, if we were to actually build a list based on our collective experience with Jenkins.

The risk of course is that we're not getting anywhere, as our varying experiences using Jenkins color our opinion what plugins are a "must have". I'm not excluding myself here -- I noticed this with a few plugins I included in the original list, that, when viewed critically, weren't nearly as universally useful as I first considered them to be.

----

That said, I suggest we continue with the current approach of a mostly popularity based list, excluding unmaintained and unsuitable plugins, for now. So please, provide some more feedback on it, and maybe think about ways to make the above work.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1C2691DD-F00D-43B7-867C-FC8E230985E9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Robert Sandell-2
If GitLab and GitHub triggers are on the list because of their SCM affiliation then Gerrit Trigger should be on the list as well.

If the neighbour’s kids gets to go to the Prom then my baby should also go to the Prom! :-p

/B

On Wed, Feb 24, 2016 at 2:05 PM, Daniel Beck <[hidden email]> wrote:

On 24.02.2016, at 13:05, Victor Martinez <[hidden email]> wrote:

> What about docker plugin? It might be a good candidate as part of the plugin selection as it's widely used and might alienate the concept of reproducibility and configuration, which are nowadays quite trendy, with Jenkins.

This is an interesting question, and one I wanted to explore once the initial plugins selection is defined:

Could we actually manage to curate a more opinionated list?

Given how the initial discussion last year went, I had my doubts -- hence this reboot that started out with a set of rules/guidelines, rather than a proposed list of plugins. I think the result could be much better, if we were to actually build a list based on our collective experience with Jenkins.

The risk of course is that we're not getting anywhere, as our varying experiences using Jenkins color our opinion what plugins are a "must have". I'm not excluding myself here -- I noticed this with a few plugins I included in the original list, that, when viewed critically, weren't nearly as universally useful as I first considered them to be.

----

That said, I suggest we continue with the current approach of a mostly popularity based list, excluding unmaintained and unsuitable plugins, for now. So please, provide some more feedback on it, and maybe think about ways to make the above work.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1C2691DD-F00D-43B7-867C-FC8E230985E9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.



--
Robert Sandell
Software Engineer
CloudBees Inc.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3prUnHO5f0tZKMoCfhcP%2BkKNdj-ZB0N1gkujLBGig2mg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Ulli Hafner
In reply to this post by Daniel Beck
How is the initial selection presented to the user? Is there already a mockup or screenshot available? Should the number of plug-ins per category be equal sized? Or are all categories shown in one screen?
E.g., if we have tabs for the categories then choosing e.g. just 3 plug-ins per category makes no sense to me.

Wouldn’t it make more sense to have some kind of profiles like
- Build Java Web Applications
- Deploy to Application Servers
- Analyze Source Code
- Measure Code Coverage
 and so on and provide a set of plug-ins per profile? Or is this not feasible due to the enormous number of plug-ins?

While the UI of Eclipse normally is not a good reference for best UI practices I think having something like the different eclipse versions is a good thing (eclipse for java developers, eclipse for testers, etc.)

> Am 21.01.2016 um 19:56 schrieb Daniel Beck <[hidden email]>:
>
> Hi everyone,
>
> For Jenkins 2.0, we're aiming for a much better 'getting started' experience, aimed for users new to Jenkins.
>
> We already talked about this last year[1], but the discussion didn't really have a great result, so I'd like to start over by defining a list of guidelines on what kind of plugins qualify for inclusion first. My initial proposal is in the wiki[2]. Please take a look and provide feedback in this thread.
>
> Specific selection of plugins would be the next step.
>
> Daniel
>
> 1: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
> 2: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/FE1E486C-43BA-4B98-9D35-A7DCFF8EA828%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (506 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Christopher Orr
There's a demo video linked from the "Jenkins 2.0" wiki page:
https://www.youtube.com/watch?v=kzRR8XR8hu4

Though I have a feeling a saw a newer version at FOSDEM; not sure where
the code can be found (not that I've looked).

Regards,
Chris


On 24/02/16 22:14, Ullrich Hafner wrote:

> How is the initial selection presented to the user? Is there already a mockup or screenshot available? Should the number of plug-ins per category be equal sized? Or are all categories shown in one screen?
> E.g., if we have tabs for the categories then choosing e.g. just 3 plug-ins per category makes no sense to me.
>
> Wouldn’t it make more sense to have some kind of profiles like
> - Build Java Web Applications
> - Deploy to Application Servers
> - Analyze Source Code
> - Measure Code Coverage
>  and so on and provide a set of plug-ins per profile? Or is this not feasible due to the enormous number of plug-ins?
>
> While the UI of Eclipse normally is not a good reference for best UI practices I think having something like the different eclipse versions is a good thing (eclipse for java developers, eclipse for testers, etc.)
>
>> Am 21.01.2016 um 19:56 schrieb Daniel Beck <[hidden email]>:
>>
>> Hi everyone,
>>
>> For Jenkins 2.0, we're aiming for a much better 'getting started' experience, aimed for users new to Jenkins.
>>
>> We already talked about this last year[1], but the discussion didn't really have a great result, so I'd like to start over by defining a list of guidelines on what kind of plugins qualify for inclusion first. My initial proposal is in the wiki[2]. Please take a look and provide feedback in this thread.
>>
>> Specific selection of plugins would be the next step.
>>
>> Daniel
>>
>> 1: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
>> 2: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>>
>> --
>> 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 [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/56CE20F6.2090904%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Manfred Moser-2
Interesting.. that video reminded me of the email from Olivier about the proxy server config. How will a case be handled were the initial start up in a datacenter requires configuration of a proxy server to be able to get to the internet/update center? 

JVM proxy config or some UI? 

manfred

On Wed, Feb 24, 2016 at 1:30 PM, Christopher Orr <[hidden email]> wrote:
There's a demo video linked from the "Jenkins 2.0" wiki page:
https://www.youtube.com/watch?v=kzRR8XR8hu4

Though I have a feeling a saw a newer version at FOSDEM; not sure where
the code can be found (not that I've looked).

Regards,
Chris


On 24/02/16 22:14, Ullrich Hafner wrote:
> How is the initial selection presented to the user? Is there already a mockup or screenshot available? Should the number of plug-ins per category be equal sized? Or are all categories shown in one screen?
> E.g., if we have tabs for the categories then choosing e.g. just 3 plug-ins per category makes no sense to me.
>
> Wouldn’t it make more sense to have some kind of profiles like
> - Build Java Web Applications
> - Deploy to Application Servers
> - Analyze Source Code
> - Measure Code Coverage
>  and so on and provide a set of plug-ins per profile? Or is this not feasible due to the enormous number of plug-ins?
>
> While the UI of Eclipse normally is not a good reference for best UI practices I think having something like the different eclipse versions is a good thing (eclipse for java developers, eclipse for testers, etc.)
>
>> Am 21.01.2016 um 19:56 schrieb Daniel Beck <[hidden email]>:
>>
>> Hi everyone,
>>
>> For Jenkins 2.0, we're aiming for a much better 'getting started' experience, aimed for users new to Jenkins.
>>
>> We already talked about this last year[1], but the discussion didn't really have a great result, so I'd like to start over by defining a list of guidelines on what kind of plugins qualify for inclusion first. My initial proposal is in the wiki[2]. Please take a look and provide feedback in this thread.
>>
>> Specific selection of plugins would be the next step.
>>
>> Daniel
>>
>> 1: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
>> 2: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>>
>> --
>> 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 [hidden email].
>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/56CE20F6.2090904%40orr.me.uk.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CABffhO5KtsM23XhvYEr5My%2Bsfx5wumsBqPGY5BhysZCodumORA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Luca Milanesio
In reply to this post by Daniel Beck
Why BitBucket, GitLab, GitHub and not Gerrit?
Gerrit is 100% OpenSource, whilst the same cannot be said about the others ;-)

Luca.

> On 24 Feb 2016, at 12:51, Daniel Beck <[hidden email]> wrote:
>
>
> On 24.02.2016, at 13:05, Victor Martinez <[hidden email]> wrote:
>
>> Mercurial and Perforce are not part of that list, although their usage are not massive compare to Git or SVN, but might be also important to have them as part of the SCM category. That's my point of view and sorry if I said something which it was already said previously.
>
> Good point. As I wrote on the wiki, SCM plugins are special (nothing much going on in Jenkins without them), so I recommend we're more accepting in that category. My current list of SCMs to include are (with approx. install count):
>
> https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin - 76k
> https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin - 123k
> https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+Plugin - 1500
> https://wiki.jenkins-ci.org/display/JENKINS/CVS+Plugin - 120k
> https://wiki.jenkins-ci.org/display/JENKINS/GitBucket+Plugin - 1200
> https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin - 20k
> https://wiki.jenkins-ci.org/display/JENKINS/Gitlab+Merge+Request+Builder+Plugin - 2000
> https://wiki.jenkins-ci.org/display/JENKINS/GitLab+Plugin - 5800
> https://wiki.jenkins-ci.org/display/JENKINS/Mercurial+Plugin - 6500
> https://wiki.jenkins-ci.org/display/JENKINS/P4+Plugin - 1500
> https://wiki.jenkins-ci.org/display/JENKINS/Repo+Plugin - 1300
> https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin - 1000
> https://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin - 2900
>
> While Perforce Plugin has more installs than P4, it stagnates, and its wiki page recommends use of P4, which is rapidly growing.
>
> --
> 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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D05C72E9-6127-4260-A8FD-0FC3D2E77E3D%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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C55B2F53-1C25-4FA1-A3FF-F46F40B8EFA0%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.0 initial setup plugin selection

Ulli Hafner
In reply to this post by Christopher Orr
Are we talking in this thread about the left or right selection in this demo (or both)? I.e. "Recommended plugins“ or "Customize your Plugins“?

> Am 24.02.2016 um 22:30 schrieb Christopher Orr <[hidden email]>:
>
> There's a demo video linked from the "Jenkins 2.0" wiki page:
> https://www.youtube.com/watch?v=kzRR8XR8hu4
>
> Though I have a feeling a saw a newer version at FOSDEM; not sure where
> the code can be found (not that I've looked).
>
> Regards,
> Chris
>
>
> On 24/02/16 22:14, Ullrich Hafner wrote:
>> How is the initial selection presented to the user? Is there already a mockup or screenshot available? Should the number of plug-ins per category be equal sized? Or are all categories shown in one screen?
>> E.g., if we have tabs for the categories then choosing e.g. just 3 plug-ins per category makes no sense to me.
>>
>> Wouldn’t it make more sense to have some kind of profiles like
>> - Build Java Web Applications
>> - Deploy to Application Servers
>> - Analyze Source Code
>> - Measure Code Coverage
>> and so on and provide a set of plug-ins per profile? Or is this not feasible due to the enormous number of plug-ins?
>>
>> While the UI of Eclipse normally is not a good reference for best UI practices I think having something like the different eclipse versions is a good thing (eclipse for java developers, eclipse for testers, etc.)
>>
>>> Am 21.01.2016 um 19:56 schrieb Daniel Beck <[hidden email]>:
>>>
>>> Hi everyone,
>>>
>>> For Jenkins 2.0, we're aiming for a much better 'getting started' experience, aimed for users new to Jenkins.
>>>
>>> We already talked about this last year[1], but the discussion didn't really have a great result, so I'd like to start over by defining a list of guidelines on what kind of plugins qualify for inclusion first. My initial proposal is in the wiki[2]. Please take a look and provide feedback in this thread.
>>>
>>> Specific selection of plugins would be the next step.
>>>
>>> Daniel
>>>
>>> 1: https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
>>> 2: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>>>
>>> --
>>> 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 [hidden email].
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%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 [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/56CE20F6.2090904%40orr.me.uk.
> 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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8C282E2F-9070-4424-AF7B-99EAF73C128D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (506 bytes) Download Attachment
1234