I haven’t written much about some of the great content and sessions that have been held in our DevOps Connect: CD Summit/Jenkins Roadshow. We have held them in Dallas, Chicago and Boston. Each event was different, but all featured some tip top speakers. One of the “regulars” at our events has been Kohsuke Kawaguchi or KK as the Jenkins world calls him. KK is the CTO of CloudBees and the creator of Jenkins. He is also one of the more intelligent people I have ever had the pleasure to meet. On top of this his humble nature only enhances his overall stature. I wanted to post a short interview I did with KK at the Dallas DevOps Connect: CD Summit/Jenkins Days. We hope to have his full keynote available on our DevOps TV YouTube channel soon as well.

Below is the the video of my interview with KK and below that is a transcript to read along as well. Also a quick reminder next week (May 23 & 24 and May 25) we are in London and Stockholm continuing this fantastic road show. Next fall we will be in 8 or 9 more cities as well. Check out DevOpsConnect.com for dates.

Step 1 of 7

14%

Which of the following best describes how you currently monitor and manage systems across your hybrid cloud environment?(Required)

Multiple separate tools for different environments

Multiple separate tools for different monitoring and management functions

Single consolidated dashboard

Custom built monitoring and management solution

No full monitoring and management solution

Don’t know

How valuable would it be for your monitoring and management solution to incorporate predictive analytics to help you identify and address system issues that are critical and not waste time or effort working through all the data and “noise” that is not critical?(Required)

Extremely valuable

Moderately valuable

Somewhat valuable

Slightly valuable

Not valuable

How do you most typically address potential system issues BEFORE they impact your operations?(Required)

Automated workflows and playbooks to remediate potential issues as soon as they are detected

An orchestrated response process that leverages automation, AI, and human expertise to rapidly respond to potential issues

Advanced monitoring tools such as predictive analytics and anomaly detection to proactively identify and address potential issues

Respond to issues as they arise, using manual processes and troubleshooting techniques

A combination of automated remediation, orchestrated response, and/or proactive monitoring to address potential system issues

Don’t know

Other

What methods does your organization use to control and monitor cloud/IT spending?(Required)

Centralized procurement processes

Pre-approved budget thresholds

Automated cost monitoring tools

Department-level spending controls

Regular cost audits and reviews

Cloud cost optimization platform

Approval workflows for resource provisioning

Native financial operations tools provided by the cloud provider

No formal controls in place

Don’t know

Other

Please specify:

Which methods do you rely on most to detect security vulnerabilities in your systems?(Required)

Automated scanning tools

Manual assessments

Vendor notifications

Threat modeling (for early detection)

None of these

Don’t know

Other

Please specify:

What are the TWO most common ways you prioritize vulnerabilities to address within your environment?(Required)

Based on potential impact

Based on exploitability

Regulatory compliance requirements

Based on CVSS scores

Risk-based analysis of multiple factors

First-in-first-out approach

No formal prioritization process

Don’t know

How do you typically handle system updates and security patches?(Required)

Automated updates and patches

Manually review and apply updates and patches on a regular schedule

A combination of automation and manual review

Apply updates and patches on an as-needed basis.

Outsourced update and patch management

No defined process

Don’t know

Other

Δ

Alan Shimel:                Hi, this is Alan Shimel, editor in chief at DevOps Connect CD Summit Jenkins Days in Dallas. Happy to be joined by KK, the founder of Jenkins and CTO of CloudBees. KK, thank you.

KK Kawaguchi:          Oh, thank you very much for having me.

Alan Shimel:                Thank you – well, it’s our pleasure to have you, but you are just coming out of the Jenkins track that you delivered, which was a very technical track on Jenkins and your keynote this morning was on continuous delivery pipeline and we spoke about Jenkins 2.0 as well as local Jenkins as a service and Jenkins certification. And what was the last one where we give you the whole package that we’re going to not certify, but what was the word?

KK Kawaguchi:          So you call that the CloudBees Jenkins platform, private label solution basically.

Alan Shimel:                Absolutely. So, for our listeners who weren’t lucky enough to be here, can you – I’m not going to ask you to do the whole 45 minutes, but can you give us a – just in five minutes, sort of the highlights of each, of what we spoke about?

KK Kawaguchi:          Yeah, so Jenkins version two, like, we are trying to move to dial  in three key areas. The one is the continuous delivery through the pipeline of code, so we want people to be able to define this choreography of orchestration, AKA, the continuous delivery pipeline as a series of text files. And then they can put that into version control system and monitor them well. So that’s one of the sort of key features in Jenkins 2.0.

The second one is this more curated out of the box experience. So we want new people who are starting Jenkins today or tomorrow to start with this 80 percent, like a richer set of functionality that represents the 80 percent of the use cases so they have right out of the box, they get something useful and they can get a lot of mileage from. And then at some point, they would start leveraging this great ecosystem in Jenkins. So that’s this out of box experience is the second part.

And then the third one is some of the GUI improvements. You know, Jenkins is something people will use every day, so we wanted to make sure that we keep up with this progress in the frontend technology. So that’s something we’ve been doing. So those are the three key pillars to the new release.

Alan Shimel:                And I think you said that fingers crossed, we’re looking at the Jenkins 2.0 or CloudBees 2.0 in the end of this month?

KK Kawaguchi:          Yeah, so the Jenkins 2.0, we are – we’ve been working on this for a good while now and we are at the final home stretch. Today is actually the release candidate day.

Alan Shimel:                Really?

KK Kawaguchi:          Yeah, and then in two weeks, if nothing bad shows up, and that’s the part where I’m crossing fingers, nothing bad shows up, in two weeks, we are shipping the 2.0 GA.

Alan Shimel:                So as you mentioned in your keynote, as someone who started this as a little project for your three, four man team inside, I imagine there’s a tremendous amount of price in seeing what this has become and –

KK Kawaguchi:          Yeah. Yeah. Little did I know that the itch that I was scratching was shared by so many other people.

Alan Shimel:                Yep, hundreds of thousands, really.

KK Kawaguchi:          Yeah, exactly.

Alan Shimel:                What was the number, 100,000 active installs, 400,000 computers?

KK Kawaguchi:          Yes, that’s right. I think the exact number I believe I think is 120,000 or something, but there’s a massive number of people using Jenkins to, I guess to help move their – to help deliver software faster and I’m really proud of being a part of that.

Alan Shimel:                Fantastic. KK, one last question. Many of our listeners and readers out there, they’ve heard of Jenkins. They’ve heard of continuous delivery. They may not know how to get started with it. For someone just looking to get started, what’s the best way?

KK Kawaguchi:          Right. So if you are really new to the whole, you know, whole CICD, then I think that the very easiest place you can start is, well, you know, the install Jenkins, it’s really easy to just really get it installed or you have it installed and so you can start one up and then you put the – like an automated build up on every commit.

So, everyone already has a build screen because that’s going to run that every time someone commits a change, even something that simple, which only takes like 15 minutes, it’s going to pay a lot of dividend.

And then once you get this idea across to your team that well, a little bit of automation helps, then you can like incrementally go a little bit by little bit over time. So next step might be running tests. Maybe that could take a lot of, you know, multiple phases. And then that’s how I start on the, like, how Jenkins spreads inside some microsystems is really where that came from. That’s how Jenkins got into so many places and that’s how people are doing it, one thing at a time, sort of a little bit over a little bit.

Alan Shimel:                Excellent. KK, thank you so much for your time. Thank you for sponsoring, CloudBees for sponsoring our CD Summits and we look forward to seeing you in future CD Summits as well as Jenkins 2.0.

KK Kawaguchi:          Yeah, thank you very much and me too.

Alan Shimel:                Thank you. This is Alan Shimel for staging-devopsy.kinsta.cloud.