Jump to content

calbzam

Administrators
  • Posts

    2,598
  • Joined

  • Last visited

  • Days Won

    75

Everything posted by calbzam

  1. Hi, It seems to be a problem with the "LibGit2Sharp" library. Do you have access to a Windows machine to try to sun the GitSync from a Windows client? Regards, Carlos.
  2. Hi, I can see you are working for Aptiv. Could you send an email to todd.r.alden@aptiv.com regarding this topic? You can CC support@codiceaoftware.com. Regards, Carlos.
  3. Hi, If you are using GitSync, please attach the client logs to debug the error: /Users/xxx/.plastic/logs Regards, Carlos.
  4. Hi, In the Plastic GUI --> Preferences, you can create a "Connection Profile" to configure your client to reach a different Plastic server. This way, you can create Plastic workspaces pointing to repos belonging to multiple cloud organizations. Regards, Carlos.
  5. Could you share with us the specific command you are running? I guess you are replacing "--server=organization@cloud" by your organization name? Is this command failing for one user or for ebery user who tries it? Regards, Carlos.
  6. Hi, When opening the terminal, the user who runs the command is the same machine user as the one configured in the macplastic GUI? Other commands like listing repos "cm lrep" are properly working on this terminal? Regards, Carlos.
  7. Hi, I think the labels are not synced due to the different natura of the labels in P4 vs Plastic SCM. Regards, Carlos.
  8. You will need to create a new cloud organization for the external developers if you don't want to share the encryption key with them (and assuming you need to access both to their repos and also your repos). A Plastic client can only be configured with one encryption key per organization. Encryption can be disabled for the full organization but I guess this is not a valid solution. Regards, Carlos.
  9. Hi, I'm afraid the encryption key is set per organization. All the users will need to know the key. But you can easily restrict the access via permissions. This is the natural way to handle it: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide Please let us know if it helps. Regards, Carlos.
  10. Hi, We are working a new multiplatform GUI. It should ease the development of a modern dark theme taht works both for Windows, macOS and Linux. Hopefully we have good new soon. I'm sharing your request with the product team. Regards, Carlos.
  11. Hi, In the following link we explain how you can map the Plastic users with the git emails when using GitSync: https://www.plasticscm.com/documentation/gitsync/plastic-scm-version-control-gitsync-guide#Mappinguseraccounts Regards, Carlos.
  12. Hi, We just released the auto-upgrade system . https://www.plasticscm.com/download/releasenotes/10.0.16.5668 Regards, Carlos.
  13. Hi, Please run the "cm unlock --help" to get the details and some examples. You will need to get first the guid of the items tom unlock via "cm listlocks --server=YourOrganziation@cloud" Regards, Carlos.
  14. Hi David, The mergebot runs a merge of the previously created shelve to apply it to the destination branch. Regards, Carlos.
  15. Hi, Please cehck the following link where they explain how to open the command prompt in Windows 10: https://www.howtogeek.com/235101/10-ways-to-open-the-command-prompt-in-windows-10/ Once you have a Windows prompt open, you can run the "cm unlock" commands. Regards, Carlos.
  16. Hi, I'm afraid this is not possible. You can only assign the permissions per repo or per branch but you will need to assign the permissions to specific a user/group. Regards, Carlos.
  17. Hi, Could you remove the user from the cloud organization and then re-invite it again and finally check if the login via the Plastic GUI works? Regards, Carlos.
  18. Hi, You can configure the "changecomment" permissions on the repo. This way, you can customize the users/groupd who are allowed to edit the changesets comments. Please let us know if it helps. Regards, Carlos.
  19. Hi, You could create your own "before-mkbranch" trigger to support this behavior: https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide#Createbranch I'm afraid this feature is not included by default. Regards, Carlos.
  20. Hi, Are you following the steps from the plugin documentation? https://plugins.jenkins.io/plasticscm-plugin/ Pipelines Please have in mind that running the cm command in a pipeline script won't automatically set the environment variables above! This command, as do all VCS commands, returns a dictionary that contains the environment values set as expected. To take advantage of that, you should do something like this: pipeline { agent any environment { PLASTICSCM_WORKSPACE_NAME = "${env.JOB_BASE_NAME}_${env.BUILD_NUMBER}" PLASTICSCM_TARGET_SERVER = "192.168.1.73:8087" PLASTICSCM_TARGET_REPOSITORY = "default" } stages { stage('SCM Checkout') { steps { script { def plasticVars = cm( branch: "main", changelog: true, repository: env.PLASTICSCM_TARGET_REPOSITORY, server: env.PLASTICSCM_TARGET_SERVER, useUpdate: false ) plasticVars.each { key, value -> println("${key} = ${value}") } } } } } } In the code above, the plasticVars dictionary would only be available in the script block inside the 'SCM Checkout' stage. If you'd like access it across different scripts, steps or stages, you can define the variable in the global scope: def plasticVars pipeline { agent any environment { PLASTICSCM_WORKSPACE_NAME = "${env.JOB_BASE_NAME}_${env.BUILD_NUMBER}" PLASTICSCM_TARGET_SERVER = "192.168.1.73:8087" PLASTICSCM_TARGET_REPOSITORY = "default" } stages { stage('SCM Checkout') { steps { script { plasticVars = cm( branch: "main", changelog: true, repository: env.PLASTICSCM_TARGET_REPOSITORY, server: env.PLASTICSCM_TARGET_SERVER, useUpdate: false ) } script { plasticVars.each { key, value -> println("${key} = ${value}") } } } } } } Regards, Carlos.
  21. Do you mean some Plastic labels are not exported to P4 or in the opposite way? I can check with the team but maybe they are not imported. Regards, Carlos.
  22. Hi, In order to set the encryption key, could you open the Plastic GUI --> "Sync with Cloud" view and try to replicate a branch from the cloud server to a local repo? It should ask you to enter the encryption key and it will be used later for any other operation like the "cm sync". Regards, Carlos.
  23. Hello Holden,1) We have recently released a new "p4sync multibranch" command that is also compatible with migrating one single branch and includes the last fixes. Could you try this command instead?eg: cm sync PlasticRepo p4multibranch P4SERVER:1666 --mainbranch=//Engine/main --branchesfolder=//Engine--user=carlos --pwd=MyPass -caseinsensitive --continueonp4error --tmpwkpath=c:\p4wks 2) Could you enable the "cm" log so we debug the issue if it happens again?https://www.plasticscm.com/documentation/technical-articles/kb-enabling-logging-for-plastic-scm-part-i Regards, Carlos.
  24. Hi @Gabriel, Is the user registered at www.plasticscm.com with this Unity ID? If you are using a paying subscription, you can open a ticket to debug it. We may need to arrange a meeting. Regards, Carlos.
×
×
  • Create New...