calbzam

If it's not a problem, this way we can try the same as you to debug the issue. Regards, Carlos.

Hi @RedHookBrett, can you open a ticket at support@plasticscm.com? We would like to futher debug your case. At least this workaround should work.

Hi @Wim Devos, can you let us know your specific repo names (or attach your gitsync.conf) so I can try the same and confirm the bug is still there? After that, I will check with the dev team if a task to fix it can be scheduled soon. Sorry for the inconveniences, Carlos.

Hi, @Olaf I will share your feedback with the product team. Regards, Carlos.

Hi, Plastic Cloud currenlty supports Unity ID, user password and Okta authentication but I'm afraid you cannot manage your own authentication system via oAuth2. It's in the roadmap supporting an API key system that should be helpful to handle authentication for automations, custom extensions... Regards, Carlos.

Hi @LucasM, if you are using Plastic SCM Cloud edition, it transparently intalls a local server to handle your local repos. But I'm afraid this local server cannot be reconfigured (you cannot change the authetnication mode, user names...). I you want to host and configure a full local on-premises server (custom authetnication, users...) you will need to buy an Enterprise license for that puporse. Regards, Carlos.

Hi, Checking the error output, can you check if intalling the "xdg-mime" package helps? http://manpages.ubuntu.com/manpages/impish/man1/xdg-mime.1.html Regards, Carlos.

Is it Plastic Cloud, right? Regards, Carlos.

Hi, Even when there is not a definited fix, the is the following workaround that should help: Please let us know if it helps. Regards, Carlos.

Hi @Mitch, Can you clarify what is your current problem? If you have a Gluon workspace that is not fully checked but you just have configured a few folders in your workspace, only the changes that happen in these folders will be automatically updated to your workspace. Regards, Carlos.

Hi @Jashan Chittesh, Can you check if Plastic is detecting the change a "Moved" or "Locally moved"? The locally moved items are the changes that Plastic is trying to match on disk. You will need to enable the move detection in the "Pending Changes" view. If the file is detected as controlled moved, it means the moved happened under Plastic control (via Plastic GUI, Unity plugin, "cm move" command...). For the moved items, Plastic doesn't need to match any file on disk to determine if this is a move or not because it already has the information of a moved that happened in the workspace. Regards, Carlos.

Hi, - I can see the operation is aborted with no additional errors. Not sure if we can make a test pusing the Plastic repo to GitHub instead. - How big is the repo database? I was guessing if you could share the repo with us for try and debug the same GitSync operation. Regards, Carlos.

Hi, - Sorry if was not clear enough but what we need is to review the Plastic client logs. If you are using the "cm", you will need to manually ernable the "cm" logs: https://www.plasticscm.com/documentation/technical-articles/kb-enabling-logging-for-plastic-scm-part-i If there is a problem in the Bitbucket side, I'm afraid we won't be able to help. - My guess is Bitbucket could be rejecting the push from Plastic. You mentioned that the repo is huge. Does the repo have big files? Do you know if LFS is enabled in Bitbucket? is it a cloud Bitbucket server? - Can we try to push the Plastic repo to GitHub to check if the issue persist? Regartds, Carlos.

Hi, - Can you check in your local machine if the Windows services panel if the "Plastic SCM Server" service is up and running? If it's running, can you attach the following file to review the port where the local server is listening? I'm guessing if it's not the default one: 8084 C:\Porgram Files\PlasticSCM5\server\network.conf - In order to replica repos between two Plastic Cloud organiaztions, please check the following link: https://support.unity.com/hc/en-us/articles/4773885917204 Regards, Carlos.

Hi, We are about to release a fix to support Rider 2022. it should be avilable in just a few days. Sorry for the inconveniences, Carlos.

Hi, This is a know issue. It should be fixed in the following weeks. Sorry for the inconveniences, Carlos.

Hi, I was able to make it work with quotation marks. Does it help? cm patch "br:/main/MyBranch 1" Does it help? Regards, Carlos

Hi, - Could you upgrade your Plastic Scm version to the lost recent one. At least this error, shouldn't appear. - Could you attach the full debug logs so we can review them? You can send it to me in private if necessary. - Does the also issue happen if you try to push the repo to some other git cloud service (GitHub...)? Regards, Carlos.

Thanks for the update. We are aware of the issues with Ubuntu 22. Hopefully we can provide a woraround soon. Sorry for the inconveniences, Carlos.

Plastic is not available (or has been ever avilable) for Arch Linux but it properly works in Ubuntu (at least until Ubuntu 21). Regards, Carlos.

@snail008 If you are refering to Sematic Merge, I'm afraid it's not possible to buy new licenses. If you still have a valid license, you should be able to keep using it. Let us know if you are facing any problem. Regarding the JVM issue, what is the current Java version you have installed? Regards, Carlos.

Hi, Are the users using Gluon and Plastic GUi at the same time? I think we should focus on a user facing the problem and debug their Plastic client logs: C:\Users\xxx\AppData\Local\plastic4\logs We will try to determine when the file was originally locked to understand what could be happening, Regards, Carlos.

Hi Jonas, This error normally happens when you had the item checked-out in a different workspace. Potentially the workspace was removed while the lock was not released. Or if for some reason the metadata of the current workspace was somehow re-created while the lock persists. If you it doesn't fit with your tests and you can reproduce the issue please reach us at support@plasticscm.com for futhter debugging. Regards, Carlos.

Hi, If I properly understand, the main problem is you are not able to make it work to get the checkin comment saved in the JIRA task via the custom field? In addition to this the field mappings and status transitions are not properly working. Not sure if you could temporary allow us access yo the JIRA project to reproduce and debug the issue. Can you reach us at support@plasticscm.com? Regards, Carlos.

Hi, The ignore rules work for private files but if the items are explicitly added to source control, they will appear proposed to checkin in the "Pending Changes" view. We need to understand what is actually adding the items to sourde control. Regards, Carlos.