As per the development team’s requirement we might end up creating TFS Server plug-ins to automate various processes. Since the TFS server plug-ins would intercept each and every (subscribed) events, we need to keep the TFS Server plug-in process very quick, so we always extend the TFS Job to perform the actual work on the background.
I have outlined the step for how to deploy those plug-ins and job extensions on the TFS servers.
TFS Server Plug-in
Caution: TFS services will be restarted whenever the plug-in assemblies are copied on TFS app server.
Copy the TFS plug-in assemblies to <System Drive>:\Program Files\Microsoft Team Foundation Server 2010\Application Tier\Web Services\bin\Plugins folder on each TFS app servers
TFS Job Extension
Fresh install
Copy the TFS Job extension assemblies to D:\Program Files\Microsoft Team Foundation Server 2010\Application Tier\TFSJobAgent\plugins folder on each TFS app servers
Update
1. Stop “Visual Studio Team Foundation Background Job Agent” on the TFS App Server.
- Copy the TFS Job extension assemblies to <System Drive>:\Program Files\Microsoft Team Foundation Server 2010\Application Tier\TFSJobAgent\plugins folder on the TFS app server
3. Start “Visual Studio Team Foundation Background Job Agent” on the App server
hi adhi
ReplyDeletecan u tell more about "I have customized Team build/MS build to compile Java applications, run JUnit tests and etc. These customizations helped the client to have unified build process for Microsoft .Net and Java applications."
i would like to know if TFS is good for java development.
Hi Ketan,
ReplyDeleteWe have been using Team build + Ant for Java development for last four years. It is working good, obviously we did lot of customizations. Now there are out of box tools/plug-ins available for java builds.
If you are using TFS for source control for Java development then Team Build + Ant is the way to build java development.
Although the page references 2012, the folder structures are specific to 2010...
ReplyDelete