Problem with msbuild task on agent running on separate machine

Hello,

I have a problem with our msbuild script. I recently added another machine with a separate build agent to our build environement.

It appears that the command line parameters specified in the msbuild build runner configuration isn't passed to msbuild on the new machine. Everything else works as expected.

We have a command line parameter like:
/p:PrepareTarget=True

From the build messages:
Target "MyTarget" skipped, due to false condition; ('$(PrepareTarget)' == 'True') was evaluated as ('' == 'True').

The build agent that is running on the machine with the TeamCity server does not display the same behavior.

Anyone have any hints on what is happening?

Thanks for any help,
Hakon

6 comments
Comment actions Permalink

What is the server version? Do you use msbuild runner?

Thanks!

0
Comment actions Permalink

Could you please try to define system property for the build configuration called system.PrepareTarget on the 'system properties and environment' page of build configuration.

Thanks!

0
Comment actions Permalink

Yes, we are using the .NET 3.5 MSBuild runner.

We are using TeamCity Enterprise Version 3.1.2 (build 6881).

/Hakon

0
Comment actions Permalink

I experience the same behavior when setting the system property: The property is ignored in the build process.

The TeamCity server is running on Windows Server 2003 32-bit and the new agent is running on Windows Server 2008 64-bit. I don't know if that may be a source of the problem...

/Hakon

0
Comment actions Permalink

Did you get a chance to investigate this problem?

0
Comment actions Permalink

Sorry for long the delay. The question is still actual with latest TeamCity release?

Kind regards,
Marina
0

Please sign in to leave a comment.