Hi
just to make sure I understand it : ° you run ccnet with the following : ccnet.exe -config:configfile -project:projectname ° and when ccnet is done, the command window does not close? if this is so, it is by design, there was a request made once : when starting ccnet console by clicking via the shortcut on the desktop, and there is a config problem, the command window goes away. Thus one can not read the error. and this was/is a very good item that needed to be addressed. Now, we can foresee a setting, let's autoclose, that will close the command window when ccnet has done. so the syntax would be : ccnet.exe -config:configfile -project:projectname -autoclose:true autoclose would be default false Would this be a solution for your situation? with kind regards Ruben Willems On Mon, May 25, 2009 at 10:49 AM, fyodorkor <[email protected]> wrote: > > Hi, > I am currently using version 1.4.2.14 and testing 1.4.4. (They both > have the same behavior) > I am trying to launch CruiseControl through cmd window with paramaters > -config:configfile -project:projectname to build only a specific > project. After the project finishes building the ccnet process does > not terminate leaving cmd window up. So there is no indication that > the build process succeeded. > Is this a bug or I miss something in ccnet.exe configuration. > > The full command line is: start "Title" /wait <path_to_ccnet.exe> - > config:<path_to_config_file> -project:<project_name> > > Thank you > > Fyodor
