ci_receipe_1

Capistrano recipe for your favourite CI

| 0 Comments

The quality of features going to production is very important; and to guarantee the highest quality we use Continuous Integration in our everyday workflow. In one of his recent posts Sergii Boiko has described how to check Travis CI build status before delivering new code to production. Afterwards, we’ve also decided to extract this recipe to capistrano-ci gem and this article will explain how to setup this gem in your deployment process.

Supported continuous integration services:

Installation

Add the following line to your application’s Gemfile:

And then execute:

Or install it yourself as:

Add to your Capfile:

Configuration

Variables list:

  • :ci_client (required) – supports travis, travis_pro, circle, or semaphore
  • :ci_repository (required) – organization or user name and repository name on github
  • :ci_access_token(required for travis_pro, circle, or semaphore) – access token specific to the service

Open Source Projects

Setup ci_client and ci_repository variables in your deployment script:

Pro Account of Travis-CI:

Additional to ci_client and ci_repository setup ci_access_token:

To have more information about Travis-CI access token, you can follow this blog post.

CircleCi:

Setup ci_client, ci_repository and ci_access_token in your deployment script:

Semaphore:

Setup ci_client, ci_repository and ci_access_token in your deployment script:

Enable ci:verify task:

Summary

That’s it, and in case your CI system isn’t supported by our gem, ask us to add it or make pull-requests by yourself!

Share
* Railsware is a premium software development consulting company, focused on delivering great web and mobile applications. Learn more about us.

Want to get more of Railsware blog?

RSS FEED

We're always ready to help!

CONTACT US