Recent Blog Posts

The Jenkins community has recently completed the 2021 elections. On behalf of the Jenkins community and the elections committee, we congratulate all newly elected board members and officers! We also thank all candidates and voters who participated this year. Election results: Mark Waite joins the re-elected Oleg Nenashev and Kohsuke Kawaguchi, Gavin Mogan and Ewelina Wilkosz on the Jenkins Governance Board Tim Jacomb will continue in the role of Release Officer (uncontested) Alyssa Tong will become the new Events Officer (uncontested) Damien Duportal was elected as the Infrastructure Officer (uncontested) Wadeck Follonier was elected as the Security Officer (uncontested) Mark Waite was re-elected in the role of Documentation Officer for another term The board positions and officer roles are an essential part of Jenkins' community governance and well-being, and we are excited to see contributors taking these roles. The board continues to require that no single company may have a majority on the Jenkins governance board. Oleg Nenashev is employed by Dynatrace, while Mark is employed by CloudBees. Governance Board election details This year we had three candidates participating in Jenkins Governance Board elections: Mark Waite, Oleg Nenashev (returning), and Ullrich Hafner (returning) All of them are awesome community leaders who actively contribute to the Jenkins project and represent its users. It would be an honor to have them on the Jenkins board. Regardless of the election results, we appreciate their participation and the time they invested in these elections. This year we were electing 2 governance board members. We were using the Condorcet Internet Voting Service that allows voters to rank their choices rather than just picking their one favorite choice. You can find full voting results here : Mark Waite (Condorcet winner: wins contests with all other choices) Oleg Nenashev loses to Mark Waite by 37–22 Ullrich Hafner loses to Mark Waite by 42–14, loses to Oleg Nenashev by 37–15 Congratulations to the returning Oleg, and the newly elected Mark, and thanks to Ullrich for his past contributions. All new board members are elected for a 2-year term unless they decide to step down earlier. The estimated end of the term for them is December 02, 2023. Officer election details All 5 officer positions were up for election this year. These roles have a 1-year term, with the estimated end of term on Dec 02, 2022. After the initial review of nominations and confirmations with potential candidates, 4 officer positions were uncontested: Tim Jacomb - Release Officer Alyssa Tong - Events Officer Damien Duportal - Infrastructure Officer Wadeck Follonier - Security Officer Documentation Officer election results Mark Waite won the biggest support as a Documentation officer ( voting results). Mark will continue as Documentation Officer. Mark Waite (Condorcet winner: wins contests with all other choices) Saeid Bostandoust loses to Mark Waite by 46–9 Thanks to all Jenkins officers for their continued leadership! Officers take responsibility for many day-to-day processes in the Jenkins community and lead the contributor teams working on them. It requires significant time commitment, and it is not taken for granted. Statistics This year we had 81 registered voters and around 59 actual votes. Feedback The Jenkins project plans to conduct elections every year. We appreciate and welcome feedback regarding the election process so that we can improve the process. We have started a Retrospective document for these elections. Everyone can suggest changes in this document, and we will integrate them. If you have any private feedback you would like to share, please send an email to the Jenkins Board. If you would like to raise any issues about the election process, please contact one of the elected Governance Board members.

Voter registration is now open for the 2021 Jenkins project elections. Two members of the governing board are up for election. Five officers are up for election. How Do I Register to Vote? Click the "Register Here" button above or open https://community.jenkins.io/g/election-voter in your browser. You will need to register with community.jenkins.io either using an existing account (like a GitHub account) or by creating a new account dedicated to community.jenkins.io and then "Join" the "election-voter" group. Am I Eligible to Vote? You’re eligible to vote if you have made at least one contribution to Jenkins before September 1, 2021. Contributions to Jenkins are recognized in many different forms, including: Connect with other users through mailing lists or chat channels Meet with other users in conferences or online meetups Code improvements for Jenkins core, Jenkins plugins, or Jenkins infrastructure Help other users through chat channels or mailing lists Translate Jenkins software or other materials Test Jenkins software interactively or with automation Document Jenkins core, Jenkins plugins, or Jenkins infrastructure Design Jenkins user interface, Jenkins artwork, or other Jenkins Review changes to code or documentation that are submitted by others Donate funds to help the project If you’ve helped someone use Jenkins or a Jenkins derived product, you’re eligible to vote. If you’ve tested Jenkins interactively or with automation, you’re eligible to vote. If you’ve assisted at a Jenkins meetup or other Jenkins event, you’re eligible to vote. Nominations Nominations for candidates are being accepted by the Jenkins election committee. Nominations will close at the end of the day, October 31, 2021. Nominees will be notified and will be asked to confirm that they are willing to serve if elected. The list of candidates for each position will be announced November 7, 2021. Who Nominates a Candidate? Anyone may propose a nomination. Nominations are being accepted for the following positions: Jenkins Governance Board Members Documentation Officer Events Officer Infrastructure Officer Release Officer Security Officer

Dear all, Time flies and the Jenkins elections period is here. This year, two board seats and all officer positions are up for election. Thanks, Oleg Nenashev and Ullrich Hafner who led the Jenkins project as board members for the last two years. Thanks, Tim Jacomb, Daniel Beck, Mark Waite for your dedication as officers over the past year. We already had two successful editions in a row. I want us to continue on that path. This is a tremendous opportunity for community members to influence the direction of the project for the next two years. To make this year’s election even better, we slightly modified the process by leveraging our new community platform aka community.jenkins.io. To participate in the election, we ask every Jenkins community member to have an account on community.jenkins.io. You can either reuse your Github account or create a new discourse account specific to community.jenkins.io. The second requirement is to be able to showcase at least one contribution done before the first of September 2021. As mentioned on jenkins.io.io/participate, they are many different ways to contribute to Jenkins and for many of them, it’s very difficult to measure. Therefore we’ll trust participants and will not require that they provide evidence of contribution as part of their voter registration. We reserve the right to ban the specific account from the election process if we identify abuse. The election works in three stages: Identify voters and nominees Voting period Announce results Voters To invite participants to vote, we need a list of email’s addresses that we would share with the Condorcet Internet Voting Service. Therefore we ask every community member who matches the requirements to join the group election-voter on community.jenkins.io. The group will be open for joining during the registration period after we’ll close registration during the voting period. We’ll use emails from the “election-voter” group members. Nominees During the same period, we invite every community member to nominate candidates by sending a message to the group election-committee mentioning the position and the motivation. On the 31 of October, the nomination period will end. We’ll notify all the nominees and get confirmation that they are interested in running as a candidate. The list of candidates will be announced on the 7th of November. Everybody can nominate candidates. This year we are looking for nominees for the following positions: Board members Documentation Officer Events Officer Infrastructure Officer Release Officer Security Officer More information about the different roles can be found on jenkins.io/project/team-leads. Election On the 7th of November, once voters and candidates are identified, we’ll invite everybody by email to vote using civs.cs.cornell.edu. At this stage of the election, nobody will be allowed to register. Voting deadline is the 30th of November. Result As soon as we have the election results, we’ll publish them. Elected members will begin their official roles on the 3rd of December 2021. Key Dates Sep 20: Nomination and voter registration begin Oct 31: Nomination deadline Nov 07: Candidates announced, Registration deadline, voting start Nov 30: Voting deadline Dec 03: Results announced Key Information: Everybody can suggest candidates by sending a private message to the group election-committee. Voters register for the election by joining the public group election-voter. Email participants will be shared with Condorcet Voting System to send voting invitations. Nobody can register for the election once we send invitations to Condorcet Voting System. Once the election is over, every member of the group"election-voter" will get a badge on https://community.jenkins.io as a “2021 Election Participant”. Once the election is over, every nominee will get the badge “2021 Election Nominee”. Cheers,

We would like to announce changes in the Jenkins Governance Board. As it was announced earlier this month, Marky Jackson has decided to step down from his elected roles. On behalf of the Jenkins community, we would like to thank Marky for all contributions and for the continued participation in the Jenkins community. As an active Jenkins contributor and community leader, Marky helped a lot of initiatives to happen: Jenkins and Kubernetes ecosystem, terminology changes, GSoC and GSoD, pipeline authoring SIG and many more activities. Thank you Marky! The governance board has followed the interim procedure to nominate the new governance board member until the end of the term. The board decided to respect the results of the 2020 elections and to nominate Ewelina Wilkosz who received the most of the votes after the elected candidates. She has accepted the nomination, and on March 10th the Governance Meeting has confirmed it. We are happy to welcome Ewelina Wilkosz as a new Governance Board Member! Ewelina will join other governance Board Members: Kohsuke Kawaguchi, Ullrich Hafner, Oleg Nenashev, and Gavin Mogan. The term will last until December 2022. About Ewelina Wilkosz Ewelina has been a Jenkins Contributor since 2017, when she got involved in Jenkins Configuration as Code Plugin development. Voted Most Valuable Jenkins Contributor in 2018. She has 14 years of experience in IT, working as a CI/CD consultant since the beginning of 2017. In that role she’s trying to solve numerous issues Jenkins users are facing daily - as developers, administrators, maintainers. Here is Ewelina’s statement from the elections: 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. What’s next for the Jenkins Governance Board? In February we had the Jenkins Contributor Summit. There we discussed many topics related to the Jenkins evolution and its roadmap. We identified several initiatives we would like to focus on, including but not limited to improving user experience, contributor onboarding, and securing Jenkins delivery pipelines. These initiatives will be a key focus until the next contributor summit we plan to organize in June. The board will also focus on maintaining the Jenkins governance processes (meetings, budget approvals, funding, etc.) and facilitating contributions to the project. Participating in Jenkins Governance Jenkins Governance Board has just a representative function in the community. The project and the community have a long history of open and inclusive governance driven by many contributors. We invite all community members to participate in the project by joining the governance meeting, participating in the mailing list conversations, and joining special interest groups driving particular topics. See this page to know more about contributing to Jenkins in general.

The Jenkins community congratulates all users and contributors with the New Year! Let’s take a look at some changes this year. We would like to thank all awesome Jenkins users and contributors who have been with us during this year. Highlights Some of the key highlights: Hundreds of first-timer contributors joined the community Major UI/UX improvements in the Jenkins core, including the landing page, plugin manager, dark theme, and read-only configurations support Outreach programs like Google Summer of Code (7 projects), Google Season of Docs, UI/UX hackfest, etc. Public roadmap for the project Terminology changes in the project, new Code of Conduct Technical debt cleanup: XStream unforking, Acegi Security replacement, etc. Continued evolution of the plugin ecosystem, especially in the area of Cloud Native solutions and tool integrations Continued documentation cleanup, great progress with plugin documentation migration Graduation in the Continuous Delivery Foundation Jenkins User Interface and User Experience This year there were many activities around Jenkins user experience and long-anticipated user interface changes. This is a coordinated effort being led by the User Experience SIG, and by many contributors to the project. Key project highlights: Look & Feel updates of the Jenkins Web UI, including styling rework, new typography and layouts Major rework of plugin management UI/UX Dark theme for Jenkins Accessibility improvements Support for read-only configuration pages In May we also organized a Jenkins UI/UX hackfest where we worked on some key stories improving user experience. Jenkins security In 2020 the Jenkins security team has released 19 advisories for the Jenkins core, plugins and other components. In total 198 vulnerabilities were fixed, and 72 plugin vulnerabilities were announced without a fix at the time of advisory publishing. As a project, we are receiving a continuous flow of new reports and continue to provide corrections. Cross-site scripting (XSS) vulnerabilities were the most popular type this year, followed by unprotected credentials. There have also been developer tooling improvements, including GitHub CodeQL evaluation for targeted security issues search and Find-Sec-Bugs adoption for static analysis of the plugin and Jenkins core code. Along with wider adoption of Dependabot and automated dependency scanning on GitHub. Documentation Jenkins Documentation SIG is working on creating more documentation for Jenkins on different platforms, including cloud platforms. Jenkins on Kubernetes was one of the key stories this year for the SIG, along with documentation migration to jenkins.io and wider adoption of Documentation-as-code in plugins. 95% of the 200 most installed Jenkins plugins have moved to "documentation as code" or have a pending pull request with updates. In total, almost 600 plugins have already been migrated. There were major updates in Jenkins documentation on jenkins.io, with a lot of content being moved from the old Jenkins Wiki. 2020 was the first year when Jenkins participated in Google Season of Docs (GSoD). This program brings together open-source and technical writers communities for the benefit of both. This year’s student, Zainab Abubakar, did an amazing job documenting Jenkins on Kubernetes. Now Jenkins users can find official documentation about deploying and scaling Jenkins in Kubernetes. See the project report by Zainab here. Jenkins Release Automation The Jenkins project has delivered weekly and long term support releases since it was formed in 2011. Those releases were delivered by Kohsuke Kawaguchi from his release infrastructure. Beginning in April 2020, those releases are delivered by the new release automation setup. It is hosted within the Jenkins’ Kubernetes cluster, with fully automated management and continuous delivery of services within the setup. We transitioned to new build processes, new code signing certificates, and new release automation jobs. Thanks to Olivier Vernin and all Infrastructure sub-project contributors for the successful completion of the release automation project! Moreover, there is ongoing work on continuous delivery of Jenkins plugins ( JEP-229) and on re-designing other Jenkins instances within the project (infra-ci, trusted-ci, and ci.jenkins.io for plugins). In the next few months these stories should provide Jenkins contributors with a modern environment for CI and CD of all Jenkins components. Terminology updates Since July, we have officially replaced the old "master" terminology with the "controller" term. It is a follow-up to the "agent" terminology introduced in 2016. We have also deprecated usages of the “blacklist/whitelist” terminology in all components. Currently the community is working on the cleanup of the remaining occurrences in the codebase and documentation, and we invite everyone to contribute. As a part of the terminology cleanup, last spring we announced the renaming of the official Docker images for Jenkins agents. As a reminder, it does not have any immediate impact on Jenkins users, but they are expected to gradually upgrade their instances. See more information about terminology updates here and here. “Jenkins is the Way” program This year the Advocacy and Outreach SIG started the “Jenkins is the Way” initiative which focuses on promoting user success stories. Over the year, the team published 54 user stories and six case studies on https://jenkinsistheway.io/ as well as a significant amount of community marketing. We also published a number of testimonial videos advertising user stories, including this Introduction to "Jenkins is the Way" video. See all the stories HERE Events Google Summer of Code 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/ Jenkins in Hacktoberfest 2020 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: 'jenkinsci', PRs: 189, Hacktoberfest contributors: 61 'jenkins-infra', PRs: 100, Hacktoberfest contributors: 40 'jenkins-zh', PRs: 37, Hacktoberfest contributors: 2 Jenkins at DevOps World 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: James Holderness - Jenkins security MVP Marky Jackson - Most valuable Jenkins advocate Tim Jacomb - Most valuable Jenkins contributor Below are just a few sessions, the full agenda can be found HERE : Jenkins Where It Is and Where It Is Going One Jenkins to Rule them All Jenkins UI Gets a Makeover Jenkins Pipeline and DevSecOps for API Security Graduation at Continuous Delivery Foundation Jenkins is the first project to graduate in the CD Foundation. In August the project announced that the Jenkins project has achieved the graduated status in the Continuous Delivery Foundation (CDF). Thanks to all contributors who made our graduation possible! Below you can find a few key changes we have applied during the graduation process: We introduced a new public roadmap for the Jenkins project. This roadmap aggregates key initiatives in all community areas: features, infrastructure, documentation, community, etc. It makes the project more transparent to all Jenkins users and adopters, and at the same time helps potential contributors find the hot areas and opportunities for contribution. The roadmap is driven by the Jenkins community and it has a fully public process documented in JEP-14. A new list of Jenkins adopters was introduced on jenkins.io. This list highlights Jenkins users and references their case studies and success stories, including ones submitted through the Jenkins Is The Way portal. Please do not hesitate to add your company there! We passed the Core Infrastructure Initiative (CII) certification. This certification helps us to verify compliance with open source best practices and to make adjustments in the project (see the bullets below). It also provides Jenkins users and adopters with a public summary about compliance with each best practice. Details are on the Jenkins core page. Jenkins Code of Conduct was updated to the new version of Contributor Covenant. In particular, it sets best practices of behavior in the community, and expands definitions of unacceptable behavior. More information can be found HERE, and HERE. Public Roadmap The Jenkins project now has a public, community-driven project roadmap. Roadmap items are major initiatives and are considered as official plans. The roadmap aggregates key initiatives in all areas of the project. Many of the 2020 released roadmap items are mentioned elsewhere in this document, including release automation, Core Infrastructure Initiative (CII) certification, user interface improvements, read-only configuration pages, and Google Summer of Code projects like the GitHub Checks API or External Fingerprint Storage. Other roadmap items include mirror infrastructure improvements, a new Windows installer, and preview releases of pluggable storage for external fingerprints, build logs, and unit test results. Jenkins 2020 Elections In October-December the Jenkins community held the regular elections. This year we were electing for 2 governance board members and for all five officer positions, namely: Security, Events, Release, Infrastructure, and Documentation. These roles are an essential part of Jenkins' community governance and well-being. We thank all candidates and voters who participated this year. Key results: Gavin Mogan and Marky Jackson joined the Jenkins Governance Board Tim Jacomb was elected as Release Officer Marky Jackson became the new Events Officer Olivier Vernin, Daniel Beck, and Mark Waite will continue as Infrastructure, Security and Documentation officers Full election results: https://www.jenkins.io/blog/2020/12/03/election-results/ And even more 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! What’s next? 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. Join us in 2021! 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 Jenkins community has recently completed the 2020 elections. On behalf of the Jenkins community and the elections committee, we congratulate all newly elected board members and officers! We also thank all candidates and voters who participated this year. Election results: Gavin Mogan and Marky Jackson will join Kohsuke Kawaguchi, Ullrich Hafner and Oleg Nenashev on the Jenkins Governance Board Tim Jacomb was elected as Release Officer Marky Jackson will become the new Events Officer (uncontested) Olivier Vernin will continue in the role of Infrastructure Officer for another term (uncontested) Daniel Beck will continue in the role of Security Officer for another term (uncontested) Mark Waite will continue in the role of Documentation Officer for another term (uncontested) The board positions and officer roles are an essential part of Jenkins' community governance and well-being, and we are excited to see contributors taking these roles. If you are interested to learn more, please see the blog post below. Governance Board election details This year we had nine candidates participating in Jenkins Governance Board elections: Andrey Falko, Ewelina Wilkosz, Frederic Gurr, Gavin Mogan, Justin Harringa, Mark Waite, Marky Jackson, Steven Terrana, and Zhao Xiaojie (Rick). All of them are awesome community leaders who actively contribute to the Jenkins project and represent its users. It would be an honor to have them on the Jenkins board. Regardless of the election results, we appreciate their participation and the time they invested in these elections. This year we were electing 2 governance board members. We were using the Condorcet Internet Voting Service that allows voters to rank their choices rather than just picking their one favorite choice. You can find full voting results here : Mark Waite (Condorcet winner: wins contests with all other choices) Marky Jackson loses to Mark Waite by 48–12 Gavin Mogan loses to Mark Waite by 51–10, loses to Marky Jackson by 31–20 Ewelina Wilkosz loses to Mark Waite by 48–14, loses to Gavin Mogan by 29–28 Justin Harringa loses to Mark Waite by 51–11, loses to Ewelina Wilkosz by 35–16 Steven Terrana loses to Mark Waite by 47–16, loses to Justin Harringa by 20–19 Zhao Xiaojie (Rick) loses to Mark Waite by 57–5, loses to Steven Terrana by 25–24 Frederic Gurr loses to Mark Waite by 52–10, loses to Zhao Xiaojie (Rick) by 25–24 Andrey Falko loses to Mark Waite by 56–6, loses to Frederic Gurr by 26–13 Although Mark Waite came first in the voting results, being on the board would violate the Corporate Involvement clause which states that "the number of board members affiliated with one company must be less than 50%". Mark will continue to be Documentation officer. Regardless of his official role, Mark has been leading many initiatives and helping a lot with various aspects of the community governance. Congratulations to Marky and Gavin, and thanks to all candidates! All new board members are elected for a 2-year term unless they decide to step down earlier. The estimated end of the term for them is December 02, 2022. We would also like to thank Alex Earl and R. Tyler Croy who step down from the Jenkins Governance Board this year. Thanks to them for all contributions and for continued community leadership. Statement from Marky Jackson: It is a tremendous honor to be elected to this roles. I am so humbled. Being part of this community is a fantastic opportunity that I have had. It has given me so many joys. Whether helping to foster community collaboration, working on the roadmap, leading various SIG’s or helping meetups or conferences, this community has given me so much. My goals are bridging the Jenkins project with other interoperability projects, defining the roadmap, achieving roadmap goals, continuing to help meetups thrive, and our conferences focus on the community. I want to ensure we are transparent in our goals and how we achieved them. I want to continue to build up a welcoming community that holds diversity and inclusion at the forefront. I look forward to working with the other members of the Governance Board to continue to deliver on the incredible things this project is known for. — Marky Jackson, Jenkins Governance Board Member and Events Officer Statement from Gavin Mogan: Gavin here. I’m still in shock that I got voted in for the Jenkins board. It felt like yesterday I just got started helping people randomly on IRC. This is truly exciting. I plan to continue to help out as much as I can wherever I can, just in a bit more official capacity. This is truly exciting. I have no firm plans or agenda, just keep pushing advocacy and getting people to help each other in a positive and safe way. My specialities lie in outside of Jenkins core, whether it be working on the plugin site, or hanging out on IRC, Gitter and Reddit helping out where I can. — Gavin Mogan, Jenkins Governance Board Member Officer election details All 5 officer positions were up for election this year. These roles have a 1-year term, with the estimated end of term on Dec 02, 2021. After the initial review of nominations and confirmations with potential candidates, 4 officer positions were uncontested: Olivier Vernin - Infrastructure officer. Marky Jackson - Events officer. Marky inherits this role from Alyssa Tong who decided to step down from the officer role and to focus on the Jenkins community marketing, including Jenkins Is The Way and many other initiatives started by Alyssa. Mark Waite - Documentation officer. Daniel Beck - Security officer. Thanks to all Jenkins officers for their continued leadership! Officers take responsibility for many day-to-day processes in the Jenkins community and lead the contributor teams working on them. It requires significant time commitment, and it is not taken for granted. Release Officer election results Tim Jacomb won the biggest support as a Release officer ( voting results). Tim will replace in this role Oliver Gondža who has been leading the Release Team and the release processes since 2016 when the role was officially introduced. Tim Jacomb (Condorcet winner: wins contests with all other choices) Baptiste Mathus loses to Tim Jacomb by 40–23 Victor Martinez loses to Tim Jacomb by 38–25, loses to Baptiste Mathus by 32–31 Here is a statement from Tim Jacomb: I’m excited for the year ahead, let’s see where we can take the Jenkins release area in the future. 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. — Tim Jacomb, Jenkins Release Officer Thanks to Alyssa Tong and Oliver Gondža for their long-time service as Jenkins officers! We are looking to continue working with them in the Jenkins community. And congratulations to Tim Jacomb and Marky Jackson for joining the team! Statistics 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. What’s next for the board? 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! Feedback Jenkins project plans to conduct elections every year. We will appreciate and welcome any feedback regarding the election process so that we can improve the process. We have started a Retrospective document for these elections. Everyone can suggest changes in this document, and we will integrate them. There will be also a public retrospective review at the next Advocacy and Outreach SIG meeting on Dec 17. If you have any private feedback you would like to share, please send an email to the Jenkins Board. If you would like to raise any issues about the election process, please contact one of the elected Governance Board members. References Jenkins Governance Board Jenkins Board Election Process Jenkins Officers 2020 election announcement 2020 election candidates Retrospective document

Jenkins 2020 Elections are over, thanks to all participants! Please see the results announcement. As you probably know, in a few weeks we will have the Jenkins 2020 elections. We will be electing two governance board members and five officers, namely: Security, Events, Release, Infrastructure, and Documentation. After the announcement on Sep 24, we have been accepting nominations from community members. After the processing and confirmations with potential candidates, the Jenkins 2020 Elections committee is happy to announce the candidates for the Jenkins Governance Board and Officer roles: Governance Board candidates: Andrey Falko, Ewelina Wilkosz, Frederic Gurr, Gavin Mogan, Justin Harringa, Mark Waite, Marky Jackson, Steven Terrana, Zhao Xiaojie (Rick) Release officer: Baptiste Mathus, Tim Jacomb, Victor Martinez Security officer: Daniel Beck (uncontested) Events officer: Marky Jackson (uncontested) Infrastructure Officer: Olivier Vernin (uncontested) Documentation officer: Mark Waite (uncontested) We encourage all community members to support the candidates and to participate in the elections! Key dates Nov 10 - Voting begins. Condorcet Internet Voting Service will be used for voting. Nov 24 - Voting sign-up is over. Nov 27 - Voting ends, 11PM UTC. Dec 03 - Election results are announced and take effect. Signing up for voting Any Jenkins individual contributor is eligible to vote in the election if there was a contribution made before September 01, 2020. Contribution does not mean a code contribution, all contributions count: documentation patches, code reviews, substantial issue reports, issues and mailing list responses, social media posts, testing, etc. Such a contribution should be public. You can register to vote in one of two ways: Fill out this Google Form. This way requires logging into your Google Account to verify authenticity. Send an email to jenkins-2020-elections@googlegroups.com. You will need to provide the information specified here. Once sign-up is over, the election committee will process the form submissions and prepare a list of the registered voters. In the case of rejection, one of the election committee members will send a rejection email. Every individual contributor is expected to vote only once. Candidates Below you can find statements, affiliations and profile links provided by the candidates. Minimum copy-editing was applied to the content by the Jenkins 2020 Elections Committee. Candidates are sorted by the first name. Governance Board Andrey Falko I have been a Jenkins user and administrator on and off since around 2010. In 2016, I got into evangelism by organizing a Jenkins 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 Ewelina Wilkosz 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) Frederic Gurr 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 called extra-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 Gavin Mogan 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 Justin Harringa 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 Mark Waite 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 Marky Jackson 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 Steven Terrana 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 Zhao Xiaojie (Rick) 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 Release Officer Baptiste Mathus 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 Tim Jacomb 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 Victor Martinez 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 Security Officer - uncontested Daniel Beck 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 management for 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 with minimal 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: GitHub Jenkins Blog Affiliations: CloudBees Events Officer - uncontested Marky Jackson 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 and here. Profile links: GitHub, Twitter, LinkedIn, Jenkins Blog Affiliations: OpsMx, Continuous Delivery Foundation, Kubernetes, Ortelius, Spinnaker Infrastructure Officer - uncontested Olivier Vernin 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 Documentation Officer - uncontested Mark Waite 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 More information Jenkins 2020 elections announcement Jenkins Governance Board and Jenkins Officers Jenkins Board and Officer Election Process 2019 election results Elections coordination in the mailing list

Jenkins 2020 Elections are over, thanks to all participants! Please see the results announcement. We are happy to announce the 2020 elections in the Jenkins project! Nominations are open for two governance board and for all five officer positions, namely: Security, Events, Release, Infrastructure, and Documentation. The board positions and officer roles are an essential part of Jenkins' community governance and well-being. We invite Jenkins contributors and community members to sign-up for elections and to nominate contributors for the elected roles. Deadline for nominations is Oct 15, voter registration ends on Nov 02. These are the second elections held by the Jenkins project. During the 2019 elections, we elected 3 board members and 5 officers. You can find the voting results here. This year, we decided to make a few changes in the election process based on the 2019 elections feedback. Key dates Sep 24 - Nominations open, voting sign-up begins. Oct 15 - Board and officer nominations deadline. Oct 26 (or later) - List of candidates is published, including personal statements. Nov 10 - Voting begins. Condorcet Internet Voting Service will be used for voting. Nov 24 - Voting sign-up is over. Nov 27 - Voting ends, 11PM UTC. Dec 03 - Election results are announced and take effect. Signing up for voting Any Jenkins individual contributor is eligible to vote in the election if there was a contribution made before September 01, 2020. Contribution does not mean a code contribution, all contributions count: documentation patches, code reviews, substantial issue reports, issues and mailing list responses, social media posts, testing, etc. Such a contribution should be public. You can register to vote in one of two ways: Fill out this Google Form. This way requires logging into your Google Account to verify authenticity. Send an email to jenkins-2020-elections@googlegroups.com. You will need to provide the information specified here. During the registration period, the election committee will process the form submissions and prepare a list of the registered voters. In the case of rejection, one of the election committee members will send a rejection email. Every individual contributor is expected to vote only once. Deadline for the voter registration is November 24. Nominating contributors Suggestions from the community members are highly valued, and the board welcomes additional nominations. If you feel that a particular person is well suited to help guide Jenkins, please submit a name and the reason for your nomination to jenkinsci-board@googlegroups.com. Self nominations are also welcome. Deadline for nominations is October 15. Terms The terms of office for these elected positions are: Officer positions (1 year): December 03, 2020 to December 2, 2021 Governing board member (2 years): December 03, 2020 to December 2, 2022 Elections committee The 2020 elections are coordinated by the Jenkins Governance Board members who are not up for re-election this year: Alex Earl, Ullrich Hafner, and Oleg Nenashev. These contributors are responsible for managing the process, preparing the nominee list for elections, forming and verifying the voter list, processing the votes, and announcing the results. You can contact the election committee via jenkins-2020-elections@googlegroups.com. Please use this email for any queries and feedback regarding the elections. References Jenkins Governance Board and Jenkins Officers Jenkins Board and Officer Election Process 2019 election results Elections coordination in the mailing list