This is a guest post by R. Tyler Croy, who is a long-time contributor to Jenkins and the primary contact for Jenkins project infrastructure. He is also a Jenkins Evangelist at CloudBees, Inc. For ages I have used the "Build After" feature in Jenkins to cobble together what one might refer to as a "pipeline" of sorts. The Jenkins project itself, a major consumer of Jenkins, has used these daisy-chained...

I am pleased to announce that we have partnered with Microsoft to migrate and power the Jenkins project’s infrastructure with Microsoft Azure. The partnership comes at an important time, after the recent launch of Jenkins 2.0, Jenkins users are more readily adopting Pipeline as Code and many other plugins at an increasing rate, elevating the importance of Jenkins infrastructure to the overall success of the project. That strong and continued growth...

A few weeks ago, my colleague Brian Dawson and I were invited to present on Scaling Jenkins for Continuous Delivery with Microsoft Azure in Microsoft’s Reactor space. Azure is Microsoft’s public cloud offering and one of the many tools available to Jenkins users for adding elastic compute capacity, among other things, to their build/test/deploy infrastructure. While our presentations are applicable to practically any cloud-based Jenkins environment, Thiago Almeida and Oguz Pastirmaci from Microsoft...

Last week we hosted our first ever Online JAM with the debut topic of: Jenkins 2.0. Alyssa, our Events officer, and I pulled together a series of sessions focusing on some of the most notable aspects of Jenkins 2 with: A Jenkins 2.0 keynote from project founder Kohsuke Kawaguchi An overview of "Pipeline as Code" from Patrick Wolf A deep-dive into Pipeline and related plugins like Multibranch, etc from Jesse Glick and Kishore Bhatia An overview of...

Last week, the infrastructure team identified the potential compromise of a key infrastructure machine. This compromise could have taken advantage of, what could be categorized as, an attempt to target contributors with elevated access. Unfortunately, when facing the uncertainty of a potential compromise, the safest option is to treat it as if it were an actual incident, and react accordingly. The machine in question had access to binaries published...

This is a cross-post of an article authored by Viktor Farcic on the CloudBees blog. Viktor is also the author of The DevOps 2.0 Toolkit, which explores Jenkins, the Pipeline plugin, and the ecosystem around it in much more detail. Over the years, Jenkins has become the undisputed ruler among continuous integration (CI), delivery and deployment (CD) tools. It, in a way, defined the CI/CD processes we use today. As a result of...

Those who fervently watch the jenkinsci-dev@ list, like I do, may have caught Daniel Beck's email today which quietly referenced a significant milestone on the road to 2.0 which has been reached: the first 2.0 release candidate is here! The release candidate process, in short, is the final stabilization and testing period before the final release of Jenkins 2.0. If you have the cycles to help test, please download the release candidate...

After first announcing the Jenkins 2.0 effort last fall, we are pleased to announce the availability of the first Jenkins 2.0 alpha builds. For months we have had builds available from the jenkins_2.0 branch of development, but the "alpha" builds mark Jenkins 2.0 being officially made available for testing and feedback. Download 2.0-alpha now Jenkins 2.0 Highlights Pipeline as Code The new Pipeline functionality in Jenkins allows you to define configuration as code, which can...

Historically January has always been a very big month for the Jenkins community. Between FOSDEM Southern California Linux Expo (also known as SCaLE) we seem to hand out more stickers during the last week in January than any other week of the year. This year’s SCaLE 14X conference finally outgrew the LAX Hilton in Los Angeles, where it had been hosted in years past, and moved over to the...

Over the past couple months, we have been working on a long overdue Code of Conduct for the Jenkins project (meeting minutes here and here). Following in the footsteps of other projects like the Apache Software Foundation, Go lang and countless others, we have adopted this code of conduct to help set guidelines for what behaviors are acceptable, and what behaviors are not, when acting within the Jenkins community or on behalf of the Jenkins...