I have been a Jenkins user and administrator on and off since around 2010. In 2016, I got into evangelism by organizing aJenkins Area Meetup in San Francisco. I spoke at Jenkins World 2017  and again at Jenkins World 2018. Justin Harringa and I wrote and open sourced the Config Driven Pipeline Plugin. For two years running, I’ve been a mentor for two Google Summer of Code projects: External Fingerprint Storage Project and Remoting over Apache Kafka with Kubernetes features.

With this nomination, I hope to continue helping strengthen and progress the community further. As a member of the governance board, I’ll bring a fresh perspective by asking questions, providing feedback, and finding opportunities for others to contribute.

Profile links:GitHub,LinkedIn

Affiliations: Stripe

As a consultant I support my customers with their Jenkins issues since the beginning of 2017. And almost from the start it was some kind of "as code" approach. The experience I gained during that time resulted in getting myself involved in the development of Configuration as Code Plugin for Jenkins. I consider becoming a part of Jenkins Community one of the most valuable experiences in my career so far. I appreciate how much I have learned and how welcoming the community is.

I am not a very active contributor these days, at least when it comes to code, but what I have to offer is rather extensive experience with Jenkins end users - from small, single instance setups to environments with hundreds of controllers run in a different way on different operating systems. Every day I see challenges those users go through, I know what issues they are facing and which features they consider valuable or missing. As a Jenkins Governance Board Member I can represent those users.

Thanks to my involvement in Configuration as Code Plugin development I had a chance to deliver a number of public presentations where I focused on the benefits of the solution and tried to make it easier for newcomers to try it. Here are a few examples of my activities related to Jenkins Configuration as Code:blogpost,cdCON presentation,podcast recording. So my focus is not only on representing users but also on educating them, and educating myself, so I actually know what they need and why.

Profile links:GitHub,LinkedIn,Twitter

Affiliations: Eficode (former Praqma)

I started to use Jenkins back in 2008, when it still had a different name. In 2011 I started to contribute and created my first little plugin calledextra-columns. Since then, using and administering Jenkins servers has become a major part of my work life, while getting involved with the Jenkins community kickstarted my interest and involvement with open source software and communities.

I’ve been working as a release engineer at the Eclipse Foundation since 2016, supporting 250+ Jenkins instances for various open source projects. I’d be honored to bring a user and admin oriented perspective to the Governance Board and help shape the future of Jenkins.

Profile links:GitHub,Twitter

Affiliations: Eclipse Foundation

I got started with Jenkins early on when I was just getting started with testing. I knew there had to be a way to run the tests automatically and report on them back to people. I started hacking my own tools before I came across Jenkins (then Hudson) and was hooked ever since. Over the years I’ve managed to install and configure Jenkins at various jobs, and even was employed making internal and external plugins and integrations. You’ll often find me on the Jenkins IRC and Gitter channels as well as the subreddit giving a hand to people who are stuck. I also try to get involved with Jenkins Infrastructure projects as much as I can. I currently maintain the plugin site, plugin site API, Jenkins Wiki exporter, and a bunch of other minor projects. I also help run Vancouver’s chapter of Nodeschool.

If elected, I would like to address improving commercial support avenues. Right now it’s a lot of people flailing in isolation. I would like to not only improve things so people can find easier ways to get help, but also encourage more users to help others, and push for a centralized source of companies providing commercial support.

Profile links:GitHub,Twitter

Affiliations: Digital Ocean, Nodeschool Vancouver

The nomination is quite an honor for me. I have been a Hudson/Jenkins user since around 2009/2010 when I started working through driving continuous integration in a corporate environment at John Deere. As time went on, I began contributing some small fixes to plugins such as the Job DSL Plugin, OpenID Plugin, and the Workflow Job Plugin. Eventually, I ended up helping maintain Salesforce’s Chatter plugin and then open sourcing plugins such as the Config-Driven Pipeline Plugin with Andrey Falko. More recently, I have also had the extreme pleasure of mentoring in 2 Jenkins projects for Google Summer of Code (Multi-branch Pipeline support for Gitlab in 2019 and Git Plugin Performance Improvements in 2020).

I have learned so much from working with Jenkins and I would love to give back to the project further. Having introduced Jenkins at both small and large companies, I would love to help contribute to the direction of the project through the Roadmap/SIGs/JEPs and encourage others to also contribute / improve Jenkins.

Profile links:GitHub,Twitter,LinkedIn

Affiliations: Salesforce, Spinnaker SIG for Azure

I’m a Jenkins contributor, a member of the Jenkins core team, one of the leaders of the Platform Special Interest Group, and leader of the Documentation Special Interest Group. I’ve served as the Jenkins Documentation Officer since 2019. I was a mentor for Google Season of Code 2020 and am one of the maintainers of the Git plugin for Jenkins.

If elected and allowed to serve on the Jenkins Board, I’ll work to increase community involvement and community development. I’m deeply interested in tooling and environments that support the Jenkins project, including the Jenkins CI environments, issue tracker, artifact repository, and source code repositories.

Profile links:GitHub,Twitter,LinkedIn,Jenkins Blog

Affiliations: CloudBees

I have been involved in the Jenkins project for many years. I started out as a plugin maintainer, SIG member and general helper. I moved to a SIG lead, speakers and Google Summer of Code and Docs org admin and mentor. My current goals are to help continue the work of the public roadmap as well and gain most community members by continuing to be a champion of the community.

For me, being on the Jenkins Board is another opportunity to improve upon the great work we have all done as well as work toward branching out our efforts to have more women, people of color and LGBTQIA members. I would be honored to have this opportunity.

Profile links:GitHub,Twitter,LinkedIn,Jenkins Blog

Affiliations: Equinix Metal, Continuous Delivery Foundation, Kubernetes, Ortelius

I have been a Jenkins user since 2017 and contributor since 2018. I am the primary maintainer of the Jenkins Templating Engine, a plugin that allows users to create truly templated Jenkins pipelines that can be shared across teams. Through that work, I’ve had the great pleasure of helping to organize the Pipeline Authoring Special Interest Group, contributing to the Jenkins Pipeline documentation, and contributing bug fixes to various plugins (including the pipeline plugin and workflow-cps library).

As a Continuous Delivery Foundation Ambassador, I’ve enjoyed doing what I can to advance the community’s approach to CI/CD and simplifying DevSecOps adoption within large organizations. It would be a privilege to serve on the Jenkins Governance Board and offer my support wherever I can.

Profile links:GitHub,LinkedIn

Affiliations: Booz Allen Hamilton, Continuous Delivery Foundation

Three years ago I joined the Jenkins community. I learned a lot during the process of contributing. I even became a Jenkins hero in my city. The most exciting thing I want to do is help more new users of Jenkins get started, and let more contributors feel comfortable. I always love to host a JAM no matter if it’s online or offline.

Plans: improve the experience of using Jenkins in different countries; reorganize the knowledge of Jenkins, for example the tutorial by text or video format; help other SIG leaders to organize meetings.

Profile links:GitHub,Twitter

Affiliations: N/A

I have been using and contributing to Jenkins for so long that it is difficult for me to check when it started exactly. My first pull-request to Jenkins was in 2011 and I had started to use it long before it. Throughout the years, I have contributed to various areas: created our local Jenkins Area Meetup with Michaël Pailloncy, helped users and developers on our mailing lists and IRC channels, contributed to the Jenkins infrastructure, the website, processing plugins hosting requests, worked full time on Jenkins Evergreen, and I am still present today.

For all these reasons, it would be an honor to serve as the Release Officer for the Jenkins Project.

Profile links:GitHub,Twitter,Jenkins Blog

Affiliations: CloudBees

I have been a user of Jenkins for the last 8 years and a regular contributor since 2018. I began with maintaining the Slack plugin and over the last couple of years I have since expanded that to many more plugins and the Jenkins core. These are some of the components I maintain when I have time: Slack, Azure Key Vault, Junit, most of the Database plugins, Dark theme, Plugin installation manager, Jenkins Helm chart, Configuration as code plugin. I am also a member of the Jenkins infrastructure team, and I was involved in the release automation project and the mirrors modernisation effort, along with the day to day support helping people regain access to accounts etc.

As a Release Officer I would like to increase automation, ease onboarding of new contributors to the release team, and ensure that responsibilities rotate among people so that I wouldn’t be a bottleneck for any task.

Profile links:GitHub,Jenkins Blog

Affiliations: Kainos

I have been involved in the Jenkins project since 2011 by different means, as a user, as an administrator, as a contributor (bug reporting, plugin development, documentation, hackfest), being active in the different Jenkins forums such as the Jenkins-dev and Jenkins-user mailing lists, working with the jenkins-infra shared library and so on. I’m also an advocate for the Jenkins project through some presentations anytime that I had the opportunity such as DevOps World 2020 and Jenkins World 2017.

I’ve been happily nominated for the Release officer role which matches not just my area of professional expertise that I’ve been doing for the last 14 years in different roles for different companies but also that’s an area of personal interest where I’d like to spend time with the Jenkins community to understand, document and automate the process in a way we can keep the project sustainable for a long term as it’s today, it’s not just about what I can bring for the community but also about growing together.

If elected as a Release officer I would aim to focus on the following areas: proceed with the existing responsibilities for this role; document and automate the release process; being an enabler for the Continuous Delivery not just for the plugins but also for the core.

Profile links:GitHub,LinkedIn

Affiliations: Elastic

I’ve been a Jenkins user since 2011, contributor since 2013, and core maintainer since 2014. In 2015, I took on the scheduling and authoring of security advisories and have been doing that ever since, working with reporters, maintainers, and the Jenkins security team to deliver security fixes. Beyond that, I regularly contribute to Jenkins and project infrastructure.

Since I’ve started in the Security Officer role, we’ve made significant improvements: Plugins no longer allow ordinary users to run arbitrary scripts (no sandbox!) as a regular feature. I introduced fine-grained permission managementfor our GitHub repositories and the Maven repository hosting our releases.Warnings directly in Jenkins inform admins when an installed component has known security issues (and their UX was improved earlier this year). The Jenkins project  is now a CVE Numbers Authority, to ensure timely and high-quality information in the CVE vulnerability database. Working with Tyler, I added telemetry to Jenkins, which allowed us to deliver multiple large-scale security fixes withminimal impact. More recently, I’ve started writing code scanning rules for common problems in Jenkins and invited maintainers to sign their plugins up, which is something I hope to properly publish and roll out more widely soon.

Profile links:GitHubJenkins Blog

Affiliations: CloudBees

I have been a part of the Jenkins community for some time, and I have received the utmost joy in volunteering. I have been extremely fortunate to have played a lead role in the Outreach & Advocacy SIG, the pipeline-Authoring SIG, and, most recently, the Cloud-Native SIG. I have taken part in many meetups, org admin, and mentor in the GSoC & GSoD. Finally, At DevOps World 2020, I received Jenkins most valuable advocate at DevOps World. I have experience advocating in other communities as well: Kubernetes Release Manager Associate, Kubernetes Mentoring Lead, Ortelius Community Manager.

Jenkins is the most widely used Continuous Integration tool around, and I want to continue to promote that by focusing on the following areas: meetups; conference presentation from the Jenkins community; new user outreach and onboarding; cross-community collaboration (e.g., Kubernetes community); working with the Continuous Delivery Foundation on interoperability; focusing on SIG events.

My roots are open-source, and I am so proud to be a part of the Jenkins community. You can read more about my journey in open-source here. You can also see some of my presentations here andhere.

Profile links:GitHub,Twitter,LinkedIn,Jenkins Blog

Affiliations: OpsMx, Continuous Delivery Foundation, Kubernetes, Ortelius, Spinnaker

I have been actively contributing to the Jenkins project for the past four years with contributions across many areas, and infrastructure is one of my favorite topics. Over my previous mandate as a Jenkins infrastructure officer, I focused on improving contribution experience, and let community members opportunities to take ownership of the different services. I worked on various sponsoring initiatives to make the Jenkins infrastructure more sustainable. We provided a new environment for releasing Jenkins core (and one plugin!), and also many more things.

For the coming year, It is hard to make commitments on what it will look like as we have things we know, like services that need some attention (“ci.jenkins.io/) and the things we don’t know yet. Anyway, It’s important to me to have a transparent project where everybody could read, learn, participate, and understand how the Jenkins project manages infrastructure and I want to continue down that path.

Profile links:GitHub,Twitter,Jenkins Blog

Affiliations: CloudBees

I’m a Jenkins contributor, a member of the Jenkins core team, one of the leaders of the Platform Special Interest Group, and leader of the Documentation Special Interest Group. I’ve served as the Jenkins Documentation Officer since 2019. I was a mentor for Google Season of Code 2020 and am one of the maintainers of the Git plugin for Jenkins.

If elected and allowed to serve as Documentation Officer, I’ll continue efforts to invite more contributors through regular Documentation Office Hours and outreach programs like Google Season of Docs, CommunityBridge, Outreachy, and Jenkins Hackfests. I’ll work to assure an inviting and welcoming environment for contributors.

Profile links:GitHub,Twitter,LinkedIn,Jenkins Blog

Affiliations: CloudBees

This year we had 92 registered voters and around 65 actual votes. It is significantly lower than in the 2019 elections when we had almost 350 voters. It can be partially explained by the change of the communication process. This year we decided to not use the previous voter registration system, and we relied on the user and developer mailing lists instead of sending messages to the entire LDAP user database. This is definitely something we need to review at the retrospective.

The last year was awesome for the Jenkins project governance. With help of many contributors and with the renewed board, we have been able to facilitate many initiatives in the Jenkins project, for example hosting contributor summits, publishing the public roadmap,Code of Conduct update,terminology changes, and graduation in the Continuous Delivery Foundation. There is a lot more work to do to grow the community and to ensure the long term sustainability of the project.

In short term, our key priority is to organize knowledge and permission transfers to the new board members and officers so that they can be effective in their new roles. The board will also focus on maintaining the Jenkins governance processes (meetings, budget approvals, funding, etc.) and defining the next steps and priorities.

There are many longer-term initiatives the board could facilitate: long-anticipated features and architecture changes, changing the Jenkins Enhancement Proposal process, creating better communication channels with Jenkins users, and onboarding of new contributors and maintainers. Such initiatives are instrumental for the evolution of the Jenkins project. The ideas will be discussed in mailing lists and during governance meetings. If you would like to share your vision and ideas about what’s needed in the project, it is definitely a great time to contribute!

In 2020 we had seven students working in the Jenkins mentoring organization. We had 6 projects focused on Jenkins and one project focused on Jenkins X. As usual, in GSoC we focused on problems important to the Jenkins users and community members. The projects delivered highly anticipated new features and key architecture changes needed for the long-term evolution of Jenkins.

This is the first-ever time in Jenkins when all GSoC students have reached the final evaluation and successfully passed it. It was an incredible effort by all the project members and, most importantly, by the students. Thanks a lot to them!

Read more: https://www.jenkins.io/blog/2020/12/22/gsoc-report/

In October we participated in Hacktoberfest. Our featured projects included the Jenkins core, jenkins.io website and plugins.jenkins.io, Helm charts, and multiple plugins. We also encouraged contributors to participate in the Documentation as Code and terminology cleanup across the entire Jenkins ecosystem.

See the details in the Hacktoberfest page.

In total we received 226 pull requests from Hacktoberfest participants. Some stats per Jenkins GitHub organization:

The annual DevOps World, formerly known as DevOps World | Jenkins World held on Sept 22-24, with workshops on Sept 25. Just like other events in 2020, DevOps World pivoted to a virtual event but that didn’t mean there was a shortage of sessions or networking opportunities. There were over 50 Jenkins/open-source. And a special congratulations is in order to this year’s Jenkins Contributor Award winners:

Below are just a few sessions, the full agenda can be found HERE:

This blog post does not provide a full overview of what changed in the project, it is just a slice of the key highlights mentioned by the contributors. The Jenkins project consists of more than 2000 plugins and components which are developed by thousands of contributors. Thanks to them, a lot of changes happen in the project every day. We are cordially grateful to everybody who participates in the project, regardless of contribution size. Everything matters: new features, bug fixes, documentation, blog posts, well reported issues, Stackoverflow responses, etc. THANKS A LOT TO ALL CONTRIBUTORS!

So, keep updating Jenkins and exploring new features. And stay tuned, there is much more to come next year!

Technical changes. 2021 will be another busy year for the Jenkins community. There are many long-overdue changes in the project, which need to happen if we want Jenkins to succeed. There are many areas on the roadmap: UX revamp, cloud native Jenkins, pluggable storage, etc. There will also be a continued cleanup of old dependencies and technical debt. Several key changes are expected to land in the March LTS baseline: update to Spring Security, XStream unforking, JQuery update, etc.(announcement). In addition to that, we will keep working on expanding platform support in Jenkins, including provisioning support for new Java versions and official images for more architectures like Arm.

Documentation. Documentation efforts will continue in the next year, with a focus on documenting Jenkins usage on modern platforms and and automation use-cases. Wide adoption of documentation-as-code will also continue for plugins By this time almost 600 plugins have been migrated, but there are hundreds more plugins to go.

Security. Another important area is Jenkins security. Automation tools like Jenkins are a key part of the software delivery process in organizations, and their security is essential for the security of products. Misconfigured or outdated systems are a common attack vector, but there are also areas for improvement on the project’s side. Be sure there will be security advisories and vulnerability fixes in 2021. We plan to keep adopting best security development and software delivery practices, and to improve dependency management and developer tools in the project. These areas will be in the spotlight for the project next year.

Events. Next month we will participate in FOSDEM, and there will be a virtual Jenkins stand there. There will also be a CI/CD devroom. If you are interested to meet Jenkins contributors, it is a great opportunity. We also plan to continue all outreach programs and on onboarding more contributors. At the moment we are looking for Google Summer of Code 2020 mentors and project ideas (announcement). We are also ready to consider other non-coding project ideas as a part of CommunityBridge. If you are interested, please contact the Advocacy and Outreach SIG.

We are always looking for more contributors, regardless of the profile and experience. Jenkins is a vast ecosystem which includes many modern technologies.

We invite Jenkins users and contributors to participate in the community and to move these initiatives forward! Join us in the mailing lists and special interest groups,

The Docker images provided by the Jenkins project rely on the operating system security processes of the operating system provider.

Our Docker images have used Debian 9 ("Stretch") for multiple years. Debian 9 security updates have been discontinued as of July 6, 2020. Debian 9 Long Term Support security updates will be discontinued at the end of June 2022. The upgrade to Debian 10 keeps us on an operating system maintained by the operating system security team.

The Debian 9 Docker images were based on the openjdk:8-jdk-stretch Docker image. The last update to that image was one year ago with the release of JDK 8u242. We need a maintained Docker base image that keeps pace with JDK releases and operating system updates so that the controller is running the most recent Java updates and most recent operating system updates.

Other Jenkins controller images have already switched from using openjdk base images to instead use base images provided by Eclipse Adoptium.Eclipse Adoptium is the Eclipse project formed when AdoptOpenJDK joined the Eclipse Foundation. This change adapts the jenkins/jenkins:latest and jenkins/jenkins:lts images to use the Adoptium JDK images in the same pattern as is already used for the Jenkins JDK 11 Docker images like jenkins/jenkins:lts-jdk11. The Jenkins Platform SIG has enjoyed very good results in our interactions with the Eclipse Adoptium project. We look forward to continuing our collaboration with them.

Thanks a lot to Alex Earl and Jim Crowley for the image build restructuring groundwork that made the image upgrade possible! Also thanks to Oleg Nenashev and other contributors for their reviews and testing.

The following source control management packages are no longer included in the Jenkins controller images for jenkins/jenkins:latest or for jenkins/jenkins:lts:

Additional packages that are no longer included in the Jenkins controller images include:

A detailed list of the exact package changes is available in the pull request.

The following Docker image definition installs the most recent Jenkins Long Term Support release with the subversion plugin and the operating system subversion command:

Build a new docker image from this Dockerfile and assign the image a meaningful name, e.g. "myjenkins-subversion:1.1":

The following Docker image definition installs the most recent Jenkins Weekly release with the mercurial plugin and the operating system hg command:

Build a new docker image from this Dockerfile and assign the image a meaningful name, e.g. "myjenkins-mercurial:1.1":

The opening session will start Tuesday, February 23, 2021 at 15:00 UTC. After an initial welcome and overview, we’ll hear from leaders in the Jenkins project as they share the results from the previous 12 months and outline ideas for the next 12 months.