Yes, I was thinking about that one. Didn't really come to a good conclusion.
Pros: * Easy to scale out * Easy to start up (you don't have to buy the hardware etc) Cons: * Security (if you need to retrieve the code and you don't want to have your version management system publicly available) * If the repo manager is locally and the build server is externally, retrieving artifacts will be slower. However, possibly not a big issue unless you need to squeeze out that extra performance (time wise). * Cost (?) What I'm thinking is that it could be an easy way to get started, but as your build server(s) is most likely something you want for a long time and it will be working constantly, I think it might make more sense having it locally on your own hardware. It think it will be far more expensive to have it "in the cloud" compared to this. However, I don't have any figures to back this up, it's just my guess. Anyone else having any thoughts? /Anders On Thu, Oct 8, 2009 at 10:17, Michael Hüttermann <[email protected]>wrote: > that is a good point. What do you think about running a build server in > the Cloud while having the repo manager locally ? > > > > While seeing the benefits of services and also of using the cloud in > > general, I'm having a hard time ignoring the fact that I would like to > > have > > my repo manager locally. One great benefit of a repo manager is improved > > speed when downloading artifacts, which I wouldn't get when it's hosted > > outside of my LAN. > > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
