Build agent 6.5.3 on Windows 7 shows no daughter windows

Colleagues,

I had TeamCity 6.0.2 build agents installed on a Windows XP SP3 as a system service under 'Local System' account with 'Allow service to interact with desktop' set. Well, when agent is being worked, I could see some daughter windows on the agent desktop (cmd.exe and so on).

Then I've migrate to Windows 7 64-bit and tried to use the build agent 6.5.3. I've configured it at the same way as older one (run as system service, under 'Local System' account, 'Allow service to interact with desktop' set). Unfortunately, now when the agent is being worked, I see no any daughter windows at the agent desktop. I've tried to start the agent service ander the local Administrator account but result is the same.

Where am I wrong? Is there any possibility to have the build agent started as a service under Windows 7 interact with desktop?

Thanks a lot,
Dmitry A. Kirov

5 comments
Comment actions Permalink

Hi Dmitry

That's a new restriction introduced By Microsoft in Windows Vista, now services are isolated from user sessions and cannot interact with desktop.
If you rerform UI automated testing then running your scripts under a service will cause other issues.

You'll have to run build agents in interactive mode within your user session by agent.bat

Michael

0
Comment actions Permalink

Hi, Michael.

I've tried to stop and disable the service and then started agent.bat. But when this agent is building my project, I still see no daughter windows as well as any information in agent window. What should I do?

Thanks,
Dmitry.

0
Comment actions Permalink

Could you post a build log please.

0
Comment actions Permalink

Hi, Michael.

I've attached my logs. BTW, I think that cmd file (cdgn-full-sln-build2010.cmd in my case) started by simpleRunner and all other utilities/scripts called by it will be 'invisible' but if some utility/script is started by 'start' command, it will have the visible window (if the agent is started by agent.bat). Am I correct?

Thanks,
Dmitry



Attachment(s):
logs.zip
0
Comment actions Permalink

OK, I better understand your case now, thanks for the logs.

Output of command-line tools is redirected to the build log, and is not displayed in agent's console directly.
Build agent is a completely automated tool, and we do not expect you interact with the agent during the build somehow. You may have tens of agent on different machines.

Web interface is the place to monitor your builds. With MSBuild or VS Solution build steps, progress is updated automatically.
In case of comman-line step, you can update it by special service messages in echo command.

Michael

0

Please sign in to leave a comment.