Emmanuel Lecharny wrote:

Another possibility is that we try to get trunks that can be compiled
online, without any problems for the user. That means we have to deploy
everytime we check-in some code. Pretty expensive.


IMO I think we should all be deploying changes with every check in. Yes it is expensive :( but we have to or no one will be able to build properly.

Last time I deployed everything, it took more than half an hour. This is
simply impossible to accept this, as long as we are working on trunks.
Working in branches is something that is not always necessary and it's
not free, too.

We have to consider that either we deliver releases more often (let say
everytime a blocker or major bug is corrected), or we must have some
kind of nightly build. Any other solution is simply too costly, IMHO.
Yes I like this idea of nightly builds.  And it does save us.

btw, I've a server that does nothing which can be used to build nighty
builds if needed.
Again, this is just MHO.

No you are right. I have always build stuff by hand and prevented breakage that way. This though took my time considerably.

ALex

Reply via email to