Can anyone give details on how they have done this? I am running into road blocks.
If I leave the version as a non-snapshot, then Hudson deploys to artifactory and overwrites the same version in the repo. I have toyed with using install:install-file goal in the install phase. Thanks, Bryan -----Original Message----- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Wednesday, March 30, 2011 1:18 PM To: Maven Users List Subject: Re: One Agile automated CI build No, it's a good idea. /Anders On Wed, Mar 30, 2011 at 18:01, Bryan Keech <bryan.keech.h...@statefarm.com>wrote: > Ok, is this a bad idea? I am wanting to have one ci build. Kind of this > flow: > > Developer checks in, ci build is done on Hudson, build is put on > artifactory, build can then be deployed to a dev, test or production server. > > Guess I am saying I don't want to do snapshot and release builds, but just > one automated build. > > Thanks, > Bryan > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
