Jeremy

FWIW, I got this same message when setting up a Jenkins build server w/PlasticSCM plugin on a GCP Windows Server 2019 vm, to run Plastic Cloud edition. On the same instance, running the PlasticSCM GUI gave me an "Unable to connect to PlasticSCM" error, even though the Preferences->check credentials worked correctly. Based on Héber's response above, I looked for the PlasticSCM service in the task manager, and found that "Plastic SCM server" and "Plastic Change Tracker" services were listed as Stopped. Once i started them, both the GUI and build errors went away :). I thought I'd mention it here in case anyone else runs into similar problems. FYI: this is how the Jenkins log reported the initial error: Running as SYSTEM Building in workspace C:\Program Files (x86)\Jenkins\workspace\my-unity [root] $ cm workspace list --format={wkname}#{path}#{wkid} my-unity#c:\Users\admin\wkspaces\my-unity#19ed8bdf-02e2-4084-8f71-0383e703d558 [root] $ cm workspace create jenkins_519ee701354b49b7b92ba7aff5d99d3a "C:\Program Files (x86)\Jenkins\workspace\my-unity\root" "--selector=C:\Program Files (x86)\Jenkins\workspace\my-unity\root\selector5933500470485475368.txt" Error: No connection could be made because the target machine actively refused it 127.0.0.1:8084

Hi Carlos, I think understand the multi-line text field problem, and that my problem was a more basic connection issue. We have been getting by on FogBugz without logging check-ins, partly because our team is small, but also because checkins and merges to don't necessarily mean the work is done, so we haven't seen the need to trigger SCM status changes with PlasticSCM events. Having PlasticSCM branch names match issue id's has been enough for us. However, since the reason we're looking at Jira is to transcend FogBugz' limitations, it could definitely be useful to have that info available in Jira. I'll look forward to your fix for the multi-line text field to see how we can make use of checkin event info in Jira--it might be especially helpful as we expand and grow our team. Fwiw, I was able to get around the "issues not listing" problem, by deleting the issuetrackers subdirectory in my profile, restarting PlasticSCM and re-entering the Jira connection info from scratch. There seemed to be a weird situation where Plastic client wrote Jira connection info to a AppData\Local\plastic4\issuetrackers\mycompany@cloud\... subdir, but was reading from a legacy config in AppData\Local\plastic4\issuetrackers\mycompany@local\... Once I cleared that out and started from scratch, Plastic was able to list the Jira issues with no problem.

FWIW: I recently tried to integrate to Jira Cloud "next gen". The configuration's "test connection" works, but the list of tasks/issues when creating a child branch is empty. It seems like it "almost works", and the log file had some jira-related errors (see below), that may be relevant. From the plasticscm log file:2020-06-23 14:15:34,225 DESKTOP-0L9ID4V\jyabrow ERROR jiraextensionrest - There was a problem performing GET https://beyondview.atlassian.net/rest/api/2/user/search?username=: The remote server returned an error: (400) Bad Request.^M2020-06-23 14:15:34,233 DESKTOP-0L9ID4V\jyabrow ERROR jiraextensionrest - Response from the server: {"errorMessages":["The username or property query parameter must be provided"],"errors":{}}^M

Hello, My team just asked me about this yesterday. Just thought I'd add another voice to the feature request; we'd also like to be able to purge old versions of large assets--the vast majority of our db size is made up of non-mergeable assets. I'm glad you're working on a feature for this. Fwiw, we'd love to have a way to specify something like "keep only latest N versions" on individual files or groups of files". Thanks, Jeremy