Preceding some of last week’s Jenkins 2.0 discussions, there had been some threads on whether we should move Jenkins to require Java 8. The introduction of Java 8 last year brought performance improvements and highly desirable API changes, which make developing Java-based applications (arguably) much easier than before. The release was followed earlier this year by the end-of-life announcement for Java 7; the writing...

With more than a thousand public plugins in the Jenkins community now, it should come as no surprise that some of them are no longer actively maintained. Plugin authors move on when they change jobs, or lose interest in the plugin, and that’s fine. Plugins are hosted on the Jenkins project infrastructure after all, and when a maintainer moves on, others can continue their...

This week we have featured a number of proposals for what we would like to see in "https://wiki.jenkins.io/display/JENKINS/Jenkins+2.0[Jenkins 2.0]", the vision of which is to make Jenkins users more efficient, productive and happy. We started with some more internally facing changes and have slowly progressed from the "inside-out" to today’s topic: improving the out of the box user experience. That is to say, the experience...

We have been featuring a few proposals this week for what "https://wiki.jenkins.io/display/JENKINS/Jenkins+2.0[Jenkins 2.0]" is going to include. Today we’ll be diving into the most noticeable changes being proposed for Jenkins 2.0: the User Experience (UX) improvements Thus far in this blog series we have reviewed proposals covering: Introducing a policy for API deprecation Splitting Groovy out of 'core' Pipeline as code front and center The UX improvements being proposed aren’t...

We have been featuring a few proposals this week for what "https://wiki.jenkins.io/display/JENKINS/Jenkins+2.0[Jenkins 2.0]" is going to include, today we’re discussing my personal favorite, which I believe will have a tremendously positive impact for years to come (not to be too biased!): moving the "Pipeline as Code" support in Jenkins to the front and center. Thus far in this blog series we have reviewed proposals covering: Introducing a...

As I mentioned in yesterday’s post, there’s been a lot of discussion recently about what "https://wiki.jenkins.io/display/JENKINS/Jenkins+2.0[Jenkins 2.0]" means. In a recent "Office Hours" session, Kohsuke Kawaguchi presented his vision for Jenkins 2.0 in a office hours session, the slides for which can be found in this Google Presentation. Roughly paraphrasing Kohsuke’s vision, 2.0 is primarily about making things better for the thousands of users out there. This week, we’ll be reviewing some...

Over the past few weeks there has been a vibrant discussion happening on the jenkinsci-dev@ mailing list as to what "https://wiki.jenkins.io/display/JENKINS/Jenkins+2.0[Jenkins 2.0]" means. While Jenkins does not currently adhere to semantic versioning, the change of a major version number does indicate a major milestone for the community. Project founder, Kohsuke Kawaguchi presented his vision for Jenkins 2.0 in a office hours session, the slides for which can be found in this...