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

> On 13.07.2016, at 12:42, Arnaud Héritier 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

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

On Wed, Jul 13, 2016 at 12:20 PM, Daniel Beck wrote: > > > On 30.05.2016, at 10:03, Arnaud Héritier 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

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

On Wed, Jul 13, 2016 at 12:20 PM, Daniel Beck wrote: > > > On 30.05.2016, at 10:03, Arnaud Héritier 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

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

> On 30.05.2016, at 10:03, Arnaud Héritier 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 m

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

ping ? On Mon, May 30, 2016 at 10:03 AM, Arnaud Héritier wrote: > Hi guys, > > What is the process to propose a new recommended plugin in the > installation wizard ? > I have this one in mind : > https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin > > Cheers > > > On Tu

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

Hi guys, What is the process to propose a new recommended plugin in the installation wizard ? I have this one in mind : https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin Cheers On Tue, Mar 22, 2016 at 9:57 PM, Baptiste Mathus wrote: > Wondering if BuildTriggerBadge

Re: Jenkins 2.0 initial setup plugin selection

Wondering if BuildTriggerBadge could/should make it in the "build features" part (disclaimer: my first plugin). It lets you quickly know what t

Re: Jenkins 2.0 initial setup plugin selection

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

Re: Jenkins 2.0 initial setup plugin selection

On 12.03.2016, at 00:33, Daniel Beck wrote: > KK released 2.0 alpha 3 earlier today. It contains a list of plugins based on > the recommendations in this thread (up until ~2 days ago), but due to a bug I > had to temporarily remove several to not make the first run experience > terrible. See

Re: Jenkins 2.0 initial setup plugin selection

On 10.03.2016, at 01:00, Daniel Beck wrote: > Hi everyone, > > based on all the feedback in this thread, I updated the spreadsheet linked > above, and opened a PR based on that: > > https://github.com/jenkinsci/jenkins/pull/2111 > > The PR description explains in detail what I did, and why.

Re: Jenkins 2.0 initial setup plugin selection

On 10.03.2016, at 20:43, James Nord wrote: > Why include CVS when Perforce is not included? I included P4 Plugin, rather than Perforce Plugin, based on a recommendation by Oleg. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsub

Re: Jenkins 2.0 initial setup plugin selection

Why include CVS when Perforce is not included? do we expect people who are still using CVS to suddenly think they need a CI system rather than a change of SCM :-) I would think that both are equally niche markets these days (for very different reasons) - so include both or neither. On Thursda

Re: Jenkins 2.0 initial setup plugin selection

On Thursday, March 10, 2016 at 10:58:38 AM UTC-5, Daniel Beck wrote: > > > On 10.03.2016, at 16:17, Samuel Van Oort > wrote: > > > > Embeddable build status plugin would be a strong candidate for > inclusion. I'm not sure what category would be best, but "Organization and > Administration"

Re: Jenkins 2.0 initial setup plugin selection

On 10.03.2016, at 16:17, Samuel Van Oort wrote: > > Embeddable build status plugin would be a strong candidate for inclusion. > I'm not sure what category would be best, but "Organization and > Administration" and "Build Features" both make some sense. Noted. FWIW I see this more in the for

Re: Jenkins 2.0 initial setup plugin selection

On 10.03.2016, at 16:39, Robert Sandell wrote: > What makes antisamy-markup-formatter an Organization type plugin? I would > have thought it to be Security related? The default is no formatting at all (escaping all the things). This allows you to use a 'safe' subset of HTML. It's also relevan

Re: Jenkins 2.0 initial setup plugin selection

What makes antisamy-markup-formatter an Organization type plugin? I would have thought it to be Security related? /B On Thu, Mar 10, 2016 at 4:17 PM, Samuel Van Oort wrote: > The list looks generally really solid (as do the recommendations). > > Looking at it, a couple comments: > > - Would it

Re: Jenkins 2.0 initial setup plugin selection

The list looks generally really solid (as do the recommendations). Looking at it, a couple comments: - Would it make sense to put parameterized trigger in the initial recommended plugins? - Is gradle plugin use strong enough to make it part of the core recommended plugins? - Junit & checkstyle

Re: Jenkins 2.0 initial setup plugin selection

On 23.02.2016, at 23:20, Daniel Beck 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 > o

Re: Jenkins 2.0 initial setup plugin selection

The stage View is presented front and center on the Jenkins 2.0 preview page, so it would be weird if that plugin wasn't in the initial plugin selection. https://jenkins-ci.org/2.0/ /B On Thu, Mar 3, 2016 at 8:07 PM, Samuel Van Oort wrote: > Would it make sense to add pipeline-stage-view plugi

Re: Jenkins 2.0 initial setup plugin selection

Would it make sense to add pipeline-stage-view plugin as a candidate for inclusion alongside the pipeline DSL? It provides greatly improved out-of-box experience for new users of pipeline. https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin As far as the wiki criteria go:

Re: Jenkins 2.0 initial setup plugin selection

On 02.03.2016, at 23:25, Ullrich Hafner wrote: > abbreviation SCM would be replaced with the full length name as in the other > categories? Great minds think alike: https://github.com/jenkinsci/jenkins/pull/2061/files#diff-b344e42853e15cd019f7758ab9783ad0R67 :-) -- You received this message

Re: Jenkins 2.0 initial setup plugin selection

On 02.03.2016, at 20:26, Slide wrote: > does a "YES" in the spreadsheet mean it will be installed by default, or be > in the recommended wizard? So far, this is the selection of available plugins only. -- You received this message because you are subscribed to the Google Groups "Jenkins Dev

Re: Jenkins 2.0 initial setup plugin selection

Wouldn’t it be more understandable for beginners if in the installation wizard the abbreviation SCM would be replaced with the full length name as in the other categories? > Am 24.02.2016 um 13:51 schrieb Daniel Beck : > > > On 24.02.2016, at 13:05, Victor Martinez > wrote: > >> Mercurial a

Re: Jenkins 2.0 initial setup plugin selection

> Am 25.02.2016 um 00:09 schrieb Christopher Orr : > > Nice work! > > I'm not sure whether `javadoc` (row 17, YES) is a useful suggestion; > it's seemingly only high on the list because it used to be part of core. > Yes, I also think that the JavaDoc plug-in is not used very often. I would al

Re: Jenkins 2.0 initial setup plugin selection

On Wed, Mar 2, 2016 at 3:00 PM, James Nord wrote: > So the credentials-binding plugin is something that I feel should be > promoted. Not sure if my opinion as maintainer of the plugin counts for anything, but if so, +1. :-) -- You received this message because you are subscribed to the Google G

Re: Jenkins 2.0 initial setup plugin selection

So the credentials-binding plugin is something that I feel should be promoted. It's the recommended (only?) way of securely using credentials within scripts in pipeline - so we should be pointing users towards it - if due to the "good practice" alone. As for PAM - does anyone use that anymore

Re: Jenkins 2.0 initial setup plugin selection

Maybe this has been answered before, but does a "YES" in the spreadsheet mean it will be installed by default, or be in the recommended wizard? On Wed, Mar 2, 2016 at 12:21 PM Jesse Glick wrote: > On Tue, Mar 1, 2016 at 2:59 PM, Kohsuke Kawaguchi wrote: > > PAM auth plugin should be in. […] it'

Re: Jenkins 2.0 initial setup plugin selection

On Tue, Mar 1, 2016 at 2:59 PM, Kohsuke Kawaguchi wrote: > PAM auth plugin should be in. […] it's hard to discover (PAM is > not in a vocabulary of most people) Maybe the plugin should just be renamed then. “Unix (PAM) Authentication”? Ditto `antisamy-markup-formatter` [sic, my fault], which tal

Re: Jenkins 2.0 initial setup plugin selection

On 02.03.2016, at 11:36, Victor Martinez wrote: > that plugin requires some Jenkins knowledge and might be tough to be used by > any newbie Jenkins user, hence it doesn't follow the 4th criteria "Are the > features it provides useful to someone fairly new to Jenkins?" Since it's a DSL there

Re: Jenkins 2.0 initial setup plugin selection

On 02.03.2016, at 11:43, Daniel Mueller wrote: > I found out later that the Git plugin seems to be installed by default > anyway, maybe you can find a way to make this more clear, I mean I was kinda > hoping to find it anyway but you got me confused for a second. The discussion on what to in

Re: Jenkins 2.0 initial setup plugin selection

distribution or any action taken or refrained from in reliance on it, is > prohibited and may be unlawful. Please notify the sender immediately. > > > > *From:* jenkin...@googlegroups.com [mailto: > jenkin...@googlegroups.com ] *On Behalf Of *Victor Martinez > *Sent:* Mittwoch

RE: Jenkins 2.0 initial setup plugin selection

oups.com [mailto:jenkinsci-dev@googlegroups.com] On Behalf Of Victor Martinez Sent: Mittwoch, 2. März 2016 11:37 To: Jenkins Developers Cc: m...@beckweb.net Subject: Re: Jenkins 2.0 initial setup plugin selection Quick question, maybe I'm again repeating the same question over and over, but

Re: Jenkins 2.0 initial setup plugin selection

Quick question, maybe I'm again repeating the same question over and over, but I've just reviewed the Jenkins2.0 alpha version and for some reason Pipeline plugin is part of the default plugin list, I'm not agains that plugin (just got some concerns about how to run unit/integrations tests with

Re: Jenkins 2.0 initial setup plugin selection

On 26.02.2016, at 23:34, Ullrich Hafner wrote: > Would’t it make sense to have the categories in the spreadsheet? So we can > select N plug-ins per category. Otherwise we would choose 3 plug-ins in one > tab and 20 plug-ins in another Currently the selection of popular plugins is not imbalanc

Re: Jenkins 2.0 initial setup plugin selection

Comment inline On Tue, Mar 1, 2016 at 12:45 PM Kohsuke Kawaguchi wrote: > Take CVS plugin for example. When you are configuring a freestyle job, > there is the SCM section and you don't see CVS in there, which makes you > realize you need a plugin. So it has a clear point of friction. > In this

Re: Jenkins 2.0 initial setup plugin selection

My comments to the current list. - PAM auth plugin should be in. It doesn't add any complexity unless used, it should be the default choice for anyone who has a proper Unix setup (like Sun was where there was a corporate wide NIS servers and all desktops & lab machines were pre-config

Re: Jenkins 2.0 initial setup plugin selection

This isn't in the criteria listed in Wiki page , but I always thought we have less incentive to include a plugin that has a clear point of friction (that there is a moment that novice users realize that he needs a pl

Re: Jenkins 2.0 initial setup plugin selection

2016-02-25 8:11 GMT-08:00 Daniel Beck : > > Please also remember that this isn't supposed to be the list of everyone's > favorite plugins -- it should actually be useful to people _getting > started_ with Jenkins. Plugins that allow configuring a hundred projects at > once don't seem that relevant

Re: Jenkins 2.0 initial setup plugin selection

I'm incredibly biased since I've spent the last few months improve its stability, but is the sauce labs plugin something that can be added to the list? On Friday, February 26, 2016 at 2:35:00 PM UTC-8, Ullrich Hafner wrote: > > I see. Would’t it make sense to have the categories in the spreadshe

Re: Jenkins 2.0 initial setup plugin selection

I see. Would’t it make sense to have the categories in the spreadsheet? So we can select N plug-ins per category. Otherwise we would choose 3 plug-ins in one tab and 20 plug-ins in another... > Am 25.02.2016 um 17:03 schrieb Daniel Beck : > > > On 24.02.2016, at 22:14, Ullrich Hafner wrote: >

Re: Jenkins 2.0 initial setup plugin selection

On Thu, Feb 25, 2016 at 5:01 PM, Daniel Beck wrote: > > On 24.02.2016, at 23:08, Luca Milanesio wrote: > > > Why BitBucket, GitLab, GitHub and not Gerrit? > > Gerrit is 100% OpenSource, whilst the same cannot be said about the > others ;-) > > On 24.02.2016, at 15:45, Robert Sandell wrote: > >

Re: Jenkins 2.0 initial setup plugin selection

On 25.02.2016, at 01:04, Arnaud Héritier wrote: > The Configuration Slicing plugin is also a must have from my POV I've seen too much brokenness from changed data formats (or data it did not support, e.g. email-ext per-trigger emails) etc. to be able to support this. So -1 from me on this sug

Re: Jenkins 2.0 initial setup plugin selection

On 25.02.2016, at 00:09, Christopher Orr wrote: > If we want to keep on using this mechanism to get translations, it > should maybe remain bundled with Jenkins, rather than appearing in this > list. The existing bundling mechanism has been removed entirely in favor of user controlled selection

Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 22:30, Christopher Orr wrote: > 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). It's on the 2.0 branch, and the "2.0-alpha-1" build uploaded by KK earlier this week has the code as well. The plugin select

Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 22:14, Ullrich Hafner wrote: > 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 no

Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 23:08, Luca Milanesio wrote: > Why BitBucket, GitLab, GitHub and not Gerrit? > Gerrit is 100% OpenSource, whilst the same cannot be said about the others ;-) On 24.02.2016, at 15:45, Robert Sandell wrote: > If GitLab and GitHub triggers are on the list because of their SCM

Re: Jenkins 2.0 initial setup plugin selection

On 25.02.2016, at 00:09, Ullrich Hafner wrote: > 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“? So far this is about the list of plugins on the right side -- I'd go for the recommended plugins i

Re: Jenkins 2.0 initial setup plugin selection

The Configuration Slicing plugin is also a must have from my POV On Thu, Feb 25, 2016 at 12:49 AM, Manfred Moser wrote: > I would suggest to add the config file provider plugin in the recommended > plugins. It seems to be the best way to provide Maven and other settings > file to a cluster witho

Re: Jenkins 2.0 initial setup plugin selection

I would suggest to add the config file provider plugin in the recommended plugins. It seems to be the best way to provide Maven and other settings file to a cluster without having to provision them on the nodes directly. Unless there is some other preferred method I dont know about. On Wed, Feb 24

Re: Jenkins 2.0 initial setup plugin selection

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 : > > There's a demo video linked from the "Jenkins 2.0" wiki page: > https://www.youtube.com/watch?v=k

Re: Jenkins 2.0 initial setup plugin selection

Nice work! I'm not sure whether `javadoc` (row 17, YES) is a useful suggestion; it's seemingly only high on the list because it used to be part of core. Having set up some jobs last week for various types of software projects, the Javadoc- and Doxygen-specific plugins don't seem to offer any obvi

Re: Jenkins 2.0 initial setup plugin selection

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 wrote: > > > On 24.02.2016, at 13:05, Victor Martinez > wrote: > >> Mercurial and Perforce are not part of that list, al

Re: Jenkins 2.0 initial setup plugin selection

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

Re: Jenkins 2.0 initial setup plugin selection

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 in

Re: Jenkins 2.0 initial setup plugin selection

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 ma

Re: Jenkins 2.0 initial setup plugin selection

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 wrote: > > On 24.02.2016

Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 13:05, Victor Martinez 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 in

Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 13:05, Victor Martinez 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 whi

Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 13:05, Victor Martinez 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

Re: Jenkins 2.0 initial setup plugin selection

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 a

Re: Jenkins 2.0 initial setup plugin selection

... and gravatar. And I believe docker-commons is just an API plugin. /B On Wed, Feb 24, 2016 at 11:44 AM, Robert Sandell 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

Re: Jenkins 2.0 initial setup plugin selection

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 wrote: > On 02/23/2016 07:08 PM, Daniel Beck wrote: > >> >> On 22.01.2016, at 14:14, ogondza wrote: >> >> How about some criteria for testing

Re: Jenkins 2.0 initial setup plugin selection

On 02/23/2016 07:08 PM, Daniel Beck wrote: On 22.01.2016, at 14:14, ogondza 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 s

Re: Jenkins 2.0 initial setup plugin selection

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 "

Re: Jenkins 2.0 initial setup plugin selection

On 23.02.2016, at 23:38, Arnaud Héritier 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 w

Re: Jenkins 2.0 initial setup plugin selection

#19 maven-plugin 100810 126144 157844 No: 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 wrote: > Hi everyone, > > I added two additional criteria to the wiki: The plugin sho

Re: Jenkins 2.0 initial setup plugin selection

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/

Re: Jenkins 2.0 initial setup plugin selection

On 22.01.2016, at 14:14, ogondza 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. No

Re: Jenkins 2.0 initial setup plugin selection

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 o

Jenkins 2.0 initial setup plugin selection

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