"CloudHub" Continuous Integration



In this post, we will learn more on the process of Mule deployment automation on to CloudHub. We will be using maven plugin named “cloudhub-maven-plugin”, to achieve the desired result. One may add this as a post build action, so that after every successful build the Mule application automatically gets deployed to the CloudHub and thereby maintain the desired environment(s) with latest code. Continuous integration facilities like Bamboo and Jenkins support maven deployments.


The reader of this article is assumed to possess some basic knowledge of Maven.

Detailed Steps

1. Add the following plugin to the project’s pom.xml:

<muleVersion>${MULE VERSION}</muleVersion>
<!--Please note that the domain need not contain cloudhub.io.
So, if the domain is myapp.cloudhub.io, mention it as myapp-->
<domain>${YOUR DOMAIN}</domain>


2. Add the following under project properties:

<!--Please note that the user name is actually a combination of
username and environment separated by @, eg. myuser@sandbox-->


3. Usage:

$mvn cloudhub:deploy


$mvn cloudhub:deploy -Dcloudhub.username=username
-Dcloudhub.password=password -Dcloudhub.domain=testdomain
-Dapplication=/path/to/app.zip -Dcloudhub.muleVersion=3.6.0




If you would like to find out more about how APIs could help you make the most out of your current infrastructure while enabling you to open your digital horizons, do give us a call at +44 (0)203 475 7980 or email us at marketing@whishworks.com

Other useful links:

WHISHWORKS Systems Integration

API Recipes with MuleSoft Anypoint Platform

Case studies 

Recent Posts