There was/is some bits on gbuild that is using Continuum... but I'm
unsure at this time how trustworthy the setup is (ie. can we trust
that a failure notice is really something broke or just something
transient).
Once the m2 build is square we should get a concrete CI setup to help
avoid future periods of build breakage.
--jason
On Jul 1, 2006, at 2:05 PM, Bryan Noll wrote:
John Sisson wrote:
* The code in svn should always build. During the development of
1.0 and 1.1 there were long periods of time where builds were
broken due to people committing code without doing a build to test
it. In some cases the developer may have done a build and it was
successful, but when they committed the changes, they accidentally
left out a file from the commit. There were a number of times
where people broke the build in their last checkin when they were
blurry-eyed and just about to head off to sleep. Developers in
other timezones then wasted time either debugging the problem, or
waiting for the developer who checked in the change to wake up or
trying to find a revision that does build.
John
This seems like a fairly fixable thing, right? Some kind of
Continuous Integration for the project... Cruise Control or
whatever? I noticed these JIRA's awhile back...
http://issues.apache.org/jira/browse/GERONIMO-301
http://issues.apache.org/jira/browse/GERONIMO-302
http://issues.apache.org/jira/browse/GERONIMO-303
http://issues.apache.org/jira/browse/GERONIMO-304
I don't know the details, but it seems like I've seen communication
either here or on the IRC about some kind of CI stuff... thinking
Blevins has worked on that stuff if I remember right. If that's
true, it's unclear to me what is currently happening in terms of CI
(anything?), and what yet needs to happen.
So, could anyone here in the know please clarify that?
Also, once I understand a bit better about what needs to be done
yet, I would be glad to help get it going.
Thanks,
Bryan
