Thanks for getting back to me Tom.
Actually I was thinking of something more along the lines of Apache Gump...
http://gump.apache.org/ in that some system is constantly checking for updates to the cvs
repository and periodically checks them out and tries to build them and then run a
standard suite of tests against it.
In the development shop where I work, we've found that sort of thing tremendously
valuable as we have people working all around the code base simultaneously. It lets us
know if someone inadvertently broke the build w/out having to discover it yourself and
then be stuck until either a fix is checked in or the change rolled back.
I usually start my day by checking the web site for our build and if it's
"green" then I do a full update of the code base, and build while I'm
reading forums, etc. Then, I know I'm good for the day to build and work with my
changes w/out worrying about how far I may have drifted from other people's work
(usually no more than a day's worth).
Thanks again for your response and AWESOME job building jbpm etc. It looks like a great
code set and I'm really looking forward to working with it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991099#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...