public
Description: Bob the Builder will build your codes
Homepage: http://integrityapp.com
Clone URL: git://github.com/foca/bob.git
foca (author)
Thu Aug 06 21:48:04 -0700 2009
commit  7084931cb3ac74914c001c2315a5e6a46331fab8
tree    44d44171aeb62e13d2209b693a6b92d9664a5695
parent  fb9bb2756a0e244d33f394608f2cb25ee02e1934 parent  31c78331d0ff5a30ec6ce96e6312ea0e3d44bd96
bob /
name age message
file .gitignore Sun Apr 12 11:56:53 -0700 2009 Gemspec [foca]
file LICENSE Sun Apr 12 12:24:44 -0700 2009 Make the comments more rdoc friendly [foca]
file README.rdoc Fri May 08 13:09:50 -0700 2009 Add a buildable mixin [foca]
file Rakefile Thu Aug 06 21:48:04 -0700 2009 Merge branch 'ninja' [foca]
file bob.gemspec Thu Aug 06 21:48:04 -0700 2009 Merge branch 'ninja' [foca]
directory lib/ Thu Aug 06 21:48:04 -0700 2009 Merge branch 'ninja' [foca]
directory test/ Thu Aug 06 21:48:04 -0700 2009 Merge branch 'ninja' [foca]
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, ...])
  1. Checkout the buildable on the specified commit
  2. Call Buildable#start_building
  3. Run the script provided in Buildable#build_script in the buildable.
  4. 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)