3 ms·
akr maintains the CI machine. It is running Lenny. You can see the output for the latest 1.9.2 build here: http://www.rubyist.net/~akr/chkbuild/debian/ruby-1
by tenderlove 16y ago
akr maintains the CI machine. It is running Lenny.
You can see the output for the latest 1.9.2 build here:
http://www.rubyist.net/~akr/chkbuild/debian/ruby-1.9.2/last.txt http://www.rubyist.net/~akr/chkbuild/debian/ruby-1.9.2/last....
All of the latest builds can be accessed here:
http://www.rubyist.net/~akr/chkbuild/debian/ http://www.rubyist.net/~akr/chkbuild/debian/
I would like to see more CI machines get deployed, but I think there are a couple challenges:
1) We use custom CI software (and the docs are in Japanese): http://github.com/yugui/chkbuild http://github.com/yugui/chkbuild
2) We have no process for people donating CPU time
I can translate the docs, but that still doesn't overcome the burden of running custom CI software. I'll email ruby-core about #2 because I'd really like to see more CI machines go up.
- Lewisham 16y agoWhat features does chkbuild offer that Hudson doesn't? Should I put a feature request in? If there's some stumbling block to adoption, it seems that switching the single CI box to Hudson, then utilizing the numerous Hudson boxes out there as slaves is quicker than trying to get people on board with chkbuild.