2026 Jenkins Election Candidate Statements

I’ve been a passionate Jenkins user for almost a decade and have had the privilege of contributing to the project since 2020. Since 2022, I’ve been serving as a board member, and I’m also part of the release team, a core maintainer, as well as a maintainer of various plugins. Additionally, I’m involved in the hosting team, where I review and onboard new plugins into the Jenkins ecosystem.

One of my personal highlights was participating as a mentor in Google Summer of Code 2024, where I successfully onboarded two students to the Jenkins project. I ensured their projects were a success, further strengthening the future of the Jenkins community.

As a board member, I’ve attended various in-person events to represent the Jenkins project and spread the word about our vibrant community. From FOSDEM 2023 and 2024 to KubeCon 2023, CdCon 2023, and a GSoC meetup in Munich and Sunnyvale, I’ve built strong connections with fellow community members and like-minded individuals.

I firmly believe in the future of Jenkins, especially with the ongoing and upcoming UI/UX rework and the efforts to ensure Jenkins stays ahead of modern technology. One of our key focuses is ensuring Jenkins can run seamlessly out of the box on platforms like Java 25.

Throughout my time on the project, I’ve documented various in-house workflows, including the LTS release process, and introduced numerous automations to reduce human input. These efforts help keep Jenkins agile and efficient as we move forward into the future.

Affiliations: Card4Vend

Profile links: Jenkins blog, GitHub, LinkedIn, Contributor spotlight, Jenkins community

I’ve been a Jenkins user since its inception in 2011 and contributor since 2018. As of today I maintain more than 50 plugins.

In 2024 I got even more involved in the Jenkins community, by participating as a mentor for the Google Summer of Code to work on the Jenkins Plugin Modernizer Tool, which is a CLI to update plugins at scale using OpenRewrite.

I’m particularly interested in the "cloud ready" aspect of Jenkins including deployments, packaging (like Jenkinsfile Runner), or distributed storage. A recent contribution on this topic is the Artifactory Artifact Manager plugin that I authored and maintain.

If I’m elected on the Jenkins governance board those will be my subjects of choice.

Affiliations: EveryWare Cloud & IT SA

Profile Links: Jenkins blog, GitHub, LinkedIn, Contributor spotlight, Jenkins community

I have been involved with Jenkins for many years, going back to the Hudson days. I got involved in the great community by making some changes that I needed at my company to one of the plugins. I then became maintainer of that plugin and continued to participate in the IRC channels and discussion forums to help improve Jenkins.

The community of Jenkins is one of the best features, in my opinion. The people are helpful, want to provide a great thing to the world, and are so invested in making Jenkins the best it can be.

As a member of the Jenkins Governance Board, I would love to continue pushing that community and excellence. Getting more people involved in development and helping is something I would like to focus on. A lot of people are intimidated by open source and contributing. I would like to work on that idea and help lower the barriers for others to get involved, learn, and contribute.

Affiliations: Arm Ltd.

Profile pages: Jenkins blog, GitHub, LinkedIn, Contributor spotlight, Jenkins community

I’ve been an active Jenkins contributor since 2021, focusing on overhauling the platform’s UX and improving the experience for both users and developers. I’ve been leading the ongoing redesign of Jenkins, working across Jenkins core and the wider plugin ecosystem. This has included modernising the interface, developing the Jenkins Design Library, improving accessibility, and rethinking pipeline visualisation with Pipeline Graph View. It’s been incredibly rewarding to see years of work come together, and we’re now approaching a major milestone in Jenkins’ evolution.

If elected to the Jenkins Governance Board, I’d love to help take Jenkins into its next chapter.

My priorities would be:

I’d love to help bring more people into the Jenkins community, build excitement around what’s next, and make Jenkins an even stronger, more innovative, and more welcoming platform for years to come.

Affiliations: AutogenAI

Profile pages: Jenkins blog, GitHub, LinkedIn, Contributor spotlight, Jenkins community

I have been a Jenkins user since 2011 where my first deployment of Jenkins was at Drexel University. In 2014, I created a self-service Jenkins model with matrix building using features Jenkins had available (freestyle jobs and matrix jobs) called Jervis (the words Jenkins and Travis CI combined); which is still a project I continue to extend.

When pipelines were released, I migrated my concept of a self-service onboarding experience to multibranch pipelines which allowed a single controller to scale to over 4000 users (people). In 2026, I am continuing to operate large-scale Jenkins infrastructure for Integral Ad Science with a single controller that has almost half a million jobs. Scaling Jenkins and pressuring it in various ways has afforded me unique environments and contribution opportunities. My latest contributions to Jenkins have been officially sponsored by Integral Ad Science, and for that I am grateful.

Since 2011 most of my contributions have been in my spare time, on my own time, and on my own equipment. I hope to see Jenkins be capable of scaling more than just its compute, but also the number of people capable of using it. I think I provide a fairly unique view into what developers want versus what we have today and so I hope to help Jenkins mature further… not just as an admin but also a developer and benefiting the organizations that rely on it as critical infrastructure.

Affiliations: Integral Ad Science

Profile pages: Jenkins blog, GitHub, LinkedIn, Jenkins community, Personal blog

I have been an active contributor to the Jenkins project for nearly 20 years. I maintain several plugins that visualize build quality, including Warnings, Coverage, and Git Forensics. I am also active in the Jenkins UX SIG, where I help move the new Jenkins user interface forward. More recently, I have been bringing my quality tools to other CI platforms. The open-source Quality Monitor GitHub Action and the Autograding Action for GitLab provide unified quality feedback, support more than 150 report formats, and offer an autograding mode for teaching.

In my day job, I am a Professor of Software Engineering at Munich University of Applied Sciences. There I involve students in open-source development through projects and theses. I also mentor new contributors in the Jenkins community and at meetups.

I would be glad to serve on the Governance Board again. I want to help Jenkins evolve with a clear vision that puts the needs of our users first, including a modern and consistent user experience. I also want to keep the community open and welcoming to new contributors, especially the next generation of developers coming from universities.

Affiliations: Munich University of Applied Sciences

Profile pages: Jenkins blog, GitHub, Contributor spotlight, Jenkins community

I would like to continue my work since late 2025 and for much of 2026 as the Docs Officer for Jenkins, this time around to perhaps introduce some overall documentation improvements in 2027, as I have observed that our docs consistency and organization could need some work. I would also like to give our planned jenkins.io retooling a bit of a push so hopefully this will be realized sometime in 2027 along with a planned Chinese site retooling project for the upcoming Google Summer of Code (GSoC) program at Jenkins.

Affiliations: HSBC

Profile Links: Jenkins blog, GitHub, LinkedIn, Contributor spotlight, Jenkins community

I have been a continuous open-source contributor to the Jenkins project since 2019, focusing on maintainability, security, and developer ecosystem health. I maintain key community plugins such as the Thin Backup and Job Configuration History plugins, regularly updating them to current standards and translating those practical insights into improved developer documentation. Over the past term, I have had the privilege of serving as the Jenkins Events Officer, where I actively shaped community presence on the ground and virtually, including moderating the Contributor Summit in Brussels, representing Jenkins at the FOSDEM booth, and initiating the Jenkins Plugin of the Month blog series to highlight impactful maintainer contributions across our ecosystem. In my daily role, I work as a Senior Expert for User-centric DevOps within a central team managing enterprise DevOps platforms and Jenkins infrastructure at a global automotive and industrial company. If re-elected as Events Officer, I look forward to:

Affiliations: Schaeffler

Profile Links: Jenkins blog, GitHub, LinkedIn, Contributor spotlight, Jenkins community, Stackoverflow

I have been a Jenkins user back to when it was called Hudson when I was an engineering student in 2010. I’ve used it since then not only for usual CI/CD but also for other fun (but production!) use cases such as integrating Terabytes of geographical data for the French Geographical Institute (https://www.ign.fr/) 10 years ago.

Currently, I am Staff Software Engineer working as SRE for the Jenkins public infrastructure at CloudBees. I am also active in the Jenkins Platform SIG as a container image co-maintainer. I am a fervent open-source citizen and active in other communities including Docker, Asciidoctor and Updatecli.

I’ve been Jenkins Infrastructure officer since December 2021 and worked in the path setup by Kohsuke, Tyler and Olivier Vernin before me with the goal of keeping the project’s infrastructure sustainable. We were able to increase its funding through many sponsorings, to decrease the billing while keeping a service running for all Jenkins users. I’m proud to have (technically) led a cross-company and cross-timezone team during all these years to keep this infrastructure healthy.

If I’m elected again, I intend to continue working hard on this platform and to continue mentoring the existing team but also newcomers always willing to help.

Affiliations: CloudBees

Profile Links: Jenkins blog, GitHub, LinkedIn, Jenkins community, Personal Page

I have been a user of Jenkins for the last 16 years and a regular contributor since 2018. I began with maintaining the Slack plugin, and over the last couple of years, I have expanded my experience with several more plugins and Jenkins core. These are some of the components I maintain when I have time: Pipeline Graph View, Slack, Azure Key Vault, JUnit, most of the Database plugins, Dark theme, Plugin installation manager, Jenkins Helm chart, and the Configuration as code plugin.

As 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 won’t be a bottleneck for any task.

Affiliations: Kainos

Profile pages: Jenkins blog, GitHub, LinkedIn, Contributor spotlight, Jenkins community

I have been a contributor in the Jenkins project in many different ways in the last 10 years, from contributing to the ATH to core’s Jenkinsfile for running ATH, the PCT, or several contributions to different plugins including several security fixes during my time as a Cloudbees Engineer.

As a manager at Cloudbees, I am in charge of the Cloudbees CI team which includes Daniel Beck and Kevin Guerroudj, well-known members of the Jenkins Security team.

Affiliations: CloudBees

Profile pages: Jenkins blog, GitHub, LinkedIn, Jenkins community