Running gazebo from TeamCity (Windows)

Question

I have a set of build steps in a project (Team City 9.0c)

One of them runs bower install , which is a simple command-line execution without parameters.

Bower is installed on the system (I can just start it from the command line on the machine), but I get the following error

[10:47:35][Step 2/7] Starting: D:\TeamCity\buildAgent\temp\agentTmp\custom_script8385462966123630321.cmd [10:47:35][Step 2/7] in directory: D:\TeamCity\buildAgent\work\5d43cd6017ab83d4\website\Amaze.Web [10:47:37][Step 2/7] 'bower' is not recognized as an internal or external command, [10:47:37][Step 2/7] operable program or batch file. [10:47:37][Step 2/7] Process exited with code 1 [10:47:37][Step 2/7] Step Bower (Command Line) failed

I saw this before when PATH did not specify the location of the npm binaries in c:\users\xxxx\roaming\... , so the TC user cannot find them, however PATH correct.

Both npm and grunt work successfully. What could be the reason for this?

Answer 1

Is the path variable a user-defined variable? If so, it should be a system variable that will be used by the TeamCity process.

Answer 2

You did not specify which accounts the build agent runs on.

I had a similar problem and my build agent worked using the local system. I had to create a special Windows user account for the teamcity build agent, in the build script I added

 npm install -g bower set path=%path%;c:\path_to_bower_for_this_user;