Deploy an application by using Bluemix Continuous Delivery toolchains

In this lab, you’ll get started creating a toolchain automatically from an existing GitHub repository. This repository has a Deploy to Bluemix button that automatically creates a continuous delivery toolchain, forks a copy of the application to your own code repository, and runs the delivery pipeline in the toolchain to deploy the application.

  1. Open the sample application GitHub repository at
  2. Scroll down to the README and click Deploy to Bluemix.

    The toolchain creation page for your new application is shown. On this page, the tool integrations are shown. The Delivery Pipeline tool is selected, and you can update the proposed name based on the original repository. Customize this if you want to as you did with the starter application. You can also customize the deployment region, organization, and space for the app or accept the defaults.

  3. Select the icon for Git Repos and Issue Tracking. You see a page where you can customize the repository settings for the copy of your application source code. You can leave the default values. This repository is hosted on Bluemix using GitLab Community Edition.
  4. Click Deploy. A confirmation message and the toolchain overview is displayed. Bluemix is running the deployment now.
  5. Click the Delivery Pipeline icon to monitor the deployment status. When it finishes, the Deploy stage will show a successful execution.
  6. Click the link for the app to open it in a new tab. This application is a document and image organizer that uses a Cloudant NoSQL database to store files that are uploaded from a web browser.
  7. The app has been created with a long and random host name. This was chosen based on a property in the manifest.ymlfile. To change this, navigate back to the application dashboard. Go back to the browser tab with the Bluemix dashboard and refresh the page if your new app is not showing. Then, click on the row for the app to open the app dashboard.
  8. Click Routes and select Edit routes.
  9. Customize the name. For example, call it secondapp or favapp with your initials and date added to the name to make it unique. Click Save, and when you’re prompted to remove the old route for the app, confirm that removal.

    The app will take a moment to restart. You can confirm that the new URL is active by clicking the new name from the Routes drop-down menu.

  10. Test the app by uploading some pictures. Note that you’ll remove this app and the Cloudant database so that you can create them again by using the Bluemix CLI in the next lab.
  11. As in the first lab, when you’re finished experimenting with the app, delete it by clicking the three vertical dots next to the app STOP button and selecting Delete. Confirm the removal of the database from the Services tab and the hostname from the Routes tab.