Continuous Integration (CI) is a hot topic right now. Companies have embraced the idea that automatically integrating software changes early and often is an effective approach to reduce cycle time, increase quality, and reduce end-to-end costs.
To identify where to introduce CI, it helps to understand how the need for CI changes as the complexity of your software delivery process grows.
It's quick and easy to specify which JDKs to build your code against! With the aid of the JDK tag, you can instruct your minion to not only use a specific JDK, but even have it create a build matrix using multiple JDKs! The JDK tag can be used in both the comprehensive minv2 image, and in the Java specific ubuntu1404_java and ubuntu1204_java images. For example, let's say you want to verify that your app builds on both openjdk and oracalejdk. This can be done with by using the following snippet in your shippable.yml file:
Looking to continuously deploy your Node.js app to digital ocean? Tired of manually trying to configure git hooks to work with you? Is SCP just a little too old fashioned and clunky. Great news! Your search is finally over as today we'll show you how to combine Shippable and Dokku to fit your deployment needs!
So, you already have Shippable setup for all your CI needs, and you're itching to take the plunge into CD? Maybe the thing that's been holding you back is you aren't sure how you can easily deploy to your dev, staging, and prod machines, without accidently pushing to production prematurely? The good news is Shippable can easily be setup to accommodate such a work flow! You can specify different deployment procedures based on your git branch.
Let's say you want to use want Shippable to perform a build for every commit, but you only want to do a deployment if it's a commit to the master branch. We keep track of what branch was pushed to via the BRANCH environment variable; This environment variable can be used to implement branch specific logic. Here is an example shippable.yml snippet:
- if [ "$BRANCH" == "master" ]; then git push -f email@example.com:$APP_NAME_PROD.git master; fi
This will push your app to Heroku, but will only do so for successful builds from the master branch. For those unfamiliar with using Shippable for continuous deployment to Heroku, please refer to our documentation.
This basic idea can be extended in many ways! For example, you could send commits from master to prod, and all other commits to dev:
Here at Shippable, we have a strong history of working well with AWS workflows. With the recent release of AWS Code deploy, we wanted to take some time to let you know how easily you can use Shippable and Code Deploy together in your continuous deployment workflow!
First off, there are some prerequisites before your Shippable minions can trigger Code Deploy. On your AWS account, you must have the following setup: