Re: Pragmatic project automation

I would think that scripted code checkout from CVS followed by compile and running the test suite was pretty usual. Given that this is only a few lines of shell or Perl why would you NOT automate it every night?

I hate doing the same stuff over and will typically spend 2-3 x as long to script it so I never have to do it over ever again. Mostly you win, sometimes you lose.....

cheers

tachyon

Comment on Re: Pragmatic project automation

Replies are listed 'Best First'.
Re^2: Pragmatic project automation by terra incognita (Pilgrim) on Sep 02, 2004 at 19:58 UTC
In our case it took a long time to create the automation but we recovered the cost (and time) very quickly, within days actually. My advice on this is to track how long is currently takes you now to do everything, that way you can show the benefit in $$$ to management. Good for those reviews and CYA. :-)	[reply]
Re^3: Pragmatic project automation by sutch (Curate) on Sep 02, 2004 at 20:25 UTC
Did you build your own tools? What tools are readily available?	[reply]
Re^4: Pragmatic project automation by terra incognita (Pilgrim) on Sep 03, 2004 at 17:58 UTC
Some are internally created, some are OS commands, and some are 3rd party. Where ever possible we have tried not to reinvent the wheel unless using another program requires significant work. We have also modified installs so that they will accept a command line. This enables us to set up the product via scripts on various machines. On UNIX this is a since the install is written in perl but on windows it requires the install team to modify the MSI.	[reply]
Re^2: Pragmatic project automation by adrianh (Chancellor) on Sep 03, 2004 at 09:34 UTC
I would think that scripted code checkout from CVS followed by compile and running the test suite was pretty usual Oh how I wish that were true.... for a start you're assuming that everybody actually has some kind of source control (gosh - I love consulting :-)	[reply]