TeamCity Support | JetBrains

Pavel Sher

Total activity 2676
Last activity October 23, 2024 12:19
Member since March 06, 2008 23:06
Following 0 users
Followed by 1 user
Votes 0
Subscriptions 90

Created July 20, 2011 09:16

As I understand you suspect that TeamCity will use wrong revision if parameter in VCS root changes. Can you reproduce this issue locally?
- 0 votes
Created July 21, 2011 11:18

I see that you are using TeamCity 6.5 (build 17834), I would try to install latest bugfix release 6.5.2 (build 17935) as it contains some related fixes.
- 0 votes
Created August 04, 2011 15:47

We understand that this is a critical issue, and we are trying to reproduce it.Could you please tell me, do you use this parametrized VCS root in other build configurations? Do you use custom build...
- 0 votes
Created December 24, 2010 07:36

It seems like the error occurrs when TeamCity tries to convert .BuildServer/config/jabber-config.xml file. This file is either empty or is not well formed xml. It is likely that it was modified by ...
- 0 votes
Created December 24, 2010 10:24

Please try to rename this file or remove it from the .BuildServer/config directory and start TC 6.0 again.
- 0 votes
Created December 27, 2010 04:52

Well, from the source code I can see that the problem occurred becuase of empty jabber-config.xml. Unfortunately the exception itself does not give a clue on the error cause.
- 0 votes
Created June 04, 2009 20:18

This can be easily done by IDE (for example, IntelliJ IDEA can show you such list). Why do you need this feature in TeamCity?
- 0 votes
Created August 31, 2011 17:11

It seems you've faced this bug: http://youtrack.jetbrains.net/issue/TW-18026Because of it if a parameter is defined incorrectly in at least one of build configurations TeamCity will show errors for...
- 0 votes
Created August 31, 2011 16:00

We plan to release TeamCity 6.5.4 in the nearest future (most likely on the next week). Our current plan for TeamCity 7.0 release: February 2012.
- 0 votes
Created August 29, 2011 13:29

This message means that checkout directory contains more recent revision than the revision associated with a build which is going to be executed in this checkout directory. Did you specify custom c...
- 0 votes