Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

prevent Team Build dropping all binaries to the root of the drop folder

Tags:

tfs

tfsbuild

The default configuration of the Team Build Number Format is:

$(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)

It drops all output to \\foo\bar\MyBuildDef_20111031.1 Great stuff so far!

The small problem is that it drops all binaries in that directory without a good indication of the dependencies of the binaries.

TFS drop files

How can you modify this property, or otherwise, to have the solution's binaries dropped in their respective project directories?

In the case above, I had expected the MVC website (complete with its bin directory) to be dropped. Instead, we got that PLUS the extra drop of the binaries in the root.

In other words: TFS, please stop dropping all binaries in the root; it looks messy, and it's confusing on which files belong/associated with what.

How can this be achieved with Team Build 2010?

like image 759
p.campbell Avatar asked Feb 02 '11 18:02

p.campbell


People also ask

What to do if you accidentally drag and drop to another folder?

The nice thing is that you can just keep a copy of your file system so if a folder is accidentally drag and drop'd to another folder, you can at least go back and find the original folder and copy it back in. Used this have this problem with my users as well and education (although the best solution) was slow and painful. Was this post helpful?

Should boot drop all tables in an embedded database on startup?

Referencing Issue #621 - there is an issue where Boot has made the decision that all tables in an embedded database should be dropped on startup. I don't think Boot should default to doing that -- for one thing an embedded db is typically empty already unless you take measures to populate it, such as placing sql in schema.sql and data.sql.

How do you deal with users who drag and drop?

I would start by educating them not to do it and then if that fails, use a length of clue-by-four They have all been told multiple times about it, but it still happens. Tell users that if you have to clean up an accidental drag and drop, they have to buy you donuts.


2 Answers

This blog post should help you out: http://blogs.msdn.com/b/willbar/archive/2011/02/05/splitting-team-build-outputs-into-folders.aspx

Essentially, you create a new 'Platform' for each project. Team Build will put each platform in a different directory by default, so you get a different directory for each of your projects.

Build configuration dialog:

Build Configuration dialog

Drop folder output: Build drop folder with separate folders

like image 194
Grant Holliday Avatar answered Sep 18 '22 00:09

Grant Holliday


Unfortunately I have not found a good way to do this yet, though it has been a while since I tried to find a better solution then what I settled on.

Current have solutions for each desktop application, and one with all the websites. I then followed the instructions here to make each solution output into a separate folder.

like image 34
Sean Lynch Avatar answered Sep 20 '22 00:09

Sean Lynch