0.01
No commit activity in last 3 years
No release in over 3 years
Capistrano recipe for checking CI build status
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
 Dependencies

Development

~> 1.3
>= 0
= 2.14.1
~> 0.7.1
~> 2.6.0
~> 1.14.0

Runtime

>= 2.5.5
 Project Readme

Capistrano::Ci

Build Status

Introduction

capistrano-ci is extension for capistrano that allows you to check status of your repository before deployment. Currently it supports:

Installation

Add this line to your application's Gemfile:

gem 'capistrano-ci'

And then execute:

$ bundle

Or install it yourself as:

$ gem install capistrano-ci

Add to your Capfile:

require 'capistrano/ci/recipes'

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:

 set :ci_client, "travis"
 set :ci_repository, "organisation-or-user/repository-name"

Pro Account of Travis-CI:

Additional to ci_client and ci_repository setup ci_access_token:

 set :ci_client, "travis_pro"
 set :ci_repository, "organisation-or-user/repository-name"
 set :ci_access_token, "your-pro-access-token"

Read explaination how to obtain Travis-CI access token. To have more information about Travis-CI access token follow this blog post.

CircleCi:

Setup ci_client, ci_repository and ci_access_token in your deployment script:

 set :ci_client, "circle"
 set :ci_repository, "organisation-or-user/repository-name"
 set :ci_access_token, "your-circle-access-token"

Semaphore:

Setup ci_client, ci_repository and ci_access_token in your deployment script:

set :ci_client, "semaphore"
set :ci_repository, "organisation-or-user/repository-name"
set :ci_access_token, "your-semaphore-access-token"

Enable ci:verify task:

 before 'deploy', 'ci:verify'

 # or in case of using capistrano-patch:
 before 'patch:create', 'ci:verify'

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Copyright

Copyright (c) 2013 Railsware LLC. See LICENSE.txt for further details.