The Jenkins project relies heavily on its infrastructure.
We use websites like www.jenkins.io and plugins.jenkins.io, ticketing systems like issues.jenkins.io , CI/CD infrastructure like ci.jenkins.io , and many other services.
Just to provide some context about the Jenkins infrastructure scale, here are some stats from April 2020:
Over 600 000 people visited www.jenkins.io
Over 250 000 Jenkins servers regularly checked the
Jenkins package server and the
Jenkins update server
API keys and secrets are difficult to handle safely, and probably something you avoid thinking about. In this post I’ll show how the new AWS Secrets Manager Credentials Provider plugin allows you to marshal your secrets into one place, and use them securely from Jenkins.
When CI/CD pipelines moved to the public cloud, credential management did not evolve with them. If you’re in this situation,...
This is a guest post by Aleksei Besogonov, Senior Software Developer at
Amazon Web Services.
Earlier this year, we published a case study on how
Lyft has used Amazon EC2 Spot instances to save 75% on their continuous delivery
infrastructure costs by simply changing four lines of code. Several other EC2 customers like Mozilla have
also reduced costs of their
continuous integration, deployment and testing pipelines by up to 90%...
The Jenkins Contributor Summit brings together current and future contributors to the Jenkins project.
At this event we will talk about the current state of the project and its future evolution.