Ticket #1887 (closed task: fixed)
|Reported by:||robe||Owned by:||robe|
I think we are outgrowing our current build infrastructure and need to start doing more automated tests of platforms.
Jenkins is a fork of Hudson that seems to garner the bulk of FOSS love. Hudson still exists and is still being extended by Oracle, but form what I can gather Hudson is catering more to Enterprise extensiosn and things that Oracle find lucrative to support.
The founder of Hudson forked it to form Jenkins and it has way more developers now than Hudson does and a ton of plugins. It has a Git plugin so seems possible to have it build our git repos as we slowly migrate to that.
The only gripe I have with Jenkins/Hudson? (which I think strk shares - funny we have something in common) is that it is Java based. I'm willing to live with that.
It does seem perfect for our project because a) it does have native installers for most OS which if you don't have JRE installs it for you b) has a Maven plugin so building our jdbc drivers with our new maven framework should be easy
c) Has support for slaves. I'm still getting up to speed with it and how the whole slave architecture works. For windows -- a slave can run as a service, probably requires java. It seems for Unix like systems as best I can gather it would require an account with shell access that can launch processes. So I think strk your concern about slaves needing to run java may not be required.