On 2/4/07, Marcel Offermans <[EMAIL PROTECTED]> 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.
CI sounds good if it doesn't deploy the snapshot artifacts if there was no change since the last deployment. Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP key fingerprints: * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
