Recent Blog Posts

At Jenkins World last month, we continued the tradition of "lunch-time demos" in the Jenkins project’s booth which we started in 2016. We invited a number of Jenkins contributors to present brief 10-15 minute demos on something they were working on, or considered themselves experts in. Continuing the post-Jenkins World tradition, we also just hosted a "Jenkins Online Meetup" featuring a selection of those lunch-time demos. I would like to thank Alyssa Tong for organizing this online meetup, Liam Newman for acting as the host, and our speakers: Oleg Nenashev Michael Hüttermann Thorsten Scherler Stephen Donner Mark Waite Keith Zantow Below are some links from the sample projects demonstrated and the direct links to each session. Developing Pipeline Libraries Locally Video link If you have ever tried developing Pipeline Libraries, you may have noticed how long it takes to deploy a new version to server to discover just another syntax error. I will show how to edit and test Pipeline libraries locally before committing to the repository (with Configuration-as-Code and Docker). Slides Source Code Demo container Delivery Pipelines with Jenkins Video link Showing off how to set up holistic Delivery Pipelines with the DevOps enabler tool Jenkins. Demo application Pimp my Blue Ocean Video link How to customize Blue Ocean, where I create a custom plugin and extending Blue Ocean with custom theme and custom components. Presentation and demo code Deliver Blue Ocean Components at the Speed of Light Video link Using storybook.js.org for Blue Ocean frontend to speed up the delivery process - validate with PM and designer the UX. Showing how quickly you develop your components. Presentation and demo code Mozilla’s Declarative + Shared Libraries Setup Video link How Mozilla is using Declarative Pipelines and shared libraries together. Google Doc with links Shared Library source code Documentation for the shared library See also the #fx-test IRC channel on irc.mozilla.org Git Tips and Tricks Video link Latest capabilities in the git plugin, like large file support, reference repositories and some reminders of existing tips that can reduce server load, decrease job time, and decrease disc use. Visual Pipeline Creation in Blue Ocean Video link We will show how to use Blue Ocean to build a real-world continuous delivery pipeline using the visual pipeline editor. We will coordinate multiple components of a web application across test and production environments, simulating a modern development and deployment workflow.

Earlier this month, a full-day event about Jenkins Pipeline was organized in Toulouse, France with the Toulouse JAM. After a warm-up on the previous Tuesday where Michaël Pailloncy had given a talk at the local Toulouse Devops user group about Jenkins Pipeline ecosystem, we were ready for more digging :-). The agenda We had planned the day in two parts: Morning would be a more driven workshop with slides & exercises to be completed Pizzas & beverages to split the day :-) Afternoon would be somehow like an Unconference, where people basically decide by themselves what they want to work on. We planned to have 30 attendees. We ended up having 25. We considered having more people, but finally decided that for a first time it would be better to start not too big. Infrastructure Infrastructure was sponsored by DigitalOcean. For each attendee, we provisioned : One Controller, preconfigured to be able to dynamically provision agents. One staging environment One production environment [ 1 ] One SonarQube instance Workshop content & infrastructure After an initial quick presentation to settle context and remind some general things about Continuous Delivery and Jenkins, we started the workshop per se. It is composed of 3 parts, which are readable here [ 2 ], but very few people were able to start the part 3. Hackergarten / Unconference So we let people decide what they wanted to work on during the afternoon. We decided to use post-its: each attendee would write down what they wanted to work on, one idea per post-it (max 2 per person). Then, we dropped those onto a white-board and tried grouping those by theme. In the end, overall, the following themes went out: Hack on Jenkins development & Contribute to Jenkins Complete the workshops Work on use-case oriented things Work on Docker & Pipeline join usages Hackergarten Many Jenkins accounts were created, and many JIRA and pull requests were filed. It was nice to see people asking questions like: "so, should I create a JIRA issue for this?" or "how do I interact with people". Pretty generic "how do I work on open source software" questions sometimes, but important because you felt like people were genuinely interested and needed not much to start contributing. Here are the pull requests filed during this afternoon: blueocean-pipeline-editor-plugin#30 jenkins#2785 jenkins#2786 jenkins#2787 jenkins#2788 You can see that though most of the PRs were typo-related, the one that got merged first was the one about code :-). So, Jeremie Violas wins the Bobble Head as promised! Why so many typo-related PRs? Simply because people were somehow encouraged to find some to get used to the round trip of: fixing an issue and filing the associated pull request, rinse & repeat. I do think this is also a pretty nice and simple first step to understand how to build Jenkins and start interacting with the community. The result People seemed pretty happy and we got some nice comments like "now I have a clearer vision of what this Pipeline thing is about". Some attendees also dropped nice comments on the meetup page. So it’s cool because when you’re doing such things on your free time, it’s the main reward you can get. If you’re an attendee to such events, don’t forget to thank people organizing those, and more importantly to provide constructive feedback. We are generally eager to know what could be done better for next time. Conclusion Overall we are very happy with the energy of that day, and we definitely plan to set up a new session in the next few months, probably with a bit more people. Some thoughts: Infrastructure: when you plan to have many VM per attendee, double-check the limits your Cloud Provider may have by default. I had bumped it to 250 the day before the workshop, and asked for another one to 500 during the workshop (though in the end, 250 was probably enough, but this’ll give room for the next time with more people :-)). Logistics: warning, secret ahead: this is very time consuming. Not necessarily the amount of work itself, more that it implies very big latency. For instance, give it 2 to 3 weeks minimum to have answers about sponsoring in general. Pinging again in case of no answer after 2 days would probably be seen as rude, and possibly lead to make things worse for obvious reasons, so plan ahead. Thank you DigitalOcean for sponsoring the Infrastructure We got way more than 100 VMs running at the same time during the day thanks to their help! HarryCow Coworking for hosting the event To CloudBees for sponsoring the food for all the participants Also for providing a bunch of goodies: stickers and T-Shirts for everybody GitHub for providing stickers 1. For the sake of the simplicity of the workshop, those environments were actually a single VM: the goal was here to illustrate what we could do using Jenkins Pipeline, discussing scalability or more involved deployment techniques was obviously out of scope. 2. in French only for now, but translating it into English to make it possibly shared and reusable among JAMs is being discussed

I do not think it is an exaggeration to say: 2016 was the best year yet for the Jenkins project. Since the first commit in 2006, the project has reached a number of significant milestones in its ten years but we have never experienced the breadth of major milestones in such a short amount of time. From Jenkins 2 and Blue Ocean to the Google Summer of Code and Jenkins World, I wanted to take a moment and celebrate the myriad of accomplishments which couldn’t have happened without the help from everybody who participates in the Jenkins project. The 1,300+ contributors to the jenkinsci GitHub organization, the 4,000+ members of the developers mailing list, the 8,000+ members of the users mailing list, and countless others who have reported issues, submitted pull requests, and presented at meetups and conferences. Jenkins 2 Through the course of 2016, the Jenkins project published 16 LTS releases and 54 Weekly releases. Of those 70 releases, the most notable may have been the Jenkins 2.0 release which was published in April. Jenkins 2 made Pipeline as Code front-and-center in the user experience, introduced a new "Getting Started" experience, and included a number of other small UI improvements, all while maintaining backwards compatibility with existing Jenkins environments. Since April, we have released a number of LTS releases using Jenkins 2 as a baseline, meaning the Jenkins project no longer maintains any 1.x release lines. The Pipeline efforts have continuted to gain steam since April, covered on this blog with a number of posts tagged "pipeline". Closing out 2016 with the announcement of the beta for Declarative Pipeline syntax which is expected in early 2017. Blue Ocean Hot on the heels of Jenkins 2 announcement"Blue Ocean, a new user experience for Jenkins", was open sourced in May. Blue Ocean is a new project that rethinks the user experience of Jenkins. Designed from the ground up for Jenkins Pipeline and compatible with Freestyle jobs. The goal for the project is to reduce clutter and increase clarity for every member of a team using Jenkins. The Blue Ocean beta can be installed from the Update Center and can be run in production Jenkins environments alongside the existing UI. It adds the new user experience under /blue in the environment but does not disturb the existing UI. Blue Ocean is expected to reach "1.0" in the first half of 2017. Azure Also in May of 2016, the Jenkins project announced an exciting Partnership with Microsoft to run our project infrastructure on Azure. While the migration of Jenkins project infrastructure into Azure is still on-going, there have been some notable milestones reached already: End-to-end TLS encrypted delivery for Debian/openSUSE/Red Hat repositories which are configured to use https://pkg.jenkins.io by the end-user. Major capacity improvements to ci.jenkins.io providing on-demand Ubuntu and Windows build/test infrastructure. A full continuous delivery Pipeline for all Azure-based infrastructure using Terraform from Jenkins. The migration to Azure is expected to complete in 2017. Google Summer of Code For the first time in the history of the project, Jenkins was accepted into Google Summer of Code 2016. Google Summer of Code (GSoC) is an annual, international, program which encourages college-aged students to participate with open source projects during the summer break between classes. Students accepted into the program receive a stipend, paid by Google, to work well-defined projects to improve or enhance the Jenkins project. In exchange, numerous Jenkins community members volunteered as "mentors" for students to help integrate them into the open source community and succeed in completing their summer projects. A lot was learned during the summer which we look forward to applying to Google Summer of Code 2017 Jenkins World In September, over one thousand people attended Jenkins World, in Santa Clara, California. Following the event, Liam posted a series of blog posts which highlight some of the fantastic content shared by Jenkins users and contributors from around the world, such as: The demos from the "Experts" Sessions on Scaling Jenkins Using Jenkins Pipeline The Contributor Summit Jenkins World was the first global event of its kind for Jenkins, it brought users and contributors together to exchange ideas on the current state of the project, celebrate accomplishments of the past year, and look ahead at all the exiting enhancements coming down the pipe(line). It was such a smashing success that Jenkins World 2017 is already scheduled for August 30-31st in San Francisco, California. JAM Finally, 2016 saw tremendous growth in the number of Jenkins Area Meetups (JAMs) hosted around the world. JAMs are local meetups intended to bring Jenkins users and contributors together for socializing and learning. JAMs are organized by local Jenkins community members who have a passion for sharing new Jenkins concepts, patterns and tools. Driven by current Jenkins Events Officer, Alyssa Tong, and the dozens of passionate organizers, JAMs have become a great way to meet other Jenkins users near you. While we don’t yet have JAMs on each of the seven continents, you can always join the Jenkins Online Meetup. Though we’re hoping more groups will be founded near you in 2017! I am personally grateful for the variety and volume of contributions made by thousands of people to the Jenkins project this year. I believe I can speak for project founder, Kohsuke Kawaguchi, in stating that the Jenkins community has grown beyond our anything we could have imagined five years ago, let alone ten! There are number of ways to participate in the Jenkins project, so if you didn’t have an opportunity to join in during 2016, we hope to see you next year!

As we near the end of the year, the number of November JAMs show that the Jenkins community isn’t slowing down for holiday season. We had a number of excellent events hosted around the world this November with plenty of great stories and presentations shared by the various members of the world-wide Jenkins community. Melbourne, Australia JAM Melbourne JAM leaders, Raisa and Bhuva hosted Blue Ocean for the inaugural meeting. Attendees learned the values of Blue Ocean, a project that rethinks the user experience of Jenkins, modeling and presenting the process of software delivery by surfacing information that is important to development teams with as few clicks as possible, while still staying true to the extensibility that Jenkins always has had as a core value. Thank you James Dumay for stopping by to take part in the inauguration. Singapore, Singapore JAM One of the members who had several years of experience using Jenkins (since Hudson days in fact) to present some basics on Continuous Integration with GitHub. It was targeted at new members who are starting out with Jenkins. We understand that we cannot always serve advanced topics to cater to the experienced users and neglect the newbies so this session was targeted to help give new users an introduction to Jenkins. It went well with about 15-20 attendees and we hope to run some hands-on workshops in 2017. Some members were looking forward to freebies like stickers and T-shirts too! Moscow, Russia JAM Moscow JAM leaders, Kirill Tolkachev and Oleg Nenashev led the inaugural meeting with a packed full agenda. Oleg began the meeting with an update on Jenkins 2 what improvements users can expect and what enhancements are in the works within the Jenkins project. Following Oleg, Kirill shared how his team in Alfa Laboratory used Jenkins to improve CD/DevOps in their projects (with Jenkins Pipeline, Job DSL and Blue Ocean), the problems they experienced and how they fixed them. Then Oleg talked about Jenkins Pipeline internals, main features and recent changes in the ecosystem. It was followed up by a discussion of large-scale Jenkins instances at the after-party. The recording of the event can be found on YouTube. Milan, Italy JAM The first meetup was a great opportunity to meet local Jenkins fans to learn and share Jenkins experiences at a local cafe. San Francisco, California JAM R. Tyler Croy performed a 30 minutes live Pipeline coding demo to a relatively novice audience (though all had used Jenkins). A good amount of questions from the audience which conveyed an appetite for the content being presented. Ryan Wallner, presenter from ClusterHQ, also gave a demo based around Pipeline talking about ClusterHQ’s "Fli" integration with a delivery pipeline. Washington, DC JAM There was a fantastic 90% showup rate at this month’s meetup - 58 RSVPs and 52 in attendance was pretty impressive. All this may be due to Fannie Mae’s story - the success of how they used Jenkins for CI/CD as part of their DevOps adoption. Afterwards, there was a lot of interests and further discussions taking place. Next month’s host will be Freddie Mac. Seattle, Washington JAM Long time Jenkins community member and Seattle JAM leader, Khai Do showed how OpenStack uses "Jenkins Job Builder" to manage and run thousands of Jenkins jobs per day in their multi-controller CI/CD system. He also compared Jenkins Job Builder with other Jenkins "Infrastructure-as-code" technologies - Jenkins Pipeline and Jenkins JobDSL. It was followed by an in-depth Q&A and discussion session. Dallas/Forth Worth, Texas (DFW) JAM The November DFW JAM was the most strongly attended of the year! DFW JAM leader, Eric Smalling discussed the benefits of dynamic build agents and demonstrated various ways to implement them such as the EC2 and Docker plugins. There was a lot of interest and discussion, especially around Docker and the ability it provides to have ephemeral agents with very little provisioning time. The recording can be downloaded from Gooel Drive. Links Start a JAM in your city if there isn’t one already. Become a JAM member. Become an online JAM member Be a JAM speaker or sponsor. Let us know jenkinsci-jam@googlegroups.com Become a Jenkins project contributor

Happy Holidays! A special shout out to all JAM leaders who continue to keep local activities going in December. Online JAM December 14 | Live Demos: Pipeline, Git, and Blue Ocean North America December 7 | Seattle JAM: Jenkins at Microsoft December 14 | Los Angeles JAM: Jenkins Days December 14 | Guadalajara JAM: Jenkins & Docker Australia December 14 | Melbourne JAM: Meeting at AWS Office Links Start a JAM in your city if there isn’t one already. Become a JAM member Become an online JAM member Speak or sponsor at a JAM. Contact us at jenkinsci-jam@googlegroups.com Become a Jenkins project contributor

November is packed full of meetups and events. If you are in any of the areas below please stop by to say "Hi" and talk Jenkins over beer. North America November 15 | SF JAM: Let’s Talk CI/CD and DevOps with ClusterHQ and Jenkins November 15 | DC JAM: Jenkins and Fannie Mae November 30 | Albuquerque JAM: Learn About Blue Ocean November 30 | Guadalajara JAM: Jenkins Install and Setup Europe November 10 | Amsterdam JAM: Jenkins and Docker - Multiple Uses for Containers and Jenkins November 10 | Milano JAM: Meet and Greet Australia November 15 | Melbourne JAM: Blue Ocean - A New User Experience Asia November 17 | Singapore JAM: CI Using Source Code on GitHub Links Start a JAM in your city if there isn’t one already. Become a JAM member Become an online JAM member Speak or sponsor at a JAM. Contact us at jenkinsci-jam@googlegroups.com Become a Jenkins project contributor

I would like to write about two last Jenkins Meetups in Saint Petersburg, Russia. Meetup #3. Jenkins Administration (May 20, 2016) In May we had a meetup about Jenkins administration techniques. At this meetup we were talking about common Jenkins ecosystem components like custom update centers, tool repositories and generic jobs. Talks: Kirill Merkushev, Yandex, "Juseppe. A custom Update Center for Jenkins" Presentation (rus) Keywords: Juseppe Anna Muravieva, EMC, "Generic jobs in Jenkins. How to build anything?" Presentation (rus) Keywords: Generic Builds, Scripted Build Wrappers Oleg Nenashev, CloudBees, "Building Jenkins Tool infrastructures with help of Custom Tools Plugin and Docker" Presentation (rus) Keywords: Custom Tools Plugin, Extra Tool Installers Plugin, Docker Meetup #4. IT Global Meetup (July 23, 2016) In Saint Petersburg there is a regular gathering of local IT communities. This IT Global Meetup is a full-day event, which provides an opportunity to dozens of communities and hundreds of visitors to meet at a single place. On July 23rd our local Jenkins community participated in the eight’s global meetup. We conduced 2 talks in main tracks and also had a round table in the evening. Talks: Oleg Nenashev, CloudBees, "About Jenkins 2 and future plans" Oleg provided a top-level overview about changes in Jenkins, shared insights about upgrading to the new Jenkins 2.7.1 LTS and talked about Jenkins plans Presentation (rus) Aleksandr Tarasov, Alfa-Laboratory, "Continuous Delivery with Jenkins: Lessons learned" Aleksandr summarized AlfaLab’s experience of Jenkins usage for Continuous Delivery in their environment. He talked about the flow based on Jenkins Pipeline, JobDSL and BlueOcean prototype. Presentation (rus) After the talks we had a roundtable about Jenkins (~10 Jenkins experts). Oleg provided an overview of Docker and Configuration-as-Code features available in Jenkins, and then we talked about common use-cases in Jenkins installations. We hope to finally organize a "Jenkins & Docker" meetup at some point. Q&A If you have any questions, all speakers can be contacted via Jenkins RU Gitter Chat. Links St. Petersburg Meetup page (follow the events here) St. Petersburg Meetup Twitter Jenkins RU Twitter Jenkins RU Gitter Chat IT Global Meetup Acknowledgments The events have been organized with help from CloudBees, EMC and organizers of the St. Petersburg IT Global Meetup.

It is hard to believe that the first half of 2016 is almost over and summer is just around the corner. As usual, there are plenty of educational Jenkins events planned for this month. Below lists what’s happening in your neck of the woods: Online JAM June 14: Plugin Development - Basics North America JAMs June 14: Pipeline in a Windows Environment - Boston, Massachusetts June 15: Open Source Jenkins 2.0, What’s New? - Washington, DC June 22: Continuously Deploying Containers with Jenkins Pipeline to a Docker Swarm Cluster - Seattle, Washington Europe JAM June 14: Jenkins 2.0 - London, United Kingdom June 22: Pipeline As Code - Toulouse, France Links Start a JAM in your city if there isn’t one already. Become a JAM member Become an online JAM member Speak or sponsor at a JAM. Contact us at jenkinsci-jam@googlegroups.com Take advantage of the super-early-bird price to Jenkins World 2016 Become a Jenkins project contributor