Can't get Remote Run command line working

I'm having a heck of a time with the Remote Run Command Line plugin. For some reason, the Command Line Tool Settings page doesn't show any build configurations in the drop down, so I had to reverse engineer how the .teamcity-mappings.properties should look. I'm not entirely sure if I got it right. Whenever I run a build I get this:


java -jar tcc.jar run --host http://server -m "Test" -c bt10 app/models/video.rb
Connecting to "http://server" TeamCity Server... done
Checking compatibility... done
Logging in... done
Collecting changes... Collected 1 files for Remote Run
Mapping local files to TeamCity... 1 of 1 file(s) have been mapped
Preparing patch... 1 new/modified file(s)
Collecting configurations for running... run: error
Invalid parameter(s): No one of [bt10] configurations affected by collected changes



Am I missing something?

We're using 6.0 (build 15772)
9 comments
Comment actions Permalink

HI Aaron,

Could you please describe us what kind of VCS are you using in TeamCity? And some words "insvisible" configurations about.

BR,
Konstantin

0
Comment actions Permalink

We're using git. I'm not sure what you're asking in regard to invisible configurations?

0
Comment actions Permalink

The server-side tool's part cannot generate mappings for git yet. We have an issue http://youtrack.jetbrains.net/issue/TW-12309 for it. Please wote and watch.

BR,
Konstantin

0
Comment actions Permalink

Ah. Could you please update the docs to reflect this so others don't spend hours trying it to no avail?

Thanks,

Aaron

0
Comment actions Permalink

Also, the steps suggested in the bug report do seem to work. I was able to get it working, thanks!

0
Comment actions Permalink

you are welcome!

BR,
Konstantin

0
Comment actions Permalink

Hi Aaron, you might be interested in TeamCity 6.5 feature 'remote run on branch':  it allows you to do remote-run by pushing you changes to the special branch in your repository. More details here.

0
Comment actions Permalink

Very cool. Is this different from the build every branch feature I heard about earlier? And does this still leave orphaned VCS roots around or are they getting cleaned up now?

Also, is there a way to get this to become a pre-tested fast forward merge in git?

0
Comment actions Permalink

It is the same and orphaned roots are still there, but we plan to fix it in the upcoming EAP. Merge is not implemented yet, sorry.

0

Please sign in to leave a comment.