Continuous Integration
There are 7 entries for the tag
Continuous Integration
The question came up via Buddy Lindsey: "on a beginner's level, why should one use a Continuous Integration solution?" Here is my honest, un-googled, from-real-world-experience answer as someone who has done non-trivial corporate team-based development both with and without CI. All of this applies equally to web and desktop development, from a mechanical standpoint there's absolutely no difference. The differences are in the code. Preamble If you are alone, writing code with no team, no release cycle, no QA, or anything of the sort of stuff that represents professional software development, then CI is probably nothing more than mental masturbation...
I’ve never seen a more timely blog entry. Like that episode of Family Guy where Joe is down about being handicapped, and a commercial comes on for the special peoples games, and then the news says “Coming up, our expose on conveniently timed television shows, but first, watch out for that skateboard Peter” and then Peter trips on a skateboard….
So…rambling…oh yeah. Earlier I was discussing my build environment, and I was a little down about NDepend not being a default integration item, and rather than putting in the work I used an <externalLink> in ccnet.config to link to the NDepend...
Finally! My day-long odyssey is over. I have a full and complete and successful build!
First, let me just say, if you are doing .NET projects of any non-trivial size, you absolutely must read Expert .NET Delivery Using NAnt and CruiseControl.NET. It is absolutely one of the most well put-together, timely, and useful software books I have read in a long time. As I was reading it, literally almost page by page, I was thinking “yes, I do want to implement something like that”.
Moving on…I had dabbled in CruiseControl.Net before, got a basic build system up and running, and left it...
Okay, I had this error that I posted about a couple days ago…CCNet was throwing an UnauthorizedAccessException when it was trying to build. I have solved that problem.
Let me just say, Lutz's Reflector is an awesome tool and a must-have for any developer’s toolbox. I’ve had it around, but never really done anything with it. So…at my wit’s end…I loaded the CruiseControl assemblies into Reflector, went to the offending method (ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vss.GetSource()) and looked inside.
The first thing in the method checks for autoGetSource to be true, then it goes and looks for workingDirectory, then it goes and tries to do some directory magic. ...
This is driving me nuts. I had CruiseControl.net v8 all up and running, then all of a sudden, every build is coming back with:
BUILD EXCEPTION
Error Message:
System.UnauthorizedAccessException: Access to the path "AssemblyInfo.cs" is denied. at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive) at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive) at System.IO.Directory.Delete(String path, Boolean recursive) at ThoughtWorks.CruiseControl.Core.Util.TempFileUtil.DeleteTempDir(String dirname) in d:\sourceforge\ccnet\project\core\util\TempFileUtil.cs:line 52 at ThoughtWorks.CruiseControl.Core.Util.TempFileUtil.CreateTempDir(String dirname, Boolean overwrite) in d:\sourceforge\ccnet\project\core\util\TempFileUtil.cs:line 27 at ThoughtWorks.CruiseControl.Core.Util.TempFileUtil.CreateTempDir(String dirname) in d:\sourceforge\ccnet\project\core\util\TempFileUtil.cs:line 20 at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vss.GetSource(IIntegrationResult result) in d:\sourceforge\ccnet\project\core\sourcecontrol\Vss.cs:line 182 at ThoughtWorks.CruiseControl.Core.Project.AttemptToRunIntegration(IIntegrationResult result) in d:\sourceforge\ccnet\project\core\Project.cs:line 168
And it’s driving me nuts. It’s finding modifications okay and trying to build, but always puking on this error. It...
This morning I set up my new CruiseControl.Net Implementation for multiple projects. I don’t know if I did it *right*, but the way I did it works and I’ll share that with you.
First, you need to edit ccnet.config for the extra projects. All that entails is setting up another <project> block with the same basic information and a little tweak or two.
What I ended up doing is under the /web folder creating folders for /project1 /project2 and /project3. Then I copied the contents of /web into each of those. This means each project has it’s own log directory. Point the <logDir>...
There’s been a lack of programming content here of late…
I’m trying to implement a continuous integration strategy with my dev team as we move forward with a new project, so I decided to look into CruiseControl .NET. V. 0.8 just came out, so I started clean with that. It was a hell of a day getting it set up, so I’m hoping I can help a few people out with this.
First of all, huge thanks to Joe Field for his excellent guide (pertinent to 0.7). It got me about 90% of the way there. Second, I don’t know everything about CCNET…I...