Pre-Tested (Delayed) Commit - Problems Executing Remote Run
Hi,
I installed TC plugin in Intellij, and configured a project in TC. Following the instructions for Pre-Tested (Delayed) Commit, I was trying to execute Remote Run but got the following error message:
Failed to collect VCS paths: Cannot determine base revision. Please check the current branch has tracking branch that is watched by TeamCIty.
I properly configured VCS with the correct git repository and chose "Branch Remote Run Trigger" as recommended in Pre-Tested (Delayed) Commit documentation.
I also added the pattern in Edit branch specification to monitor other branches other than the default.
There is one issue in YouTrack that says that this might be caused by changes that contain a file that doesn't belong to any module, but I don't think this is the case.
Any guidance would be much appreciated.
Nivi
Please sign in to leave a comment.
Hi Nivi,
the message is telling you to ensure that the branch you are currently working on is monitored by teamcity, a.k.a. is part of the branches listed in the "Branch specification" of the VCS Root. Could you check whether this is the case?
Hi Denis,
Thank you for your guidance.
I specified +:refs/heads/remote-run/* in Branch specification when I first created the project. I monitored some of the branches and saw that Team City refers to the remote run ones as +:refs/remote-run/* so I changed it accordingly. Remote run through Intellij still doesn't work.
In addition, I was able to get TC to recognize branch change but it put it in pending and never ran the build. What was I doing wrong.
Hi Nivi,
sorry for the delay, I have been asking around with the people involved in the module in particular. First, remote run is only available for the default branch, so please keep that in mind.
The typical solution for this problem is to simply push a commit to the default branch, as sometimes the commits need to be both in the VCS Root in teamcity and in the local machine. If the commits that the plugin is using to take as reference don't match in one of the two places, the issue might appear, and this often happens because the last ones haven't been pushed yet. Could you try?