(replies inline) On Mon, 08 Aug 2016, Jesse Glick wrote:
> On Mon, Aug 8, 2016 at 11:48 AM, R. Tyler Croy <[email protected]> wrote: > > If your plugin > > repository already has a `Jenkinsfile`, or you're interested in creating one > > for your plugin, I would love to have your plugin built on our existing > > Jenkins-on-Jenkins. > > I continue to advocate having *all* plugins built via a predefined > script¹, as we do on jenkins.ci.cloudbees.com, rather than having > dozens of similar but subtly different `Jenkinsfile`s strewn around > the organization in various states of disrepair. > > > ¹At least one per build technology, like Maven or Gradle. This is a noble goal, but it simply is *not* enough (see the recent thread on Travis CI for plugins). The loss of flexibility has centralized responsibility for jenkins.ci.cloudbees.com in a way that has resulted unnecessary overhead (manually creating jobs) and stagnation (you only get JDK7 and you'll like it). I'm interested in having a few early adoptors for writing Jenkinsfiles for ci.jenkins.io so we can identify commonalities that should be going into a Global Library steps and uploaded appropriately. The top-down approach for templates in jenkins.ci.c.c worked when there was nothing in its place, but to me the Jenkinsfile and Pipeline is the correct means for distribution of responsibility here. I will not start inviting all plugins under jenkinsci/ until I'm confident that: * We have the right set of steps to reduce copy-paste * We can run Jenkins Pipeline with hundreds of committers and/or the right access control scheme that ensures system stability and security To me, this is the beginning of the iterative process to accomplish those tasks. - R. Tyler Croy ------------------------------------------------------ Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F ------------------------------------------------------ -- 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/20160808192003.GU22427%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
