devopsy.kinsta.cloud

Tag: JUC

  • The Jenkins JUC is coming to Santa Clara

    The Jenkins JUC is coming to Santa Clara

    sacha-laboureydevopsy.kinsta.cloud spoke with Sacha Labourey, CEO, CloudBees about the upcoming Jenkins User Conference, its value, purpose, and focus, and about CD. It’s fitting coming into the JUC to highlight Mr. Labourey’s recent accomplishments. “Last year, we announced the Jenkins workflow, so the ability to build pipelines to create Continuous Delivery environments,” says Labourey. Noting Jenkins’ focus heretofore on CI and the notion of single jobs, Labourey offered that CI was not sophisticated enough to build those pipelines. “So the workflow enabling CD is receiving a lot of attention from the community and customers,” concludes Labourey.

    Moving on to more recent news, Labourey agrees that Jenkins’ support now for Docker is leading the community to consider how it can better leverage Docker. “Or, if they are already using Docker, they want to see how they can streamline the process by which they are going to build those images, register those, test them and so on,” says Labourey. These developments are key to understanding what customers and the DevOps-minded community will likely bring to the JUC, and what they can hope to take away from it.

    Great Expectations

    Labourey has great expectations for the JUC. “First, it’s a nice party. A lot of those people discuss together at the forums or through other means and that’s a great way to connect,” says Labourey. The JUC will be one big multi-topic Jenkins / CD conversation between and among attendees and presenters. There’s something to be said for face-to-face meetings despite the many unified communications channels and presence technologies available today for remote exchanges, collaborations, and white boarding.

    Second, and if the Washington and London Jenkins UCs are any clue, the Santa Clara Conference will see more of what Labourey calls “traditional companies” sending teams to this event to learn new Jenkins features, how other companies applied best practices to solve problems, and what did and did not work for them.

    Addressing the Community: the State of CI &CD

    devopsy.kinsta.cloud specifically asked Mr. Labourey if as we come into the conference he would briefly address the state of CI & CD. Labourey details the changing Jenkins audience and what waits in store for them.

    “The historical users of Jenkins can have a pretty strong focus on Continuous Integration. That’s how the project was born. That’s how it became successful. I think we are seeing a new wave of users now, a fresh wave coming from a Continuous Delivery standpoint looking at the full lifecycle rather than just the development section of it. Sometimes I feel like Jenkins CI is the wrong name. It should be Jenkins CD now because Jenkins CI sends the wrong message. I hope a lot of people can spend quality time thinking about that and educating themselves about those new features because they’re not just new features. It’s Jenkins tomorrow. It’s really the problems that Jenkins will have to solve tomorrow. It’s like a new era for the Jenkins project. I really hope that people attending the conference can realize this.” – Sacha Labourey, CEO, CloudBees.

    The JUC keynote and events will mirror Labourey’s statement in that the content, especially the presentations will include real use cases with innovative deployments and CD as well as technical discussions of how to master new features. “We see that people attending for their second year have done some quality work with Jenkins within their companies. They come back to present their experience in the form of a company use case or some extensions they’ve created,” says Labourey.

    A Vision for Jenkins and CD

    “It’s very important for everybody to realize the success of their company and also the success of Jenkins itself will happen if everybody makes the transition to CD and understands it,” says Labourey. Labourey sees the JUC sessions as covering the new tools that make Jenkins the leader of CD. The JUC committee carefully selected presenters and topics in order to target that goal.

    And since not everyone can attend a JUC, says Labourey, CloudBees as a company will be hiring people that will be much more active in educating the Jenkins community about this new era of Jenkins.

  • Jenkins User Conference is a win-win for CloudBees

    Jenkins User Conference is a win-win for CloudBees

    The Jenkins User Conference and CD Summit US East, will be held in Alexandria, Virginia in a couple weeks. Gene Kim is one of the keynote presenters and the event includes an impressive list of sponsors, presenters, and attendees highlighting the momentum of DevOps. I spoke with CloudBees CEO Sacha Labourey—who will also be attending the event in Virginia—about the Jenkins User Conference, the growing Jenkins community, and CloudBees’ role in it all.

    Labourey expressed satisfaction with the growth and strength of the open source community involved in developing and maintaining Jenkins. It is the success of the community that both demands and allows for the Jenkins User Conference to be organized at locations around the world throughout the year.

    Continuous Delivery

    Jenkins is a platform for continuous delivery or continuous integration. The concept may initially have been targeted at developers but Labourey believes that the focus on continuous delivery is now higher up in the corporate food-chain. It’s now IT operations people and even the CIO and other executive leaders who are addressing the question, “How can we improve the delivery of software within the organization?”

    There is no single solution—no cookie cutter, one-size-fits-all way to do continuous delivery, though, according to Labourey. Every case is different.

    That’s why an event like the Jenkins User Conference is so valuable. Those considering Jenkins or exploring continuous delivery can learn more. Those already using it can share their own lessons learned and best practices. The community can collaborate and compare notes. By meeting and sharing companies and individuals can understand how other organizations are accomplishing things and take away the tips and advice that make sense and try it out for themselves. The cooperative nature of the Jenkins community is the fuel that drives it.

    Separation of church and state

    I asked Labourey to explain the relationship between Jenkins and CloudBees. CloudBees business focuses on delivering Jenkins continuous integration / continuous delivery for customers, so CloudBees obviously has strong incentive to ensure the success of Jenkins. He told me that CloudBees is a significant supporter of and contributor to the Jenkins open source project. CloudBees does not own or control Jenkins, though, and believes strongly in maintaining what Labourey called the “separation of church and state.”

    CloudBees has developers and engineers actively involved with Jenkins—contributing code and providing support. However, the Jenkins community organizes itself and manages the open source project without any involvement from CloudBees. The Jenkins community wants to remain independent and manage its own destiny according to Labourey.

    As noted above, though, CloudBees’ business relies on Jenkins. The stronger Jenkins is, and the better its features and capabilities, the better it is for CloudBees. That is why CloudBees has taken on the role of helping to organize and fund the Jenkins User Conferences. It’s a win-win because whatever helps the Jenkins community also helps CloudBees.

    Labourey promised that attendees of the Jenkins User Conference and CD Summit will not be disappointed. The sessions are filled with valuable content, and there will be discussion of recently added features and capabilities as well as the unveiling of some new ones. If you’re organization is using continuous delivery / continuous integration—or even considering it—you should check out the Jenkins User Conference.