Forum Discussion
If it's part of the build process, you probably need to start that as an interactive session.
This isn't something I've ever done myself, but this looks like it might be helpful?
https://msdn.microsoft.com/en-us/library/ms181712(vs.110).aspx#interactive
- Florian_Hofmann8 years agoContributor
Thanks a lot, this looks like it's worth trying...tomorrow.
I'll keep you updated if it finally solved the problem and mark your post as answer if it does.
- tristaanogre8 years agoEsteemed Contributor
Starting it as interactive is the first step. However, you will still need to make sure that there is a user session logged in with some sort of active UI available. You don't necessarily need to have a monitor up and running or anything like that but you can't click on a UI if there is no UI.
- Florian_Hofmann8 years agoContributor
Thanks a lot, I can now organize and run my tests from Team Foundation Server.
But as Tristaanogre pointed out, I still have to have an active GUI...which I expected, since it was the same when I used to run the tests from batch scripts via the Windows task schedule.
Thing is: The way I understood it, Team Foundation Server itself should be able to open and keep a user session with GUI access, since it uses the build PC as a user to log on to the server where the tests are executed - I thought this would remove the need of a human user logged onto the test execution server.
Anyone can help on this please?
Thanks in advancem
Florian
Edit: The message is "The job has been abandoned because agent xxx-CI-Agent did not renew the lock. Ensure agent is running, not sleeping, and has not lost communication with the service.", which might be a TFS issue of its own, rather than an error in my approach...
Related Content
Recent Discussions
- 2 hours agoSubhraDas