You are abusing the version system by trying to re-deploy different bits as the same version. If you don't release, then you have snapshots even if you preferred a different name for it. Why deploy anywhere else if you just want to make those bits available to other (Maven) users? You can simply use Jenkins as the Maven repository, see http://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Maven+Repository+Server
Kalle On Wed, Mar 30, 2011 at 11:24 AM, Bryan Keech <[email protected]> wrote: > 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: [email protected] [mailto:[email protected]] 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 > <[email protected]>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: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
