Skip to content

CloudBees' Blog - Continuous Integration in the Cloud
Syndicate content
CloudBees is the only cloud company focused on servicing the complete develop-to-deploy lifecycle of Java web applications in the cloud – where customers do not have to worry about servers, virtual machines or IT staff. The CloudBees platform today includes DEV@cloud, a service that lets developers take their build and test environments to the cloud, and RUN@cloud, which lets teams seamlessly deploy these applications to production on the cloud.
Updated: 17 hours 54 min ago

Jenkins - The Man Behind The Curtain

Mon, 03/31/2014 - 20:11
While most of the cloud world was obsessed with price reductions coming from Google and Amazon last week, some of the more astute observers picked up on what is ultimately an even more important theme.

Right. Google seems to have understood very deeply that the key to upping the competitive game with Amazon and Microsoft in the public cloud is through developers. More than live migration and race-to-the-bottom pricing, they know that they can use their savvy as developers to differentiate the platform for developers. They use the phrase “meeting developers where they are,” and have committed big time to using Jenkins - as Google's Chris Smith put it - as the “man behind the curtain” to orchestrate continuous delivery from code to production.
1411 People Stared in Awe at the Mighty Power of the Jenkins Update Center During Google Cloud Platform Live
That phrase “meeting developers where they are” is kind of interesting, too, almost un-Google like. They’re not inventing a new Google-icious CI or build tool. They’re giving developers what they’re used to and are productive with - IntelliJ (aka Android Studio), Git, Jenkins, Maven and Gradle. They’re glueing those powerful tools together in a simple flow that fits seamlessly across their properties and Google Cloud Services, all leading toward deployment on Google Compute Engine and App Engine and Android devices.
That’s a pretty expansive vision, a fundamental change to the way developers build, test and deliver applications in the cloud world. A real platform play. It’s something we at CloudBees have been delivering on for a while now and that our customers have been depending on 24x7 to run their businesses. Here are a few of the important things we've learned in our journey to delivering the most advanced developer-centric Platform as a Service in the market:
  • Hybrid is reality, and will be for a long time. We love the cloud and run our business on it, but most businesses have existing investments (technical, capital and procedural) that are reality for them. Those businesses and the developers in them want to use the cloud, too. So, you need to live in both worlds and connect those worlds. For continuous delivery to be meaningful to the developers living in this hybrid world, you need to bridge them securely and painlessly, and that’s particularly true for people in the enterprise. That's why we've invested in things like RBAC, on-prem executors, VPN connectivity, and SAML support. Meeting developers where they are sometimes means you need to meet them in their own data center.
  • Continuous integration - and continuous delivery even more so - requires connections to all kinds of surrounding systems. This is one of the reasons Jenkins is so incredibly popular, because if you can’t do that using one of the 900 or so plugins in Jenkins today, you can build one yourself. Heck, that’s why Google is using it, too! Part of the “trick” of providing Jenkins as a hosted service is to do it in a way that exposes the flexibility and community-powered plugin set. The Update Center is the window into those plugins, so it's nice to see it being visible in Google's demo. Ultimately, all this relates to "running at scale" - supporting teams and the larger scale business processes that developers live within. Those developers will demand direct access and tweaks to the plugins and the ecosystems they unlock. Developing and deploying a web or mobile app is often just a part of a bigger chain of automation, which often spans reusable common libraries into post-deployment testing. Giving teams of developers the tools to collaborate and thrive within this kind of larger flow, continuously - that’s running at scale.
  • Community is key. The great thing about the Jenkins project is that Jenkins itself is built to encourage community, and it is operated to build community. Like any community, it has leaders and highly engaged participants. But, it also welcomes people who jump in and dabble, who do a quick project to solve a specific problem, or who extend the work of others. People participate because their investment pays back and often makes them feel good at the same time. So Google, my advice to you is to jump in. Don’t just keep the butler downstairs waiting for you to ring the bell for CI service. Come on down and have a beer with the rest of us. I guarantee you’ll be welcomed!

    This last week was a big one for cloud. The message should be crystal clear for competitors to the Google Cloud Platform. If you want to leapfrog Amazon (or Amazon: if you want to avoid being leapfrogged), you need to connect with developers. Those developers have long ago gotten used to instant access to on-demand infrastructure. Yawn... has the price dropped again? They want to consume a service, not build it if it’s not core to the problem they’re solving for the business. What’s more interesting to these developers and the people who employ them - and whose businesses depend on them - is how to create, update and deliver better software faster, continuously. The man behind the curtain to make that happen, to put the power of community and connectivity to work, turns out to be Jenkins.

    -- Steven G.

    Steven Harris is senior vice president of products at CloudBees. Follow Steve on Twitter.
    Categories: Companies

    Continuous Performance Testing in the Cloud (French)

    Thu, 03/27/2014 - 16:29
    Le Continuous Delivery est un des sujets brûlants de l’actualité. Pouvoir livrer une application en continu signifie que tous les processus de livraison ont été automatisés et que les développeurs et les opérationnels peuvent se concentrer sur des tâches à plus forte valeur ajoutée.

    Venez découvrir comment mettre en place des tests de performances en continu et un pipeline de Continuous Delivery avec les technologies Open Source Jenkins et JMeter grâce à la plateforme CloudBees et aux services BlazeMeter et NewRelic.

    Cette présentation utilisera comme fil conducteur l’application Spring PetClinic.

    Date : Lundi 31 mars 2014 19:30
    Durée : 1h30
    Lieu : Soat - 104, bis rue de Reuilly (voir la carte)Domaine : Java, Continuous Delivery, CloudNiveau : IntermédiaireSpeaker : Cyrille Le Clerc et Yohan BeschiEvenement gratuit
    Détails et inscription ici.

     A propos des speakers

    Cyrille Le Clerc Architecte Solutions chez CloudBees après 14 années dans les services et le conseil, Cyrille Le Clerc est passionné par le Cloud, la culture DevOps et le Continuous Delivery.
    La nuit, Cyrille est Committer sur le projet embedded-jmxtrans.

    Yohan BeschiDéveloppeur passionné, Yohan Beschi ne fait quasiment que du Java depuis 2002. Il s’est récemment penché sur le développement Dart, qu’il évangélise depuis.
    Il participe à la team d’expertise Soat dans le cadre de ses expériences dans le domaine du web et Java.
    Pour suivre ses contributions, cliquez ici.
    Categories: Companies

    Sacha Labourey on CloudBees Series C Funding

    Wed, 03/05/2014 - 16:03
           I’m proud to announce that CloudBees has just closed an $11.2 million Series C financing round. The round was led by Verizon Ventures, along with our current investors, Matrix Partners and Lightspeed Venture Partners, as well as angel and private investors.
    This news comes on the heels of CloudBees being positioned by Gartner in the “Visionaries” quadrant of the newly published Magic Quadrant for Enterprise aPaaS and our recent partnership announcement with Verizon Cloud. Needless to say this is a great time for CloudBees!
    2013 has been a very important year for CloudBees. Continuous Delivery is radically re-shaping the way enterprises deliver value to the business by accelerating the way applications are built and deployed. CloudBees holds a strategic position at the core of this phenomenon and has been going through tremendous growth, both on-premise and in the public cloud, thanks to our innovative Jenkins CI and PaaS-based solutions.

    I'd like to take this opportunity to share my pride for the amazing work that has been achieved by our team and congratulate them all: working in an environment where the overall good of the company comes before individual egos and performance is very powerful. And humbling.

    In 2014, we obviously aim to drive continued sales growth and product expansion, but we will also be announcing more partnerships aimed at bringing the power of Continuous Delivery to more developers, more solutions and more businesses around the globe.



    Sacha Labourey is the former CTO of JBoss, Inc. He was also co-general manager of middleware after the acquisition of JBoss by Red Hat. He ultimately left Red Hat in April 2009 and founded CloudBees in April 2010. 

    Follow Sacha on Twitter.
    Categories: Companies

    Meet the Bees: This Week, Meet Vivek Pandey

    Tue, 03/04/2014 - 19:27
    Vivek, enjoying the serenity of his home garden.At CloudBees, we have a lot of seriously talented developers. They work hard behind the scenes to keep the CloudBees Platform as a Service (PaaS) and our on-premise Jenkins solutions up-to-date with all the latest and greatest technologies, gizmos and overall stuff that makes it easy for you to develop amazing software.
    Vivek Pandey has fifteen years of experience working with key web technologies. Prior to CloudBees, he spent ten years at Sun Microsystems as the dynamic language lead for Glassfish, ensuring enterprise-grade deployment and scalability of languages and frameworks such as Ruby/Rails, Groovy/Grails, Python/Django, Scala or Lift on Glassfish.

    Vivek was a lead engineer in Sun's GlassFish team. At Sun he worked at various middleware projects related to web services technologies. Being an OSS fanatic, he was lead developer and committer on various open source projects. Vivek lives in the San Francisco Bay area with his wife, two daughters and a dog. Vivek is based in the CloudBees Los Altos office.
    You can follow Vivek on Twitter.
    Vivek, what is your role at CloudBees?

    At the top of Mission Peak, in California.I am an engineer and architect at CloudBees. I work on various platform pieces - GrandCentral, the services platform, security services, integration systems and services. I also lead partner engineering, which involves on-boarding partner services as integrated CloudBees services. I also get to work on Jenkins and DEV@cloud engineering and hack RUN@cloud whenever I get the chance.

    In my spare time, I like photography, hiking, movies, reading books and, of course, hacking - in reverse order. I am not much into workouts or outdoor activities except occasional hikes to Mission Peak or a trip to the movie theater. :)
    What are some of your best tips for developing or testing apps?

    Everyone's favorite butler!I start my development projects by first doing a high level spec to define various abstractions and their relationships. Then I continue further, breaking down each component. Most of the breaking down happens while writing code for high level abstractions. It lets me think in terms of how each software component interacts with other components. Often this cycle gets repeated to optimize my design. The thing is, once abstractions are defined well, the rest of the pieces fall into place easily. Also writing good and comprehensive tests is very important to avoid expensive regressions, but it's a challenge to balance delivering code with good code coverage and delivery timelines.

    Above all, continuous integration and continuous delivery are the key. Simply put - use Jenkins!
    What has been the best thing you have worked on since joining CloudBees?

    Recently I worked on new ways to represent collaborative distributed REST resources. We have named this work Cloud Resources. At CloudBees almost everything is defined as a REST resource or some kind of HTTP service accessible via API. These resources have the potential to integrate, interact and collaborate with each other in a secure way. Cloud Resource defines such contract where each of these resources expose themselves as publicly accessible HTTP URLs, define their capabilities, their types in a consistent and secured way. There is a central registry for all Cloud Resource providers, making them discoverable. We envision all of our APIs will be Cloud Resources and we are making them so they collaborate with other Cloud Resources running anywhere on the Internet.

    What is your favorite form of social media and why?

    None in particular. I am more a passive user of Twitter and some Facebook.
    If you could eat only one meal for the rest of your life, what would it be?

    Some hot and spicy dosa, waiting to be devoured by Vivek
    I love South Indian food, the most flavorful and spicy food you can find on the planet. :)  To be specific, if I had to pick one thing, it would be dosa.

    Categories: Companies

    CloudBees Buzzes on Verizon Cloud

    Wed, 02/19/2014 - 15:02
    We value the relationshipWe announced today the plan to make the CloudBees PaaS available on Verizon Cloud.  We’ve had a longstanding respect for the Verizon and Terremark businesses, back from the CloudSwitch and Terremark businesses when they were independent, and the strength of this Verizon Cloud offering.  We believe Verizon appreciated our relationship with the enterprise developer and brand, as well as our focus on accelerating the full application delivery lifecycle.  Continuous Delivery is a very current topic of discussion and CloudBees helps deliver that on a Verizon Cloud.
    Helping customers help themselvesLarge enterprises are service providers themselves to their departmental and divisional constituents or customers.  These business customers of Verizon Cloud will be able to rapidly build applications that their employees and own end customers need.  Mobile, web, social apps, the new applications that an enterprise needs - e.g., a sales applications for their field force that depend on existing back-end infrastructure, e-commerce applications that drive revenue, support applications that cut costs and help with customer care - all can get to market more quickly with the help of the CloudBees PaaS on Verizon.
    More choiceOur customers will benefit from a great service through a new partner.  Verizon Cloud has a great sales and support team and enterprise customer relationships that both overlap with and are incremental to our own.  Success with this joint effort is in making more customers happy with enterprise PaaS in the public cloud. 
    Accelerating application deliveryThe CloudBees PaaS speeds development and improves quality as there is a consistent experience across products from coding to building to testing to staging to production.  Enterprises also want a solutions benefit and a better way of doing things, like continuous delivery, not to be sold unstitched patches of disparate tools from various vendors.  While the CloudBees PaaS and Verizon Cloud are key anchor elements to this, we also rely on other technology partners to complete the cycle.  Still, offering that in an integrated and cohesive experience is important to our developer users and customers.
    More to comeThere’s still more work to do as the the Verizon Cloud is currently in beta.  We expect to offer CloudBees on Verizon Cloud in a reasonable timeframe after general availability.  CloudBees itself has been a generally available service since Jan 2011.  So, get to know us and then get to know us on Verizon Cloud.

    Andrew Lee is vice president, business development, at CloudBees
    Categories: Companies