Geeks With Blogs

News
Rob Reynolds

Subscribe to Fervent Coder RSS
Subscribe to Fervent Coder by Email

About Me

I manage several open source projects. Need...
   ...package management for Windows?
   ...automated builds?
   ...database change management (migrations)?
   ...your application to check email?
   ...a monitoring utility?

I also write for



Like what you are reading? Want to buy me a cup of coffee?
PayPal - The safer, easier way to pay online!

Fervent Coder Coding Towards Utopia...by Rob Reynolds

In Part 1 we create a project. In Part 2 we set up the Build Configuration. In Part 3 we ran the build. Now we are just going to note how we get to our code.

 

Code Drop / Artifacts

TeamCity stores all artifacts in a database. So for every build, the drop location is not a physical disk location, it’s actually in a database.

  clip_image002_thumb[2]

This is why we called zip.bat instead of build.bat. We have to download the items from TeamCity and want to just download the one file. If we download that file and unzip it, we can see that the DLLs were versioned correctly.

  clip_image004_thumb

 

 UppercuT - TeamCity Integration Series

  1. Part 0 - Prerequisites
  2. Part 1 - Set up TeamCity Project
  3. Part 2 - Build Configuration
  4. Part 3 - Run the Build
  5. Part 4 - Code Drop / Artifacts

With this knowledge you shall build.

kick it on DotNetKicks.com Posted on Monday, June 8, 2009 7:05 AM | Back to top


Comments on this post: UppercuT - TeamCity Integration - Part 4 (Code Drop / Artifacts of the Build)

Comments are closed.
Comments have been closed on this topic.
Copyright © Robz / Fervent Coder | Powered by: GeeksWithBlogs.net | Join free