This may be more a Robohelp issue but I am having difficulty in an executable for Adobe Robohelp not triggering when running in a command prompt build step in Team City.
Performing the same step on the agent desktop manually works fine.
Performing the same step as a Windows Scheduled task in a command prompt on agent desktop works fine.
Performing the same scheduled task in a command prompt build step also works fine (yes the task being triggered by Team City Command Prompt build step is indeed triggering the executable to run correctly).
I would really like to be running the exe directly from a Command Prompt build step (or PowerShell) in Team City so I don't need to sleep a set period of time while i wait for exe to finish.
Could there be something I can review to further diagnose this issue? Is there a way Team City is running command-line build steps that consider them interactive or something?