TeamCity fails to recognize updated build file!

Hi,

I have been using TeamCity for over six months now.
Of late, I have observed a peculiar issue. I made some changes in the build.xml so that the build script is compatible for both windows and mac environment.
Also, I added an Ant command line parameter "propertyfile".

TeamCity never picked up the new build.xml, and also it seems that its not able to read the commandline parameter either.
For now, I have worked this around by specifying the property file in the build script itself and putting the build script directly into the TeamCity Build Runner configuration.

Has anyone else seen this kind of a problem? Is this a bug that has been logged already?

Thanks,
Gourav



10 comments
Comment actions Permalink

Please provide more details. What version of TeamCity do you use? What version control system is configured in your project?

0
Comment actions Permalink

I first saw this anomaly in TeamCity version 3 and thats when I moved to version 4.0.1 (build 8171) and the issue was still there. This looks like some kind of environmental abnormalities, unfortunately though I was not able to figure it out.
The CVS is P4, Release 2007.

0
Comment actions Permalink

Did TeamCity detect your change in build.xml? Does the change is shown in the web UI? Do you have checkout rules configured in your project?

0
Comment actions Permalink

No Pavel, TeamCity doesn't pick up modified build.xml, it somehow continues using the old one, when I make the changes in the agent's checkout directory. Besides this, the question that haunts me is why TeamCity isn't able to pick up the build property file for ant?

I haven't set any checkout rules either.

0
Comment actions Permalink

I think I do not fully understand you. Your build.xml file is under the version control system which is Perforce, right? So if you make a change in this file and commit it in Perforce does TeamCity detects this change and shows it in the web UI for your build configuration?

0
Comment actions Permalink

I can't check anything into my VCS until I find that it works, so I changed the file (build.xml) on the checkout folder on the agent itself. Changes are picked up from TC, but the change in the build script not present in the VCS but only local to the Build Agent are not picked up when TC invokes a build.

0
Comment actions Permalink

Please check that option "Clean all files before build" on the Version control settings of the build configuration is turned OFF. If not then TeamCity will always take the last revision of the build.xml committed into the Perforce.

If you need to check how your build.xml works but do not want to checkin it into the Perforce the most convenient way is to use personal builds.

0
Comment actions Permalink

Thanks for your help Pavel, I will try this out

0
Comment actions Permalink

Thanks Pavel, for your help
I can't say that my problem is completely solved. However, having checked in the build.xml, the correct one is being picked up, but the latter part of my problem still exists.
TC still won't recognize the ant command line parameter that I am placing for it. This option works on command line though. Here's a snapshot of the parameter I am using.

PropertyFile.bmp

0
Comment actions Permalink

I've just checked it on my side and it works just fine. Please try to run Ant in verbose mode, i.e. add -verbose parameter to this field. Also please check that property file is in the checkout directory on the agent.

0

Please sign in to leave a comment.