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 (
commit a4a0d824b015623108168022cf5711d91b7a9858
tree 42a6ad1febeec91f1d8c2d4ece163a40feb3099c
parent 4227e860a76a66a17932426abecb9de8a926bd69
tree 42a6ad1febeec91f1d8c2d4ece163a40feb3099c
parent 4227e860a76a66a17932426abecb9de8a926bd69
| name | age | message | |
|---|---|---|---|
| |
README | ||
| |
github-buildbot-commitbot.rb |
README
Github-BuildBot CommitBot ========================= This is a Merb "very-flat" application. You need to first do: $ gem install merb-core json In order to get Merb installed. Once that's done, you can fire up your new github-BuildBot CommitBot with: merb -I github-buildbot-commitbot.rb This listens on port 4000 by default but can be overriden. Then add a post-receive hook as: http://buildhost.example.com:4000/commit A Github (or other remote repo post-receive hook) triggers the script to update a local Git repo, submit the commits to the git_buildbot.py script which then processes the changes and submits them ot BuildBot. This assumes you have PBChangeSource enabled in your BuildBot configuration. Before you start sending things through it, I recommend you pop open the source and edit the variables at the top. Specifically: c[:project] = "Name of Project", c[:buildhost] = "BuildBot Hostname", c[:git_dir] = "path to local Git repo", c[:git_buildbot] = "path to Buildbot git_buildbot.py script", c[:tmp_commit_file] = "location of temporary file to hold commit data",








