calbzam

Hi, The "ignore.conf" needs to be stored at the root of the workspace. Doesn't matter if the ignore rules apply to the parent repo or some Xlinked repo. If you have a "ignore.conf" in some subfolder (eg: Xlink), these rules won't be taken into account. Regards, Carlos.

Hi, Are you using Plastic Cloud edition? This post refers to an on-premises server. If you are using Plastic Cloud. You select to enable the encryption when creating the cloud organization. You don't need any extra step to enable it. Regards, Carlos.

Hi, Could you attach your Plastic client logs? Could you try creating the workspace on a different path? eg: not external disk. regards, Carlos.

Hi, The ignore rules should be applied to private items doesn't matter if the belong to an Xlinked repo or not. Note that the ignore rules doesn't apply to items that are already under source control. In that case, you will need to add them to the hidden changes list. Regards, Carlos.

Hi, cm find changeset --format={id} --nototal Regards, Carlos.

Hi, If the goal is using the branch name in some CLI tool, you may also prefer to get via command. eg: cm find branches --format={name} --nototal Regards, Carlos.

Hi, From the "Branches" view, you can right-click a branch --> Properties, and this way copy the branch name. The same from the "Branch explorer" in the Properties panel. Regards, Carlos.

Hi, If you are using Plastic Cloud edition, you can also use local repos and replicate the branches on demand from local to cloud. This way (following a distributed workflow), you don't need permanent internet access (just when pussing your changes to the cloud). Check "Distributed developers"in the following link: https://www.plasticscm.com/plasticscm-cloud-edition Regards, Carlos.

Hi, In the Preferences panel, you should be able to enter your crendentials. Or via Terminal running: macplastic --configure Regards, Carlos.

Hi @amineoxstudios, What is your problem when syncing aginst Azure repo, could you attach your client logs? Regards, Carlos.

Hi, In modern SCMs we need to think as changeset/commit like the basic unit. So you are not merging single files but changesets. Following these steps, if I try to update my workspace and this update involved a file conflict, Plastic will detect it and it will propose you to run a merge: Resolving a merge is not a problem as soon as you are working with text files. files Regards, Carlos.

Hi @amineoxstudios, We can ignore these error messages. It's a localization error but it shouldn't affect the sync operation. We are about to fix it. In your screenshot, I can seee the initial sync with a Bitbucket repo was succesful. Regards, Carlos.

If you are using the Jenkins plugin, when you run a build, it will create a local workspace and update it with the branch to build. It's automatically handled by the jenkins plugin. https://plugins.jenkins.io/plasticscm-plugin/ Regards, Carlos.

Hi, - If you are using the Plastic GUI, the basic unit is the changeset (similar to git) and the default workflow is the branck per task workflow (you create the task branch before start performing changes on the files). The workspace is always pointing to a specific changeset and you cannot update/merge indiviudual files but changesets. This design makes the merge performance in Plastic/git much better than other SCMs. Even if you don't have cheked-out items but just locally changed items, we need to be careful when switch to different branch because the following error could happen: 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 - In the scenario you are mentioning I guess both developers are workinng on the same branch. This fits with a Gluon workflow (not Plastic GUI). Gluon is the GUI designed for artists or developers working with binary files. In Gluon, the basic unit is the file (similar to SVN). The workspace structure is more flexible. You can potentially update/load items from different changesets. If you forgot lock/checkout an item and there is a conflicts, Gluon will be able to resolve the merge conflict for this specific file. More details in the following blog post: https://blog.plasticscm.com/2019/10/incoming-changes.html Please let us know if it helps. Regards, Carlos.

Hi @wfk Are you easily reproducing the issue if start the local Plastic server in macOS and leave it running for a few hours? I guess the load of your local server is low. We would like to check the server logs when this issue happens. Regards, Carlos.

Hi, The Jenkins/TeamCity/bamboo plugins are aslo compatible with cloud servers. The only feature that is not supported for cloud is mergebots. Regards, Carlos.

Hello, I'm afraid this is not possible at the moment, some admin will need to remove you. We already had tracked this feature request. I will share your feedback with the team. Sorry for the inconveniences, Carlos.

Thanks for the update!

Hi, Thanks for your feedback. In this thread there were multiple comments but most of them had something in common (having a way to reduce the size of the repository so you can control storage growth of the repos). For now, we addapted the existing "cm archive" command to be supported in the cloud. I will share your feedback with the product team so your comments are considered for future improvements. Regards, Carlos.

Hi, The following task has been released: https://www.plasticscm.com/download/releasenotes/10.0.16.6241 All platforms - Cloud: Archiving revisions is now available in Cloud! You can reduce the size (and the costs :)) of your cloud repositories by archiving revisions to an external storage. Regards, Carlos.

Hi, This is a workaround to install Plastic SCM for Ubuntu > 19.https://plasticscmsupport.zendesk.com/hc/en-us/articles/360013103159-How-to-Install-Plastic-GUI-in-Ubuntu-19-10-and-later- Please let us know if it helps. Regards, Carlos.

Hi,Thank you for reaching out to us. Sorry to hear that you are experiencing this behaviour.I suspect that the additions and deletions were not selected to be checked in on the Pending Changes view. Please can you review the workspace where you pushed your changes and confirm whether there are outstanding items to check-in?The Plastic SCM client does not automatically select these items, all changes made need to be reviewed in the Pending Changes view. If you really want to check in everything without reviewing the items, this can be done via the CLI...cm checkin --all --privateI hope this information is helpful to you. Please let me know if you have any further queries or concerns, and I will be happy to assist. Regards, Carlos.

Hi, As an update, we are handling this error via support ticket and we are working on a fil for the null error. Regards, Carlos.

Hi, cloaked.conf is a configuration file only available for the Plastic GUI. If I properly understand. you would like a similar feature so you can configure similar rules than the supported in Plastic GUI (file types...) but in Gluon? Regards, Carlos.

Hi, I'm afraid the changeset id inside a Plastic repo is a local identifier and it can't be changed. If you replicate this changeset to a different Plastic repo, this number may also change. Plastic changeset also have a guid (universal indetifier for the Plastic changeset even if you replicate it to a different repo). Regards, Carlos.