<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hudson on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/hudson/</link><description>Recent content in Hudson on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 06 Jul 2011 18:15:00 +0200</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/hudson/index.xml" rel="self" type="application/rss+xml"/><item><title>Using NuGet in a MSBuild-target to have the packages at the last stand</title><link>http://blog.marko-apfel.de/posts/using-nuget-in-a-msbuild-target-to-have-the-packages-at-the-last-stand/</link><pubDate>Wed, 06 Jul 2011 18:15:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/using-nuget-in-a-msbuild-target-to-have-the-packages-at-the-last-stand/</guid><description>&lt;h2 id="motivation"&gt;Motivation&lt;/h2&gt;
&lt;p&gt;Encouraged from the article “&lt;a href="http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages"&gt;Using NuGet without committing packages to source control&lt;/a&gt;” I decided to wrap the NuGet-call in a MSBuild target instead of using a pre-build event.&lt;/p&gt;
&lt;p&gt;Because we also trigger FxCop and StyleCop via targets this fits better in our project management.&lt;/p&gt;</description></item><item><title>Integrate NUnit in Hudson CI-server</title><link>http://blog.marko-apfel.de/posts/integrate-nunit-in-hudson-ci-server/</link><pubDate>Wed, 07 Jul 2010 15:41:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/integrate-nunit-in-hudson-ci-server/</guid><description>&lt;h2 id="precondition"&gt;Precondition&lt;/h2&gt;
&lt;h3 id="naming"&gt;Naming&lt;/h3&gt;
&lt;p&gt;Its a good practice to have a common naming schema for test projects, fixture categories and fixture. Especially to configure automatic runs of unit tests is much more easier with this.&lt;/p&gt;</description></item><item><title>Integrate Simian in Hudson CI-server</title><link>http://blog.marko-apfel.de/posts/integrate-simian-in-hudson-ci-server/</link><pubDate>Wed, 07 Jul 2010 00:04:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/integrate-simian-in-hudson-ci-server/</guid><description>&lt;h2 id="steps-to-integrate-simian"&gt;Steps to integrate simian&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;add simian to VCS&lt;br&gt;
(in our case folder &lt;code&gt;./trunk/build/simian&lt;/code&gt;)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;add build step to your Hudson job&lt;br&gt;
(Execute Windows batch command)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;use following two commands&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bat" data-lang="bat"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;.\trunk\build\Simian\bin\simian-2.2.24.exe
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; -formatter=xml:.\trunk\bin\Simian.Result.xml
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; -excludes=**/*.Test/**/*.cs
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; -excludes=**/*.DbFrame/**/*.cs
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; -excludes=**/*.DbLayout/**/*.cs
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; -excludes=**/*.Designer.cs
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; -excludes=**/XServer1\_8.cs
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; -threshold=10
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; **/*.cs
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="k"&gt;EXIT&lt;/span&gt; 0
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="explanation"&gt;Explanation&lt;/h2&gt;
&lt;p&gt;For better visibility and understanding I have split the first call (simian) over several lines. Needless to say that you must contract all parameters and arguments of the simian call in one line.&lt;/p&gt;</description></item><item><title>Hudson error: could not delete ..config.xml</title><link>http://blog.marko-apfel.de/posts/hudson-error-could-not-delete-config-xml/</link><pubDate>Tue, 06 Jul 2010 16:44:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/hudson-error-could-not-delete-config-xml/</guid><description>&lt;p&gt;Today we updated our &lt;em&gt;Hudson&lt;/em&gt; CI-server. After changing job-configuration &lt;em&gt;Hudson&lt;/em&gt; throws an error, that the &lt;code&gt;config.xml&lt;/code&gt; could not be deleted.&lt;/p&gt;
&lt;p&gt;But the new entries are correct saved.&lt;/p&gt;
&lt;p&gt;Nevertheless such behavior bothers.&lt;/p&gt;
&lt;p&gt;The trick was to update also the plugins. After that all works fine again.&lt;/p&gt;</description></item></channel></rss>