Skip to main content

Unfuddle repository callback and cruisecontrol.net

So as you may know I've started a personal project that I hope to turn commercial one day and I'm using Unfuddle to do the "project/development management" which includes a SVN repository.

I've got CruiseControl.Net setup to CI my code and it all works gloriously well but I was chatting to Glyn the bloke that put me onto Unfuddle and he mentioned that Unfuddle has a repository callback feature - rather than have CC.Net ping my Unfuddle SVN every 30 seconds to detect if a commit has occurred Unfuddle will POST details of the latest commit to the url you register as your callback - a much more efficient Pub/Sub approach.

Ok - so how to get a callback to trigger a CC.Net build? Easy!

Attempt 1
  1. I Fiddlered the url that the CC.Net webdashboard calls when you press the "Force Build" button on a project - it looks like this, http://[yourserver]/ccnet/server/local/project/[yourproject]/ViewProjectReport.aspx?ForceBuild=Force
  2. I entered this into the Unfuddle repository callback url
  3. Opened the required firewall ports to allow this traffic into my server (I changed port 80 to something else)
  4. Modified my CC.Net project config to remove all triggers (force build only)
  5. Committed some code...and waited...and waited....no build triggered :(

Little grey cells time....
I entered the same callback url into a browser and it worked, hmmmmm
Had I even been called by Unfuddle, maybe they were busy?
I checked the IIS log and there is was a POST from Unfuddle BUT they had stripped the querystring off the url (?ForceBuild=Force) - this is obviously the magic bit that forces a build so...

Attempt 2
  1. Installed the URL Rewrite module from IIS.Net
  2. Configured the URL Rewriter for the ccnet virtual app to include a new rule - rewrite http://[yourserver]/ccnet/[yourproject]/unfuddle.aspx to the actual url (see above) that would trigger the build
  3. Updated the callback url in Unfuddle to http://[yourserver]/ccnet/[yourproject]/unfuddle.aspx
  4. Committed again - bingo, about 20 seconds later my build was triggered :)


Labels

Labels:

Comments

Unknown said…
HI James,
Thanks for this post, helped me a lot. I'm trying to integrate CruiseControl.NET with Unfullde too.
And I need to to "pull" rather than "push". Any advice on that?
4 Dec 2012, 21:37:00
Post a Comment

Popular posts from this blog

Walk-Thru: Using Wolfpack to automatically deploy and smoke test your system

First, some history... The advent of NuGet has revolutionised many many aspects of the .Net ecosystem; MyGet, Chocolatey & OctopusDeploy to name a few solutions building upon its success bring even more features to the table. I also spotted that NuGet could solve a problem I was having with my OSS System Monitoring software Wolfpack ; essentially this is a core application framework that uses plugins for extension ( Wolfpack Contrib ) but how to unify, standardise and streamline how these plugins are made available? NuGet to the rescue again - I wrapped the NuGet infrastructure (I deem NuGet to be so ubiquitous and stable that is has transcended into the software "infrastrucuture" hall of fame) with a new OSS project called Sidewinder . Sidewinder allows me to wrap all my little extension and plugins in NuGet packages and deploy them directly from the Wolfpack application - it even allows me to issue a new version of Wolfpack and have Wolfpack update itself, sweet huh...
5 comments
Read more

Configuration in .Net 2.0

11-Dec-2007 Update I've updated this post to fix the broken images and replaced them with inline text for the example xml and accompanying C# code. This post has been by far the most hit on this blog and along with the comments about the missing images I thought it was time to update it! Whilst recreating the examples below I zipped up the working source code and xml file and loaded this onto my Project Distributor site - please download it to get a full working custom configuration to play with! Just click on the CustomConfigExampleSource link on the right hand side, then the "Source" link to get the zip. We are in the process of converting our codebase to .Net 2.0. We've used Enterprise Library to great effect so decided that we should continue with this in the form of the Jan 2006 release which targets 2.0 and I've got the job of porting our Logging, Data Access etc wrappers to EntLib 2.0. ...And so far so good - the EntLib docs aren't bad and the migrati...
9 comments
Read more

Deployment - the final (.Net) frontier

[Update 19th Apr 2012]  - mission complete!...v2.4.0 of Wolfpack has been released and this includes a new set of plugins that can automatically download a NuGet package then execute a deployment tool (eg: DropkicK, MSBuild.exe) - it can even run NUnit tests (via the console runner). Wolfpack v2.4.0 Wolfpack.Contrib.Deployment [Original Post] Another day, another project and deployment raises its head... Thinking that this problem must have been cracked by now I had a look around the .Net landscape and found two interesting solutions. Octopus Deploy - a .Net convention based deployment system using NuGet packages, loosely based on AppHarbour's approach. DropkicK (aka DK) - another awesome initiative from Dru Sellers et al. I like the simplicity of Octopus but also like DK's  fluent code based deployment. Hmmm, this has got me thinking - Wolfpack could easily be adapted to be used as a deployment agent. Wolfpack can already monitor a NuGet feed for new pac...
6 comments
Read more