5 ms·

We use Debian for the CI machine. CI failures are taken quite seriously, and we have a person maintaining this CI box. I believe that is why Debian is conside

We use Debian for the CI machine. CI failures are taken quite seriously, and we have a person maintaining this CI box. I believe that is why Debian is considered highest. The next level of OS support are core developers that use that OS for work / home, but we don't have CI machines. I think if we had more CI boxes, then more platforms could join the "highest level" support. I know there was a conversation on the Japanese dev list about this, and I can try to dig it up if people are interested.

regularfry 16y ago
When you say "we," I presume you mean ruby-core?
- tenderlove 16y ago
  I am on ruby-core. :-)
  - regularfry 16y ago
    That's what I thought :-)
Lewisham 16y ago
What are your CI boxes running? The Hudson team used to have a number of Hudson slaves running various OSs and distros just building Hudson on-demand. That cluster drifted away, but there are a lot of Hudson servers out there that are mostly idle, and people seem generally happy to donate the CPU time. I've got an Ubuntu one here that could run Ruby slave builds.
- 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 ago
    What 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.

regularfry 16y ago

When you say "we," I presume you mean ruby-core?

tenderlove 16y ago
I am on ruby-core. :-)
- regularfry 16y ago
  That's what I thought :-)

Lewisham 16y ago

What are your CI boxes running? The Hudson team used to have a number of Hudson slaves running various OSs and distros just building Hudson on-demand. That cluster drifted away, but there are a lot of Hudson servers out there that are mostly idle, and people seem generally happy to donate the CPU time. I've got an Ubuntu one here that could run Ruby slave builds.

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 ago
  What 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.