cruisecontrol.net

I'm currently in the process of setting up a continuous integration environment at work. We are using VisualSVN Server and CrusieControl.NET. Occasionally a build will fail and a symptom is that there are conflicts in the CruiseControl.NET working copy. I believe this is due to the way I've setup the Visual Studio solutions. Hopefully the more projects we run in this environment the better our understanding of how to set them up will be so I'm not questioning why the conflicts happen at this stage. To fix the builds I delete the working copy and force a new build - this works every time

I my problem is quite simple, i have a CI server wich run msbuild and mstest. The problem is that the Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll doesn't exist( and i thinks other file related to mstest...) if we don't install VS in the server wich is pretty stupid for a CI server... Anybody have a solution about this problem ? Ruben Bartelink Unfortunately, there is no supported or easy way around having to install VS on the build agent machine in 2005 or 2008 ( There will be a test agent installer in 2010 ). UPDATE: See this post from Steve Smith for more info which says pretty

I would like use a continuous integration system in my projects. However, I don't want to use a server sitting in my office, instead I'd like my continuous integration server to run on Windows Azure. Has anyone set this up? Are there recipes to host Hudson or CruiseControl.Net (or any other CI system) within Azure? We use the Build Manager in Team Foundation Server to push our automated builds to Azure. We set up our Azure hosted services to allow for Web Publish through remote desktop using this plugin - http://dunnry.com/blog/2010/12/20/UsingWebDeployWithWindowsAzure.aspx You do not need to

I have two projects set up in CruiseControl.NET: CI build and nightly build. Both of them execute the same NAnt script, but with different parameters. The CruiseControl.NET label (currently generated by the DefaultLabeler ) is embedded into AssemblyInfo as the build part of the version (for example, MajorVersion.MinorVersion.CCNET_Label.SVN_Revision ). For more consistent versioning I would like both projects to share the same CruiseControl.NET label value. I have investigated the labelers that are available as part of the CruiseControl.NET installation, but I could not find one that does what

I would like to integrate QTP with Cruise Control, which I have done so far, i'm stuck at the reporting part. I would like to somehow report back to Cruise Control with the results, how can I accomplish this? Please help? I remember there was a useful series on how to integrate CCNET with various build and testing tools including QTP. This is what I bookmarked: Part 1: Continuous Integration using MSBuild, CruiseControl.NET, FxCop, NUnit, NCover + Subversion - From the software development trenches But somehow it seems to have vanished. Today I found the updated version by accident. It doesn't

I want to set up ccnet to: Send mail to committers after each build (regardless of the status) Send mail to all other developers when the build breaks or is fixed With every new version of CCNet the email publisher gets refactored (and supposedly improved), but I still have the same problem: only the committers get notified - if the build breaks, other developers don't get the email message . So either I don't get the system, or there is a long-unfixed bug in the email publisher. I'm using the v1.4.4.83. My example configuration (I removed the irrelevant stuff): <email includeDetails="true">

We have 4 different environments at the moment (Lab, Test, Stage, LIVE) and we have implemented automatic deployment using Nant/CC.Net. I am investigating and doing some research as to what can be done more efficiently with new MSDeploy tool. What I want to achieve is to create a package with a Configuration folder inside which we will have all the different configuration files for all the possible environments (basically adding all config transform files) What I want to achieve is automatic deployment in our enterprise environment where development team hasn't got any access to the server