Recent Blog Posts

As you probably know, on this year Jenkins projects participates in Google Summer of Code 2016. You can find more information about the accepted projects on the GSoC subproject page and in the Jenkins Developer mailing list. On this week GSoC students are going to present their projects as a part of mid-term evaluation, which covers one month of community bonding and one month of coding. We would like to invite Jenkins developers to attend these meetings. There are two additional months of coding ahead for successful students, so any feedback from Jenkins contributors and users will be appreciated. Meeting #1 - June 23, 7:00 PM UTC - 9:00 PM UTC Support Core plugin improvements by Minudika Malshan Intro blogpost External Workspace Manager by Alex Somai Intro blogpost Plugin documentation publishing to jenkins.io by Cynthia Anyango Intro blogpost Q&A session Meeting link Meeting #2 - June 24, 8AM UTC - 9 AM UTC Jenkins WebUI: Improving Job Creation/Configuration by Samat Davletshin Intro blogpost Q&A session Meeting link Both meetings will be conducted and recorded via Hangouts on Air. The recorded sessions will be made public after the meetup. The agenda may change a bit. Links Mid-term presentations announcement on Jenkins Developer mailing list Jenkins GSoC 2016 Wiki Page Jenkins project page on the GSoC2016 website

As you probably know, Jenkins project has been accepted to Google Summer of Code 2016. During last month we were working with students in order to discuss their project ideas and to review their application drafts. Thanks again to all students and mentors for your hard work during about ten office hours and dozens of other calls/chats! Current status We have successfully handled the student application period We have received a bunch of good project proposals (mentors cannot disclose the number) We have done the preliminary filtering of applications GSoC mentors and organization admins have prepared the project slot application draft Currently we are looking for mentors. We have a minimal required number for the current project slot application plan, but additional expertise would allow us to share the load and to provide more expertise to students. If you want to be a mentor: Check out mentor requirements here. Check out the project ideas here. Student application period is finished, so it is too late to propose project ideas for this year You can join the mentor team for one of the mentioned projects Hot areas: UI improvements, Fingerprints, External Workspace Manager Contact Google GSoC admins via jenkinsci-gsoc-org@googlegroups.com Links GSoC2016 page on our Wiki Jenkins page on the GSoC2016 website

A bug was introduced in Jenkins versions 1.645 and 1.642.2 which caused Jenkins to send anonymous usage statistics, even if the administrator opted-out of reporting usage data in the Jenkins web UI. If you are running one of the affected versions, the best/easiest solution is to upgrade. The bug does not affect Jenkins 1.653 or newer, or Jenkins LTS 1.642.4 or newer. If you cannot upgrade, it is possible to immediately disable submission of usage statistics by running the following script in "Manage Jenkins » Script Console": hudson.model.UsageStatistics.DISABLED = true This will immediately disable usage data submission until you restart Jenkins. To make this permanent, change your Jenkins startup script so it passes a system property to the java process: java -Dhudson.model.UsageStatistics.disabled=true -jar …/jenkins.war For information how to do this when using one of the installers/packages, see the installer/package documentation here. To verify that usage stats submission is disabled, run the following script in "Manage Jenkins » Script Console" and confirm the result is true: println hudson.model.UsageStatistics.DISABLED We have much more information about the issue and our usage statistics process in our wiki. While we do not consider this a security advisory, if you are a Jenkins administrator we highly recommend subscribing to our jenkinsci-advisories@ mailing list.

We are happy to announce that Jenkins project application has been accepted to Google Summer of Code 2016 (GSoC). Thanks to everybody who helped prepare the application and submitted project ideas! We would like to invite students to join the Jenkins community and work together on the ongoing Jenkins 2.0 activities and other medium-term projects. The student projects we are primarily interested in would improve the overall Jenkins user experience in a number of different aspects. This includes user interface changes and stability improvements but also major new features such as Pipeline as code. The projects we’ve suggested revolve around all parts of the Jenkins project: core, plugins, website and our internal automation infrastructure. More details on what has been suggested can be found on the wiki which include: Jenkins web interface improvements "Update Center 2.0" New generation of the fingerprinting engine External workspace manager Integration of Docker plugins with Jenkins 2.0 features Plugins for Electronic Design Automation and Embedded tools integration Improvements of the Support plugin Improvements to Jenkins project infrastructure: core infra, website, plugin documentation and more If you are a student: Check out the project ideas here. Select an interesting project idea or draft your own proposal. If you are not familiar with Jenkins, we highly recommend trying it out with one of your previous projects. You can also try available Jenkins features from the project ideas. Introduce yourself the community and start your project proposal discussion (see the guidelines here). Join us at GSoC office hours. We plan to have two meetings starting on March 7th. If you want to be a mentor: Feel free to team up with other mentors We accept extra project proposals from mentors until March 9th. Links Jenkins project page on the GSoC2016 website GSoC2016 page on our wiki Announcement in Twitter

On January 20, the first San Francisco JAM (Jenkins Area Meetup) of the new year was held at Mesosphere ’s offices. We had two speakers - myself, and Roger Ignazio, an infrastructure automation engineer at Mesosphere. Around forty people attended and enjoyed the food and drinks Mesosphere provided for us. Links to the talks are below: Elastic Jenkins with Mesos and DCOS, by Roger Ignazio Who is Jenkins?, by Andrew Bayer More JAMs will be happening in the coming months - for example, the first Los Angeles JAM is tentatively planned for early March, 2016! You can always find out the latest on JAMs around the world at the Jenkins Area Meetup page.

On December 15, the Toulouse JAM was co-hosted with the Toulouse JUG and Toulouse DevOps. Indeed it made sense since Jenkins is written in Java, makes use of Groovy code in many places (system groovy script, job dsl, workflow…​), and it also made sense to co-organize with the local DevOps community since Jenkins is also a great tool to enable Continuous Integration, Continuous Delivery and automation in general. There were 103 RSVPs, with 80 to 90 people in attendance. There were 3 talks planned for the evening: Job DSL Intro [fr], by Ghislain Mahieux Video recording Workflow plugin [fr], by Michaël Pailloncy (co-maintainer of the Build Trigger Badge plugin) Video recording Feedback on almost 10 years of CI and what’s upcoming [fr], demo with Jenkins build scaling with Docker Swarm, by Baptiste Mathus Video recording Photos can be found here

Thank you to Netflix for sponsoring the yummy burrito bar and offered up their brand new auditorium to host Jenkins Developers and Users Meetup group on Dec 16. We had 96 RSVPs which was impressive. Our speaker for the evening was Akshay Dayal, Software Engineer at Google. Akshay’s session was about Scaling Jenkins - how and why Google decided to scale their existing Jenkins cluster (OSS) to meet their security/availability and failover requirements and how heavy automation played an important role in this effort. The second talk was about how Google worked with Jenkins to read config data externally. Slides are listed below. The video will be posted on the meetup page) once it becomes available. Slides for the talks are linked below: Scaling Jenkins External Project Check out where Jenkins Area Meetups (JAMs) are located in the world. Don’t see a JAM in your area? why not start your own, here’s how.

Although December is a short month due to the holidays, there has been a good amount of local Jenkins activities that took place regardless of holiday obligations. Today and tomorrow I will be doing a series of posts to summarize December JAM World Tour. Special thanks to the JAM organizers and co-organizers who made it all happen in these cities: Lima, Peru St.Petersburg, Russia Toulouse, France Bay Area, CA On December 9 Lima JAM hosted their first Jenkins meetup in Lima, Peru. There were attendance from various roles of DevOps: Dev, QA, and Ops. There was also a good mixture of different levels of Jenkins users, some were new and just starting to use Jenkins while others had extensive Jenkins experience. The group has been invited by Docker and Ansible meetup organizers for a joint event in January to showcase technologies from Jenkins, Docker, and Ansible. Congrats to Lima JAM group. Slides from the meetup can be found here. Additional shared resources used in the Lima JAM can be found here. Check out where Jenkins Area Meetups (JAMs) are located in the world. Don’t see a JAM in your area? why not start your own, here’s how.