thanks for your feedback (feel welcome to rate the project :) )
It is totally possible to run SPSD remotely.
I do that too with the solutions where TFS has access to the staging environment.
You build the deployment package of SPSD automatically with the team build.
This can be accomplished if you have a deployment project in your VS solution which collects all WSPs and packages them nicely together for SPSD. The sister project "SharePoint Software Factory" availalbe at
provides already such a project in solutions ou create with it. SPSD will soon have its own prject template available here to have the feature without SPSF.
So everytime your team build runs the deployment package is available in your drop location. I haven't work with team city, but in TFS you could start the batches or the PowerShell directly. i.e. by PS-Remoting on the staging farm.
You just build the WSPs and drop them in an existing SPSD deployment package (in the solutions folder) or specify a custom solutions location (your drop location) when calling SPSD to tell it where to take the solutions from.
Can be called like in scenario 1.
I an previous project we built a staging web service which was running on the staging farm.
When setting the build quality of the team build to "Ready for Deployment" in TFS, a custom staging workitem was created.
In that you could choose whereto the build should be deployed and the web service on the respective staging farm was called with the droplocation as parameter.
When the deployment was finished, the deployment log was added as attachment to the staging workitem.
This is a pretty neat solution, though it require
- configuration / installation of the webservice on each staging farm
- additional configuration in TFS and adding the custom staging workitem type to each team project.
If you have any further questions or ideas, let me know :)