git-release-tagger 0.0.2

Small CLI utility to enable the CI environment to communicate the deployment progress through the use of git tags.

Small CLI utility to enable the CI environment to communicate the deployment progress through the use of git tags.

Installation

$ pip install git-release-tagger

Usage

$ tag-release [-h] [-t TRIGGER] [-v] [-m MESSAGE]
               prefix {pending,deploying,failed,success}

Prefix is self explanatory.

If the release was triggered by a tag (like ‘release’) - use the –trigger option to have the tagger remove it automatically. This enables the user to retry a failed deployment just by tagging the same commit again.

Use -m to add a message to the commit. For example - a link to the build status on Jenkins / TeamCity / other CI.

Examples

$ tag-release production pending

will remove tags:

• ‘production_pending’,

• ‘production_deploying’,

• ‘production_failed’,

• ‘production_success’

will add tags:

• ‘production_pending’

$ tag-release production success

will remove tags:

• ‘production_pending’,

• ‘production_deploying’,

• ‘production_failed’,

• ‘production_success’

will add tags:

• ‘production_success’

• ‘production_success_2015-11-02_16_34_26’

$ tag-release -t production production success

will remove tags:

• ‘production’

• ‘production_pending’,

• ‘production_deploying’,

• ‘production_failed’,

• ‘production_success’

will add tags:

• ‘production_success’

• ‘production_success_2015-11-02_16_34_26’

Release History

0.0.2 (2016-03-09)

• ‘git push’ is run with –no-verify to skip pre-push hooks.

0.0.1 (2015-11-03)

• Initial release.