Allow overriding the <UpdateBuildNumberDropLocation Task - by mcdonaldn

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 366931 Comments
Status Closed Workarounds
Type Suggestion Repros 2
Opened 9/9/2008 2:51:52 PM
Access Restriction Public

Description

According to this post, Team Build’s <UpdateBuildNumberDropLocation Task has code in it which needs to update permissions on the drop location.  From what I understand, the code will change the permissions so the App Tier service account has access to the drop location (it needs access to delete builds and such).  To see this, Right Click on a file located on the drop location and notice how the App Tier service account has full access to the folder and any sub files or directories.  The <UpdateBuildNumberDropLocation is doing this.

The issue that I’m running into is, when the drop location is a NFS system, there are no permissions at the file or directory level.  So the build fails because permission can't be set.  But when the drop location is a NFS mount, there are no file/directory permissions.
Sign in to post a comment.
Posted by Microsoft on 9/12/2008 at 6:22 AM
We are addressing this problem in a future release. As a workaround for now, you could implement your own UpdateBuildNumberDropLocation task and update the Targets file to use yours. It is not the easiest workaround but is certainly attainable.