No commit activity in last 3 years
No release in over 3 years
Mark the phase of unfuddle tickets in staging and production during deployments
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 0
>= 0
>= 0

Runtime

>= 3.0.1
>= 0
 Project Readme

Slackistrano

Gem Version Code Climate Build Status

Mark the phase of the tickets during releases to staging and production deployments

Requirements

  • Capistrano >= 3.1.0
  • Ruby >= 2.0
  • A Slack account

Installation

Add this line to your application's Gemfile:

gem 'release-tickets', require: false

And then execute:

$ bundle

Configuration

Require the library in your application's Capfile:

require 'slackistrano'

Note that in your ENV you must define your unfuddle account and password, like this:

export UNFUDDLE_USER=fred export UNFUDDLE_PASSWORD=super-duper-secret

This account must have privileges to mark the tickets.

Test your setup by running:

$ cap production release_conductor:deploy:finished

Usage

Deploy your application like normal and the tickets should be marked.

TODO

To publish a new version: (0.0.5 in this example)

  1. fix the bug
  2. update version.rb
  3. git commit -a -m "0.0.5 "
  4. git tag 0.0.5
  5. git push --tags
  6. gem build release-conductor.gemspec
  7. gem push release-conductor-0.0.5.gem

To upgrade CODE to use the new version of the gem

  1. git checkout code-dev
  2. bundle update release-conductor
  3. git commit -a -m "@wip upgrading release-conductor gem"
  4. git woe minor (OR, merge the new Gemfile.lock into all the branches that need it)

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