Tag: cloudbees

  • Fast Pass: Your Ultimate Guide to the Best of Jenkins World

    Fast Pass: Your Ultimate Guide to the Best of Jenkins World

    At the end of the month, Jenkins users and DevOps professionals from around the world will head to San Francisco for the annual Jenkins World conference, taking place Aug. 28-31. The conference lasts four days, but time flies when you’re attending trainings, keynotes, sessions and networking events. To make sure you get the best of everything at Jenkins World, we’ve put together a guide that will ensure you have the most productive and enjoyable experience.

    NOTE: devopsy.kinsta.cloud readers can get 20 percent off registration with the code JWDEVOPSCUST.

    Take the Time to Develop Your Skills

    The first two days of the conference will be full of workshops and training sessions. Regardless of skill level, there are trainings for everyone. Those just getting familiar with Jenkins can attend an “Introduction to Jenkins” training for free and learn how to easily create pipelines while putting in place best practices for continuous integration (CI) and continuous delivery (CD).

    Those a bit farther along their Jenkins journey can attend workshops such as “The Final Mile: Jenkins Pipeline and Patterns for Operations,” where attendees will review patterns of common problems and solutions specific to operations teams in a CD environment , as well as how to create Jenkins pipelines that address the needs of operations.

    Don’t Miss These Essential Sessions

    All attendees should make sure they make it to each of the keynotes, of course! Keynote speakers include Sacha Labourey, CEO of CloudBees; Kohsuke Kawaguchi, founder of the Jenkins project; and Jez Humble, CTO at DevOps Research and Assessment LLC.

    In addition to top-notch keynote speakers, there are a number of DevOps professionals you’ll want to hear from while at the show. Try to attend at least one of these sessions:

    Keep an Eye Out For …

    Make sure you listen in to find out who the winners are of the first annual Jenkins World Awards Program. There are two awards tracks: Jenkins Community Awards and CloudBees Innovation Awards. Each track has several categories including Jenkins Contributor Award, DevOps Automation Excellence Award and more. Winners will be announced Thursday, Aug. 31, at the show.

    You’ll also want to stop by the sponsor expo hall to check out dozens of great vendors. As with any good conference, there will be plenty of swag passed out. Exhibitors will include GitHub, BlazeMeter, Docker, JFrog, Fugue, Sonatype and others. Don’t miss out on taking a photo with the famous Jenkins butler at the CloudBees booth!

    Can’t Forget to Network

    With so many great sessions to attend, don’t forget to make time for networking events. It would be a waste to not take advantage of dedicated networking time to speak with experts and peers who have likely dealt with some of the challenges your organization may be facing. There will be several networking opportunities, including a reception Aug. 30 sponsored by CA BlazeMeter. Or if you’re looking for ways to stay active, attend a scheduled walk or yoga class.

    If you can check off all of the above activities, you’re bound to leave Jenkins World a better professional! Make a checklist at the start of the conference to ensure you hit all the events and sessions you’re most excited for.

    If you haven’t registered yet, there’s still time! Use the promotional code JWDEVOPSCUST for 20 percent off.

    About the Author / André Pino

    André brings more than 20 years of experience in high technology marketing and communications to his role as vice president of marketing at CloudBees. He has experience in several enterprise software markets including application development tools, middleware, manufacturing and supply chain, enterprise search and software quality and testing tools. André has particular expertise in working with the executive teams of enterprise software companies to create unique competitive positioning, build pipeline and establish sustainable market leadership. Prior to joining CloudBees, he served as principal analyst serving technology marketers at Forrester Research. He has also held a number of senior management positions in marketing and communications with companies such as Segue Software, Hewlett-Packard, Unisys Corp. and Bluestone Software. André holds a BS from Eastern University.

  • 5 Can’t-Miss DevOps Sessions at Jenkins World

    5 Can’t-Miss DevOps Sessions at Jenkins World

    In less than a month many Jenkins users and DevOps professionals will gather in San Francisco for Jenkins World, taking place Aug. 28-31. With more than 60 sessions to choose from, covering a wide range of topics, it can be difficult to narrow down your schedule. That’s why it’s important to go into the show with a goal in mind.

    For those of you specifically looking to hone your DevOps skills, here are five can’t-miss sessions that fall under the DevOps tracks.

    NOTE: devopsy.kinsta.cloud readers get 20 percent off their registration with the promotional code JWDEVOPSCUST.

    DevOps: Delivering on the promise of innovation, agility and velocity

    Forrester Analyst Rob Stroud will discuss recent Forrester research that confirmed organizations are leveraging agile development techniques, automated CI/CD pipelines, testing and release automation to deliver differentiated products. The interactive discussion will allow attendees to review their DevOps maturity versus that of the market. Stroud also will lead discussions of how DevOps is adding value within enterprises and how the adoption of containers and serverless computing will further drive DevOps adoption.

    DevOps Leadership Panel

    Attend this panel to hear from a variety of experts on topics such as software delivery challenges, business value realized from DevOps, building internal support and more. Panelists will include:

    • Rob Stroud, Principal Analyst, Forrester – moderator
    • Kolby Allen, AWS Architect, WatchGuard Technologies
    • Andrey Falko, Principal Engineer, Salesforce
    • George Swan, Director of Engineering Solutions, Autodesk
    • Stas Zvinyatskovsky, Engineering Leader and Architect, Accenture

    Mapping Your DevOps Journey with the DevOps Quadrant Maturity Model

    In this session, Brian Dawson, DevOps evangelist at CloudBees, will map the DevOps journey to the DevOps Quadrant Maturity Model. He’ll go through the characteristics of organizations within each quadrant and present strategies for moving to the next stage of DevOps maturity. The DevOps Maturity Model is a great way to assess your current state of DevOps.

    Banking on DevOps: How Leading Financial Services Organizations Are Driving the DevOps Transformation

    Hear from financial services executives about how their organizations are embracing DevOps practices to speed innovation and deliver more value to customers. The financial services industry faces specific security, governance and regulatory hurdles that can prove challenging when changing processes and technology. This session will be moderated by Andre Pino, VP of marketing at CloudBees. Speakers will include:

    • Brock Beatty, Director, Software Engineering, Capital One
    • Karthrik Loganathan, Director, Business Technology, ESQM, Discover
    • Stefan Simenon, Head of IT Tooling & Software Development, ABN AMRO Bank N.V.
    • Moied Wahid, Director, Software Development, PayPal

    Leading a DevOps Transformation

    In this session, Jez Humble, CTO at DevOps Research & Assessment LLC (and also a Jenkins World keynote speaker), will discuss how implementing DevOps is more than just implementing tools. He’ll walk through how a DevOps transformation requires a different way of thinking about everything from budgeting to management to compliance. He’ll also break down exactly what DevOps is and isn’t.

    Don’t miss out on the hundreds of DevOps leaders and trailblazers to learn from at Jenkins World. You can view the full Jenkins World agenda to see what other sessions can help boost your DevOps skills!

    If you haven’t registered yet, make sure you to do so today with the promotional code JWDEVOPSCUST.

    — Alan Shimel

  • Jenkins World Preview: Q&A with Jez Humble

    Jenkins World Preview: Q&A with Jez Humble

    As we approach Jenkins World, scheduled for later this month in San Francisco, we sat down with Jez Humble, author of “Continuous Delivery” and one of the best-known names in DevOps. Jez will be keynoting this year’s event, along with CloudBees CEO and founder Sacha Labourey. Here’s what he had to say.

    Alan Shimel: What are you most excited for at Jenkins World?

    Humble: This is my first Jenkins World! I’m most excited to meet the community and find out what people care about, what problems they’re solving, what obstacles they’re facing, and what’s making them excited or sad. I’ve spent over a decade doing and teaching continuous integration and working on tools, so I’m always looking to validate and challenge my views.

    Shimel: What do you plan to cover in your keynote?

    Humble: I’ll be talking about DevOps, and how it’s transforming the world of software and the businesses it powers. I’ve been working on a research project into DevOps for the last few years so there will be some hard data. I’ll also be covering the principles and practices, as well as the obstacles that teams commonly face implementing them, and how to overcome them.

    Shimel: What do you hope attendees take away from your talk?

    Humble: First, I want folks to understand that this transformation is real, not just hype. High performers achieve higher levels of throughput, stability, and quality, and lower costs. Second, it’s hard. We’ve been talking about continuous integration for nearly twenty years now—it’s one of the basic agile engineering practices—and still the majority of people who think they’re doing it actually aren’t. But my other message is that whatever kind of organization you’re in, whatever your technology stack, you can apply these principles today. The essence of high performance is to work on getting better every day as part of your daily work, and that’s something all of us can—and should—commit to.

    Shimel: What are the major DevOps trends you’ve seen this year?

    Humble: I’ve not seen anything brand new jump on the scene this year. I think that’s a good thing. We’ve had so many transformational new technologies in the last few years from containers and serverless to new tools that I think we were in danger of drowning under shiny objects and hype. I think what I’ve seen in the last year is a better understanding of the contexts in which these tools and technologies can be effectively applied.

    Overall, the last few years has been pretty exciting as we’ve seen devops and continuous delivery be applied in every domain from government (I spent most of last year working at 18F in the U.S. Federal Government helping to implement a DevOps, cloud-first approach to software delivery there) to mainframes in  financial services to firmware. One of the common objections to devops is the “won’t work here” attitude, and we’ve comprehensively demolished that. 

    Shimel: How do you expect DevOps to change in the next five years? 

    Humble: I’m hopeful that many of the core practices such as infrastructure-as-code, continuous delivery, disposable/immutable infrastructure and blameless post-mortems will become business-as-usual in organizations of all types and sizes. However the field is still moving pretty fast, so I think we’ll continue to see plenty of innovation both in terms of the practices, their implementation, and the tools. 

    Shimel: What are the three most important things DevOps professionals need to focus on to achieve DevOps success?

    Humble:

    1. Know what success looks like in measurable terms. What are the organization-level goals we’re all working towards, and when do we want to have achieved them? Leaders should be setting clear, prioritized, measurable goals—for example, “Release every two weeks without anybody working outside normal business hours”—and then giving teams the resources and support they need to achieve them.
    2. Most of your problems are going to be cultural. People like to focus on tools, and tools are definitely important, but that’s not normally where the failure modes are. I recently said my #1 devops advice was to buy lunch for and actively listen to someone in the role you complain about most in your org, whether that’s the auditors, the testers, or the DBAs. Find them and work out something you can do to make their life a bit better and then do it.
    3. You’re never done: keep going! As I said, high performers are always working to get better. Devops and continuous delivery are implemented through working to get a little bit better every day. Most of the big lessons I learned in my career I learned not by working on exciting new technologies but by doing unglamorous grunt work using tools like CVS and bash. Find out what your team’s biggest obstacle is right now and do something to improve. Then find the next obstacle! Rinse and repeat.

    — Alan Shimel

  • DevOps Chat: Jenkins World Preview with Cloudbees CEO, Sacha Labourey

    DevOps Chat: Jenkins World Preview with Cloudbees CEO, Sacha Labourey

    Jenkins World, at the end of the month, promises to be the biggest and best yet. There could be upwards of 2,000 people at this year’s event. With a schedule full of training, sessions, keynotes and more, it is a don’t-miss event if you are into Jenkins, DevOps, CD and more. We sat down with Cloudbees CEO Sacha Labourey to discuss a Jenkins World preview.

    Sacha has guided Cloudbees on its journey in working with the Jenkins community while making the value of the Cloudbees offerings readily apparent. His past experience with JBoss has helped much. There is a Q&A with Sacha that we did as well, which has a lot more information.

    As usual, the streaming audio of our conversation is below, followed by the transcript of our conversation. Have a read or listen and hope to see you at Jenkins World!

    Audio

    Transcript

    Alan Shimel: Hey, everyone, Alan Shimel, devopsy.kinsta.cloud here for another DevOps Chat, and today’s DevOps Chat is all Jenkins World all the time. I’m joined by none other than Sacha Labourey, Labourey – I messed it up, but we’ll let Sacha pronounce it correctly. I only know Sacha about three or four years now and still can’t pronounce his name correctly, but, more importantly, Sacha is the CEO and visionary behind CloudBees. Sacha, welcome to DevOps Chat.

    Sacha Labourey: Thanks a lot, Alan, and my last name is a disaster to say for English-speaking person, so it’s “Labourey” – think about “Labor Day” and remove the “D,” but even that is hard to compute fast, so you did well.

    Shimel: Okay. Labourey. So, Sacha, we’re gonna talk about Jenkins World, and, for those of our listeners who aren’t aware, Jenkins World 2017 is coming to San Francisco. It’ll be at the Marriott Marquis Hotel there, right in downtown. And the conference runs from August 28th through August 31st. There’s so much planned this year, but, Sacha, this is – what? – the third or four, maybe more, Jenkins World that you’ve done?

    Labourey: Yeah, actually, I was looking at some of the numbers. I remember the first edition, probably – I’m not even sure if it was called “Jenkins World” back then, but, in 2012, we had 200 persons attending and we’re extremely proud of this, obviously. If you remember, the Jenkins Project was relatively new – it had just changed names in 2011 – so 2012 was 200 people. And, this year, we’re expecting at least 10X that number, so it’s gonna be a massive event in San Francisco.

    Shimel: Yep. And for our math-challenged friend out there, 10X of 200 is 2,000. And –

    Labourey: I think so, yes.

    Shimel: Yep. And, even comparing last year, Sacha, to this year, I think – I mean, last year was the biggest year ever done and I wanna say it was around 1,300, 1,400, something like that.

    Labourey: Yeah, absolutely. So it’s a big jump. You know, it’s almost 50 percent more than last year, so it’s a big step forward.

    Shimel: Good and congratulations on that. I think it’s testament, though, Sacha, to both the popularity and usage of Jenkins, as well as CloudBees. Right? And, you know, it –

    Labourey: Yeah –

    Shimel: Yep. Go ahead.

    Labourey: Yeah, you’re right. I think it’s like the perfect wind condition, you know? It’s, on one hand, you have DevOps maturing and being on everybody’s to-do lists, and so a lot of people wanna know more, wanna learn, want to share their experience. Jenkins is doing extremely well, as a project. Lot of new features in the last few years, you know, starting with Pipeline, Blue Ocean, and so on, so that makes it a very hot topic.

    And I think CloudBees, as you said, we’re doing extremely well as a company and we’re obviously extremely active in that field. We’re working a lot with the Jenkins community – I know you wanna talk about that, at some point – and so, yeah, I think it’s all of those different winds coming together and making that amazing conference.

    And, you know, we talk a lot about the numbers, right? Obviously, 2,000 people or above – it’s gonna be an amazing conference – but it’s also the quality of the content, the number of tracks and so on. This year is really gonna be a step up from last year, which was already an amazing conference.

    Shimel: Yep. Let’s talk about speakers and stuff for a second, if we can, Sacha. Obviously, you’re there and you will be doing one of the keynotes – I guess it’s the first day of the conference, right? The 30th?

    Labourey: Yeah, I’m gonna – yes. I’m gonna be one of the keynote, yes.

    Shimel: And, without letting the cat out of the bag and making new news here, can you give our audience maybe just a little bit of an idea of what to expect or what topics, areas you wanna cover, as part of your –

    Labourey: Yeah, absolutely.

    Shimel: – talk?

    Labourey: Yeah, the good news is, first, I’m not gonna be singing or dancing or anything like that, so you should be safe. And from a –

    Labourey: – from a content – [chuckles]

    Shimel: Uh-huh?

    Labourey: – from a content standpoint, obviously, like I try to do every year, we’re gonna be doing kind of a “state of the union” on what happened and where things stand, what we’ve learned, what works, what doesn’t work maybe, and show so a vision for the future. And the vision needs to be multiple years ahead, but it also need to be actionable, practical, and so we’re gonna be talking about some of the new things we’re gonna be announcing at Jenkins World, some amazing features. It’s gonna be great timing when you look at the maturity of DevOps itself. The type of requirements and needs from DevOps people also evolved with the other whole maturity of the space, and so I think we’re gonna have some pretty significant announcements that week that will fly very, very well with the community there.

    Shimel: Great. And then, in addition to yourself, Sacha, of course, Kohsuke – you know, KK – will be speaking and I’m sure everyone in the Jenkins and CloudBees community will be looking forward to that. He’s kind of revered within the community there, right? So…

    Labourey: Yeah. Every year, KK – so Kohsuke is doing his keynote and so he’s – I’m taking more of the business angle and the impact on the businesses; KK is obviously taking the community angle and the evolution of the project. And, when you look at KK, you see – you know, you perceive somebody who is not shy but pretty reserved, as a person, but I can tell you, when he’s on stage every year, it’s such a pleasure to see him there and make his status of the union, go through the numbers, and he’s a lot of fun. He’s really, really fun on those keynotes, so I’m really excited about this one.

    Shimel: Yeah. I mean, I’ve had the pleasure of watching KK present at a lot of the Jenkins Days and CD Summit roadshows that we did, over the last couple years. And I will tell you, you know, I think he kinda feeds off the members of the community and they, in turn, kinda feed off of him, so it is a great thing. I wanted to just also briefly mention another keynote speaker that you guys will be featuring at Jenkins World, and that’s my friend Jez Humble.

    Labourey: Yes, absolutely. Jez accepted to come and talk as a keynote speaker. Very excited as well. He makes great presentations. He has unique insights into this market, this transition, so I’m extremely excited about Jez Humble’s presence here.

    Shimel: Yeah. And, of course, Jez – I mean, Jez literally wrote the book Continuous Delivery, as well as the Lean Enterprise, and Jez is also a cofounder and, I think, working full time now with DORA, DevOps Research and Analysis, along with Gene Kim and Dr. Nicole Forsgren. So he had some great insight. You know, they surveyed something – I think it was 25,000 or 27,000 people over the last – or organizations over the last 4 or 5 years, and it really – I mean, again, great, great presentation.

    Sacha, if we can, while we’re on topic, you brought it up earlier or mentioned it, but I wanna really kinda bring it home for our audience, and that is that, yes, this is Jenkins World. It’s about Jenkins. Jenkins is an open-source project that, literally, millions of people are involved in, in one way or another. And CloudBees is intrinsically linked to Jenkins, right? But the relationship between CloudBees and Jenkins, Sacha, how do you explain it to our audience?

    Labourey: Yeah, you’re right. It’s a very important topic and I think we feed the community, the community feeds us. I think there is a very healthy relationship there. First, I think every company-slash-open-source-project behaves in a slightly different fashion. You know, I used to be at JBoss, at Red Hat, so we had already, in two companies, very different ways to interact with open-source communities and build a business on top.

    At CloudBees, I would say, we have yet another way to do that, and it’s really this church-and-state separation and the community’s the community. We obviously have an impact on the community because we’re pretty massive contributors to the project, but they are independent. They have their board; we provide requests that get approved or sometimes denied. So I think it’s very healthy to have this independent community and you can see it through the massive community beyond the Jenkins core itself, right? We’re talking about more than 1,400 different plug-ins, and each of those plug-ins are kind of like mini-communities around the project, so it’s a pretty massive ecosystem out there.

    And so, obviously, as a company, we leverage these install days and the power of this install days and help enterprises adopt Jenkins at scale and get insight into their installation and so on. But the community’s also benefiting a lot from, I think, CloudBees’ involvement. We’ve been massive contributors and initiators of projects like Pipeline; like Blue Ocean, the new user interface. If you look at some of the security issues that have emerged in Jenkins, much like in lots of Java programs out there, CloudBees has stepped up and spent – top quality engineers that have spent their weekends and weeks fixing a number of those. And that’s for the good of the community; that’s for the good of everybody. And, if CloudBees was not to do that, well, I’m not sure who else would be doing it, so I think, yes, there is a very healthy sharing taking place here, and I’m very proud we’ve been able to put that in place.

    Shimel: Excellent. Sacha, let’s turn a little bit – I said earlier on that the Jenkins World is August 28th through August 31st. The sessions, the keynotes, the exhibits – those are August 30 through 31st, but trainings and workshops actually start August 28th. And I wanna say the 30, 31st is a Wednesday, Thursday, and I believe the 28th is Monday, Tuesday.

    Labourey: Correct.

    Shimel: And there’s a whole lineup of training – some of it’s sold out already, but there’s a whole schedule of, I think, Jenkins training, Jenkins certification, and not just one curriculum of the same class being repeated. There’s a deep bench of different Jenkins training sessions and workshops available, correct?

    Labourey: Yeah. And, last year, that was already a huge success, so, this year, we’ve made sure that we have even more training course available, even more seats, but that’s a big, big one. And think about it. Obviously, for people who live in San Francisco and the Bay Area, it’s a relatively easy one to attend Jenkins World – it’s almost like a no-brainer – but we actually have a pretty important number of people traveling from the US but also from APAC or from Europe, and, for those people, it’s very important to make sure that they, quote unquote, don’t “just” attend the conference, and, way this layout are just laid out, you have a way to get trained, to get ready to be certified, which is great for your career. You get to attend workshops. So it’s very hands-on. You really come back and learn, have something you can factually show on your resume to your boss and explain that you’re really, you know, one, two steps above from where you were the week before, so it’s a great combination to come the weekend before, spend a few days doing training and workshops, and then attend the conference, meet with people, share expertise and so on, so it’s an amazing pack, I think.

    Shimel: Yeah. No, it’s a great opportunity. I mean, I should also mention that the DevOs Institute, partnering with CloudBees, will be offering some certification classes on the 28th and 29th at Jenkins World as well. I think they’ re gonna be offering the continuous testing engineer class, taught by Mark Cornbee, who wrote the curriculum, and I think they might be debuting “DevOps Leader,” which is aimed for people who wanna lead the transformation, and that’s a great class as well. I’m not 100 percent sure. If you go to Jenkins World, to the website on CloudBees, the Jenkins World section, you could see the DevOps Institute classes, as well as all – and, as I said, there’s as deep bench of CloudBees and Jenkins training available the 28th and 29th, and there are some workshops as well, I believe, on the 30 and 31st, for maybe people who just can’t get there all four days.

    Sacha, I wanted to talk about some of the other sessions that are gonna be on for the 30 and 31st. One, you know, shameless, I’ll promote – I’m actually moderating a DevSecOps panel on the 31st. I believe it’s at 10:30 in the morning. And that one will feature Rob Stroud of Forrester – I think Rob’s gonna be on a number of panels and sessions at Jenkins World. I’ll also have several of my friends from the security community, including Pete Chestna of Veracode, Andrew Storms of New Context. I think Andrew Wallgren, CTO of Electric Cloud, will be joining us. Derek Weeks or Curtis Yanko of Sonatype, and Pathik Patel, I believe, also. So that’s gonna be a great panel, but, Sacha, what panel or session would you – you know, give us three sessions, if you will, that maybe you’d like to recommend to our listeners.

    Labourey: Well, so there’s gonna be some special tracks on finance, for example, and I think those will be very well-received. We see a big interest from specific verticals, interested in sharing expertise, right? So, you know, I was just looking before, you have the Federal Reserve Bank of New York was gonna talk about their path to DevOps, so those are pretty amazing presentation, I think. DevOpsSec – obviously, there’s gonna be your presentation, but there is more to it. DevOpsSec is – I’m not gonna be arguing with you on this – it’s a very hot topic, so quite a bit around DevOpsSec coming up. That’s very interesting. And I think, also, a lot around testing. A lot of companies are interested now in automating testing – that’s still the part that adds the most friction to their delivery pipeline – and so you’re gonna see a lot of great presentations around testing there.

    Shimel: Great. Looking forward to that. Sacha, we’re almost out of time, unfortunately – it goes really quickly – but I just wanted to make sure we hit everything. People can still register for Jenkins World, right, if you go to cloudbees.com/jenkinsworld, home –

    Labourey: Absolutely. Yes, yes. The time is now. And it’s the right time, if you’re traveling, to think about it. You have to book your hotel; you have to book your plane. So don’t wait until the last minute to do it. Absolutely. Now is the time.

    Shimel: Yep. One other thing I wanted to quickly mention, something I’m really looking forward to, is, like last year, devopsy.kinsta.cloud will have a video broadcast booth set up on the show floor – we’re gonna be upgrading it a bit this year – but, on the second day, we’re actually gonna do a CEO panel, and, Sacha, you’re kind enough to join us, and we will have Rob Stroud again from Forrester there, as well as a few other CEOs. And we’re gonna do a wrap-up, really, of Jenkins World and the state of DevOps and CD and CI and where we are in the market, from a CEO’s perspective, so, for listeners, you know, that’s something – it should be up within a few days after Jenkins World. I highly recommend you listen in on that to get that CEO perspective.

    Labourey: Yeah, we’re gonna have some big names there, so it’s very exciting.

    Shimel: Yep. Should be fun. Sacha, before we wrap up, anything we left out about Jenkins World or anything else our listeners should be aware of?

    Labourey: Well, if you’re into DevOps, you can’t miss that event. That’s the only thing I wanna say. Just think about the amount of training, of workshops, the number of valid tracks you can attend. If you’re really serious about DevOps, it’s part of your job. Really, this is gonna be the conference you need to attend, so now is the time. Let’s go.

    Shimel: Okay. And, listeners, if you go through devopsy.kinsta.cloud, use the code “jwdevopscust,” so that’s J-W-D-E-V-O-P-S-C-U-S-T. I’ll put it in the show notes of the thing and maybe that’ll help, but, if you do, you’ll get a 20-percent discount, and everyone can use a 20-percent discount, that’s for sure.

    Labourey: [Chuckles]

    Shimel: Anyway, hey, we’re gonna call it wrap on this episode of DevOps Chat. Sacha, thank you so much for taking time out your – I know it’s later in your day over in Europe, and we will see you in San Francisco in just a few weeks.

    Labourey: All right. See you there, Alan. Thanks a lot.

    Shimel: Okay. Sacha Labourey, CEO, CloudBees, talking to us about Jenkins World. I’m Alan Shimel for devopsy.kinsta.cloud, DevOps Chat. Thanks, everyone, and we’ll see you soon on the next DevOps Chat.

    — Alan Shimel

  • Jenkins World: Q&A with CloudBees CEO Sacha Labourey

    Jenkins World: Q&A with CloudBees CEO Sacha Labourey

     The Jenkins Community and DevOps professionals around the world are excited for Jenkins World, coming up in just a month, Aug. 28-31 in San Francisco. CloudBees, the hub of enterprise Jenkins and DevOps, is the lead organizer and premier sponsor of the event. We sat down with CloudBees CEO Sacha Labourey to discuss everything Jenkins World.

    NOTE: If you haven’t registered yet, there is still time! devopsy.kinsta.cloud readers can register now with the code JWDEVOPSCUST and get 20 percent off.

    Q: How has Jenkins World evolved since its inception?

    A: It’s been quite the journey since the beginning of Jenkins World. The very first Jenkins World was back in 2011. We had 200 people attending and we were extremely proud of that. The Jenkins project was still new, as it had just changed its name in 2011, so we were excited to see the community already coming together. Fast forward to 2017 and we’re expecting about 2,000 attendees at this year’s event. We’ve grown 10x since the first show and even from last year to this year we’re expecting almost 50 percent more attendees. It’s been great watching the conference mature and grow over the years. 2017 will be our best show yet!

    Q: What’s new at Jenkins World this year?

    A: This year we’re expanding everything, covering a wide range of topics including DevOps culture, process design, automated testing, performance measurement, security, leadership and more. We’ve added a welcome reception and evening event in the expo hall so attendees have more opportunities to network and learn from each other.

    Additionally, we’ll be kicking off the first-ever annual Jenkins World Awards. These awards recognize the achievements of CD innovators and Jenkins contributors from around the world. There are two award tracks: Jenkins Community Awards and CloudBees Innovation Awards. Winners in each track will be featured at Jenkins World.

    Q: What can attendees expect from the keynotes?

    A: We have a great lineup of keynotes this year, including myself! My keynote will be a state of the union that looks at what’s happened in the last year, what worked, what didn’t work and what we’ve learned from it. Stemming from that I’ll also offer a vision for the future. This will be actionable, and practical—something we can truly act on. I’m excited to say that there will be some significant announcements throughout the week as well.

    Kohsuke Kawaguchi will also be keynoting. His keynote is always excellent. He’ll offer a state of the union from the Jenkins community angle. He’ll go over the evolution of the Jenkins project and run through the latest numbers. It’s such a pleasure to watch him on stage each year; his talks are always exciting.

    We’re also thrilled that Jez Humble will be keynoting this year. He literally wrote the book on DevOps, so if you’re looking to learn about DevOps, he’s the man you want to hear. He’ll be discussing the DevOps market, challenges, opportunities, the evolving requirements and needs of DevOps professionals and more.

    Q: What advice do you have for first-time attendees?

    A: My advice is: Take advantage of the trainings, workshops and certification opportunities. Last year, workshops and training were a huge success, so we’re offering even more this year. It’s a great way to further your career. It’s very hands-on and provides an opportunity to show tangible results of how the conference helps you improve your skills and ultimately helps your career.

    Also, make sure to network with fellow professionals. It’s the perfect time to find out how others are approaching their projects, what challenges they faced and how they’ve overcome them. It’s such a great community of professionals to learn from.

    Q: Are there any sessions you recommend?

    A: I’d certainly recommend checking out some of the specialized vertical sessions. For example, we’ll have a number of sessions that focus on the financial services industry with speakers from Capital One, PayPal and more.

    We’ll also have some great DevSecOps presentations. It’s a very hot topic and is increasingly important in DevOps. I’d highly recommend attendees get to at least one of these sessions.

    Finally, there will be several sessions focused on testing—which often adds the most friction to delivery pipelines. These sessions will prove really helpful for attendees looking to enhance their testing processes.

    There you have it! This year’s show is bound to be bigger and better than ever before. Register now with your 20 percent off code: JWDEVOPSCUST.

    — Alan Shimel

  • Why Your Manager Will Want to Send You to Jenkins World 2017

    Why Your Manager Will Want to Send You to Jenkins World 2017

    Jenkins World 2017 is right around the corner. The conference will be held in San Francisco Aug. 28-31 and will be the biggest event of the year for Jenkins users, with approximately 2,000 people expected to be in attendance! You will not want to miss out on this event, full of learning and networking opportunities.

    Need some help convincing your manager why you should attend? No problem—we have laid out all the reasons why attending would be beneficial to you and your company. Once you have convinced your manager to attend, don’t forget to register today! (As a media sponsor for Jenkins World, we are providing a special offer for our readers. Register with this promotional code and get 20 percent off your registration: JWDEVOPSCUST.

    Educational Value

    Jenkins World will be offering more than 60 educational sessions given by real Jenkins experts—a chance to learn from the most experienced users. Did we mention that you can also receive a free Jenkins exam with the purchase of a full conference registration? Imagine the benefits for both your résumé and team.

    At the conference, you’ll be able to take advantage of great training sessions to better enhance your Jenkins capabilities. The training sessions include Jenkins Certification Training, Introduction to Jenkins, DevOps Leader Certification Training and DevOps Test Engineering Certification Training. We recommend highlighting to your manager what sessions you will want to attend in advance. Check out the full agenda here.

    Jenkins World is offering keynotes from many industry leaders. Be sure to emphasize to your manager the importance of hearing from the very best in the Jenkins community, live on stage and in the breakout sessions. From Jenkins founder Kohsuke Kawaguchi to CloudBees CEO Sacha Labourey and featured speaker Jez Humble, your manager will greatly appreciate the knowledge you bring back to the office from listening to such experienced industry experts.

    Networking Opportunities 

    The Jenkins World conference will provide numerous networking opportunities. Learn what similar problems and challenges other organizations are facing in the industry. Make it known to your manager that you will be exposed to people like you, with like business needs and challenges, that you will be able to connect with.

    Prove ROI

    When convincing your manager to let you attend, it is first important to make them aware of the potential ROI of this opportunity. Detail exactly your expenses including airfare, hotels and meals. This will better help your manager understand the exact cost to send you to Jenkins World. Make sure you also present how this knowledge will help push you and your team forward, ultimately propelling your entire organization forward. The ROI will be evident – make that clear! (And the ROI just got better, because devopsy.kinsta.cloud readers can use this discount code and get 20 percent off: JWDEVOPSCUST.)

    We hope this provides enough information to help you convince your manager to let you attend! We have also created an email template to use when sending all this over to your manager for review. Once you have successfully convinced your boss, go register!

    — Alan Shimel

  • Top 5 Reasons to Attend Jenkins World

    Top 5 Reasons to Attend Jenkins World

    The countdown is on! Jenkins World 2017 is coming to downtown San Francisco, Aug. 28-31, for the annual opportunity to learn about all things Jenkins, DevOps and continuous delivery. This year’s event will be held at the Marriott Marquis and will bring together approximately 2,000 Jenkins users, comprised of Jenkins experts, IT executives, DevOps practitioners and partners from all over the world. The event is led and sponsored by CloudBees, the hub of enterprise Jenkins and DevOps, and will offer attendees opportunities to learn, explore and network, while shaping the future of Jenkins.

    As a special offer to devopsy.kinsta.cloud readers, we are offering a discounted registration. Use the promotional code JWDEVOPSCUST during your Jenkins World registration and get 20 percent off!

    Need more convincing? Below are five reasons to attend this year’s Jenkins World:

    • Hear keynotes from industry leaders: Kohsuke Kawaguchi, founder of the Jenkins project, kicks off the conference with the opening keynote this year. Other keynotes you won’t want to miss include Sacha Labourey, CEO of CloudBees and Jez Humble, CTO at DevOps Research and Assessment LLC and co-author of “The DevOps Handbook,” “Lean Enterprise” and “Continuous Delivery.” Kohsuke will provide perspective on the dramatic milestones reached in the community this year, while Sacha will provide perspective on how CloudBees and DevOps are transforming industries. Jez will discuss DevOps principles and practices, how to overcome typical obstacles and the results companies are realizing from DevOps initiatives.
    • Attend optional training and workshop sessions: Leave Jenkins World a Jenkins master by getting certified and/or learning the fundamentals of Jenkins by attending trainings for the Certified Jenkins Engineer (CJE) exam, and the Certified CloudBees Jenkins Platform Engineer (CJPE) exam. There are several other training opportunities and a wide range of workshops addressing topics such as pipeline automation, Docker, Blue Ocean and more. Maximize the learning opportunities through the options offered early in the week, then stay for the conference and get exposure to another 60+ conference sessions.
    • Brush shoulders with the Jenkins stars: Get access to some of the biggest Jenkins experts in the world, attend their sessions and network with them. A sampling of sessions from the Jenkins World agenda includes:
      • DevOps Leadership Panel from Dirk Luedtke, SAP; Kolby Allen, WatchGuard; Moied Wahid, PayPal; Stas Zvinyatskovsky, Accenture
      • The Ten Commandments of Continuous Delivery from Viktor Farcic, senior consultant at CloudBees
      • How We Do DevOps at Rosetta Stone from Kevin Burnett, DevOps lead at Rosetta Stone
      • Azure DevOps Open Source Integrations from Arun Chandrasekhar, senior program manager at Microsoft
      • You also won’t want to miss the ever-popular Ask the Experts booth, where Jenkins experts from around the globe address your specific issues and questions on the spot. You’ll return from the conference armed with a solution to that vexing issue you have been trying to solve!
    • Visit a variety of vendors: At the expanded Sponsor Expo you can check out a range of technologies that integrate with Jenkins as well as DevOps services provided by experts. Check out the booth swag and make sure to check out the news coming from the vendors.
    • Meet the Butler and snap a selfie: You may have seen the Butler on his wild social media adventures recently, but at Jenkins World you’ll have the chance to meet him in person. Don’t forget to snap a pic with him at the social media booth and share with your friends. There will also be Flat Jenkins floating around beforehand—stay tuned to social media (specifically #JenkinsWorld on Twitter) to see where he lands before Jenkins World!

    All of this and so much more awaits you at Jenkins World. Go register now! Use this code JWDEVOPSCUST and get 20 percent off your conference registration.

    See you soon!

    About the Author / André Pino

    André brings more than 20 years of experience in high technology marketing and communications to his role as vice president of marketing at CloudBees. He has experience in several enterprise software markets including application development tools, middleware, manufacturing and supply chain, enterprise search and software quality and testing tools. André has particular expertise in working with the executive teams of enterprise software companies to create unique competitive positioning, build pipeline and establish sustainable market leadership. Prior to joining CloudBees, he served as principal analyst serving technology marketers at Forrester Research. He has also held a number of senior management positions in marketing and communications with companies such as Segue Software, Hewlett-Packard, Unisys Corp. and Bluestone Software. André holds a BS from Eastern University.

  • DevOps Chat: BlueOcean Puts CD Pipelines Within Reach of Every Team

    DevOps Chat: BlueOcean Puts CD Pipelines Within Reach of Every Team

    Blue Ocean brings easy-to-use continuous delivery for teams to everyone. Years in the making, Blue Ocean is a major project built from the ground up for Jenkins Pipeline. I had a chance to speak with two of the key contributors from CloudBees and the Jenkins community, James Dumay and R. Tyler Croy. Tyler is on the Governance Board for Jenkins.

    Blue Ocean provides:

    • Sophisticated visualizations of CD pipelines, allowing for fast and intuitive comprehension of pipeline’s status.
    • Pipeline editor makes creation of pipelines approachable by guiding the user through an intuitive and visual process to create a pipeline.
    • Personalization to suit the role-based needs of each member of the team.
    • Pinpoint precision when intervention is needed and/or issues arise. Blue Ocean shows where in the pipeline attention is needed, facilitating exception handling and increasing productivity.
    • Native integration for branch and pull requests enables maximum developer productivity when collaborating on code with others in GitHub and Bitbucket.

    As usual our conversation in the streaming media player is immediately below.

     Streaming Audio

    Transcript of our conversation

    Alan Shimel: Hey everyone. This is Alan Shimel, editor in chief of devopsy.kinsta.cloud. Welcome to another DevOps Chat. We have two guests today on DevOps Chat. We have James Dumay and R. Tyler Croy of the Jenkins community. James, Tyler, welcome to DevOps Chat.

    James Dumay: Nice to be here, Alan.

    R. Tyler Croy: Thanks for having us.

    Shimel: Thank you. Let’s start off though with just a little background of each of you. James, you’re coming to us all the way from Australia. In deference to the distance, we’re going to let you go first. Why don’t you share with our audience a little bit of your background?

    Dumay: Yeah, sure thing. So I’ve been probably building development tools for the last 10 years. I think I’ve found my calling here. I love making developers more productive. I also want to make developers happier. So I do have this bee in my bonnet that developer tools are difficult when they’re boring and they’re not very pleasing. It’s my life’s mission to turn that around.

    Shimel: Excellent. Tyler, how about you?

    Croy: I’ve been with the Jenkins project a little over eight years now. I started using it when I was a back-end services engineer, a few startups ago. Every single company that I’ve joined needs more continuous delivery or some non-zero amount of continuous delivery stuff. So I found myself getting more and more ingrained in the Jenkins project and bringing Jenkins to bear in companies to ship products faster. Now I work at CloudBees talking about how you can do that and help other people see the light with some of the Jenkins stuff I’ve been doing for a while.

    Shimel: Tyler, I don’t want to embarrass you. You actually are—I don’t even know the word, but you’re one of the—on the steering committee or the governing committee for Jenkins. Is that the right way to put it?

    Croy: I guess you would say I’m on the Jenkins governance board. In the beginning of the Jenkins project, there was Kohsuke Kawaguchi who was the founder of the project, and then there are a few other core folks that were floating around that helped get Jenkins off the ground. Andrew Bayer who is a major contributor to the pipeline toolset, is one of those people. So I’ve just—Jenkins became a really important part of my life. I started spending a hell of a lot more time with Jenkins, and now I’m one of the people that makes sure that the project continues to move forward.

    Shimel: Excellent. James, I don’t know if you mentioned your role other—at this point, other than you’re cuckoo for Jenkins. What exactly is your role right now?

    Dumay: I’m director of Product Management at CloudBees, but I’m also a community leader for the Blue Ocean project. I do all the outreach and talk to all the users. It’s good fun, but previously before I was at CloudBees, I was at a small Australian startup called Canva. They do an online design tool. Prior to that, I spent seven years at Atlassian, where I was product manager for actually a competing product.

    Shimel: Absolutely. Well, we’re allowed to have competing products. They may not be any good. I’m only kidding. James, you mentioned the magic word. You get the first prize today. That was Blue Ocean. Today’s a bit of a—more than a bit—today is a big day in the Jenkins community. This release has been highly anticipated. It’s been in beta and in testing, alpha before that for some time. Talk to us. What about it? Why should people care?

    Dumay: All right. That’s a big question. So I guess we’re living in a really interesting time in the industry. We have this—there’s this ride of exponential change that is happening across our industry, whether it’s tooling and technology and process, or just the raw number of people writing computer software in the—we’ll be in the year 2020 soon. I think if you look back in the previous 10–20 years, the amount of companies out there that are writing software today and were not writing software 10 or 20 years ago. So Marc Andreessen speaks about software eating the world, where all the value that companies provide slowly but surely are being made, not by the engine in a Ford motor vehicle, but it’s the software on board the Ford motor vehicle.

    So it’s an interesting time to be a software developer, or to be in this field, but it’s also a really interesting time to be a tools creator. I think with this increase of people in the industry—it’s not like we have lowered the bar to what we call a software developer, but I think there’s a lot more people today who, in their jobs, whether it be financial services, or in other industries, who are finding their job involves writing software. I think there’s a big challenge here, and Blue Ocean is founded on going out there and solving this problem, that how do we make the millions of software developers or even people who are just writing software as part of their jobs, how do we make them more productive? How do we make sure they can get what they need to get done as quick as they can get it done at the highest quality that they can get it done with the best tools possible?

    So with Blue Ocean, we’re sort of focused in on the practice of DevOps and on continuous delivery. We set ourselves a goal. What if we can make it really easy for people to adopt continuous delivery? Blue Ocean is our answer to that.

    Shimel: Tyler, James—I think James made some important points. What can you add there? Why—let’s step back a second. Let’s say our audience is vaguely familiar with Jenkins. Most of them probably use it, but there’s some maybe that don’t. What is—let’s start with what is Jenkins to them? What does Blue Ocean represent to Jenkins?

    Croy: Sort of at a high level, Jenkins is an automation server. Jenkins is probably the most well-known tool of its kind across the entire software industry. As far as helping developers build and test and deploy their software, chances are with most organization today, if someone doesn’t think they’re running Jenkins, they might just not be aware, or they might be so far removed, or that it’s hiding, that they don’t know that it’s actually there. It’s pretty omnipresent in the industry right now.

    One of the big things about I would say the shift in the industry that has made Blue Ocean important—when I first started in northern California about 10 or— [inaudible] 10 years ago, continuous integration was this really big, important thing. I kept coming to companies who either didn’t have a continuous integration server, or didn’t practice—nobody but the developers knew that there was a continuous integration server. As the industry has shifted towards this more and more rapid pace of “Let’s practice continuous delivery. Let’s get product and value to our customers as soon as possible,” it’s no longer acceptable for just the developers to get feedback to what’s going on in that process.

    So I think the important thing for Blue Ocean, and I would say broader software industry, is that continuous delivery is not a developer thing. It’s an entire team thing. It’s an organizational thing. Blue Ocean is designed from the ground up to make sure that people who might not be writing code every single day, or they might be designers, or they might be product managers, or stakeholders of some form or fashion in the software development process. They need to know what’s going on and Blue Ocean is going to give them a window into what’s going on in the delivery pipeline. That’s a pretty dramatic shift from the Jenkins that was created 10 years ago, which was just for developers.

    Shimel: Got it. Got it. Now guys, I’ve had the—I don’t know if the word is a pleasure, but I’ve had the—well, it was a pleasure in a lot of ways, but I’ve had the experience of being involved with open-source projects in the past. It’s a fickle thing being part of a community. It’s even harder when you have a corporate entity such as CloudBees in this—CloudBees isn’t alone in this. There are many companies that are mentoring, managing—whatever you want to call it—open-source projects. Talk—I loved what I saw of how that relationship was handled as it applied to Blue Ocean.

    Guys, can you give us a little color on that? No pun intended with Blue Ocean and color, but a little background on how you worked with the community to deliver, I think, what the community consensus was what was needed.

    Dumay: Just to preface this. So this is my first time working full-time on behalf of the commercial entity for _____ community. So I—when we started at Blue Ocean, I kind of put myself in Tyler’s very capable hands. Tyler had had a lot of previous experience, not with Jenkins, but with other projects, walking that fine line between community and the need for the business sponsor, I guess. So it’s been an interesting process. I think certainly for CloudBees, a healthy Jenkins community is a healthy CloudBees, and a healthy CloudBees is a healthy Jenkins community. It all feeds into each other. As long as, I think, we take things from a project perspective, like what’s good for Jenkins, we’re making good decisions in both aspects.

    Certainly, we had been running—more in terms of Blue Ocean itself, we had been running for multiple years Jenkins community surveys, and one of the top issues people would have liked to see addressed in that feedback had been the user experience with Jenkins. They really wanted it to be easier to get started. They really wanted clarity when they’re looking for particular cases, information. I think there was a real groundswell there to see some improvements, and see some sort of more modern thinking around how to solve problems. I hope that we’ve done that. Certainly the feedback that we’ve been getting from the community has been pretty great.

    Just on the community itself, I think software developers can be a pretty passionate tribe of people. So it’s—the Jenkins project is no different from the wider developer community. They’ve been passionate in a very encouraging way, in a very forgiving way as well. Particularly when you go ahead and think about any product that has—web product that has been redesigned. So the people get very upset. They’re very invested in the tools that they use, or the products that they use, and then you move their cheese, and people go “Where did that thing go? Where did this other thing go? No. I was using that. Bring it back.” I think with the Jenkins community, I think they’ve been very—I think they’ve wanted the change for so long that as things change, we—they’re getting some new goodies in their bag and they’re happy to let some of the old bits disappear.

    Croy: I think there’s also—if you look at that feedback from the Jenkins user list going back years and years and years, there’s been—most people, I would say, that contribute to the Jenkins project, note they’re new, I guess past tense, because Blue Ocean is one meadow now—knew that something needed to get fixed, and someone needed to do something to really improve and set up Jenkins for the next 10 years. The skill set and the passion and the vision really wasn’t there.

    So when James and his team, his colleague Michael Neale and some of the other people, really started to get involved, I think it was easier for other contributors in the project to rally around that. It was clear that not only did they know what they were doing, but they understood the challenge in that we needed to think about the design from the ground up, as opposed to reskinning or reseaming Jenkins. They needed to evaluate it from a user experience standpoint and start from 2016 rather than 2006, which is when the project really started. So I think that was really helpful to have some—a passionate group of people with vision to drive it forward.

    Shimel: A passionate group of people with vision can accomplish a lot. That’s for sure. Guys, let me ask you—we’re almost out of time. What—for each of you, and we’ll go with James first. James, what do you think is the single biggest aspect or feature of Blue Ocean that our listeners should take a look at?

    Dumay: That’s very unfair, Alan. I love them all.

    Shimel: How can a parent decide? But guys, so pick one. Doesn’t have to be your favorite or biggest, but one that we’d like to call out.

    Dumay: The official pipeline editor. So _____ delivery pipeline is difficult at the best of times for people to create. So we set ourselves a challenge. What if we could make it very easy for people to create a continuous delivery pipeline using Blue Ocean UI. The one thing I really like about it is it really is for everyone. We talk a lot about—we’ve got a lot of plans for the Blue Ocean in the future. One thing we talk about is the Fisher Price’ing of the editor. I don’t know if you’re familiar with Duplo blocks you give a toddler. But you can get all these different attachments, all these crazy things, and you can customize your own creation using Duplo. It’s non-checkable Lego. So really, Duplo is for everybody. So anybody of any age can—of any skillset, can construct something from Duplo.

    The thing that I like about the—I guess the vision behind the editor is anybody can construct a continuous delivery pipeline, even if they don’t have coding knowledge. Maybe they want to take—they have—we can go as far as they can have a PHP website on a Dropbox folder and they want to upload that, deploy that continuously to their webhost, their DreamHost or something like that. That’s the kind of—we want to bring continuous delivery to everyone.

    I think the communal pipeline editor is the vehicle to do that. One of the great things about the editor as well is that it is what you see is what you get. So when you build it in the editor, that’s exactly how you visualize it later on in Blue Ocean, as that pipeline is executing. It’s really powerful in that way.

    Shimel: Great. Makes sense. Tyler, how about you?

    Croy: So my interactions with Jenkins are typically when something goes wrong. I think that’s maybe a bit more common for an infrastructure administer or developer. So, for me, I would say the No. 1 killer feature with Jenkins—with Blue Ocean and Jenkins is that the clicks to get from a failure or something going wrong to seeing what actually went wrong, it’s pretty much one click. So the visualization of status is so much faster and more immediate in Blue Ocean that when I come to Blue Ocean to figure out what test failed, or what went wrong in my pipeline, I get that in a matter of seconds, as opposed to drilling around and hunting through console help. So for me, that’s probably the killer feature.

    Shimel: Make sense. Guys, we’re going to wrap up here in a moment, but just quickly, for people who want to find out more about Blue Ocean, where can they go? James, Tyler?

    Dumay: No problem. They can go over to Jenkins.io/projects/blueocean or the Jenkins blog, which is Jenkins.io/blog.

    Shimel: Okay, Tyler, I’m going to hit you with the last question. Now that Blue Ocean is 1.0, what’s next?

    Croy: [laughter]

    Shimel: [laughter] You didn’t expect to get a rest, did you?

    Croy: No, no. I think the really important thing that’s next for the Jenkins project is I would say the next three months of Jenkins pipeline and Blue Ocean adoption. Now that we’ve got the tools that we’ve brought to the broader software industry for building and constructing and running continuous delivery pipelines, we’re going to need to iterate, on them and we’re going to need to make them better as more and more people start to adopt continuous delivery. I think we’re, certainly before the end of the year, we’re certainly going to find new things that we can add into Jenkins to make that an even more enjoyable experience.

    Shimel: Absolutely. Hey guys, congratulations. I know it’s easy on release day to say something came out. There was a lot of work here, an awful lot.

    Croy: Indeed.

    Dumay: Very much so. Thanks.

    Shimel: Thank you, James, Tyler, great job. R. Tyler Croy, James Dumay of CloudBees and Jenkins talking about Blue Ocean, the big news around Jenkins and CICD Pipelines. Guys, thanks very much. Hopefully we’ll have you back soon on another DevOps chat.

    Croy: Thanks a lot. See you later.

    Dumay: Thanks.

    Shimel: This is Alan Shimel with DevOps Chat. We’ll see everyone soon on another DevOps chat, but until then, have a great day.

    — Alan Shimel

  • Jenkins Community Introduces Blue Ocean, a Radical Evolution of the User Experience That Makes Jenkins the Clear Leader for Continuous Delivery

    Jenkins Community Introduces Blue Ocean, a Radical Evolution of the User Experience That Makes Jenkins the Clear Leader for Continuous Delivery

    SAN JOSE, CA, and PARIS, FRANCE – APRIL 5, 2017 – The Jenkins project, comprised of a community of practitioners using Jenkins, announced the official release (1.0) and general availability of Blue Ocean, its dramatic new UX implementation. The anticipated launch of Blue Ocean brings a new user experience to Jenkins based on a personalized, modern design that allows users to graphically create, visualize and diagnose continuous delivery pipelines. This is more than just putting a modern face on Jenkins: Blue Ocean re-imagines the Jenkins user experience by enabling teams to more easily adopt continuous delivery. CloudBees, Inc., the hub of enterprise Jenkins and DevOps, founded the Blue Ocean project and subsequently open sourced the software.

    Jenkins is the most popular automation server in use today. With continued annual growth of about 30%, the Jenkins community now has 533,839 active nodes, with more than 11 million jobs defined in Jenkins on them.

    With the official release of Blue Ocean, Jenkins now allows any member of a DevOps team to adopt continuous delivery without having the expert knowledge previously required to use Jenkins. Continuous delivery pipelines are inherently complex, making it difficult for team members – from developers to IT operations to management – to get a common understanding of the progression of software through the pipeline. Blue Ocean simplifies the development of software pipelines by allowing developers to create them with a visual pipeline editor and then visualize the process flow in an intuitive way, such that the whole organization, not just developers, can understand it. Blue Ocean naturally fosters collaboration by providing a common view of the end-to-end pipeline that all team members can understand. Using Blue Ocean, team members gain a graphical overview of the entire pipeline, enabling them to quickly identify issues and then drill down to find the source of the problem. Blue Ocean is underpinned by Pipeline as Code which enables the pipeline definition to be stored with the application code and infrastructure as code; allowing teams to reproduce previous configurations and processes easily when things go wrong.

    CloudBees and the Jenkins community have collaborated to architect and develop the Blue Ocean user experience with key features such as:

    • Visual Pipeline Editing – Team members of any skill level can create continuous delivery pipelines from start to finish using the intuitive and visual pipeline editor. No code or text editing is required. Anyone can create sophisticated pipelines with just a few clicks.
    • Pipeline Visualization – Enables teams to visually represent pipelines in a way anyone in the organization can understand – whether technical or not, improving clarity into the continuous delivery process for the whole organization.
    • Pinpoint Troubleshooting – Blue Ocean enables teams to locate automation problems instantly, without endlessly scanning through logs or navigating through many screens.
    • GitHub and Git Integration – Pipelines are automatically created and run for all feature branches and pull requests, with their status reported back to GitHub. The whole team has visibility into whether changes need work or are good to go. Blue Ocean provides native, in-depth integration with Git.
    • Personalization – Team members can make Jenkins their own by customizing their dashboard so that they only see the pipelines that matter to them.
    • Built with and for Declarative Pipeline – Any pipeline created with the visual editor can also be edited in your favorite text editor bringing all the benefits of Pipeline as Code.

    “The Blue Ocean project has had incredibly positive feedback from the community since its inception. It brought a breath of fresh air to the working horse of developers everywhere that is Jenkins,” said Kohsuke Kawaguchi, Jenkins founder and CTO at CloudBees. “The new and very modern and intuitive UX makes Jenkins more approachable and continues to enhance the power and usability of Jenkins. It takes an organized team of contributors like CloudBees provided to the Jenkins project to drive a large effort like Blue Ocean. As CTO of CloudBees, I’m very proud that we made this happen.”

    Blue Ocean’s visualization of a software delivery pipeline 

    Blue Ocean’s visual pipeline editor 

    Additional Resources

    About Jenkins and the Jenkins Community

    Jenkins is the leading open source automation server supported by a large and growing community of developers, testers, designers and other people interested in continuous integration, continuous delivery and other modern software delivery practices. Built on the Java Virtual Machine (JVM), it provides more than 1,300 plugins that extend Jenkins to automate with practically any technology software delivery teams use.

    The Jenkins community advocates the use of Jenkins to the global development community, serving as a central source for tutorials, forums and other helpful resources for Jenkins users of all experience-levels. By recognizing the numerous contributors to the Jenkins project, the Jenkins project creates and fosters a community-powered infrastructure for maintaining and further developing Jenkins. You can follow the Jenkins community on Twitter (@JenkinsCI).

     

    — Jules Louis

  • Open Source is Not Enough for Modern Application Delivery

    Open Source is Not Enough for Modern Application Delivery

    It’s the same everywhere you turn. Companies are trying to transform their digital experiences and increase customer engagement all while improving customer experience. This is giving rise to a whole new generation of modern applications that are built fast, scale out, are mobile-first and go global on public cloud infrastructure.

    Developers building modern applications depend on:

    • An evolving set of DevOps needs
    • Modern architectural principles
    • Pervasive use of open source frameworks and tools

    Forrester Analyst, Jeffrey Hammond, and CloudBees DevOps Evangelist, Brian Dawson, discussed how developers are meeting the demand for speed without blowing budgets. They shared the best practices they have seen companies use to take full advantage of open source tools and frameworks.

    RECORDING

    SLIDES

    [slideshare id=73429224&doc=cloudbeesandforesteropensourceisnotenough-finaldraft-170321163125]

    — Jules Louis