setting up Credentials in Toolchains automatically creates another Deployment profile


I have a SFTP remote set up at "Build, Execution, Deployment | Deployment". Let's call this "test server".

Now I want to set up "Build, Execution, Deployment | Toolchains" so that I can build and run on "test server". 

I created a new profile under "Build, Execution, Deployment | Toolchains" by clicking "+" at the bottom, chose "Remote Host" option, and set up "Credentials" to the server. It was wierd that I didn't see credentials to "test server", since I have already set it up under "Deployment" , but I went a head and re-established the "Credentials". However, once I do that, there is another profile under "Build, Execution, Deployment | Deployment" which is a near-dubplicate of the "test server". Let's call this newly created profile "test server2". "test server2" has different file mappings compared to "test server", but everything else seems to be the same.

So why is "test server2" created when I am using the same credentials as "test server"? Is there an option to chose from one of the profiles under "Build, Execution, Deployment | Deployment" when I am trying to set up "Credentials" in "Build, Execution, Deployment | Toolchains"?

1 comment


In the current implementation the setup scenario is reverse: first a user creates a connection entity for the remote toolchain, then CLion automatically puts it in the list of server access configurations in Settings / Preferences | Build, Execution, Deployment | Deployment.

Feel free to comment or upvote in order to get updates. See if you are not familiar with YouTrack.


Please sign in to leave a comment.