UppercuT - Automated Builds - Getting Started Part 2 (Add UppercuT to Your Project)

 

In Part 1 we downloaded or built from source control. We are now ready to add UppercuT to our project. Let’s UppercuT our code!

Add UppercuT to Your Project

 

1. We open the folder at the top level of the project (usually just under trunk or a branch). Below you can see we have a project called MoneyQIFGenerator and it has no automated build love yet.

2. We already have a references folder (lib) so we are going to do something differently when bringing in UppercuT. For any existing project this could be 3rdParty, ThirdParty, References, External, lib, libs, etc. This is where you keep your external references and tools and where we will ultimately put parts of UppercuT. The remainder of the time we are going to call this third party references folder lib.

 clip_image002_thumb[1]

3. We pull up the folder where we have downloaded or compiled UppercuT.

 clip_image004_thumb[1]

4. We select everything except the lib folder. We already have a lib folder so we are going to bring the items in this folder over in pieces. If we are adding this to a brand new project we select the lib folder as well and bring it over in whole.

 clip_image006_thumb[1]

5. Select [Edit]->[Copy] in the UppercuT folder.

 clip_image008_thumb[1]

6. Go to the project folder. Select [Edit]->[Paste]. 

 clip_image010_thumb[1]

7. We should now have all of these new folders and files ready to add to source control.

 clip_image012_thumb[1]

8. If we brought over the lib folder, we can skip the next few steps. If we are adding to a project that already had a references folder, we go back to UppercuT’s folder and into the lib folder. 

 clip_image014_thumb[1]

9. Open the lib folder on the project. This could be 3rdParty, ThirdParty, References, External, lib, libs, etc. This is where you keep your external references and tools.

  clip_image016_thumb[1]

10. In the references folder (UppercuT side), copy either the MbUnit or NUnit folder over to the project’s references folder. If you already have the references to your test framework (as we do below), there is nothing to do (unless there are missing components).

 clip_image018_thumb[1] clip_image020_thumb[1]

11. In the tools folder (UppercuT side), we have NAnt and NCover. If we already have these referenced, we don’t need to copy them over. If we don’t have these referenced, bring over the entire tools folder into the lib folder. You can see that we don’t have either of these in the project, so we bring over the entire tools folder.

  clip_image024_thumb[1]clip_image022_thumb

 clip_image026_thumb[1]

12. Now we need to add all of these files to source control. If we are using TortoiseSVN, we right click in the top level folder (but not on a file, click in the white space). Select [TortoiseSVN]->[Add…].

 clip_image028_thumb[1]

13. Make sure all items are selected.

14. If you already have a build_output folder, a code_drop folder, or a SolutionVersion.cs/SolutionVersion.vb file, uncheck those entire folders and that file. You would only have these the first time if you have already tried to build. These are items we never want in source control (they are generated items).

 clip_image030_thumb[1]

15. Click {OK}.

16. The items are being staged to be committed to source control.

 clip_image032_thumb[1]

17. With Subversion, this is basically what we should see as a result.

 clip_image034_thumb[1]

UppercuT - Getting Started Series

Part 0 - Prerequisites
Part 1 - Get UppercuT
Part 2 - Add UppercuT to your project
Part 3 - Configure UppercuT.config
Part 4 - A note about the external tools / libraries
Part 5 - Build It!
Part 6 - Source Control / What NOT to check in
Part 7 - Setting up TortoiseSVN to Globally ignore UppercuT output folders and files
Part 8 - Next Steps

With this knowledge you shall build.

kick it on DotNetKicks.com

Print | posted @ Friday, May 29, 2009 7:27 AM

Comments on this entry:

Comments are closed.

Comments have been closed on this topic.