I'm not aware of a way to do what you suggest. The PowerShell task is tightly integrated with CCDN. It's not run from a batch file.
Since I force the exit code to 0 from the PowerShell script, it *SHOULD* be reporting zero, which would indicate a successful build. Is there a way to turn on error level tracing? On Sunday, August 19, 2012 2:47:06 AM UTC-7, Ruben Willems wrote: > > Hi > > what is the return value? > if you do echo %errorlevel% immediately after the ps script, > what number do you see? > > with kind regards > Ruben Willems > > > On 15 August 2012 23:22, KenBobPDX <[email protected] <javascript:>>wrote: > >> I'm trying to figure out why CCDN (1.8) reports a PowerShell script task >> is failing when it is not. The PS task uses the VMWare library to stand up >> a virtual box and load our latest build. When I look at the build log, it >> shows that everything completed properly. >> >> I have put some Write-Output lines inside the PS script to show the >> current state and insure no errors have occurred and they are reporting as >> I expected, no errors. Yet, CCDN is reporting a failed build. I have >> checked the CCDN trace and log files and they don't report anything in >> regards to this project. I have also checked the Windows event logs and >> not found anything. What am I missing? Can someone point me in the right >> direction please? >> > >
