7 comments
Comment actions Permalink

Hi,

Could you please describe your use case in more details?

We have Command Line Remote Run plugin, would it be useful for you?
0
Comment actions Permalink

Hi Alina,

I don't mean doing a remote run from a command line. I mean that existing TeamCity build configs that include a command line build runner as one or more of its build steps are not available to IntelliJ as a remote run option. We have either maven build runners or command line build runners or a combination of both in our build configs. The only build configs available to IntelliJ are ones that only include maven build runners as build steps.

-Dave

0
Comment actions Permalink

Hi,

Sorry for delay. In IDEA all suitable build configurations should be available, not depending on runner type. Could you please provide VCS settings in both IDEA and TeamCity, are used VCS roots the same? Do you see commits in TeamCity UI if you push them through IDEA?

0
Comment actions Permalink

The VCS paths (svn 1.6) are exactly the same in TeamCity and IntelliJ. Developers see commits in the TeamCity UI if they are committed through IntelliJ.

-Dave

0
Comment actions Permalink

Hi,

What VCS checkout mode do you use for affected build configurations? Remote run does not work with "do not checkout automatically" mode.
If you do not use this mode, then please create issue in our tracker and attach all teamcity logs and also IDEA logs while reproducing the issue.

0
Comment actions Permalink

The VCS checkout mode for the TeamCity build config is: Automatically on agent (if supported by VCS roots).

0
Comment actions Permalink

Hello,

This turned out to be user error. When the VCS roots match in IntelliJ as well as TeamCity, the builds are indeed available to IntelliJ as remote runs.

-Dave

0

Please sign in to leave a comment.