Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Don't put the dependency in the CC.NET project settings. You need to control the project build order via the NAnt script. You don't have to build on a solution level, you can build on an individual project level.</p> <pre><code>&lt;target name="Project1" depends="Projects2" description="Builds project 1"&gt; &lt;msbuild&gt; &lt;executable&gt;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe&lt;/executable&gt; &lt;workingDirectory&gt;C:\dev\ccnet&lt;/workingDirectory&gt; &lt;projectFile&gt;CCNet.sln&lt;/projectFile&gt; &lt;buildArgs&gt;/noconsolelogger /p:Configuration=Debug /v:diag&lt;/buildArgs&gt; &lt;targets&gt;Build;Test&lt;/targets&gt; &lt;timeout&gt;900&lt;/timeout&gt; &lt;logger&gt;C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll&lt;/logger&gt; &lt;/msbuild&gt; &lt;/target&gt; &lt;target name="Project2" depends="Projects3" description="Builds project 2"&gt; &lt;msbuild&gt; &lt;executable&gt;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe&lt;/executable&gt; &lt;workingDirectory&gt;C:\dev\ccnet&lt;/workingDirectory&gt; &lt;projectFile&gt;CCNet.sln&lt;/projectFile&gt; &lt;buildArgs&gt;/noconsolelogger /p:Configuration=Debug /v:diag&lt;/buildArgs&gt; &lt;targets&gt;Build;Test&lt;/targets&gt; &lt;timeout&gt;900&lt;/timeout&gt; &lt;logger&gt;C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll&lt;/logger&gt; &lt;/msbuild&gt; &lt;/target&gt; &lt;target name="Project3" description="Builds Project 3"&gt; &lt;msbuild&gt; &lt;executable&gt;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe&lt;/executable&gt; &lt;workingDirectory&gt;C:\dev\ccnet&lt;/workingDirectory&gt; &lt;projectFile&gt;CCNet.sln&lt;/projectFile&gt; &lt;buildArgs&gt;/noconsolelogger /p:Configuration=Debug /v:diag&lt;/buildArgs&gt; &lt;targets&gt;Build;Test&lt;/targets&gt; &lt;timeout&gt;900&lt;/timeout&gt; &lt;logger&gt;C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll&lt;/logger&gt; &lt;/msbuild&gt; &lt;/target&gt; </code></pre> <p>You can run your unit tests on an individual project level, so you shouldn't need to make duplicate runs over multiple projects.</p>
    singulars
    1. This table or related slice is empty.
    1. POBuild order in CruiseControl.NET with project dependencies
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USThe Matt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBuild order in CruiseControl.NET with project dependencies
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODoing it this way would mean that I would have to duplicate the build instructions for each dependency project into each dependent project. But I guess if it turns out that I can't control the build order in CC.NET, I'll have to be redundant. At least I can use CC.NET's support for XML Entities to encapsulate a project's build steps.
      singulars
      1. PO
      1. USJacob
    2. CONot necessarily. Use a single cruise.build file to store the NAnt script. Share this single cruise.build file across the projects, that way they all adhere to the dependency hierarchy and you're not duplicating the script.
      singulars
      1. PO
      1. USThe Matt
    3. COAlthough it sucks that the build box would still have to do duplicate building, it's looking like there's no good way around it. This answer looks like the best one.
      singulars
      1. PO
      1. USJacob
 

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