Skip to content
This repository

A simple guard script to place a failure image or success image after a build has finished in a consistent location for jenkins jobs.

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 lib
Octocat-spinner-32 spec
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .rvmrc
Octocat-spinner-32 Changelog.yml
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Rakefile
Octocat-spinner-32 Readme.markdown
Octocat-spinner-32 guard-jenkins.gemspec
Readme.markdown

Guard-Jenkins

Thanks for checking out Jenkins Guard!

Guard-Jenkins checks for the modification of the nextBuildNumber file in a job's directory and then creates a symlink from either fail.png or success.png to $JENKINS_HOME/userContent/jobs/JOB_NAME/current_status.png

A RoadMap can be found on the Wiki.

And a brief introduction can be found on the project's Homepage

Usage:

  # rb-inotify allows guard to learn of fs events in much more
  # performant way than simple polling
  gem install rb-inotify guard-jenkins

  # in either ~/ or $JENKINS_HOME
  guard init jenkins
  guard [start]

Contributing:

Everyone should pitch in!

If you want to do development on this project you will need:

Rspec ~> 2.6

SimpleCov ~> 0.4

Submit an Issue:

Please file complete bug reports when filing issues That includes your complete environment, exactly what you were doing when it occurred, and for good measure your zodiac sign, hair color, and favorite color.

Even better! If you could provide a link to a Gist or patch with tests that quickly shows how to replicate the issue, that would be perfect

Add a Feature:

Fork the project. Add tests in a similar style to those that already exist (hrm...) Add the feature Issue a pull request!

Write Documentation/Show Examples:

Got an amazing jenkins configuration you've buit with this? Add it to the wiki!

Something went wrong with that request. Please try again.