Build And Release Pipeline

Currently we use 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. Update CHANGELOG to reflect all of the changes that has happened between last release and now. The Unreleased link in the CHANGELOG gives you a nice diff.
  2. make sure the README is updated as neccessary.
  3. Update the version using semver2
  4. make a git release. Example with hub: hub release create major.minor.patch
  5. Make sure the gem is actually uploaded to rubygems. It’s rare but I’ve seen times when it doesn’t upload for whatever reason.
  6. travis will only deploy if the build is passing so make sure master is building before cutting a release.

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