Inconsistent File Checkout Behavior

We are using TeamCity 3.1.2 accessing StarTeam. From time to time (about once a week) we are seeing some odd behavior with our builds. Sometimes the files that are checked out are not always up to date. We have had numerous occasions when a user will check in two files at the same time. However, when TeamCity checks the files out, one will be up to date but the other will be an older revision. We can manually re-run the build and the exact same behavior occurs. The only way to cure this problem is to delete the source cache in the .BuildServer/system/cache/sources directory. I have actually opened that file (the cache) and seen the incorrect file version in there. Our only workaround at this point is to create a cron job that will delete the entire cache every night before our build kicks off. This does not seem like a viable longterm solution to this problem. Is this a problem anyone else is seeing? If so, has this been addressed in the 4.0 release of TeamCity scheduled to come out soon? I have turned up logging in TeamCity, but I have not seen any odd bahavior such as odd revision times or anything. I would attach the file, but it is several megs in size. Thanks!

Rick Cole
Principal Software Engineer
Pitney Bowes Business Insight

23 comments
Comment actions Permalink

Could you please tell me what versions of StarTeam server and StarTeam SDK do you use?

0
Comment actions Permalink

StarTeam 2006 R2 with SDK version 9.3.

Rick Cole

0
Comment actions Permalink

Hello Rick,

Please, enable debug logging (see instructions below), repeat the build before
and after clearing the cache and send me the following files

teamcity-activities.log
teamcity-vcs.log
teamcity-server.log
teamcity-starteam.log

In teamcity-server-log4j.xml uncomment appender STARTEAM.LOG and category
"jetbrains.buildServer.buildTriggers.vcs.starteam".
For category "jetbrains.buildServer.VCS" add line

]]>


Thank you.

StarTeam 2006 R2 with SDK version 9.3.

Rick Cole

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

I am seeing similar behavior in the 5.0 EAP build 10380, using StarTeam 2009 and SDK 11.0. Did this issue ever get resolved?

0
Comment actions Permalink

I have upgraded to TC 5.0 EAP build 10522, and I still see this problem. I have to manually clear the source cache to work around this problem.

0
Comment actions Permalink

Please describe your VCS settings in more details. Do you use quiet period in VCS trigger? Do you have two or more VCS roots pointing to the same repository?

0
Comment actions Permalink

Triggering is not enabled. I have multiple VCS roots pointing to this StarTeam project, but to different folders within the project. Here is my VCS connection URL:

starteam://hostname.nuvox.net:49201/ProjectName/ViewName/ChildFolder

Other VCS roots use similar connection URLs, but with a different child folder.

0
Comment actions Permalink

I continue to see this problem, even since upgrading to TeamCity 5.0 (build 10669). I am currently seeing a problem that I cannot resolve, even by manually deleting the cache and restarting TeamCity.

0
Comment actions Permalink

Hi,

I would like to know if there was a solution for this problem. We are currently using Teamcity 4.5.4 (build 9071) and have the same behavior where we need to delete the Teamcity cache in order to Teamcity to see the latest change. Sometime a force checkin will fix the problem but it's not always the case.

Thanks,

Marc-André Lamoureux

0
Comment actions Permalink

Hello,

Unfortunately the problem's still unresolved because of its high instability and inability to reproduce it locally. If you like to help us in this investigation (follow the logs, make experiments, accept debug paches, etc.), we would really appreciate it.

0
Comment actions Permalink

Hi,

Of course, i will send you all the log that you require do i need to activate some property in order to get more info in the log? Like you said it's hard to reproduce the problem, when this will happen again.

If you have any patches for this, feel free to send it to us and we will test them. Is there an issue already create for this?

Thanks,

Marc-André Lamoureux

0
Comment actions Permalink

Thank you.

First of all let me know your environment.

What versions of the StarTeam server and client do you use?
How is the VCS root configured? (a screenshot of the settings page would be enough)
How is the StarTeam view configured (tip, reference, etc)?
Does it have references to files/folders of other views?
What permissions does the StarTeam user account have?

If you feel unconfortable providing this information in the public forum, you can send it to teamcity-feedback@jetbrains.com

Have you noticed any pattern/regularity of the problem appearance?

0
Comment actions Permalink

No i did not notice any pattern yet.

I will get the information that you requested and send it by email.

Thanks

0
Comment actions Permalink

We continue to see this problem, though rarely, running TC 5.0.2 (build 10784) and StarTeam 2009. Clearing the cache does not fix it, I have to check-in an additional change for it to pick up the original change.

0
Comment actions Permalink

Hi again, Bruce.

I remember you mentioned that one of these files (tcbuild.xml) is shared from another view.
Were all the files not being updated likewise shared?

Were the corresponding changes also not present in changelists each time the problem appeared?

0
Comment actions Permalink

I have seen it now with other non-shared files as well, so I now believe that that doesn't have anything to do with this issue. Don't know if the files in question were in the changelist or not. I just know that the changes do not show up as pending for the build configuration.

I will also volunteer to try out any patches that you folks can come up with to help debug or address this issue.

0
Comment actions Permalink

Thank you.
I'll prepare a patch with total logging in the beginning of the next week. And you'll need to be on the watch and send me the logs. OK?

Are you going to upgrade to 5.1?

0
Comment actions Permalink

On our side we are using Teamcity 4.5.4 (build 9071). We do not plan to upgrade to version 5 yet. Will the patch be available for that version to?

Thanks.

0
Comment actions Permalink

It's up to you, though we always encourage it.

I'm asking because I need to know which code branches I'll have to modify in parallel.
I'll try to make the patch for 4.5.x too.

0
Comment actions Permalink

Gentlemen,

I've been out due to an illness until today. The whole next week I'll be at the JAX conference, Germany.
I'm going to spend the rest of this week working on the patch, but without any guarantee of completing before my departure because of switching between many tasks.
So please be patient. Anyway, if not this week, I'll finish the work when I get back from Germany.

I can assure you I won't leave you alone with your problem.

Thank you.

0
Comment actions Permalink

Hello,

The patch is ready. Could you please send an email to teamcity-feedback@jetbrains.com so that I can send it by replying.

0
Comment actions Permalink

The problem has been fixed in 5.1.2. Please upgrade.

Regards!

0

Please sign in to leave a comment.