Using Travis CI for Deploying Mulesoft Applications to Cloudhub

What Is Travis CI?

  • Travis CI is a hosted continuous integration service used to build and test software projects hosted at GitHub and Bitbucket. Travis CI provides various paid plans for private projects and a free plan for open source.
  • Travis CI is available at https://travis-ci.org/.
  • https://travis-ci.org/ supports only public repositories. To support GitHub private repositories, you can use https://travis-ci.com/.

Prerequisites

To start using Travis CI, make sure you have:

To get started with Travis CI using GitHub, follow these steps:

  1. Go to Travis-ci.com and Sign up with GitHub.
  2. Accept the Authorization of Travis CI. You’ll be redirected to GitHub.
  3. Click on your profile picture in the top right of your Travis Dashboard, click Settings and then on the Left-hand side, Sync Account button. This will sync all your repositories in the GitHub with Travis CI.
  4. Add a .travis.yml file to the root of your repository to tell Travis CI what to do. Below is the example of a travis.yml file that I used to build the integration:

language: java
jdk:
– openjdk8
cache:
directories:
– “$HOME/.m2”

before_install:
– cp .travis.settings.xml $HOME/.m2/settings.xml

jobs:

– stage: Start
name: “Application is ready”
script:
– echo “$applicationName is ready to be installed”
– stage: Test
name: “Run Tests”
script:
– mvn clean package

– stage: Deploy #stage type
name: “Deploy stage” #stage name
script:
– mvn deploy -DmuleDeploy -Danypoint.username=$username -Danypoint.password=$password -Danypoint.environment=$environment -Danypoint.workerType=$workerType -Danypoint.businessGroup=$businessGroup -Danypoint.workers=$workers appName=$applicationName -Danypoint.objectStore=$objectStore

notifications:
email:
recipients:
– kuldeep.rana@gmail.com
on_success: always
on_failure: always

  1. Add .travis.setting.xml to the root of your repository. This will have the url to all the repositories from where all the dependencies will get downloaded to build the project. Below is the example of the file used in the integration :




anypoint-exchange-v2
${username}${password}

org.mule.toolsmule-extra-repos

true



mule-public
https://repository.mulesoft.org/nexus/content/repositories/public

mule-public
https://repository.mulesoft.org/nexus/content/repositories/public
Mule

true



MuleRepository
MuleRepository
https://repository.mulesoft.org/nexus-ee/content/repositories/releases-ee/
default

true


true


Now, for deploying Mulesoft application to Cloudhub, you need to configure mule maven plugin in POM.xml:


https://anypoint.mulesoft.com
${app.runtime}
${anypoint.username}${anypoint.password}${anypoint.environment}
${anypoint.appName}
${anypoint.workerType}
${anypoint.workers}
${anypoint.businessGroup}
${anypoint.objectStore}value

Declaring Environment Variables at Travis CI

For declaring the variable, you can activate the repository and click on settings. It will navigate to the build screen. Now click on More Options ⇒ Settings. Scroll down and it will show you the Environment Variables tab to declare your variables.

For the above code, all environment variables have been declared — required by Mule maven plugin like workers, workerType, Application Name, etc. and username and password required by .travis.settings.xml

Environment Variable screenshot.

Once all the changes are pushed to the git, and Travis CI is activated for that repository, the Continuous Integration, and Continuous Deployment process will take place. You can check the logs for further details.

Logs screenshot.

The application is successfully applied to Cloudhub.

Successful message screenshot.

Reference Links

.

Leave a Comment