Recommended path handling on TeamCity without plugin?

[thill]

We build on a dedicated Amazon AWS TeamCity server where execution of the AI portion of the build is done in an Ant script.

We develop the AI installer on the D: drive where full manual builds are done. TeamCity is setup on C: by default on AWS.

It appears that the TeamCity builds are grabbing files off D: when it should all be relative to the TeamCity work directory on C:

Is there any documentation or recommended approach or procedures for making and keeping AI paths relative so it works no matter where it is built?

Thanks very much for your time.

[thill]

Upon further research it appears to work.

The concern is/was that paths in the .aip project were referencing files outside of the project directory. In this case pulling files from the D: development drive during a TeamCity build on the C: drive.

My test was simple (on a Sunday). Got on the AWS TeamCity server desktop as Administrator and renamed the root of the development directory tree on the D: ... then fired a TeamCity build using that web site. It did not fail.

However I do not really understand how.

So - to closed this item a question please: On a TeamCity system is it alright to not use the AI TeamCity plugin. Or is it recommended to use the plugin in that environment?

Thanks!

[Daniel]

Hello Todd,

Please accept my apologies for the delayed reply.

Yes, there should not be any problem if you don't use the AI TeamCity plugin. The project paths will be relative to the project root path as long as the project referenced files from disk are on the same drive as the Project Root Path.

All the best,
Daniel

[thill]

Thanks a lot Daniel. Yes, that confirms the test I did.

[Daniel]

You're always welcome Todd.

All the best,
Daniel