Feature/bonsai asset

[jspaleta]

Pull Request Checklist

General

• [X] Update Changelog following the conventions laid out here

• [X] Update README with any necessary configuration snippets

• [ ] Binstubs are created if needed

• [X] RuboCop passes

• [X] Existing tests pass

Purpose

Build Sensu assets using sensu-ruby-runtime as part of travisCI release tagging.

Additional Changes

update gemspec to use latest sensu-plugin update gemspec and travis to drop old ruby no longer supported in travisCI.

[jspaleta]

Note 1: I'm expecting the before_deploy command to change again slightly, I have a pending PR against the helper repository. Once that is merged I can change the before_deploy to pull master branch, or specific commit instead of the feature branch.

Note 2: I'm using travis encrypt to save a personal oauth GITHUB_TOKEN used to upload binaries into the github release as part of the asset deploy script, This token might need to change if there is a sensu-plugins org-wide preferred token to use here.

[jspaleta]

Okay I think this is good to go.

Note the new bonsai badge committed as part of the README won't work until after this PR is merged and a new release is tagged. I'll need to manually add this plugin into Bonsai after this PR is merged and a new release tagged.

[jspaleta]

For an example of what the hew travis config does, you can look at my fork. I've built a 4.0.2-pre tag as part of my repository fork firing off the new asset build and release logic.

[sensu-discourse]

This pull request has been mentioned on Sensu Community. There might be relevant details there:

https://discourse.sensu.io/t/how-to-use-the-sensu-plugins-kubernetes-plugin/1286/2