Build And Release Pipeline

Currently we use Codeship for testing and Travis is used to run tests across all forks and deploying the gems.

When a Pull Request is submitted, Travis will automatically execute all default tasks defined in the Rakefile found in the repo root and display the results in the PR. When a committer wishes to deploy a new release the following procedure should be followed:

  1. ensure all tests pass (the deploy won’t happen if this fails)
  2. ensure the CHANGELOG.md is updated by the end user following the conventions laid out in Keep A Changelog
  3. ensure the version was bumpped in ../lib/plugin/version.rb by the user
  4. create a release in the gh gui or create a tag and push it. The tag should be the same as the new version.

All tag commits that pass tests in all supported runtimes will kick a deploy to Rubygems.

Sensu Plugins

The home for all Sensu Community plugins, handlers, and mutators. Open Source under MIT License.

Copyright © 2015-2016 Sensu-Plugins and contributors.

Sensu - sensuapp.org

Monitor servers, services, application health, and business KPIs. Get notified about failures before your users do. Collect and analyze custom metrics. Give your business the competitive advantage it deserves. Open Source under MIT License.


Join in on the fun!

We welcome contributions and usually accept pull requests within a week! Pick any of our 150+ plugins and hack away!

https://github.com/sensu-plugins
https://github.com/sensu

Follow @sensu-plugins
Watch Star