As an independent open source project, the Jenkins project maintains most of its own infrastructure including services which help to keep the project running. The kind of things that fall into "infrastructure" can span from operating virtual machines, containers, configuring network or developing and maintaining project-specific applications to make the development of Jenkins core and plugins more efficient.
Because we strongly believe in Open Source principles, we also apply them to our infrastructure. As such we consider ourself as an open infrastructure project where everybody is invited to learn, share, contribute.
Want to contribute? Like for Jenkins, there is also a community behind its Infrastructure, and we invite you to join us and participate. Connect to the Community on social media and in chats, mailing lists and meetings participate and contribute.
See also Jenkins Project Governance and Values and Code of Conduct.
About this GitHub org This is the main GitHub organization of the Jenkins Infrastructure, with its help desk dedicated to infrastructure issues and status website
You can learn more about this subproject on the website. You're encouraged to submit pull requests, propose features and discuss issues!
The GitHub organization of the main Jenkins community including repositories of the Jenkins core, plugins, libraries and developer tools is here: https://github.com/jenkinsci/
The annual Jenkins awards is happening now! It recognizes contributions from individuals in the community and the progress made in the name of Jenkins.
Nomination categories are:
- Most Valuable Jenkins Contributor → Nominate Someone
- Most Valuable Jenkins Advocate → Nominate Someone
- Jenkins Security MVP → Nominate Someone
Awards timeline:
- Nominations close: April 14, 2025
- Voting opens: April 22
- Voting closes: June 5
- Winners announced at cdCon 2025 on June 23 - 25, 2025
See the announcement blogpost for more details for voting and nominate candidates.
