Q-and-A With CloudBees CEO Sacha Labourey and Jenkins Community Evangelist Tyler Croy Ahead of DevOps World | Jenkins World (Part 2)

DZone 's Guide to

Q-and-A With CloudBees CEO Sacha Labourey and Jenkins Community Evangelist Tyler Croy Ahead of DevOps World | Jenkins World (Part 2)

Hear more about the upcoming DevOps World | Jenkins World conferences as well as what's new on the Jenkins product map from CloudBees CEO Sacha Labourey and Jenkins Community Evangelist Tyler Croy.

· DevOps Zone ·
Free Resource

Just recently, I shot over some questions to Sacha Labourey, CEO of CloudBees, ahead of the DevOps World | Jenkins World conferences to learn more about what we can expect to see at the shows. As I couldn't stop myself from writing questions, this interview spilled into a two-parter (part 1 is here), with Sacha joined by Tyler Croy, Jenkins Community Evangelist, to speak more specifically to the product questions I had about Jenkins.

Hope you enjoy the interview!

What’s new in Jenkins these days? What are you guys doing to continuously innovate?

Tyler Croy, Jenkins Community Evangelist, CloudBees

The Jenkins community continues to grow. We are probably undergoing the heaviest period of major innovation in the history of the Jenkins project. Here is a summary, in no particular order, of the major projects the community is working on right now.

1. Jenkins Pipeline. We are introducing a new user experience with Jenkins Pipeline. A really exciting development having to do with restartable stages. This functionality allows a user - should a failure occur - to restart from the failure point, meaning restarting from the last successful point in the pipeline before the error occurred. This is particularly important for long-running jobs, as having to start from the beginning after a failure could mean a lot of lost time.

2. Jenkins X and Kubernetes. Creating a highly efficient and opinionated platform to deliver apps into Kubernetes. This project is all about the developer workflow. With Jenkins X, we are providing a way to deliver software apps into Kubernetes very rapidly.

3. Configuration as code. This functionality will allow people to describe how their Jenkins implementation should be configured, completely in code. With this capability, Jenkins environments become easily reproducible - exactly reproducible. This is important when you are trying to trace back an error, or even when you want 100% compatibility between dev and test, or test and staging environments.

4. Jenkins Evergreen. This is all about continuous delivery for Jenkins. With Jenkins Evergreen, the Jenkins project will automatically update an online distribution of Jenkins. We will then deliver that new update to Jenkins implementations. Updates will include enhancements to the most important plugins and Jenkins core. This service will help users keep their Jenkins installation running smoothly.

5. Cloud native. This project involves architectural work within Jenkins core. We are improving the core of Jenkins to more natively integrate with cloud APIs like CloudWatch and S3. Along with that, the Jenkins project has created a Special Interest Group (SIG) to work with AWS and Microsoft (and others), both of whom are keenly interested in making Jenkins more cloud-native.

The trend we are seeing is that CD has become understood by large segments of the developer community. All of these projects embody that shift in interest from CI to CD. We have offered CD capabilities in Jenkins for several years, already - but these projects really take it forward in huge leaps.

What are the most popular plugins for Jenkins?

Tyler Croy, Jenkins Community Evangelist, CloudBees

The Jenkins Pipeline suite of plugins have proven to be very popular, particularly as the concepts around configuration as code hit more mainstream usage. Jenkins Pipeline is growing very rapidly. Since introducing Pipeline with Jenkins 2, in April 2016, there has been such significant adoption of Jenkins Pipeline that almost every plugin created or updated is now Jenkins Pipeline-native. Jenkins Pipeline has become the de facto way for developers to interact with Jenkins and deliver software. Likewise, hand-in-hand with Jenkins Pipeline, Blue Ocean continues to be strongly adopted and is evolving the whole Jenkins UI. As of the latest stats from the Jenkins project (July 2018), there are about 3.5 million+ configured pipelines.

We continue to see significant adoption of people using Jenkins with Docker, and thus using the Docker integration with Jenkins. Docker is part of the mainstream CI/CD toolkit now and we are seeing heavy adoption of the Docker plugins, especially when coupled with Jenkins Pipeline.

Of all projects that use Jenkins, what is the most common language? (Java, I would presume, yeah?)

Tyler Croy, Jenkins Community Evangelist, CloudBees

Since the project doesn't track platforms/languages being used, I am not sure it is Java. I would say it would probably follow the general language popularity trends, for example, JavaScript would be popular for sure. Of course, there is still strong Java adoption, but we do see Jenkins being used with all types of technologies. For example, .Net Core from Microsoft (C#). Microsoft uses Jenkins to build and test it. Java is strong because of the Jenkins heritage, but there are plenty of other platforms and languages being used, too. An interesting recent development is that with the surge of infrastructure as code - tools like Puppet, Chef, Ansible, Terraform - many organizations are using Jenkins to adopt this trend.

What is the market share that Jenkins has in the DevOps world?

Tyler Croy, Jenkins Community Evangelist, CloudBees

The best, most targeted information we have is the recent JetBrains survey and the older ZeroTurnaround surveys. Consistently, Jenkins is the CI/CD tool used by the vast majority of engineers surveyed. We know at least 60-70% of the developer community is using Jenkins. Automation is an intrinsic part of the DevOps transformation wave that is occurring and we know that Jenkins is the preferred automation tool for most. The JetBrains survey actually shows more people using Jenkins than the next four solutions, combined.

Why would you use Jenkins over TeamCity, Travis, Bamboo?

Tyler Croy, Jenkins Community Evangelist, CloudBees

Jenkins gets improved day after day by an enormous, vibrant community of open source contributors. As a result, it supports every tool or technology anyone would ever need/want to use. Based on the strength of the community and the innovation they contribute to Jenkins, those are the top two reasons.

Can you speak to the strategic decision for Cloudbees acquiring Codeship? What’s been happening there recently?

Sacha Labourey, CEO, CloudBees

The acquisition of Codeship extends CloudBees value and leadership in the rapidly evolving continuous delivery/DevOps marketplace. Over the years, CloudBees has focused its product development efforts on the enterprise Jenkins market. We have helped organizations to scale their software development and continuous delivery capabilities by providing a highly scalable platform that forms the foundation of their DevOps strategy.

Now CloudBees Codeship meets a new and growing market requirement for SaaS-based software delivery toolchains. These are opinionated tools that offer fast learning and simple operation.

Increasingly, development teams want self-service tools that are easy to learn and manage, in order to support their development efforts. The addition of CloudBees Codeship — a SaaS solution — to the CloudBees portfolio enables CloudBees to address this need. We now provide self-service tools that are easy to use and manage. CloudBees CodeShip also broadens our addressable market in a significant way and caters to a segment of the market that we were not previously engaged with. We see this as an opportunity to increase our customer acquisition and transaction velocity.

Is there anything else that I’m leaving out which you think our audience of mostly enterprise software devs and architects would like to know about?

Sacha Labourey, CEO, CloudBees

Yes, they should attend DevOps World!  Seriously, CD is a lot closer than you may have realized. At DevOps World | Jenkins World you will be able to chart the path today and learn about the tools, technologies and best practices you need to get there. Every single topic we have touched on in this Q&A will be included in workshops, trainings and conference sessions. It is truly one-stop shopping for learning everything you need to know about CD and DevOps.

Thanks very much to both of you for the interview!

Learn More About the Conference

Now that you have the scoop on DevOps World, don't forget to register for San Francisco and use the special promotional code DZone has made available for its readers. Simply enter JWDZOCUST and you will get a 20% discount off of your full registration.

cloud native, conferences, devops, jenkins, kubernetes

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}