Using Proxy server with Plastic cloud

[darrensocks]

Hi,

The documentation seems to suggest the proxy server can be used with Plastic cloud, but I can't seem to find any information of how to configure this.

Does the proxy server support the cloud?
Can the teamcity plugin be configured to use the proxy?

Thanks

[calbzam]

Hi,

Firstly, it says to download the Proxy Server Installer from your downloads page. There is no Proxy Server Installer as far as I can see in your downloads, only the portable proxy server. When I download and extract that, it appears to just be a normal server?

After downloading the .NET Core Proxy server from www.plasticscm.com --> Downloads --> More installers --> Proxy server .NET Core bundle

1) Copy the following files from the "config_samples" folder to the binaries folder:

• plasticcached.conf 
• plasticcached.log.conf 
• plasticcached.network.conf

2) In "plasticcached.conf " you set the output path for the output cache folder. 
    In "plasticcached.network.con" you set the port.

3. You can run the proxy in console mode via this command:

C:\Users\albaz\Downloads\PlasticSCM-10.0.16.5432-win-x64-proxy-server-netcore\server>plasticd.exe proxy
plasticcached daemon up. 10.0.16.5432 313 ms startup time. Data path: C:\tmp\cache

4. In order to install the proxy as a Windows service:

sc.exe create plasticscmservernetcoreproxy binPath= "C:/PathTo/plasticd.exe proxy"

The proxy server by default listens on the 8085 port: YOURSERVER:8085

Could you rename the following file, restart the GUI and check if this way you can enable the proxy?
C:\Program Files\PlasticSCM5\client\cloudedtion.token

 

- At the end of the day, The TeamCity plugin just internally runs "cm" commands so you could configure the Plastic client intalled in the TeamCity machine to use the proxy server.

Regards,
Carlos.

[darrensocks]

Thanks, this looks like it worked. 

Renaming the token file, did seem to cause a few issues with the cloud login but after a few tries seemed to sort itself out.

[darrensocks]

Although the visual editor is now working (with the cache) It looks like TeamCity won't connect to the server.

When I try to "Test Connection" it never seems to return a result. I did at some point have this working (before I setup the proxy). I've copied "client.conf" to the client folder as suggested in another post - This I think got it working but that was before I started using the proxy setting. I've tried removing the proxy server setting but still doesn't seem to work.

[calbzam]

Hi,

- I'ts very important that you copy the "client.conf" to the "client" binaries folder. I guess the TeamCity server is running with a different user taht your Plastic user (eg: SYSTEM user) and after copying the "client.conf" to the binaries folder, all the machine users will be using the same client configuration.

- If you have any "cm.exe" process running in the TeamCity machine, please kill them so it's restarted with the new client configuration.

- Let's try to make it work first without the proxy server. The proxy server is just a field inside the "client.conf":

<CacheServer></CacheServer>

Regards,

Carlos.

[darrensocks]

Hey both, agent and TeamCity server are running on the same machine (not sure if that makes any difference). Both look they are using SYSTEM user.

I've made a build step which was just 'cm lrep'

The output was the following (*** the @cloud name but the team name is correct)

Quote

Select the system you want to use to sign in to the organization: **********@cloud
14:12:06   0 - unityid
14:12:06   1 - email
14:12:07   Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your system [0-1] Select your sy....................

So I'm guessing it's trying to auth me again?

A build step with the command 'cm whoami' outputs my user email correctly so it does seem to picking up some details correctly.

If I just do 'cm lrep' using a command prompt (same machine) it returns correctly.

 

[calbzam]

Hi,

- Could you also copy al the *.conf file from your user folder to the "client" binaries folder?

- If you are paying customer, we can arrange a meeting for further debug.

Regards,

Carlos.

[darrensocks]

Copying the *.conf files to the "client" binaries got me a bit further and allowed the test connection to come back success, although it didn't seem to be fully connecting.

After some more poking around (I wish I could say what the solution was), everything now seems to be working correctly with the proxy server and TeamCity.

 

Thanks for your help!

[Cookseyyyyyy]

Just jumping on this old thread as I'm about to set up the proxy cache. 

 

I'm having trouble finding the installer however. Has it been removed or is it a part of another package now? Attached is a screenshot of the options I have for download.

[Erik S.]

On 2/17/2022 at 1:57 PM, Cookseyyyyyy said:

Just jumping on this old thread as I'm about to set up the proxy cache. 

 

I'm having trouble finding the installer however. Has it been removed or is it a part of another package now? Attached is a screenshot of the options I have for download.

I know this is an old post and my answer is probably not relevant to you anymore but I want to leave a reply here in case someone else finds it useful in the future, since I was also a bit confused about this myself when setting up a proxy.

The answer is, the proxy server is, at the moment of writing, packaged together with the server package for Windows and MacOS. To start a proxy, run the server executable with proxy-specific arguments. There are also Windows-only arguments available to run proxy as a service. See the docs for more info.

[redicisfollows]

If your system is configured to use a proxy server, Plastic SCM may automatically use those settings. Ensure that your system's proxy settings are configured correctly. Some version control systems allow you to configure proxy settings at the client level. Check Plastic SCM client configuration settings for any proxy-related options. If you are using a TeamCity plugin with Plastic SCM, check the plugin's documentation for proxy configuration options. TeamCity itself may have its own proxy configuration settings. If you can't find the information you need in the documentation or through online resources, consider reaching out to Plastic SCM support. They should be able to provide guidance on configuring a proxy server with Plastic SCM and its integration with other tools like TeamCity.