Please add support for perforce.

Let's add "user-agent" the same way it is currently made for all IDE plugins.

Example for Visual Studio:
User-Agent: MS Visual Studio/14.0 (TeamCity Integration 2017.3.2 )

We need to find suitable build configurations by sending repository info and list of modified files.

Currently the extension don't filter suitable build configurations - it shows all the configurations under the root project. It should be fixed.

Under the command section there is the following typo:
"The extension provides several commands for interacting with Team City API. In the Command Palette (F1), type TeamTity and choose a command."

Currently the TeamCity extension shows suitable build configurations as a plain-list. It would be great to add a hierarchical structure to a suitable build configuration view which allow to hide build configs under projects and expand them.

According to https://stackoverflow.com/questions/29971624/visual-studio-code-cannot-detect-installed-git there is a property "git.path" in the "user settings", which could specify a particular git path for vscode. The extension should check this path during GitSupportProvider initialization.

After the running personal build we need to commit modified files.

My team uses TeamCity to run builds. Our code is committed via git, then we manually kick off builds when we are ready. That will eventually become more automated, but for now thats how we do it.

I've successfully installed the plugin and logged into my TC instance. However nothin shows up in the list. I expected to at least see the various Projects and their build statuses.

If that support isn't built in yet, then thats my feature request. If it is and I'm just missing something please let me know. Thanks in advance. Excited to see VS Code support in general.

We need to have repository information to find a suitable build configuration.

Since VS Code 1.16 it's possible to use multiple SCM provides, so we could do that: https://code.visualstudio.com/updates/v1_16#_source-control

When attempting to log in, I am receiving an error message
(TeamCity) Unknown XML-RPC tag 'TITLE'

The authentication doesn't work and every time I attempt to add my credentials I get this same message.

Installed version: teamcity-vscode-extension-1.0.0-beta.6.vsix
MacOS: 10.13.5 (High Sierra)
VSCode: 1.24.0

From the README.md

Type "Install from VSIX" and choose the tc.vsix file in the opened dialoge box

Where does one get tc.vsix? Clearly I'm missing something obvious here.

Separate all data requests via window.showQuickPick into another module

Following tasks should be done for Preview Version of TeamCity extension for VS Code.

Integration with existing VS Code SCM Providers

• Get list of modified files from Git Provider #2
• Get list of modified files from TFVC Provider #3
• Get repository info from Git Provider #4
• Get repository info from TFVC Provider #5
• Commit modified files on behalf of SCM Provider #6

Integration with TeamCity APIs

• Authentication via login/password #7
• Find suitable build configuration #8
• Queue personal build with modified files #9
• Subscribe on IDE notifications #10

Dialogs in TeamCity VS Code Extension

• Login dialog: server URL, login, password
• Remote run dialog: show list of modified files & suitable build configurations
• Custom settings for remote run build: put on top, override configuration parameters
• My changes dialog: list of commits and affected build configurations & statuses
• My investigations dialog: list of investigations in the project structure

Since this plugin is deprecated, is there any alternative to integrate teamcity into vscode?

We need to have a list of modified files to trigger a personal build.

Important: The preferred way of running personal builds with Git on TeamCity is to use Branch Remote Run Trigger which creates builds on branches in TeamCity.

Please refer to the wiki page for more information about Git support.

The extension should store session even after restarting VSCode.
We should implement storing user credentials on a disk.

Does this plugin support github authentication to teamcity?
(my company uses teamcity, but I'm using SSO via github, I can't seem to setup the plugin)

Asking if this supports SVN, and if not, are there any plans for it?

Providing a https url to sign in results in (TeamCity) socket hang up. Looks like default is port 80 and this can't be overriden.

We should be able to trigger personal builds in TeamCity for specified build configurations by sending request with a list of modified files.

We need to have a list of modified files to trigger a personal build.

Currently when user successfully executes a Remote Run command with multiple SCM providers,
the extension executes a post commit logic for each SCM provider.
Also we should think of messages for checkininfo for each commit.

From my point of view it's not correct.

We need to subscribe on notifications for logged in TeamCity user to display them in IDE.

Now it works in Intellij, so we could also try to support it.

We need to have repository information to find a suitable build configuration.

Hello,

I have installed the recent version (0.0.3) of the plugin into VS Code 1.19.2.
I have TeamCity Enterprise 2017.1.4.
I can successfully connect from the plugin to my TC server.
Both my local working directory (opened in VSCode) and the TeamCity build project use the same (remote) Git repository.
I have admin rights on the TC's build project.

Unfortunately the uncommitted changes, which I make in VSCode, don't appear in the TeamCity view of VSCode (but I see them in the VSCode "Source Control" tab).
The "TEAMCITY: Refresh files..." doesn't make any change.
As a result I'm getting the error Please, choose at least one changed resource and I can't send my changes for the remote build.

The only message from TeamCity in the Output is You are successfully logged in. Welcome to the TeamCity extension!.

How can I make the plugin to detect changes in my local workspace?

Here is my plugin debug log:
teamcity-extension.log

We need to access TeamCity to authorize in its APIs