This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
bob /
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Sun Apr 12 11:56:53 -0700 2009 | |
| |
LICENSE | Sun Apr 12 12:24:44 -0700 2009 | |
| |
README.rdoc | Fri May 08 13:09:50 -0700 2009 | |
| |
Rakefile | ||
| |
bob.gemspec | ||
| |
deps.rip | Thu Oct 01 10:05:18 -0700 2009 | |
| |
hack.rip | ||
| |
lib/ | ||
| |
test/ |
README.rdoc
Bob the Builder
Given a Buildable object with a determined API (described in it’s documentation), Bob will, when called like:
Bob.build(buildable, commit_id) # or Bob.build(buildable, [commit_id, commit_id, ...])
or from your buildable (if you are using the Bob::Buildable mixin provided) as:
buildable.build(commit_id) # or buildable.build([commit_id, commit_id, ...])
- Checkout the buildable on the specified commit
- Call Buildable#start_building
- Run the script provided in Buildable#build_script in the buildable.
- When the build process finishes, it will call Buildable#finish_building with the commit_id, the build status (true if the script returns a status code of 0, false otherwise), and a string with the build output (both STDOUT and STDERR).
If you pass an array of commits, the steps 1-4 will be repeated for each commit provided, in order.
Do I need this?
Probably not. Check out integrity for a full fledged automated CI server, which is what most people need.
Credits
| Authors: | Nicolas Sanguinetti (foca) and Simon Rozet (sr) |
| License: | MIT (Check LICENSE for details) |








