I have setup a trigger to detect when changes are checked-in to my team project however, FBServer doesn't ever detect these in the trigger.
I was getting an error stating that "TFS client wasn't installed" so (rather than installing it) I copied the bare-minimum for the command line TFS to work and put the path to these files into the %PATH%. This has worked for the build machines and I can now run all TFS commands from the command line.
Since then the error displayed in the FBServer status screen has gone, but no check-ins of code will fire the trigger.
I've looked in the FBServer logs, but these have not helped either. All they say is that I;ve changed the project but there are no further details.
Is there any way I can see why the trigger is failing?
TFS2012 was released after the last update to FinalBuilder Server and as such it is missing some of the new features added to TFS. For example if a system is using multiple collections instead of just the default I am sure that FinalBuilder server will not pick these up correctly.
I suggest turning on diagnostic level logging in the application log for FinalBuilder Server to see if more information presents itself.
Another option would be to shift towards using Continua instead of FinalBuilder Server. Its triggering is simpler, has a great deal more logging attached to it, and supports the latest TFS servers.
With the diagnostic logging enabled no extra information is displayed. Just this:
09:17LogReturn item to pool. 1 items now left in the pool 09:17Log-* Closes Session: b57898dc-c9ef-4de9-b666-96ae032d323e 09:17Log** Start Session: b57898dc-c9ef-4de9-b666-96ae032d323e 09:17LogObject taken from Pool. 0 left in the pool. 09:17LoggingCleaning up existing logs which are older then 7 days. 09:17LoggingCleaning up existing logs which are older then 7 days.
However, since I upgraded to .350 yesterday NONE of my triggers are firing. Timed ones, CVS ones and TFS ones.
When I manually start projects, they just sit in the queue and never get run. i.e. .350 is not working at all for me and has broken my builds - please help ASAP!
OK - so I restarted my server (not great for a PROD server) and the builds now run but I still get this error in the trigger
Unable to access Team Foundation Source Control. It appears that the Visual Studio Team Foundation Client is not loaded on this machine. If you have changed your Team Explorer installation since installing FinalBuilder Server, you may need to reinstall.
Sadly I don’t think Continua is an option for us yet - we have 3 FB licenses and can run as many concurrent builds as we want. This will be reduced to 1 in Continua and our CI tests takes a few hours to run.
Also note that restarting the FinalBuilder Server is possible through the plugin available in the control panel. This allows starting, stopping and restarting of the website.
“Sadly I don’t think Continua is an option for us yet - we have 3 FB licenses and can run as many concurrent builds as we want. This will be reduced to 1 in Continua and our CI tests takes a few hours to run.”
Understand. As FinalBuilder Server is no longer being developed I was just putting out suggestions which would provide more future proofing, and support in the long run.