If you’re a journalist, blogger or anybody else who might consider themselves "press" this page should help you refer to, explain or otherwise cite the Jenkins project correctly. If this page does not sufficiently answer a question you may have, or you’re seeking comment, please reach out to one of our Press Contacts below.
Jenkins is an open source automation server which enables developers around the world to reliably build, test, and deploy their software.
Jenkins, originally founded in 2006 as "Hudson", is one of the leading automation servers available. Using an extensible, plugin-based architecture developers have created hundreds of plugins to adapt Jenkins to a multitude of build, test, and deployment automation workloads. In 2015, Jenkins surpassed 100,000 known installations making it the most widely deployed automation server.
Our Governance Document outlines the project’s philosophy, structure and guidelines. This also includes information on the Governance Board, which is the group with acting executive authority. While board members are available for comment, we encourage you to reach out to our Press Contacts as an initial point of contact for press inquiries.
The Jenkins project is part of Software in the Public Interest, a 501 (c) (3) non-profit organization, which holds the Jenkins trademark and acts as a legal umbrella organization.
We ask that the following branding guidelines be used when referring to or writing about the Jenkins project:
the Jenkins project
On our Logo page we have documented some versions of our logo, including the color palette our branding uses. Our logos can be downloaded in a number of sizes, or as vector graphics, from here. Please do not use any of our "fun logo" variations like Ninja or Superhero Jenkins in publications.
When embedding our logo in an article, we prefer the
logo.png (see Figure 1)
to be used over the
If you have any questions about artwork, please ask one of the Press Contacts.
Blue Ocean is a new user experience for Jenkins based on a personalizable, modern design that allows users to graphically create, visualize and diagnose Continuous Delivery (CD) Pipelines
Developers of any skill level can create Continuous Delivery pipelines from start to finish using the intuitive and visual pipeline editor.
Enables developers to visually represent pipelines in a way even their boss’s boss can understand, improving clarity into the CD process for the whole organization
Developers locate automation problems instantly without endlessly scanning through logs or navigating through many screens.
Developers can make Jenkins their own by customizing their dashboard so that they only see the Pipelines that matter to them.
Pipelines are run for all feature branches and pull requests, with their status reported back to Github, so the whole team knows if your changes need work or are good to go.
Also available for download in full high definition.
The following individuals can be reached out to for comment, clarification or questions about the Jenkins project. Please bear in mind that many are volunteers so availability and time may be limited.