[Sorting changesets in CodeReview]

Hi,

Yes, we already have an internal task to fix this problem. We will update the thread as soon it's released.

Sorry for the inconveniences,

Carlos.

[Invalid password. Review your user/password configuration.]

Hi,

What is your authetication mode? Custom user/password?

Is the PC where you are getting the "Invalid credentials, Username or password is not valid" error connecting to the same central server? Or maybe you are using local repos?

If you copy the same "client.conf" from the working machine to the others, it should also work (unless you are reaching a different Plastic server).

Regards,

Carlos.

[The method version 2 is not supported.]

Could you reach us at support@codicesoftware.com? We need to review the "plastic.debug.log.txt" in order to determine the key of the problem.

I would check first your Plastic client version and also the server version. You may need to upgrade to the last.

Regards,

Carlos.

[CLI does not work]

Hi,

Do you have installed a Plastic client installed in the server machine? "cm" is the Plastic client CLI.

Regards,

Carlos.

[PSA: Beyond Compare merge params are flipped on their website!]

Thanks for your feedback!

Carlos.

[Find all changesets which changed file encoding]

Hi,

 

There is not one single command that allows you to get this information. In guessing the best approach.

We need to get all the file revisions  ("cm find revisions") and then, for each one, run "cm cat". The output of the "cm cat" can be passed to an external app that gives you the enconding.

 

In summary:

cm find revisions where path.... | for_each_rev cm cat --download | tool_check_bom

 

Rgerads,

Carlos.

[PlasticSCM Cloud not syncing with Jira-Cloud Issue]

Thanks for the update

Carlos.

[Backups and the new Jet backend]

Please check the followng link:

https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide

Regards,

Carlos.

[Code Review changeset by changeset]

We have in our roadmap to create a new panel (a third panel) that will show a diff against the head of the branch when you are performing a review changeset by changeset.

For now, you can open a diff of the branch and take notes of the proposed changes so can take a look if they are already applied. Not the ultimate solution but hope it helps.

Regards,

Carlos.

[PlasticSCM Cloud not syncing with Jira-Cloud Issue]

Hello,

If you configure the JIRA integration in the preferences panel, is the "check connection" working?

We need to review the Plastic client logs to debug the issue.

Regards,

Carlos.

[GetWorkingMode errors with Proxy]

Great, thanks for the update!

Regards,

Carlos.

[New workspace default directory]

You are using a very old client version. Anyway, the file to edit is:

C:\Users\xxx\AppData\Local\plastic4\plasticgui.conf

...

DefaultWorkspaceRoot=c:\Users\carlos\MyWorkspaces

...

 

Regards,

Carlos.

[Code Review changeset by changeset]

Hello,

Why don't you create a code review for the full task brannch? This way, you can review all the changes at the same time and you don't need to guess if some pending changes were actually performed on a later changeset.

Regards,

Carlos.

[Cloud repository access]

Hi,

I think we could arrange a meeting to help you with the permissions configuration. You can reach us at support@codicesoftware.com:

Quote

 We added "Project X Devs" to our Project X repository, however we had to manually compare it to the default "Developers", and painstakingly go through each checkbox, click "override" and then set the right value. This felt very clumsy and unintuitive.

If you neither allow the pemrissions at the server level, you won't need to overwrite any permission. You will be able to assign the permissions at the repo level.

Quote

Then, we ran into this issue: we cannot remove "Developers" from that repository because it is telling us "Cannot remove an inherited entry". So the repository seems to be stuck with "Developers" (?)

You cannot remove an inherited entry. You need to open the server permissions (not repo but server permissions) and remove the group at this level. This way, it won't be inheritted to the below permission levels.

Regards,

Carlos.

[can't install in ubuntu 19.10]

I'm afraid we still don't have available packages for the last Ubuntu 19 version.

Regards,

Carlos.

[GetWorkingMode errors with Proxy]

Hello,

- Could you enable the full debug log replacing the configuration file by the attached one?

plasticcached.log.conf

- Are you connecting to your Plastic server via SSL port?

- If you open the Plastic client configurator, is the check connection with the proxy server working?

- What is the Plastic client, proxy server and Plastic server versions?

Regards,

Carlos.

 

[Jira Integration on Mac]

Hi, Thanks for the update. At least we have an explanation. I remember some other issues we fixed in the past raleted to the OS in Turkish.

Regards,

Carlos.

[Jira Integration on Mac]

It seems the user you have configured is wrong, right? "plastic@highgames.io".

The user should be "jira@higames.io"? Could you re-open the GUI after editing the configuration file?

Regards,

Carlos.

 

[Cloud repository access]

HI,

The Plastic SCM server has different level permissions that inherit between them: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide

- You can configure permissions at the Plastic server level. Then, at the repository level, you can apply new permissions or overwrite the permissions inherited from the server level.

- When you edit the repo permissions, these "default" repo permissions you are seeing are inherited from the server permissions level.

- If a permissions is neither allowed nor denied, you won't be allowed. But this is sometimes useful when you don't want to set any permissions in the server level so they are not inherited to the repo level.

Our guide has some real scenarios you can check and we are open to connect with you to assist with the permissions configuration: support@codicdesoftware.com

https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide

Regards,

Carlos.

 

[Feature request: incremental backups for Plastic Cloud]

Thanks for your feedback. We will follow up in the user voice thread if we have some questions.

Regards,

Carlos.

[Requiring me to "finish" a merge that has already been finished?]

We are already in contact with @michael77 via support ticket. We will update this thread as soon as we have more information.

Regards,

Carlos.

[Issues Setting Up Group Permissions with LDAP Configuration]

Hi Nick,

Doesn't matter if you use the LDAPWorkingMode and you apply the permissions to the AD groups, or if you define custom groups and you define permissions to this groups, the permissions should be applied.

How are you applying the permissions to the groups?

How are you checking that they are actually applied?

Regards,

Carlos.

[Error using fast-import for cloud repo]

Great! Thanks for the update

Regards,

Carlos.

[Error using fast-import for cloud repo]

If you are going to use a Plastic cloud organization, please install Plastic Cloud edition. This way, you can use local repos with no extra license.

Quote

I tried running Update Workspace but I wasn't prompted for the encryption key. The repo is empty at the moment though.

If the repo still doesn't have any content, you should be requested to enter the encryption key the when you perform the initial checkin.

Regards,

Carlos.

[Error using fast-import for cloud repo]

Hi Joe,

- If you installed Plastic cloud edition, it also transparently installs a local Plastic server to host your local repos. You could try to import the fast-export package to a local repo (instead of cloud) and then push the local Plastic repo to the cloud.

- Anyway, the encryption can be configured in both the client and server side. If you create a new Plastic workspace from this client pointing to a cloud repo and run an update operation, you should be requested to enter the encryption key for your client. Once the key is stored, you shouldn't need to enter it again for future client-side operations.

Regards

Carlos.