We have a project that includes a TFS Get action, with the options to Force retrieval of all files and Overwrite existing writable files chosen. The action is set to run as a service account that has access to our TFS collection. It is set to get Latest Version.
There are two of us who use this project at varying times on our FB server. When I run the project, the Get action performs as expected. When my team member runs it, it consistently returns the message “All files are up to date” - implying that it is NOT forcing retrieval of all files.
Theaccount connecting to TFS is the same no matter which of us is logged into the server, so we cannot figure out why the action is behaving this way.
Can anyone explain this?
Hi Andy,
Just to clarify your running a FinalBuilder Server, and running the scripts through the web user interface? In addition when the FinalBuilder project is run, it is running under a service account user no matter who starts the project. Is this correct?
The information that might also be of assistance are:
- Version of TFS being used
- What the get command options are, is it using a common workspace location?
Thanks
Sorry about that. We are running FinalBuilder ON a server, that is our build server, but we are not running FinalBuilder Server.
When the project is run, it is running as the user account who starts it. But when it executes the TFS get, it is connecting to TFS as a service account, so no matter who is running the project it uses the same workspace (that service account’s workspace). This works fine in FB 7, when we upgraded to 8 it started acting weird.
TFS is 2013 update 5.
FB version is 8.0.2116 - I didn’t realize we were this far behind, we’ll update to the newest version and see if the issue is still happening.
Hi Andy,
I suspect this might be that FinalBuilder 8 needs to be started as Administrator, or that the user account under which the script is failing does not have the rights to impersonate the service user.
Andy,
the root cause of this situation is the service account that serves you both.
TFS uses the same workspace for both of you, that’s why one is doing fine and the other gets “all files are up to date” because TFS looks at the workspace when you Get files.
keeping this in mind you can workout this issue in several ways.
what I did is a stream of actions in every FB project dealing with TFS:
- remove the workspace (to be on the safe side).
- create the workspace - at this action you must combine some FB variables to make sure a unique workpace name.
- map folders.
- get the files.
- remove the workspace.
the only cost is the first time “coding” this project, don’t be lazy, the ROI is huge.
after choosing that solution path, all TFS annoying messages were gone completely. and you may run this FB project in any way you want.
Meant to update this yesterday - the upgrade appeared to fix the issue. We are both able to run the same project now with the expected results, using the most recent build of FB8.