UppercuT - Automated Builds - Getting Started Part 1 (Get UppercuT)

So you've decided to UppercuT your code and you want to get started.

You are making a step in the right direction when you choose to use automated builds. As you read through this, you will see how easy it is to get into the world of automated builds. As you read through some of the other documents, you will learn just how powerful UppercuT is.

The first thing you need to do is download or pull the source to your computer and build it. 

Get UppercuT

Download

1. Head out to http://code.google.com/p/uppercut/downloads/list and download the latest.

 clip_image002

2. One thing to note, when you do download the zip file, the very first thing you will want to do (before extracting) is right click on that file and select [Properties]. On the General tab click {Unblock} if you have it. Otherwise you may have to unblock each file one at a time later.

 clip_image004

 clip_image006

3. Unzip the files. What we will need to bring into a project is in the UppercuT folder.

 clip_image008

Get the Source

1. The other way to get UppercuT is to point your favorite SVN client at http://uppercut.googlecode.com/svn/trunk/.

2. Once it has completed downloading, just click on the build.bat (or open a command line in this directory and type build).

3. Once it has completed, there is a folder called code_drop. This is one of the artifact folders of UppercuT. We will talk about that later. For now, navigate to the folder. What we will need to bring into a project is in the UppercuT folder.

 clip_image010

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:13 AM

Comments on this entry:

Comments are closed.

Comments have been closed on this topic.