Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I retain compiler warnings in Hudson (CI) when using SVN Update?
    primarykey
    data
    text
    <p>I've got a continuous integration setup using Hudson and lately I've configured the jobs to use svn update to get the latest version of the code. I really like this approach since it allows msbuild to version appropriately and only build the effected assemblies.</p> <p>However, I've noticed that since I'm not doing a build of all the assemblies again, I loose all of the compiler warnings for those assemblies if they aren't built.</p> <p>For example, if I have 3 assemblies with dependencies demonstrated via indenting:</p> <ul> <li>Assembly 1 <em>10 warnings</em> <ul> <li>Assembly 2 (Depends on 1) <em>10 warnings</em> <ul> <li>Assembly 3 (Depends on 2) <em>10 warnings</em></li> </ul></li> </ul></li> </ul> <p>The first build will build all 3 assemblies and log 30 warnings.</p> <p>Next build, if I only change Assembly 3, Hudson will only build Assembly 3 and I will only get 10 warnings for that build, effectively marking 20 warnings as "fixed".</p> <p>As far as I can tell, there isn't going to be any way around this, but I would love to know if anyone has configured Hudson to retain these compiler warnings from one build to another.</p> <p>Edit: Yes I realize that this can turn into a debate of "you should / shouldn't be doing an update on a CI box", but there are reasons we went with the update approach. </p> <ul> <li>Its roughly 3x faster</li> <li>We're still producing the most up to date assemblies </li> <li><a href="https://stackoverflow.com/questions/1126880/how-can-i-auto-increment-the-c-assembly-version-via-our-ci-platform-hudson">msbuild can version the assemblies appropriately</a>.</li> </ul>
    singulars
    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.
 

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