Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Just trying to build a bit on what mjmarsh said, since he laid a great foundation...</p> <ul> <li>Visual Studio. MSBuild works fine.</li> <li><a href="http://nant.sourceforge.net/" rel="noreferrer">NAnt</a>.</li> <li><a href="http://nantcontrib.sourceforge.net/" rel="noreferrer">NantContrib</a>. This will provide additional tasks such as Perforce operations.</li> <li><a href="http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+CruiseControl.NET" rel="noreferrer">CruiseControl.net</a>. This is again basically your "build dashboard".</li> </ul> <p>All of the above (save for VS) is open source, so you're not looking at any additional licensing.</p> <p>As Earwicker mentioned, build early, build often. Knowing something broke, and you can produce a deliverable is useful for catching stuff early on.</p> <p>NAnt includes tasks for <strong>nunit</strong>/<strong>nunit2</strong> as well, so you can actually automate your unit testing. You can then apply stylesheets to the results, and with the help of the framework provided by CruiseControl.net, have nice readable, printable unit test results for every build.</p> <p>The same applies to the <strong>ndoc</strong> task. Have your documentation produced and available, for every build.</p> <p>You can even use the <strong>exec</strong> task to execute other commands, for instance, producing a Windows Installer using InstallShield.</p> <hr> <p>The idea is to automate the build as much as possible, because human beings make mistakes. Time spent up front is time saved down the road. People aren't having to babysit the build by going through the build process. Identify all the steps of your build, create NAnt scripts for each task, and build your NAnt scripts one by one until you've wholly automated your entire build process. It also then puts all of your builds in one place, which is good for comparison purposes. Something break in Build 426 that worked fine in Build 380? Well, there are the deliverables ready for testing -- grab them and test away.</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.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      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