Fog Creek Software
Discussion Board




joel test - step 2?

re:  http://www.joelonsoftware.com/articles/fog0000000043.html
step 2 - Can you make a build in one step?

can someone enlighten me on how to do an automatic build using install packages - installsheild, inno setup? 


While I can do an auto build from the source right up to ftp upload to a site - any suggestions to automate the installation step?

Regs PR

peter renshaw
Monday, June 02, 2003

Most installer have a command line interface specifically for automated build scripts. If your installer doesn't have one, dump it and get a better one.

As for specifics on InstallShield or Inno, I can't tell you. I hate InstallShield with a passion and never used Inno.

Chris Tavares
Monday, June 02, 2003

InstallShield (at least up to 6.x - haven't tried anything later) has a command line utility ISBuild.exe. Run that on its own with no arguments and it should give some examples of how to run it in a batch file.

Better Than Being Unemployed...
Monday, June 02, 2003

We have just started using Visual Build. I can't comment on how effective it is (no, I can - its great) as we haven't finished evaluating it.

There are buttons on the tool bar with setup packages on them - I guess you just click one and it inserts a build step that does setup. We haven't got that far yet.

Free eval copy available from http://www.kinook.com

We also looked at FinalBuilder and a few others. I preferred VisualBuild as it came with a load of example build scripts.

There have been a few threads on the dicussion board about build tools. Search for "build tool" or something.

Justin
Monday, June 02, 2003

Peter, you mentioned uploading to a site... is this a server-side app you are talking about? If so, I'd suggest taking a look at Apache Ant ( http://ant.apache.org ).

John C.
Monday, June 02, 2003

InnoSetup has a command line compiler.

I use FinalBuilder, which interfaces with it very well: http://www.atozedsoftware.com. Well worth the price of admission.

Tim Sullivan
Monday, June 02, 2003

Sorry, forum doesn't like trailing periods.

http://www.atozedsoftware.com

Tim Sullivan
Monday, June 02, 2003

InstallShield Professional 7 has a command line as does Wise Installer.  I have written batch files that simple call the main build system then the Installation build and then copy it where ever I wanted (This was a quick fix till I could write a correct make file (in this case) but it I am still using it as of today 2.5 years later)  I know that InstallShield has a menu item that allows you to generate a batch file for the install presently open.  Also I know Kinook software http://www.kinook.com , Visual Build tool has built in support for InstallShield and Wise Installer tools this one step automation.  In fact here is the Web site of supported tools http://www.kinook.com/VisBuildPro/thirdparty.html

A Software Build Guy
Monday, June 02, 2003

I meant that this is one step in automating a build like this.  Other build automation tools (from make to jam to Open Make to Perl can be used to get to one step)  InstallShield command line is actually two steps one is to run COMPILE.exe to create the install script byte code and then ISBuild.exe to create the media files.  I have not used other products to give you there command lines but a little research on their command should work.

A Software Build Guy
Monday, June 02, 2003

*excellent responses*

*I didn't look to see what command line options are available for the installers I have and at the moment this is what I am sticking with ( though the advice given here is making me think twice).
-Inno 3 and InstallSheild (cut version)

*as for the application
-win32 binary app(s)  AND/OR
-php scripts for Apache/Php ( without using Pear at moment )
-win32 + python scripts

*i'll certainly evaluate
-FinalBuilder ($$)
-Visual Build ($$)
-Ant (not sure if its applicable).

But I will see if I can hack, ( I mean automate) using 'COMPILE.exe' and 'ISBuild.exe' [installShield)]  and/or the Inno command line tools via some scripting language,
perl,python,php and see what then limitations are.

Maybe I should have mentioned that I wanted to automate 
my installs using *existing tools*  without additional costs.

The steps being:

#    description
---------------------
1. *binary/scripts* dumped into build dir from CVS
2.  automatic build script runs *install tool* as service/at comand at regular period at say 1300hrs
3.  *built install* dumped in upload dir
4.  script to upload  *latest install build* to website to download.

The step I could not figure out was # 2* -  how to automate the actual installation program?

The rest I pretty much do with python/perl etc.

Reg PR

Regs PR

peter renshaw
Tuesday, June 03, 2003

*  Recent Topics

*  Fog Creek Home