Legacy TeamCity VS Addin not working (TC 9.1.3)

Avatar
Permanently deleted user
Created
Hello,the Legacy TeamCity VS Addin fails to start with the message:Selected build configurations can not be started in one remote-run:“Compile”: Submitted changes cannot be applied to the build configuration.This was working fine with TC 8.1.5..The project uses VS2012 with R#7.1 and svn.What could cause the problem?Regards,Helios

Votes

0

Share

8 comments
Avatar
Alina Mishina
Created

Hello,

The message "Submitted changes cannot be applied to the build configuration" suggests that TeamCity cannot understand how to apply the changes to the working copy of the build belonging to the build configuration selected. Most probably this is the result of misconfigured VCS settings. Have any VCS settings changed? Please check that everything is configured correctly. If you believe the operation should be allowed by TeamCity, please provide the following information:
- Full VCS settings of the build configuration selected (VCS root settings + checkout rules)
- TeamCity VS addin plugin settings
- The full paths of the files that are selected for the remote run

0
Avatar
Permanently deleted user
Created
Hello,we just upgraded from 8.1.5 to 9.1.3 and as reported in the following issue https://devnet.jetbrains.com/message/5559918#5559918 there were also changes (not visible in the UI) done in all VCS roots. (during the upgrade and not by a user)The VCS roots look ok and they work fine with current (not private) changes. The local checkouts are still at the same place and the settings in the VS Addin are the same as in 8.1.5 (see attachment). The full path of a file I just tested is C:\repo\Test\trunk\UI\Properties\AssemblyInfo.cs.Thanks,Helios

Attachment(s):
VSaddin.PNG
0
Avatar
Permanently deleted user
Created
Comparing the changes of an svn vcs root shows that in 8.1.5 the xml is referencing "../../../project-config.dtd" in 9.1.3 this was removed and it contains now a uuid. Could this be the reason why private builds don't work anymore? Doing a clean checkout locally doesn't solve the issue. Probably this is the reason why all projects did a clean checkout after the upgrade. (see other thread)
0
Avatar
Permanently deleted user
Created

Anyone successfully triggered private builds using the legacy TCVSAddin with VS2012 and svn with TC 9.1.3?

0
Avatar
Permanently deleted user
Created

The TeamCity VS Addin log shows two exceptions:

--- EXCEPTION #1/2 [WebException]Message = “The remote server returned an error: (407) Proxy Authentication Required.”
--- Outer ---
--- EXCEPTION #2/2 [LoggerException]Message = “The remote server returned an error: (407) Proxy Authentication Required.”

Anything changed regarding proxy?

0
Avatar
Alina Mishina
Created

Hi,

Sorry for delay. Yes, since 9.0, TeamCity tries to establish WebSocket connections between the browser and the server for the UI updates. If you have a proxy server (like nginx) in front of the TeamCity web UI, make sure that the proxy is configured properly to support WebSocket connections. Please find more details in the upgrade notes.

0
Avatar
Permanently deleted user
Created
Not sure if this is related to the issue with the TC VS Addin. According to the upgrade notes "...If the proxy is misconfigured or does not support the WebSocket protocol, a server health item will be shown for TeamCity system administrators..." there is no such server health item listed.
0
Avatar
Permanently deleted user
Created
A server reboot solved the issue.
0

Please sign in to leave a comment.