It is great to see the pick up of local activities through hosted JAMs. In October, the Jenkins community hosted Atlanta JAM and Bay Area JAM. Many thanks to our sponsors: Ericsson, CloudBees, Blazemeter, NetRoadShow. Here’s a summary of what was discussed: Atlanta JAM - Jenkins workflow and Docker to reduce friction in DevOps efforts. Bay Area JAM- Performance testing strategies, incorporating performance tests into Jenkins workflows...

Updated 2015-11-11 15:00 UTC: We have released Jenkins 1.638 and 1.625.2 which contain a fix for this vulnerability. See the security advisory for more information about these releases. Updated 2015-11-06 03:55 UTC: Included a updated mitigation script which doesn’t have a Jenkins boot race condition Earlier today we received numerous reports about a previously undisclosed "https://en.wikipedia.org/wiki/Zero-day_%28computing%29[zero day]" critical remote code execution vulnerability and exploit in Jenkins...

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...