Skip to main content Skip to Footer


December 20, 2016
ADOP with Pivotal Cloud Foundry
By: Mark Rendell

As I have written in a previous blog, the DevOps Platform (aka ADOP) is an integration of open source tools that is designed to provide the tooling capability required for Continuous Delivery.

In this blog I will describe integrating ADOP and the Cloud Foundry public PaaS from Pivotal. Tweet. This opens a new window.

While it is, of course, technically possible to run all of the tools found in ADOP on Cloud Foundry, that wasn’t our intention. Instead we wanted to combine the Continuous Delivery pipeline capabilities of ADOP with the industrial grade cloud-first environments that Cloud Foundry offers.

Many ADOP cartridges, for example, the Java Petclinic one, contain two Continuous Delivery pipelines:

  • The first, to build and test the infrastructure code and build the Platform Application.

  • The second, to build and test the application code and deploy it to an environment built on the Platform Application..

The beauty of using a public PaaS like Pivotal Cloud Foundry is that your platforms and environments are taken care of, leaving you much more time to focus on the application code. However, you do, of course, still need to create an account and provision your environments.

  1. Register here.

  2. Click Pivotal Web Services.

  3. Create a free tier account.

  4. Create an organization.

  5. Create one or more spaces.

With this in place you are ready to:

  1. Spin up an ADOP instance.

  2. Store your Cloud Foundry credentials in Jenkins’ Secure Store.

  3. Load the Cloud Foundry Cartridge (instructions).

  4. Trigger the Continuous Delivery pipeline.

Having done all of this, the pipeline now does the following:

  1. Builds the code (which happens to be the JPetStore).

  2. Runs the Unit Test and performs Static Code Analysis using SonarQube.

  3. Deploys the code to an environment also known in Cloud Foundry as a Space.

  4. Performs functional testing using Selenium and some security testing using OWASP ZAPP.

  5. Performs some performance testing using Gatling.

  6. Kills the running application in environment and waits to verify that Cloud Foundry automatically restores it.

  7. Deploys the application to a multi-node Cloud Foundry environment.

  8. Kills one of the nodes in Cloud Foundry and validates that Cloud Foundry automatically avoids sending traffic to the killed node.

The beauty of ADOP is that all of this great Continuous Delivery automation is fully portable and can be loaded time and time again into any ADOP instance running on any cloud.

There is plenty more we could have done with the cartridge to really put the PaaS through its paces, such as generating load and watching auto-scaling in action. Everything is on Github, so pull requests will be warmly welcomed! If you’ve tried to follow along but got stuck at all, please reach me @markosrendell.

Popular Tags

    More blogs on this topic



        COMMENTS (0)




        Your Data Privacy

        By providing your e-mail address, you agree to the terms
        outlined in our privacy statement associated with
        commenting on the site. Your e-mail address will not be
        used for promotional marketing purposes.

        Change the CAPTCHA codeSpeak the CAPTCHA code