TeamCity Support | JetBrains

Kirill Maximov

Follow New articles and posts New articles, posts, and comments

Total activity 2298
Last activity March 09, 2020 11:30
Member since March 15, 2006 04:04
Following 0 users
Followed by 0 users
Votes 0
Subscriptions 881

Kirill Maximov commented, March 09, 2020 11:30
If I'm not mistaken, the problem should be less critical after the fix of https://youtrack.jetbrains.com/issue/TW-60588. I.e. TeamCity agent should re-check for the docker presence periodically sin...
- 0 votes
Kirill Maximov commented, March 03, 2020 17:30
Hmm. If your server is running inside a docker container (did not realize that), the p4 is not available to the server. To make it available, p4 should be installed inside the corresponding docker ...
- 0 votes
Kirill Maximov commented, March 03, 2020 14:02
Official comment
Guys, sorry for the problem. I've created an issue in our tracker - https://youtrack.jetbrains.com/issue/TW-64796 and attached a perforce.zip plugin with extra debug information which could probabl...
- 0 votes
Kirill Maximov commented, March 02, 2020 17:06
Thanks for the log. As a dumb idea - could you please restart the TeamCity server? I suppose there could be a cache which keeps invalid output of the `p4 info` command.
- 0 votes
Kirill Maximov commented, March 02, 2020 16:49
Hi, could you please run `p4 info` command and attach it here? TeamCity is looking for the line "Server date:" in the output, probably p4 output does not match. Regards,
- 0 votes
Kirill Maximov commented, January 27, 2020 16:41
Hello, The per-directory .svn directory was used in subversion 1.6, since subversion 1.7 only one .svn directory is created: http://subversion.apache.org/docs/release-notes/1.7.html#single-db ...
- 0 votes
Kirill Maximov commented, December 06, 2019 18:32
Official comment
Hello, I'm really sorry for the problem. Please vote/watch this issue: https://youtrack.jetbrains.com/issue/TW-60588 and probably this one as well: https://youtrack.jetbrains.com/issue/TW-61211 ...
- 0 votes
Kirill Maximov commented, October 16, 2019 09:32
I'm afraid your guess is wrong. When TeamCity starts build agents using agent.sh script from the plist file, it does not use plist mechanics on upgrade. So the reason of agent not coming back after...
- 0 votes
Kirill Maximov commented, October 16, 2019 07:48
So, the upgrade process does not touch /Users/builduser/Library/LaunchAgents/*.plist files, and that's correct. So after the upgrade, if you reboot the machine, both build agents will start as expe...
- 0 votes
Kirill Maximov commented, October 16, 2019 07:12
Does it change the label in `/Users/builduser/Library/LaunchAgents/jetbrains.teamcity.BuildAgent2.plist`?
- 0 votes