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 <svan...@cloudbees.com > <javascript:>> 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 former category. 'Build Features' is a > hack anyway and I would love to see some other suggestions…
> > Distributed builds is feeling very thin so far (as you've mentioned), > perhaps some of the docker stuff: > > > > - docker-plugin (fills the distributed *and* docker categories, woo) > > - docker-workflow plugin? (the docker pipeline). Or possibly under > pipelines? > > Are both of them strong enough if we don't consider the category issue? > Worst case we'll need to rethink those so it makes sense for the plugins we > suggest to new users. > Having worked with it extensively at this point, the docker pipeline is *definitely* strong enough; the warts are mostly around the initial docker configuration. I mention the docker-plugin because it is quite popular (doubled installation in the last year), and has guides for using it out: https://developer.jboss.org/people/pgier/blog/2014/06/30/on-demand-jenkins-slaves-using-docker?_sscc=t https://wiki.bitnami.com/Applications/BitNami_Jenkins/Configure_Jenkins_container_slaves Presently I'm using the docker pipeline for similar use cases (and then some), but it seems like a logical choice for many users. Or at least there should be another option out of the docker options to suggest for distributed builds in docker containers (whether it's this, docker-slaves, or docker custom build environment, etc etc). Since this is a common use cast, it would be quite helpful to have a specific option for users. > > ----- > > > - 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 would probably make sense in the top recommended > plugins list > > I guess we're starting the conversation on the initial plugin selection > now? :-) > Did I stick a foot in it? :-) The general recommendations there seem overall quite sensible though, but perhaps I'll un-stick my foot since this may be a tad contentious. > > A reminder: > > > For the recommended plugins, I had to improvise, as these have not been > discussed yet. Despite this I decided to provide a "real" selection as > we've received quite confused/negative feedback on the previous list > contents, and didn't want that repeated with the recommended plugins list. > > Your suggestions look sensible. FWIW I mainly added Gradle (and Ant) to > not have that category empty (and failed to do the same for build > analysis…). Maven plugin is out of the list, and Maven build step is a core > feature, so the list lacks wrt those. > > > -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4e86e07b-35ae-4623-9f48-06d6ca243e82%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
