search

JetBrains / teamcity-vscode-extension

TeamCity integration for Visual Studio Code (VS Code)
MIT License
29 stars 6 forks source link

The plugin doesn't detect changed files: "Please, choose at least one changed resource" #23

Open o7g8 opened 6 years ago

o7g8 commented 6 years ago

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

rugpanov commented 6 years ago

@o7g8 , hi! Thank you for your request. From log file it seems you didn't stage your changes and that's why the extension probably can't find them. Please can you verify whether files were staged or not and reply in this ticket. In case they weren't try to stage them and execute the "Select Files For Remote Run" command.

o7g8 commented 6 years ago

@rugpanov Thank you for your quick answer!

I have staged a file and indeed, I was able to see my staged file in the TEAMCITY view. So it's a step forward at least :)

However after I execute Find Suitable Build Configurations I don't see my build configuration in the TEAMCITY view. In my case the view shows only top-level node of my TC project tree (which contains 200+ builds). Here is the tail for the plugin log:

2018-01-17T08:37:38.958Z - debug: [02196] GitSupportProvider#getLocalResources: 1 changed resources was detected 2018-01-17T08:37:38.958Z - debug: [02196] GitSupportProvider#getRequiredCheckinInfo: absPaths is notempty 2018-01-17T08:37:39.138Z - debug: [02196] GitSupportProvider#getRemoteBrunch: remote branch is origin/hybrid-build 2018-01-17T08:37:39.389Z - debug: [02196] GitSupportProvider#firstRevHash: first month revision is 7dcb8f348cd709f438afe6d3d99b719a44b65c3f 2018-01-17T08:37:39.505Z - debug: [02196] GitSupportProvider#getLastCompatibleMergeBaseRevision: last merge-based revision is 723e4351f48ccb7b254716c2306e0bee2dbef11a

2018-01-17T08:40:45.501Z - info: [02196] GetSuitableConfigs#exec: starts 2018-01-17T08:40:45.501Z - debug: [02196] XmlRpcBuildConfigResolver#requestConfigIds: changedFiles: jetbrains.git://7dcb8f348cd709f438afe6d3d99b719a44b65c3f-723e4351f48ccb7b254716c2306e0bee2dbef11a||/IMS/build.cake 2018-01-17T08:40:45.609Z - debug: [02196] XmlParser#parseBuilds: start collect projects 2018-01-17T08:40:45.614Z - debug: [02196] XmlParser#parseBuilds: collected projects: 2018-01-17T08:40:45.614Z - debug: label=IMS, collapsibleState=1, children=[] 2018-01-17T08:40:45.614Z - info: [02196] GetSuitableConfigs#exec: finished

The Plugins OUTPUT view shows:

You are successfully logged in. Welcome to the TeamCity extension! Build for change #133126 has "CHECKED" status. http://mi6/viewModification.html?modId=133126&personal=true Build for change #131372 has "PENDING" status. http://mi6/viewModification.html?modId=131372&personal=true Build for change #131249 has "PENDING" status. http://mi6/viewModification.html?modId=131249&personal=true Build for change #130745 has "PENDING" status. http://mi6/viewModification.html?modId=130745&personal=true

I think the issue is evident in the line 2018-01-17T08:40:45.614Z - debug: label=IMS, collapsibleState=1, children=[] of the plugin log - I would expect some children there. The "path" to my build project on the TC server is IMS\Migration\PoC\Release: Hybrid Build2.

What can I do in order to make my build configuration available for selection in the plugin?

rugpanov commented 6 years ago

@o7g8 , hi! Unfortunately, in this case I suppose you have found a bug. Let's try to understand what has happened. First of all, is "/IMS/build.cake" correct relative path of your file from the root directory?

Also I prepared a version of the extension with extra logging which should help me to understand whether build parsing works fine or not: teamcity-vscode-extension-0.0.3.1.vsix.zip

I would appreciate if you collect logs with this version of extension and attach the log file to your reply.