devopsy.kinsta.cloud

Tag: cloudbees

  • CLOUDBEES ANNOUNCES INDUSTRY’S FIRST CERTIFICATION PROGRAM FOR JENKINS ENGINEERS

    New Technical Certification for Jenkins and the CloudBees Jenkins Platform adds value for engineers, teams and employers

    SAN JOSE, Calif. – March 15, 2016 – CloudBees, Inc., the enterprise Jenkins company and continuous delivery (CD) leader, today announced the rollout of a professional certification program for both Jenkins and CloudBees Jenkins Platform engineers. Though Jenkins and the CloudBees Jenkins Platform are utilized in over 128,000 projects globally by countless engineers, no formal certification existed until now. CloudBees developed the certification program in collaboration with a Certification Advisory Board comprised of Jenkins subject-matter experts, as well as CloudBees customers and partners. Registration opens on March 15 and engineers can take the exam in Prometric test centers around the world as of May 12.

    The program offers two options for certifications:

    • Certified Jenkins Engineer, for demonstrated knowledge and hands-on experience in the use of the open-source Jenkins server and plugin ecosystem
    • Certified CloudBees Jenkins Platform Engineer, for certification of additional, specific knowledge and hands-on experience in the use of the CloudBees Jenkins Platform, which adds enterprise functionality on top of the open source Jenkins server

    Achieving certification can benefit engineers in several important ways. Along with recognizing them for their Jenkins skills, certification helps engineers build credibility with colleagues, differentiate themselves from their peers and gain additional knowledge through the certification preparation process.

    The certification program offers benefits to employers and organizations, as well. Hiring managers can more easily identify qualified candidates and have confidence that they are acquiring an employee with a documented level of expertise. Alternatively, if an IT manager contracts a services organization employing certified staff, the IT manager will feel more confident that they will receive competent, skilled Jenkins experts for their project. Finally, services organizations who employ certified staff will be confident that their teams have the right skills, showcasing the organization’s qualifications and differentiating their services from competitors.

    “I volunteered to be part of the Certification Advisory Board created by CloudBees,” said Senior Director of DevOps at Ellucian, Jason Shawn. “I see the certification program as very strategic – for both the community of practitioners who are using Jenkins or the CloudBees Jenkins Platform and for hiring managers, such as myself, who want to be sure they are getting someone with a documented level of skills.”

    Attaining Certified Jenkins Engineer status will mean the engineer possesses the technical skills and knowledge necessary to effectively implement and use Jenkins with a proven level of proficiency. The exam questions are designed to test an engineer’s knowledge and hands-on experience with Jenkins throughout all stages of the software delivery process – from development to build, test, stage and deployment. Achieving Certified CloudBees Jenkins Platform Engineer status means the candidate has answered additional exam questions related to functionality specific to the CloudBees Jenkins Platform.

    “As the popularity of Jenkins for continuous delivery grows, the market demand for advanced skill levels in Jenkins as a discipline is tracking right alongside that growth,” said VP of Customer Success at CloudBees, Francois Dechery. “We’re proud to offer Jenkins and CloudBees Jenkins Platform certification opportunities. We’re looking forward not only to helping engineers build knowledge and improve their career prospects as domain experts, but also to making a contribution to the overall improvement of DevOps and CD practitioner skills available in the marketplace.”

     

    The customary certification exam fee is $200. However, for the first year of the Jenkins Certification Program, the exam fee is based on registration date, as follows:

    • Early bird: $50 for registrations between March 15 – March 31, 2016
    • Extended early bird: $150 for registrations between April 1, 2016 – March 31, 2017
    • Ongoing: $200 for registrations as of April 1, 2017

    Additional Resources

    About CloudBees

    CloudBees (www.cloudbees.com), the Enterprise Jenkins Company, is the continuous delivery (CD) leader. CloudBees provides solutions that enable DevOps teams to respond rapidly to the software delivery needs of the business. Building on the strength of Jenkins, the world’s most popular open source continuous delivery hub and ecosystem, the CloudBees Jenkins Platform provides a wide range of CD solutions that meet the unique security, scalability and manageability needs of enterprises. The CloudBees Jenkins Platform supports many of the world’s largest and most business-critical deployments.

    Backed by Matrix Partners, Lightspeed Venture Partners and Verizon Ventures, CloudBees was founded in 2010 by former JBoss CTO Sacha Labourey and an elite team of continuous integration, continuous delivery and DevOps professionals. Follow CloudBees on Twitter, Facebook, LinkedIn and Google+.

    Media Contacts:

    Katelyn Campbell / Gaby Berkman

    PAN Communications

    +1.617.502.4300

    cloudbees@pancomm.com

     

  • CloudBees Signs 13 New Reselling and Services Partners in Q4 2015

    New Partners Reflect Growing Demand for Jenkins-Powered Continuous Delivery Around the World;

    New Portal Designed to Drive Partner Profitability and Customer Success

    SAN JOSE, Calif.–(BUSINESS WIRE)–CloudBees, Inc., the enterprise Jenkins company and continuous delivery (CD) leader, today announced rapid growth in its partner community in Q4 of 2015. The growth of the reselling and services partner ecosystem in Q4 alone was nearly 50 percent and facilitates ready-access to more Jenkins-related services and CloudBees products in all global regions. To support the growing partner community, the company launched a new partner portal to provide greater access to CloudBees resources.

    New CloudBees partners reflect growing demand for #Jenkins powered CD around the world!

    New reseller, services and training partners were brought on-board during the final three months of 2015. New additions included two global services partners, two partners in the U.S. federal government sector, four partners for expanded coverage in the Asia/Pacific region and five new partners in Canada and the U.S.

    The new CloudBees partner portal, launched this month, provides the CloudBees partner community with a single destination to uncover and manage new opportunities and expand DevOps and enterprise-scale Jenkins business. Exclusively for CloudBees partners, the portal delivers marketing, sales and technical content and tools to help partners architect the best enterprise Jenkins solution for customers, help partners manage opportunities and facilitate the closing of sales.

    “The expansion of our partner ecosystem is a direct result of the global and growing demands for enterprise Jenkins solutions,” said Durga Sammeta, CloudBees senior director, global alliance and channels. “Customers are seeking enterprise Jenkins solutions and trusted advisors who can help them identify and implement continuous delivery in their transformation to a DevOps culture. These partners join CloudBees’ already extensive set of global reseller, services and training partners that enable enterprise software delivery teams to more easily embrace continuous delivery with Jenkins-based solutions.”

    The latest moves follow a series of innovations over the past year in the CloudBees partner program. The company revamped the program in July 2015 to include new tracks for reseller and training partners. By expanding these categories of partners, CloudBees ensured that customers seeking enterprise Jenkins solutions had expanded buying choices from trusted partners in the application development and DevOps sectors.

    New partners recently signed include:

    Global Services Partners:

    • InfoStretch – Global, Platinum Services and Reseller Partner
    • Unisys – Global, Services and Reseller Partner

    Reselling and Services Partners focused on the US Federal Government:

    • KP SOFT – U.S. Federal, Gold Services and Reseller Partner

    Reselling and Services Partners in APAC:

    Reselling and Services Partners in U.S. and Canada:

    Partner Comments:

    “With organizations under pressure to constantly deliver fully-featured, quality software that’s a step above the competition, the need for automation is a critical success factor. We are excited to partner with CloudBees to support customers through their continuous delivery and DevOps transformations.”
    – Adam Edwards, CTO, Middleware360 Solutions

    “U.S. Federal Government Agencies seeking to increase standardization and use of best practices, are turning to DevOps and IT automation solutions. Aurotech is excited to partner with CloudBees to help our government customers re-engineer IT practices.”
    – Imneetpal Brar, DevOps Program Manager, Aurotech

    “For InfoStretch’s enterprise customers, Jenkins is crucial for continuous integration and continuous delivery initiatives. By using the CloudBees Jenkins Platform, our customers’ will evolve their mobile strategy toward quality engineering and greater agility.”
    – Guy Vachtel, Senior Director of Global Partners & Business Development, InfoStretch

    “Alten is thrilled to resell CloudBees’ innovative solutions across the APAC region. Alten’s presence in China, Hong Kong and Korea, in particular, provides our mutual customers with leading edge technology, guidance and expertise in implementing CI and CD initiatives.”
    – Lawrence Kole, Managing Director, ALTEN China

    “It’s fantastic to work with an organization as committed to partnerships as CloudBees. What’s really compelling is to see the resources and investment CloudBees has made in its channel strategy. That aligns well with how we approach partnerships.”
    – Tyler Davey, VP Sales, Architech

    “Jenkins plays a key and essential role and is a recommended best practice to our clients for continuous delivery practices. The advanced enterprise features offered by CloudBees makes Jenkins a natural fit for our customers looking to implement scalable continuous integration and continuous delivery processes across DevOps teams.”
    – Joe Dickman, SVP, Vizuri

    Resources

    About CloudBees
    CloudBees (www.cloudbees.com), the Enterprise Jenkins Company, is the continuous delivery (CD) leader. CloudBees provides solutions that enable DevOps teams to respond rapidly to the software delivery needs of the business. Building on the strength of Jenkins, the world’s most popular open source continuous delivery hub and ecosystem, the CloudBees Jenkins Platform provides a wide range of CD solutions that meet the unique security, scalability and manageability needs of enterprises. The CloudBees Jenkins Platform supports many of the world’s largest and most business-critical deployments.

    Backed by Matrix Partners, Lightspeed Venture Partners and Verizon Ventures, CloudBees was founded in 2010 by former JBoss CTO Sacha Labourey and an elite team of continuous integration, continuous delivery and DevOps professionals. Follow CloudBees onTwitter, Facebook, LinkedIn and Google+.

    Contacts

    PAN Communications
    Katelyn Campbell / Gaby Berkman, +1-617-502-4300
    cloudbees@pancomm.com

  • Middleware360 Partners with CloudBees

    Partnership brings strength of technology along with continuous delivery & DevOps expertise to enterprise customers.

    Vancouver, British Columbia (PRWEB) January 14, 2016

    Middleware360 Solutions, experts in business automation, system integration solutions, and custom application development, today announced a services partnership with CloudBees, the Enterprise Jenkins Company and continuous delivery (CD) leader. Middleware360 Solutions will provide implementation and training services to its clients who want to adopt continuous delivery practices and are implementing the CloudBees Jenkins Platform as the foundation to do so.

    “We are pleased to be working closely with CloudBees, as they support our goal to offer clients continuous delivery solutions that are stable, scalable, flexible and fast,” said Derek Marley, CEO for Middleware360 Solutions. “The CloudBees Jenkins Platform enables enterprises to accelerate the software development process through automation, giving them the ability to build and deploy software faster, while saving time and money,” said Marley.

    The CloudBees Jenkins Platform is the industries most proven, fully featured technology platform for implementing continuous integration (CI) and continuous delivery (CD). It extends open source Jenkins with key CloudBees-developed features and capabilities that meet the unique security, scalability and manageability needs of enterprises.

    “With Jenkins adoption accelerating, strategic partners like Middleware360 are essential to delivering the enterprise-scale Jenkins solutions customers are seeking,” said Durga Sammeta, senior director of global alliances and channels, CloudBees. “We are excited to partner with Middleware360 as they are uniquely positioned in having the expertise necessary to guide customers through continuous delivery and DevOps transformations, supported by the CloudBees Jenkins Platform.”

    Offering end-to-end IT services, Middleware360 is helping clients streamline business processes, increase business flexibility, and decrease system complexity. “We are seeing more organizations looking to invest in continuous delivery as a way to seize opportunities quicker and stretch dollars further, and CloudBees helps to automate and streamline this process. Using the Jenkins platform, we are now capable of innovating in light speed bursts while remaining flexible to try different approaches to solve our client’s challenges. We look forward to many years of collaboration with CloudBees,” said Marley.

    About Middleware360 Solutions, Inc.

    Middleware360 Solutions is a dynamic full service partner focused on business automation & integration solutions, custom application development, and IT managed support that delivers accelerated results for cross-industry organizations. Middleware360 offers flexible services encompassing solutions & architecture, project delivery, and application & integration managed support. Based in Vancouver, British Columbia, we work with organizations across Canada to achieve greater business efficiency. Learn more at http://www.middleware360.com

    For more information, please contact:

    Adam Edwards

    1-844-236-0360

    info(at)middleware360(dot)com

    For the original version on PRWeb visit:http://www.prweb.com/releases/2016/01/prweb13162477.htm

  • Jenkins Founder Kohsuke Kawaguchi Talks DevOps Leadership, Part 2

    Jenkins Founder Kohsuke Kawaguchi Talks DevOps Leadership, Part 2

    In part one of this two-part series, we covered the early work of Kohsuke Kawaguchi, founder of Jenkins while he was at Sun (now Oracle) and also how he addressed the project’s challenges to growth by applying extensibility/plugins, incentivizing sharing in the community, and removing barriers that can result from apprenticeships. Now let’s continue as Kawaguchi shares the rest of his story.

    Explosive Community & Tooling Growth

    Today the Jenkins Project and its open source community boast more than 120,000 members and 1,000 plugins. It was by design that Kawaguchi spurred that growth. Here are the challenges he faced, his solutions and his good fortune.

    Though continuous integration (CI) and continuous delivery (CD) have sprouted an immense amount of automation in DevOps, it was necessary to have diversity in the software development environment/toolkit to ensure that each developer and team have the tools best-suited to their goals and uses.

    “This is where our extensibility features came in handy—by letting people reuse what they could and build the missing pieces. As developers, we prefer flexible building blocks over rigid software that does things in just one way,” says Kawaguchi. This diversity encouraged community growth by removing a tooling stumbling block and brought even more plugins to life.

    Jenkins emerged at a time when IT began embracing open source projects and, as a result, benefited from that momentum. “Companies recognize that it’s better in a lot of ways to rely on open source software than proprietary tools. It gives them more control,” he says.

    Jenkins as a Key Component for Build Orchestration

    The DevOps movement has helped Jenkins become a key component of helping teams orchestrate their builds. From its roots of using time-based activity triggers and requiring a developer complete “this task, then that one” in a cascading, triggering fashion, Jenkins has moved on to model what people do and then pull that work into Jenkins as automated functions.

    The automation capabilities of Jenkins kept expanding and Jenkins entered what Kawaguchi calls the “orchestration-idioms-as-plugins” era, with different people in the community developing different patterns for orchestrating/automating activities. “I created one such plugin called the Promoted Builds plugin, which basically was a generalization of how different teams collaborated within Sun to release software,” says Kawaguchi. By creating these idioms within the model of executable plugins that others can adopt, the Jenkins Project fostered even more efficiency in sharing, adopting and reusing proven orchestrations.

    As automation spread from builds to tests, deployments and releases, these orchestrations gained new importance but presented still another challenge, which a plugin also solved. “Idioms were useful but different idioms created by different people weren’t really composable,” Kawaguchi said. “In recognizing that, we’ve built the Workflow plugin, which creates a single framework to describe any orchestration, whether simple or complex. We can share and compose these fragments.”

    Kawaguchi’s Leadership Accelerates DevOps Acceptance

    As both a leader of the Jenkins open source community and the CTO of CloudBees, Kawaguchi has helped the open source community and enterprise teams alike wade in to DevOps. The open source Jenkins ecosystem helped to move automation ahead. It gave developers a fast track to useful, functional software that would please ops and enter production quickly. At the same time, it enabled developers to innovate swiftly and improve on that same software to see more utility and recurring rewards.

    “Now with CloudBees, we have allowed the project to have a number of full-time engineers, which increased its velocity. It also brought commercial support, an enterprise version of Jenkins, professional services and training,” Kawaguchi notes. “It made Jenkins more viable in the mind of large-scale conservative enterprise users who value those things and allowed Jenkins to be deployed at scale in those organizations.”

  • Jenkins Founder Kohsuke Kawaguchi Talks DevOps Leadership, part 1

    Jenkins Founder Kohsuke Kawaguchi Talks DevOps Leadership, part 1

    Kohsuke Kawaguchi, founder 0f open source continuous integration tool Jenkins, was an early leader in DevOps, guiding the development of the Jenkins Project during his time at Sun (and later, Oracle) and plotting the course it would follow.

    “This project started as a hobby while I was at Sun,” Kawaguchi says. “From the project’s inception, it was not popular. During those early days, my leadership was really just to keep the project going. It was easy for me because the project was so useful that I didn’t need any external encouragement.”

    Once Jenkins steadily gained acceptance, Kawaguchi worked on polishing it and making it more user-friendly. “Writing software that works for you is much easier than writing software that works for other people, especially first-time users,” he says, noting he drew from his experiences supporting users to make Jenkins a better tool.

    Kawaguchi applied his previous open source project experience to make Jenkins an application/project that others could join, invest in and enjoy using. “As the project grew even more popular, I expended more conscious effort into those initiatives, specifically into extensibility and incentivizing sharing,” says Kawaguchi.

    Kawaguchi’s Vision for Extending Jenkins & Incentivizing Sharing

    Kawaguchi decided to use a plugin model for extensibility to solve the potential bottleneck of using an increasing number of contributors while managing change. Sensible software development does not permit unbridled change; developers must propose changes or at least innovate in an environment where they can retract changes that create issues.

    To attract more contributors into Jenkins, Kawaguchi decided to let people add whatever they wanted to it, through plugins. “Selling me on a software change need only happen when a change affects my use, so if we can split things up such that your change is in your plugin, I’m not affected by your change so long as I don’t use your plugin,” explains Kawaguchi. “This enables developers in the Jenkins Project to go from idea to implementation without getting blocked by someone, which reduces organizational overhead and encourages innovation.”

    But while this approach solves the extensibility issue, it also can create a new one. Without any incentive to share plugins with other users, extensibility can lead to siloed development in which only the group that created the plugin benefits from it. It then becomes difficult for the open source community to locate, leverage and improve on others’ advances, leading to plugin abandonment should the developer of that extension relocate to another project.

    Kawaguchi pressed for an update center and set a rule that plugins listed in the update center must be available to the entire community. “This created a positive feedback loop that encourages users to install plugins through the update center and developers to bring their plugins to the community,” says Kawaguchi.

    Breaking Down the Walls

    While extensibility and sharing accomplished much, the Jenkins Project faced another hurdle. Other projects such as the Apache Project use apprenticeships (the “committerships”), an approach designed to create a stable of tried-and-true contributors. But it also can be a hurdle, discouraging many developers.

    The Jenkins Project, however, simply asks that contributors apply good judgment when considering whether a plugin/change is good for the larger open source project and its community. “This might sound scary to some, but it really strikes the right balance between the speed of progress and quality,” says Kawaguchi. “Besides, everything is version-controlled, so if we later find a problem, we can always roll things back.”

    Stay tuned to devopsy.kinsta.cloud for the rest of Kawaguchi’s DevOps journey with Jenkins.

  • DevOpsQA NJ Meetup – Jenkins Workflow Tech Talk

    DevOpsQA NJ Meetup – Jenkins Workflow Tech Talk

    DevOpsQA NJ just held oIMG_5444ur November Meetup on Jenkins Workflow with Kishore Bhatia and Isaac Cohen from CloudBees  as speakers.   The venue was provided by  ROKITT at a state-of-the-art office space with breathtaking views of NYC.   Even though it was heavily raining outside, there was a great turnout of veteran and new members.     

    We kicked off with a fun speed networking over pizza and drinks provided by TEKSystems.  Following that, I did an introductory session on Transformation thru Automation via Jenkins talking about 10 steps to get a head start on continuous integration and deployment.  The steps include Identifying Bottlenecks, setting up a common repository, automating of the build, unit testing, environment configuration, test data management, regression testing and reporting.   

    Next, Kishore and Isaac gave an introduction to Jenkins Workflow followed by a detailed demo.  IMG_5445

    Kishore started off with a famous saying by Marc Andreessen, co-founder of Netscape –  “Software is eating the world”.   More and more things are getting automated and every business is becoming a software business.   We are automating Ops so that we can do more Ops and automating Manual QA so that we can do real (valuable) Manual QA (e.g. exploratory testing).  

    Jenkins is the tool that orchestrates all the SDLC steps from code commit to binary delivery. There are currently 1183 plugins for Jenkins with new one developed every week.   With today’s plugins, you
    have to create atomic jobs that then call each other, which ends up hard to visualize how the ensemble works, especially when you have a lot of different projects.

    Workflow was designed tIMG_5449o automate and scale pipeline steps and tools and solve common pipeline problems such as Parallelism, Branching, Looping, Restarts, Checkpoints, Manual Input, etc.   Jenkins Workflow is mostly open source with some advance features offered via enterprise edition by CloudBees.  Workflows can be defined in one concise script, with a groovy-based DSL and 15 simple keywords.

    Isaac took over to give the Workflow Demo.  He explained that stages will be the different steps of the pipeline. The workflow script doesn’t have to be written directly in the jenkins job, but as an external file in your source code repository. New DSL can be c
    reated to abstract the individual actions like source code checkout, build, test, etc. It will be possible to share this DSL in your jenkins and with the world, as well as download and use other people’s DSLs to leverage their code and avoid writing it yourself. Checkpoints can be combined with notification methods like email to get the input directly from the notified person. The multibranch Workflow system will support branching, any new branch in git will create a new workflow in Jenkins.  Jenkins will scan all the GitHub repositories and add all the projects with Jenkins files automatically, as well as scan new projects and add them automatically in Jenkins.

    IMG_5450At the end of the session,  Kishore and Isaac gave us a glimpse of Jenkins 2.0 release which includes focus on Continuous Delivery use cases and UI/UX improvements.

    If you would like to learn more about Jenkins Workflow, you can reach Kishore at kbhatia@cloudbees.com  or Isaac  at icohen@cloudbees.com .   For more information about CI/CD transformation you can reach me at tanya.kravtsov@rokittech.com

    At the end we had a great Q&A session and a very warm open discussion.   Looking forward to our next session.

  • DevOps Connect: cdSummit SoCal

    DevOps Connect: cdSummit SoCal

    I know we have mentioned it before but we haven’t officially announced our DevOps Connect: cdSummit SoCal event on December 3rd in Los Angeles.  The event co-produced with CloudBees, the enterprise Jenkins company, IBM and devopsy.kinsta.cloud will take place from 9am to 6pm at:

    The Olympic Collection Banquet & Conference Center
    11301 W. Olympic Blvd., #204
    Los Angeles, CA 90064

    We have a great line up of speakers and sessions for this event and I wanted to share 4 of them with you today:

    JohnWillis11st Keynote/Headliner: John Willis, evangelist at Docker – That’s right, the one and only @botchagalupe will be kicking things off. If you have been lucky enough to catch John present before you know that he never disappoints.  Partly because his experience and knowledge give him superior insight into the issues and problems that IT teams face today, but also because he is so passionate about what he presents on.  John will be presenting:

    Kata

    Mike Rother in his book Toyota Kata implied there was an invisible side to why Toyota was so successful over the years.  As we we have explored the transitions from Lean to Agile and now to Devops we often fight the visible versus the invisible in accomplishing our goals.  This presentation will take a look at what Kata meant at Toyota, Alcola over the years and bring it full forward with companies line Netflix and Etsy.

    andypem2nd Keynote: Andy Pemberton, Sr. Director, Solution Architecture at CloudBees. I have seen Andy present several times now and he does a great job of showing how the technology we are using everyday in our lives is being pushed, pulled, stretched and shaped by DevOps, Continuous Delivery and Agile. Andy will be presenting:

    Orchestrating the Continuous Delivery Process

    Continuous delivery is an end-to-end process and orchestration is the engine that drives continuous delivery. Automating the continuous delivery pipeline starts with understanding the process and of the entire toolchain. It sounds daunting, but it can be approached in stages to keep up with the demands for application delivery speed.

    522972Boyd Hemphill, Director of Evangelism, StackEngine. Boyd is one of the great Austin DevOps folks. He runs the Austin DevOps Meet up Group, helps with Austin DevOps Days, Container Days and so much more. Like John Willis and Andy Pemberton, I have seen Boyd present a few times and he also just really brings a great talk. Boyd presented on “HomeOps, lessons he learned about DevOps while doing work at home.  It is funny, insightful and a really great presentation.

    HomeOps – Learning DevOps At Home

    DevOps is great. You can see the benefits. All the success stories have you champing at the bit to become your very own Unicorn. Oh, but you are smarter than that. You know that every one of those success stories comes with many, often hidden, trials and tribulations.

    HomeOps is the way I have become familiar with many of DevOps models such continuous delivery, lean thinking and cultural impact. Bringing these models to work with the ability to anticipate problems helped me save nearly $1.0m in costs while opening $1.8m in revenue.

    Come gain some of the missing insight to your continuous delivery journey.

    bobBob Reselman – Publisher and Managing Writer: The World in Which We Live. Bob is half of the ROELBOB team that has been creating some of the funny cartoons here on devopsy.kinsta.cloud. Bob also has many, many (did I say many?) years of tech experience under his belt which gives him the perspective he needs in his role at The World in Which We Live. Bob will be presenting:

    Making a Linux Container: My pain and agony in grueling detail

    Allow me to share an intimacy: I an experienced technology writer. Also, I am a container newbie. But, I understand that containers are an important step forward in computer virtualization. Knowing the stuff is a whole lot better than not knowing it.

    So I took the plunge and decided to get down and dirty by building a containerized microservice.

    I do have a method. I am a learn by doing guy. First I get the concepts down, then I get hands-on and write about it as I go. I assumed there must be a lot of Hello World type stuff out there to get me up to speed with the basics. Then, I could take things a bit further and build my microservice container on what I learned in the Hello Worlds.

    I mean, it can’t be that hard, right?

    Wrong!

    It turns out that making my first container was a journey into pain and agony. No human should have to go through such an ordeal. So I am going to share my story with you in grueling detail so that you don’t have to experience such torture… ever.

    We have another 5 or 6 sessions/speakers that we are finalizing right now and will announce next week.  However, there are still one or two slots open and if you are interested in presenting you can write me at editor@devops.com with contact info and we will contact you.

    Besides the great sessions and speakers, we will be featuring demos of Jenkins, CloudBees, IBM BlueMix and more. Also lunch, refreshments and more will be served.  There is plenty of free time built in for networking as well including caricatures by the ROELBOB team and more surprises in store. We will also be announcing additional sponsors in the coming days.

    So if you are in the Southern California area and into DevOps, CD, Jenkins, BlueMix or want to learn more, this is a can’t miss event. You can get more info here. You can register for the event (there is a $99 charge for the day) on Eventbrite.

    We hope to see you in Southern California on December 3rd.

  • DevOps Connect: cdSummit at Austin Innotech

    DevOps Connect: cdSummit at Austin Innotech

    Last week I was down in Austin, Texas for the DevOps Connect: cdSummit @Innotech show. With almost 1900 people registered for Innotech, we had a solid 150 folks specifically for cdSummit.  I think it fair to say that the attendees got their money’s worth!

    The morning started off with a great presentation by Jez Humble.  If you are talking CD, who better than the guy who literally wrote the book to kick things off.  Jez never disappoints and he didn’t last week.  His presentation is below.

    After Jez, Andy Pemberton of CloudBees presented.  Andy has a great delivery and I have seen him present before. It was a great engaging presentation and it is below for you to view.

    Following Andy we were very lucky to have David Lindquist, IBM Fellow, VP of Development, Mobile and Cloud DevOps. David gave us some great insight into IBM’s own journey of using DevOps to make an enterprise work at startup speed. Again his slides are below.

    We then broke for a great, relaxing lunch break and to give our attendees a chance to explore Innotech. There was a demo theater on the show floor featuring Jenkins, BlueMix, New Relic and AppDynamics demos. Innotech also featured a “Women in Tech” show and CIO roundtable with some great content.

    After lunch we broke into two rooms in a dueling track format. We have enclosed those below. My favorites were from the great, welcoming and amazing Austin DevOps community. Ernest Mueller previewed the talk he is giving at DOES next week.  James Wickett, one of my heroes from the Rugged DevOps movement did a great job on his session and Boyd Hemphill brought the house down closing out with his HomeOps presentation which I found witty and incredible.

    All of the speakers were really good and the feedback from the attendees echoed this.  Many thanks to our sponsors, CloudBees and IBM as presenting sponsors, AppDynamics and New Relic as gold sponsors. Most of all thanks to all of the people who came out and spent a great day with us! We are holding the next cdSummit on December 3rd in Los Angeles and if you are interested in speaking, attending or sponsoring, contact me at editor@devops.com.  We will announce more details shortly.

     

     

  • Come to DevOps Connect: CD Summit in Austin, October 8th with Jez Humble

    Here at devopsy.kinsta.cloud we are very happy to announce that we are teaming up with Prospera Events (producers of the InnoTech Conferences), CloudBees, the enterprise Jenkins company and IBM to bring a DevOps Connect: CD Summit to Austin, Texas on October 8, 2015. The event will be held at the Austin Convention Center as part of the InnoTech Austin Conference.  Full details can be found here.

    jezThe event will be headlined by renowned author and Continuous Delivery/DevOps expert Jez Humble. Jez will speak about architecting CD. Additional keynotes will be by Andy Pemberton of CloudBees and IBM. Additional topics will be covered in two separate tracks, one technical and one business related. Additional speakers in the tracks include DevOps pioneer Ernest Mueller, of the Agile Admin and Boyd Hemphill who will speak on “HomeOps”.

    In addition to lunch and an after conference reception, CD Summit attendees will join with and have full access to the InnoTech Conference taking place at the same time. An expo floor of exhibitors will include a demo theater to showcase some of the leading apps and technologies in DevOps. Among these IBM will demonstrate Bluemix, its market leading cloud application development platform.

    Attendance for DevOps Connect: CD Summit requires a separate $99 admission which includes InnoTech admission too. There are sponsorships available as well. More information is available on the DevOpsConnect site.

    Besides the Austin event, additional CD Summit events are scheduled for December 3rd in Los Angeles and later in December in Boston. Further details on these events will be announced shortly.

  • 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.