calbzam

Great! Thanks for the update

Hi, If you want to allow switching to a different branch with pending changes (even if they are ignored in the "Pending changes" view), you can configure this behavior in the GUI "Preferences" --> "Other options" panel. You can "allow", "allow showing a warning" or "don't allow". With this warning, we try to avoid errors like the one we explain in the following article: https://plasticscmsupport.zendesk.com/hc/en-us/articles/360014970894-The-parent-revision-of-the-item-is-inconsistent-with-the-loaded-one-in-changeset-cs-xxx Your feedback is welcome. Regards, Carlos.

Great! Thanks for the update

Hi, You can use a sync view to clone a repo: https://www.plasticscm.com/documentation/gui/plastic-scm-version-control-gui-guide#Chapter23:TheSynchronizationview Regards, Carlos.

Thanks for the update!

Hi, I'm afraid this is a known issue. We already have a task to fix it and to improve the API REST. We will let you know as soon it's released. Sorry for the inconveniences, Carlos.

Hi, we designed the help system to not only help newcomers but also to prevent frustration to experienced users. The system is able to detect frustration scenarios such us empty views, unused features and so on. Right now there's no way to disable the system but notice that those cards you choose to hide will not appear again.Can you please get feedback from your users about the messages that shouldn't appear? We can improve the system with their feedback. Regards, Carlos.

Hi, I don't fully understand your question. If you need to configure a Plastic client, you can do it via GUI preferences or via console running "clconfigureclient". Regards, Carlos.

Great! Thanks for the update

Hi, If you are the Plastic server admin (or if you don't have denied permissions for any specific repo), you can get the full repo list by running: cm repository list Regards, Carlos.

Hi, In Plastic, there is not such a concept. When you list the repos, you will see all the repos where you have permissions enabled. I mean, if some repos are not appearing in the list, it is because you don't have "view" permissions to see them. Otherwise, you will have access to all of the repos. The only way to handle repo access is via permissions: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide Regards, Carlos

Hi Scott, We have just released a new task that should be helpful in scenarios like yours: [Bug] 8.0.16.3433 All platforms - Plastic, Gluon: We improved the behavior when you have local changes and the changeset loaded in your workspace is deleted by a different user. Before these improvements, this meant that you got stuck: at that point you were unable to checkin, shelve or undo your local changes. We modified the client behavior to enable you to undo your local changes, letting you out of that loophole. Shelving or checking them in will still be unavailable, as they wouldn't have a parent changeset. The 'undo' behavior will be slightly different depending on the client you use: Gluon will always allow you to undo the local changes. If the original contents aren't available anymore, the head contents of the current branch will be used instead. Plastic, on the other hand, will notify you about the inconsistency and then ask you for confirmation to undo all your local changes and update the current workspace. Regards, Carlos.

When you install Plastic, there is always a "default" repository. You can remove it if you don't need it anymore. Regards, Carlos.

Hi @SDSChad, When you run an initial Gitsync operation, one the repos involved always need to be empty. The problem is: In the Machine B, you don't have any previous GitSync mappings. This machine is not aware of the previous GitSync performed in Machine A. When you sync the git repo, the commits are duplicated into your Plastic repo (at the end of the day breaking the repo). Machine B doesn't know that there was a previous sync. You will need to manually remove the duplicated changesets. Summary: - Always perform the GitSync from the same machine. - If you want also do it from a different machine, you will need to use a clean new repo for the initial sync. These ways, the mappings will be also generated in the new machine (and not changesets will be duplicated). Regards, Carlos.

Hi, No problem All the 8.0.16.X clients will be compatible with a 7.0.16.X server. The third number "16" sets the compatibility. Regards, Carlos.

Hi,We have released the following task: [Bug] 8.0.16.3433 All platforms - Plastic, Gluon: We improved the behavior when you have local changes and the changeset loaded in your workspace is deleted by a different user. Before these improvements, this meant that you got stuck: at that point you were unable to checkin, shelve or undo your local changes. We modified the client behavior to enable you to undo your local changes, letting you out of that loophole. Shelving or checking them in will still be unavailable, as they wouldn't have a parent changeset. The 'undo' behavior will be slightly different depending on the client you use: Gluon will always allow you to undo the local changes. If the original contents aren't available anymore, the head contents of the current branch will be used instead. Plastic, on the other hand, will notify you about the inconsistency and then ask you for confirmation to undo all your local changes and update the current workspace. Regards,Carlos.

Hi, Please, attach the full server debug log in order to debug the issue. But checking the error: https://knowledgebase.abbyy.com/article/641 This problem usually occurs when the user that is trying to create the database doesn't have the necessary permissions in SQL Server. If you use the Administrator's account to create the database, this situation can be avoided. You can also check if the account that failed to create the database has the permissions described in this article. The problem can also occur if the name of the database you attempted to create is already in use by another database or if files from a database with the same name remain on the computer. Try creating a database with a different name. Check if the disk on which the SQL Server is trying to create the database has enough free space. By the way, aren't you considering migrating your databases to Jet? Most of our bigger customers are already using it. Regards, Carlos.

Ok, thanks for the update! Anyway, it seems to be weird that the issue happens when entering the ports via the server config tool. Are you using the web admin? Regards, Carlos.

Hi Thomas, I'm not able to reproduce the issue with your same permissions enabled. Could you check if this user also belongs to other groups? There should be something in the permission configuration denying the change comment operation for this user. Regards, Carlos.

It's not necessary. You can use the Plastic SCM integration with the free Unity version. Regards, Carlos.

Hi, Even if you want to install a Plastic server on Linux, also installing the client is normally a good idea (just in case we need to run some CLI client commands). For using GitServer feature, you will also need to install the client. If you want to install only the server, just install the "plasticscm-server-core" package. Regards, Carlos.

Hi, As you comment, I'm afraid the users will need to manually upgrade. The auto-upgrade feature will only work if the client and server version are not actually compatible. If they are compatible (7.0.16.X), I'm afraid that the auto-upgrade feature will not work. Regards, Carlos.

Hi again, In order to restart your local macOS server: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Serverstartup sudo launchctl unload /Library/LaunchDaemons/com.codicesoftware.plasticscm.server.plist sudo launchctl load /Library/LaunchDaemons/com.codicesoftware.plasticscm.server.plist After that, the lock should be released. Regards, Carlos.

Great! Thanks for the update

Hi, We were not reported false positive issues specifically with Bitdefender in the past. We are going to report it to Bitdefender guys. We would appreciate if you do the same in the following link: https://www.bitdefender.com/support/what-to-do-when-bitdefender-detected-a-clean-file-as-infected-(false-positive)-851.html Regards, Carlos.