Marcel Offermans wrote:
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.
Yes I agree with you. Especially if you're talking about building with
Ant. However I was thinking of using maven. And with maven the deploy
fails when tests fail. Tests are always run by maven when you try to
install or deploy artifacts. So really a CI tool using maven is just a
daemonized Maven with a UI and some utilities.
I don't think continuum or other build systems respond out of the box to
email notifications. I hope I am wrong about it. I think I have to be tho.
Alex
