Never mind.  It seems to be a permission thing regarding the account ccservice 
is running under being able to run the program to create the installer.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Beth Hechanova
Sent: Tuesday, April 20, 2010 9:10 AM
To: [email protected]
Subject: [ccnet-user] CC.NET calling NAnt exec task hangs

Hi,

The final step in our automated build is to create an msi installer using a 
product called Advanced Installer.

In my ccnet.config project, my publishers task calls a specific NAnt build 
file, with a basedir, and a timeout of 300 seconds (5 minutes).
In my NAnt build file, the exec task is used to execute this program the 
command line version of this product.    However this section of the script 
just hangs.  I then added a timeout value for the NAnt exec call of 5 seconds 
so the cc.net build would not hang.

If I log into my build machine and execute the build script via the command 
line with the same parameters (base directory, etc), the NAnt script correctly 
creates my msi installer.
So there is something amiss in the way that cc.net is invoking this same third 
party product.

I have also added the verbose flag to the NAnt exec task to see the values of 
the "Starting program..." and the data that cc.net gives me matches what I get 
when I invoke the NAnt script from the command line.  It does seem to find the 
program as TaskManager will have the process (if I don't have the timeout).

I am honestly not sure if this is a cc.net issue, or a NAnt issue.  But since I 
can run the NAnt script from the command line, I'm starting with cc.net.  What 
can I look at to see why my executable is not being run as expected?

I am using cc.net 1.5.6804.1, and NAnt 0.86 (Build 0.86.3412.0; nightly; 
5/5/2009).
My build machine is Windows XP, SP2 Virtual Machine.

One other tidbit - the beginning of our build process invokes this same program 
to edit the installer build file to set the version number.  This process works 
fine.  But invoking this same program with the command line argument to create 
the installer hangs when called via cc.net.

I am stumped as to what else to look at.  Any ideas?
Thanks,
Beth





__________________________________________________________________

This email and any files transmitted with it are confidential & proprietary to 
Systems and
Software Enterprises, Inc. (dba IMS). This information is intended solely for 
the use of
the individual or entity to which it is addressed. Access or transmittal of the 
information
contained in this e-mail, in full or in part, to any other organization or 
persons is not
authorized.

__________________________________________________________________







-- 
Subscription settings: http://groups.google.com/group/ccnet-user/subscribe?hl=en

Reply via email to