Databases
StackOverflow2013
Postsdbo
POCruiseControl.Net Failed Build - No explanation
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCruiseControl.Net Failed Build - No explanation
    primarykey
    data
    text
    <p>I am just beginning to set up a Continuous Integration Server using CruiseControl.Net. To keep things simple to begin with, I used the Visual Studio Task to carry out the build, pointing it at the project solution file. However, when the build process occurs, CC.Net successfully gets the latest source version from Subversion, and appears to run the devenv command. The build process then fails, but there is no explanation about why. Here is the output:</p> <blockquote> <p><strong>BUILD FAILED</strong><br> Project: MyProject<br> Date of build: 2009-09-09 16:31:13<br> Running time: 00:00:49<br> Integration Request: Dashboard triggered a build (ForceBuild) </p> <p>Modifications since last build (0) </p> <p>Tests run: 0, Failures: 0, Not run: 0, Time: 0 seconds No Tests Run This project doesn't have any tests</p> </blockquote> <p>There is nothing else displayed on the page. My XML Logs don't show any build results either.</p> <p>This is my configuration file:</p> <pre><code>&lt;!--&lt;ccnetconfig&gt;&lt;configurationVersion&gt;1.4&lt;/configurationVersion&gt;&lt;/ccnetconfig&gt;--&gt; &lt;cruisecontrol&gt; &lt;project name="MyProject"&gt; &lt;workingDirectory&gt;C:\Users\Builder\Desktop\builder-pc\MyProject&lt;/workingDirectory&gt; &lt;sourcecontrol type="svn"&gt; &lt;trunkUrl&gt;svn://builder-pc/MyProject/trunk&lt;/trunkUrl&gt; &lt;workingDirectory&gt;C:\Users\Builder\Desktop\builder-pc\MyProject&lt;/workingDirectory&gt; &lt;executable&gt;C:\Program Files\Subversion\bin\svn.exe&lt;/executable&gt; &lt;autoGetSource&gt;True&lt;/autoGetSource&gt; &lt;tagOnSuccess&gt;True&lt;/tagOnSuccess&gt; &lt;/sourcecontrol&gt; &lt;tasks&gt; &lt;devenv&gt; &lt;solutionfile&gt;C:\Users\Builder\Desktop\builder-pc\MyProject\trunk\MyProject.sln&lt;/solutionfile&gt; &lt;configuration&gt;release&lt;/configuration&gt; &lt;buildtype&gt;Rebuild&lt;/buildtype&gt; &lt;executable&gt;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe&lt;/executable&gt; &lt;buildTimeoutSeconds&gt;600&lt;/buildTimeoutSeconds&gt; &lt;/devenv&gt; &lt;/tasks&gt; &lt;/project&gt; &lt;/cruisecontrol&gt; </code></pre> <p>I have deliberately removed things like the SVN username and password.</p> <p>Building the solution using the VS Command Prompt works, albeit with warnings. This is using the same swtiches that CC.Net would be using. </p> <p>Can anyone help? Is it failing because there are no unit tests to run, or because of the warnings? Or is it best to switch to MSBuild or NAnt instead of using the Visual Studio Task?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USGaryJL
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCruiseControl.Net Failed Build - No explanation
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCruiseControl.Net Failed Build - No explanation
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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