Note that there are some explanatory texts on larger screens.

plurals
  1. POCruiseControl.NET process exited event received, build results in error
    primarykey
    data
    text
    <p>Similar to <a href="https://stackoverflow.com/questions/15511551/using-cruisecontrol-net-and-msbuild-to-publish-a-website">Using CruiseControl.NET and MSBuild to publish a website</a></p> <p>I'm encountering a situation where the MSBuild task in the ccnet.config does appear to work, but at the very end the process terminates with </p> <pre><code>standard-output stream closed -- null received in event standard-error stream closed -- null received in event process exited event received </code></pre> <p>When run from the command line, all appears well. </p> <p>I've looked in all the logfiles I can think of, but I am stumped, I've dumped a lot of time into this. Please help!</p> <p>UPDATED 11/13: As requested here is excerpt from CCNET.CONFIG</p> <pre><code> &lt;msbuild&gt; &lt;executable&gt;$(msBuildExe)&lt;/executable&gt; &lt;projectFile&gt;"src\Solutions\Apprentice - Core Tests - VS11.sln"&lt;/projectFile&gt; &lt;buildArgs&gt;/noconsolelogger /p:Configuration="$(msbuildConfig)" /v:diag&lt;/buildArgs&gt; &lt;logger&gt;$(ccnet)\server\ThoughtWorks.CruiseControl.MsBuild.dll&lt;/logger&gt; &lt;environment&gt; &lt;!-- allow NuGet to auto restore packages --&gt; &lt;variable&gt; &lt;name&gt;EnableNuGetPackageRestore&lt;/name&gt; &lt;value&gt;true&lt;/value&gt; &lt;/variable&gt; &lt;/environment&gt; &lt;/msbuild&gt; </code></pre> <p>With</p> <pre><code> &lt;cb:define msBuildExe="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe" /&gt; &lt;cb:define msbuildConfig="Debug - No MSEL" /&gt; </code></pre> <p>At the top, amongst others</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload