Tim Jacomb
Jenkins core maintainer, along with slack, azure-keyvault and configuration-as-code plugins. Tim started using Jenkins in 2013 and became an active contributor in 2018. Tim enjoys working on open source software in his “free” time.
As we welcome 2025, we take a moment to reflect on the past year and celebrate some of our most memorable achievements, impactful projects, and significant changes over the last 366 days. Every contribution, no matter its form, plays a vital role in shaping the Jenkins project. Without the collective efforts of our contributors, supporters, and community members, Jenkins wouldn’t be...
Candidate nominations for the 2024 Jenkins elections are now complete. Thanks to everyone who submitted nominations and to the candidates that have accepted the nominations. Register to vote Voters must register an account on the Jenkins community forums and must have made at least one contribution to Jenkins before September 1, 2024. You can use an existing GitHub account or create a new account...
This is a speaker blogpost for a DevOps World 2024 talk. We last gave a talk about the Jenkins user experience at DevOps World 2022. Two short years later, we’re back to showcase what’s new and upcoming in the world of Jenkins UX. We’ll discuss how we’re bringing the best of BlueOcean back to Jenkins, a redesigned builds widget, a new search...
This is a speaker blogpost for a DevOps World 2022 talk in Orlando, Florida ... at the 'Transformation of the Jenkins User Interface and Where it’s Going Next' talk at DevOps World 2022, Thursday, September 29 10:45 AM - 11:30 AM EDT. We’ll be giving a talk on the history of the Jenkins user interface, where we stand today, and a look...
In common CI/CD use-cases a lot of the space is consumed by test reports. This data is stored within JENKINS_HOME, and the current storage format requires huge overheads when retrieving statistics and, especially, trends. In order to display trends, each report has to be loaded and then processed in-memory. The main purpose of externalising Test Results is to optimize Jenkins performance and storage by querying...
I’m excited to announce that the 'read-only' Jenkins feature is now available for preview. This feature allows restricting configuration UIs and APIs while providing access to essential Jenkins system configuration, diagnostics, and self-monitoring tools through Web UI. Such mode is critical for instances managed as code, e.g. with Jenkins Configuration-as-Code plugin. It is delivered as a part of the JEP-224: Readonly system configuration...
This blogpost was updated to reflect the general availability of the feature after the release of GitHub Branch Source 2.7.1 on April 26th, 2020. I’m excited to announce support for authenticating as a GitHub app in Jenkins. This has been a long awaited feature by many users. It has been released in GitHub Branch Source 2.7.1 which is now available in the Jenkins...
Azure Key Vault is a product for securely managing keys, secrets and certificates. I’m happy to announce two new features in the Azure Key Vault plugin: a credential provider to tightly link Jenkins and Azure Key Vault. huge thanks to Jie Shen for contributing this integration with the configuration-as-code plugin. These changes were released in v1.8 but make sure to run the latest version of...