Project

ci-killer

0.0
No commit activity in last 3 years
No release in over 3 years
ci-killerjeroenj/ci-killerHomepageDocumentationSource CodeBug TrackerWiki
Kills CI nodes if they have been running for too long.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
4,463
Stars
0
Forks
1
Watchers
3
 Releases
Current version
0.1.1
Total releases
2
First release
2017-07-14
Latest release
2017-10-02
 Issues
Open Issues
2
Closed Issues
0
Total Issues
2
Issue Closure Rate
0%
 Pull Requests
Open Pull Requests
0
Closed Pull Requests
0
Merged Pull Requests
1
Pull Request Acceptance Rate
100%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2017-08-30
Reverse Dependencies
0

 Dependencies

Development

bundler
~> 1.15
pry
>= 0
rake
~> 10

Runtime

droplet_kit
~> 2.2
thor
~> 0.20
 Project Readme

Ci::Killer

This kills CI instances if they have been running for too long. Currently only Digital Ocean instances are supported.

Installation

$ gem install ci-killer

Usage

Digital Ocean

You'll need to set your access token as an environment variable:

DIGITAL_OCEAN_ACCESS_TOKEN = "<token>"

Droplets that have been running for longer than the time passed in minutes will be deleted:

ci-killer digital_ocean 60

This will kill all instances that have been running for 60 minutes or more.

Development

After checking out the repo, run bin/setup to install dependencies. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bin/rake install. To release a new version, update the version number in version.rb, and then run bin/rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/jeroenj/ci-killer.

License

The gem is available as open source under the terms of the MIT License.