Whoops - sent too early
- Jenkins
- Ugly
- Java (I could probably stop there)
- Crappy client (requires fairly specific versions of Java files and has
flaky connection issues)
- Bad interface for custom build scripts
- Really made for testing Java web-apps
- Did I mention it's ugly and
Clients poll (simply http requests on port 80). That was important to us
for the same reason (and one of the reasons I don't like some of the other
CI systems).
Not just buildbot. Here's a list of systems we tried/looked at and their
issues:
- BuildBot
- client in constant connection with ser
I've got no issues - as for the clients, does the server communicate out or
wait to be polled? I ask because I've got some client resources, but they are
behind a firewall and can't just listen on a random port... They could
periodically poll out though.
Looks interesting!
I take it you've
I'll also make it run a "make check" - I forgot to mention that part. We
can expand from there later...
On Friday, February 21, 2014, Derek Gaston wrote:
> All,
>
> I got pissed off at all other continuous integration capabilities so I
> wrote my own. It's currently hosted at moosebuild.com (y
All,
I got pissed off at all other continuous integration capabilities so I
wrote my own. It's currently hosted at moosebuild.com (you can go there,
but please don't sign in yet because everything isn't finalized and I don't
want you to lose anything you do on there - not too mention that all of
