deployment.sh

#!/bin/bash
set -e

## This script is used to test the BASH script commands
## of a Jenkins Job using the Cloud Foundry CLI.
## This script is based on previous version written by Matt Stine and Jamie O'Meara
## Author - Sufyaan Kazi - Pivotal

usage ()
{
  echo 'Usage : Script <user> <password> <org> <space>'
  echo '               <domain> <app_prefix> <build_version>'
  echo '               <serviceName> <memory> <path_to_app> <instances>'
  echo ' e.g. ./deployment.sh -u suf -pw ******** -o suf-org -s dev -d emea.fe.pivotal.io -ap cities-ui -sn citiesService -m 512m -p artifacts/cities-ui.jar i 1 -v 9'
  exit
}

echo $CF_USER $CF_PASSWORD

if [ -z $APP_PATH ]
then
  echo "!!!!!! Please supply the path to the app to be deployed !!!!!!!!!!!!!!"
  exit 1
fi

echo_msg () {
  echo ""
  echo ""
  echo "************* ${1} *************"
  echo ""

  return 0
}

## Variables used during Jenkins Build Process
APP_NAME=$APP_PREFIX-$BUILD_VERSION
HOST_NAME=$APP_PREFIX-$CF_USER-$BUILD_VERSION

## Log into PCF endpoint - Provided via Jenkins Plugin
echo_msg "Logging into Cloud Foundry"
## wget http://go-cli.s3-website-us-east-1.amazonaws.com/releases/latest/cf-linux-amd64.tgz
## tar -zxvf cf-linux-amd64.tgz
cf --version
cf login -u $CF_USER -p $CF_PASSWORD -o $CF_ORG -s $CF_SPACE -a https://api.$CF_DOMAIN --skip-ssl-validation

# ^^^^^^^^^^^^^^^^^^^^ Commands for Jenkins Script ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

## These steps complete the following, they are the only required steps for the Jenkins Job
##
##   1. Determine the name of the deployed app. The naming convention for this
##      app is map-build-BUILD_NUMBER, ex map-build-45. We assume only 1 previous build
##      exist but this script can be modified to support multiple previous builds.
##
##   2. If an app is found by querying the list of deployed apps then unmap a
##      convenient url, ex map-dev.cfapps.io, and delete the existing app. In this 
##      situation we are ok with downtime as we deploy the new app in development.
##   
##   Note: route name must be unique in a foundation. If you use Pivotal Web Services
##         you need to make sure your convenient URL is unique.
##   
##   3. Push the next released version, bind an existing Rabbit service to the app, map
##      the convenient URL to the new instance and start the app.
##
##   4. Log out
##

DEPLOYED_APP_NAME=$(cf apps | grep $APP_PREFIX | tail -n 1 | cut -d" " -f1)
#DEPLOYED_APP_NAME=$(cf apps | grep $APP_PREFIX | sed '2!d' | cut -d" " -f1)
if [ -n "$DEPLOYED_APP_NAME" ]; then
 echo_msg "Deleting previous microservice version: $DEPLOYED_APP_NAME"
 cf unmap-route $DEPLOYED_APP_NAME $CF_DOMAIN -n $APP_PREFIX-$CF_USER
 cf delete $DEPLOYED_APP_NAME -r -f 
fi

echo_msg "Pushing new Microservice"
cf push $APP_NAME -p $APP_PATH -m $MEMORY -n $HOST_NAME -i 1 -t 180 --no-start
if [ ! -z "$SERVICE_NAME" ]
  then
    cf bind-service $APP_NAME $SERVICE_NAME 
fi
cf map-route $APP_NAME $CF_DOMAIN -n $APP_PREFIX-$CF_USER

echo_msg "Starting Container & Microservice"
cf start $APP_NAME
if [ ! -z "$INSTANCES" ]
  then
    cf scale $APP_NAME -i $INSTANCES
fi
cf logout