ruben

Hi Jordan, Did the user run a merge that wasn't checked-in before trying to run the Incoming Changes? If the answer is yes, he needs to run a new merge from the last changeset in the branch (or the branch itself) to retrieve the latest changes in the branch before checking-in his local changes. The Incoming Changes is not able to run if there is a pending merge to checkin in the workspace. You can check the pending merge links in the Pending Changes view: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide#MergeinthePendingchangesView If the answer is no, I guess he run an Incoming Changes operation that threw some error. The problem is that the Incoming Changes operation failed in the middle (because internally it runs a merge in a first stage). Could you send the client log files to support@codicesoftware.com. You can fin the log files (plastic.debug.log.txt) located in the plastic user folder C:\Users\xxxx\AppData\Local\plastic4\logs\plastic.relevant.log.txt To continue using the workspace, he can try two different options: manually backup the local workspace changes, undo all the workspace changes, reapply them manually in the workspace and retry the operation. shelve (and undo) the workspace changes, update your workspace to the last changeset in the branch, apply the shelve in the workspace and checkin your changes. I hope it helps! Rubén.

Hi Mikael, We have just release the version 2.14 of the Plastic SCM - Jenkins plugin. Now, you have a checkbox in the 'source code management' configuration to use multiple workspaces or not. If it isn't checked, the plastic workspace path & the jenkins workspace path will match fixing (hopefully) any issue with the shared libraries. Thank you for your detailed report! Rubén.

Hi Mikael, We changed that behavior long time ago to support multiple plastic workspaces for the same jenkins project (The 'additional workspaces' entry in the Source Code Management section). This way you are able to setup different workspaces for the same jenkins project and customize their relative paths through the 'Workspace Name' field. Couldn't you configure your project builds to take advantage of this behavior in your setup? If it doesn't suit you at all, we could review how to support also plastic workspaces directly in the jenkins workspace.