I have to run the nant script on a remote computer from where the
software is being installed because of required reboots.. so I can't use
exec to directly launch the installer... that really complicates life :)
The build script for that project looks like this
<target name="all" description="Does it all">
<call target="mapRemoteDir"/>
<call target="deployUninstall"/>
<call target="deployReboot"/>
<call target="waitForCleanServer"/>
<call target="deployFiles"/>
<call target="deployInstall"/>
<call target="deployReboot"/>
<call target="waitForTMSServer"/>
</target>
The nant script is run by one machine, which pushes the nightly build to
another machine. It uninstalls the last version on that remote, reboots
it, waits for it to come back, pushes the new installshield files to it,
starts the installer remotely, when the installer is finished, reboots
the machine, and then waits to ensure the machine is back.
It got even worse when the standard utilities to do this remote stuff
(launching processes) did not work from my build agents, hence why I had
to use my own visual basic scripts. Also, all the remote process stuff
that uses WMI are 'fire and forget' methods. Your local process does
not wait for the remote to finish. Further complicating from a script
perspective knowing when to move to the next step.
-Steve
-----Original Message-----
From: Bob Archer [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 16, 2008 9:48 AM
To: Steve Kapinos; nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] summary of nant lessons learned, and some
examples
Nice info. Thanks.
Although, so you not use the Install Shield stand alone builder? Because
it does return error codes to the exec task just fine.
BOb
-----Original Message-----
From: Steve Kapinos [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 10:14 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] summary of nant lessons learned, and some examples
After finally getting around a looking at the results.. after a few
projects using nant, including what were for me, some serious stumbling
blocks.. I've pulled together examples from my scripts and some 'duh'
moments and put them all together hoping future users will find them
when they are coming across the same problems. As with most things.. if
you had lots of examples from the start.. you'd probably save time. So
here's my contribution back to the net for nant
Topics included
Starting a process on a remote computer
Deleting and recreating a directory without generating error messages
Setting a property up to have a default value or override it via
environment variable.
Nant and visual basic scripts, including console messages and error
return codes
Nant reading the result code of an Installshield Install
Nant Map a Windows Share
Nant reboot remote computer
Rename a group of files
I hope someone finds some use in these... if you see anything incorrect,
please feel free to comment
http://coreplex.blogspot.com/search/label/nant
-Steve
------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
