Re: Snapshot Deployment Best Practices
This the wrong list for helping you with Team City and Nexus. I suggest you talk to some Team City people or possibly Nexus people; we're Maven people. /Anders On Mon, Dec 5, 2011 at 17:39, prakyat prakhyathpra...@gmail.com wrote: Hey, I am a novice in Continuous Integration. Please can you list out a few steps on how I can go about setting up Team City to deploy to Nexus. The system currently uses archiva repositories and want to move to Nexus. It would be great if you could tell me how you went about it so I don't miss anything. Many Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/Snapshot-Deployment-Best-Practices-tp126575p5049415.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Snapshot Deployment Best Practices
Hey, I am a novice in Continuous Integration. Please can you list out a few steps on how I can go about setting up Team City to deploy to Nexus. The system currently uses archiva repositories and want to move to Nexus. It would be great if you could tell me how you went about it so I don't miss anything. Many Thanks. -- View this message in context: http://maven.40175.n5.nabble.com/Snapshot-Deployment-Best-Practices-tp126575p5049415.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Snapshot Deployment Best Practices
Nexus has a Purge Snapshots job you can schedule. It is pretty flexible. You can decide how many snapshots you wish to keep around. Ideally, you should normally only need the latest, but on the rare occasion you may want to point to an older one. In our environment, the job runs every night and only leaves the last 2 snapshots. Although we are now considering only keeping the latest since I don't think anyone has ever wanted to point to the second latest. --- Todd Thiessen -Original Message- From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] Sent: Friday, November 13, 2009 12:21 PM To: users@maven.apache.org Subject: Snapshot Deployment Best Practices I have figured out how to deploy all my artifacts to my local Nexus repository, and I have even set up my CI tool (TeamCity in my case) to deploy the snapshot artifacts every night. Because I am not at the release stage yet, I have just been deploying snapshot after snapshot. This means that my snapshot page on Nexus for this artifact is getting loaded with entries down the page. My questions relate to the best practices associated with this sort of practice: *Is it OK and desirable to build up artifacts between releases? *If not, is there a way to replace the previous snapshot artifacts with the latest ones? *Are there any steps I am missing? Thanks for your insight. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Snapshot Deployment Best Practices
Also, avoid deploying snapshots if nothing's changes. This is easier to accomplish if you have a truly modular build with sub-modules following their independent release cycles rather than a one monolithic multi-module buid. It'll certainly work if you always deploy everything just in case, but especially if your modules are big, you and all your devs end up spending extra unnecessary seconds every day downloading the dependencies even if they haven't changed. Kalle On Fri, Nov 13, 2009 at 9:57 AM, Todd Thiessen thies...@nortel.com wrote: Nexus has a Purge Snapshots job you can schedule. It is pretty flexible. You can decide how many snapshots you wish to keep around. Ideally, you should normally only need the latest, but on the rare occasion you may want to point to an older one. In our environment, the job runs every night and only leaves the last 2 snapshots. Although we are now considering only keeping the latest since I don't think anyone has ever wanted to point to the second latest. --- Todd Thiessen -Original Message- From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] Sent: Friday, November 13, 2009 12:21 PM To: users@maven.apache.org Subject: Snapshot Deployment Best Practices I have figured out how to deploy all my artifacts to my local Nexus repository, and I have even set up my CI tool (TeamCity in my case) to deploy the snapshot artifacts every night. Because I am not at the release stage yet, I have just been deploying snapshot after snapshot. This means that my snapshot page on Nexus for this artifact is getting loaded with entries down the page. My questions relate to the best practices associated with this sort of practice: *Is it OK and desirable to build up artifacts between releases? *If not, is there a way to replace the previous snapshot artifacts with the latest ones? *Are there any steps I am missing? Thanks for your insight. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
