On Feb 4, 2007, at 2:06 , Alex Karasulu wrote:
Steven E. Harris wrote:
Trustin Lee <[EMAIL PROTECTED]> writes:
Thanks for the discussion.
In my case, I usually deploy whenever I resolve an issue.
Where do you deploy to? Are these snapshots public, or were you just
describing your internal working model?
I know Timothy Bennett just recently wrote up some code to suck
down emails from gmail.com and possibly respond to SVN commits. It
may be possible to use that with a subscriber to the felix scm list
to trigger deployment automatically after say a 15 minute wait (in
case there is a rapid train of commit activity).
Is this something worth doing?
To be honest, I think this is something that should be done by a
continuous build system, because I don't think you want to just
publish a new snapshot after a commit. In general, the risk of
publishing artifacts that don't work is too big. By integrating the
publication of snapshots into a continuous build, you could at least
make sure that all tests run correctly before publishing anything.
Greetings, Marcel
