I would recommend to deploy a shared storage on EC2 and map it to your nodes when you create them. Fresh Maven repos checkout will decrease the build speed and also cause a huge traffic, so additional storage expenses seem to be reasonable
четверг, 9 июля 2015 г., 10:30:47 UTC+3 пользователь Basil Brunner написал: > > Hi all, > > I’ve successfully installed Jenkins on a host running in AWS EC2. We’re > also using the > Amazon EC2 plugin [1] to start slaves, which is working fine as well. > > To save costs, I’ve configured the slaves to terminate after being idle > for 5 minutes. > If we start the next build job, a new, clean EC2 instance gets started. > > Since the slaves are now most of the time in a clean state, we also don’t > have a pre-filled > local Maven repository which means that each and every dependency is > loaded from remote > repositories, which takes quite some time. > > What is best practice with regards to Maven repositories? Does it make > sense to always > fetch from a remote repo? Is there some kind of “shared” Maven repo I > could use? Any > other suggestions how to deal with that situation? > > > Thank you very much for your feedback! > > -- Basil > > [1] http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/63199629-d987-4381-9df3-72ffadeef29d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
