Jump to content

calbzam

Administrators
  • Content count

    1,273
  • Joined

  • Last visited

  • Days Won

    26

calbzam last won the day on May 18

calbzam had the most liked content!

Community Reputation

49 Excellent

About calbzam

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

45,565 profile views
  1. "Idea was to have single repository (easier to locate and manage) with dedicated top-level branch for each library." [carlos] My recommendation is to use one repository per library. If you commit the libraries code in different branches, then when running merges, you will end up with code from the different libraries in the different branches. Using a repo per library is cleaner. Also for managing the permissions, it will be easier because you will assign permissions at the repository level. If you decide to configure the permission at the branch level, you can don't either allow nor deny permissions at the repository level, then you can explicitly allow the permission for the desired groups at the branch level (this way you can overwrite permissions). In our security guide give have examples for most of the scenarios: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide.shtml#Preventchangesonabranch Enabling the view/read should enough to accessing the code, but you may also want to enable the rest of the permissions to the group who is going to work in this branch: checkin, add, change, createlabel, removechangeset... "Prefer result should be that user from GroupA can access repository and see only branch LibA... (of cource if user is in GroupLibA and GroupLibB he/she should see branch /libA and /libB but not /libC)." [carlos] This requirement fits with creating one repository per library. This way, "GroupLibA" users will only see the "libA_repo" and "GroupLibB" will only see the"libB_repo". Based on your requirements, this is the cleaner and the easier to configure solution in Plastic. Best regards, Carlos.
  2. Hi, I have repository with several branches which contain different libraries (each specific branch is dedicated for library). [carlos] I guess you have a repository with different libraries and then you have independent branches where you edit each library? Why don't you use independent repositories for the libraries and then you configure the repo permissions for the different groups? You can also use Xlinks: https://www.plasticscm.com/documentation/xlinks/plastic-scm-version-control-xlinks-guide.shtml If you assign permissions at the repository level, they will be applied to all the branches of the repo and then you can also customize permissions per branch if necessary. You can neither allow nor deny permissions at the repository level and then explicitly allow the permission for the desired groups at the branch level. We have a security guide explaining those scenarios in detail: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide.shtml#Preventchangesonabranch Regards, Carlos
  3. calbzam

    Not a fan of the new Branch Explorer UI

    [New] 7.0.16.2228Windows GUI: Some users reported that merge link colors in the Branch Explorer don't have enough contrast and they are not visible enough. Changed to use a stronger green. Regards, Carlos.
  4. calbzam

    cm find ordering or sort?

    Hi, I'm afraid you will need to filter the output yourself. Regards, Carlos.
  5. calbzam

    Plastic SCM Plugin for Crucible

    Hi, Yes, it should be also doable: 1) You will need to run a "cm find shelve" where you can get the changeset id for your desired shelve. 2) Once we have the id, we will need to run the following command with the negative value that represents this is actually a shelve and not regular changeset. Option 2.1) cm diff cs:-123 --download=c:\ExportFolder Option 2.2) cm patch cs:-123 Regards, Carlos
  6. Hi Alec, you can just create a new workspace in the new path. If it's big, you can copy the files from the old workspace so they shouldn't be downloaded again. But don't copy the old ".plastic" folder. The new workspace will create a new ".plastic" folder. Regards, Carlos.
  7. calbzam

    Plastic SCM Plugin for Crucible

    Hi Phil, I'm afraid a shelf is a temporary changeset with no id and it doesn't appear in the list when you are creating a new code review. Regards, Carlos.
  8. calbzam

    "Evaluation Guide Results "

    Hi, Could you reach us at support@codicesoftware.com? We will send you the free T-shirt. Regards, Carlos.
  9. Hi Mikael, Do you have a scenario/steps we can follow to reproduce the problem? Or is it randomly happening? Regards, Carlos.
  10. Hi, Every time you sync with git the sync settings and data are stored in the client directory. To completely delete all sync information about a previous git sync, first find out the repository GUID by running cm lrep --format="{repid}->{repname}->{repguid}" You'll get something like this: 6605->doc->fa890de2-16d1-435f-acf7-2a6b2f4d1f2c 6606->XBRL->f45fbfd3-95cb-4c32-8d15-06d1e2087063 6607->indexertest->e0cd9d8b-ee88-4c84-b524-4d9c6acaa35d 6608->monodevelop->c80bf02b-f394-4bd4-bba4-db5dbd49192c 6609->plasticdocu->3480b2d8-fd23-462b-bbf0-52a0fb48ea5d Find out your repo and copy the GUID. Now go to C:\Users<your-user>\AppData\Local\plastic4\sync\git (Windows) or $HOME/.plastic4/sync/git (linux) and delete the directory named after the repository GUID. Please have in mind that this will remove all mappings between Plastic SCM changesets and Git commit SHAs. It means that syncing against another git repo will probably create duplicate changesets in Plastic; however, if you just want to push your Plastic SCM repo to an empty Git repo, you'll be fine. All Plastic SCM data will be pushed into the git repo and the sync mapping will be created according to the new operation. Best regards, Carlos.
  11. calbzam

    Plastic 7.x incredibly slow?

    Hi, We would like to get connected to debug your scenario. I've sent you an email. Regards, Carlos.
  12. Hi, We are also in contact with Mikael debugging the issue via regular ticket. When refactoring/moving folders in your workspace, it will be a good idea to enable the Plastic Change Tracker service for Windows to precisely track file moves and renames beyond heuristic guessing. https://www.plasticscm.com/download/releasenotes/6.0.16.1151 It seems this service is still not properly working for Mikael, so we will update this ticket when we know what was the problem and we have all the details. Regards, Carlos.
  13. calbzam

    Shelving

    Hi, I'm afraid that creating a shelve directly in a cloud repo is not currently possible. If you are following a distributed workflow (pushing/pulling your local repos with the cloud), you will be able to create shelves for the local repos. Regards, Carlos.
  14. calbzam

    Cannot Undo Changes

    Hi, we are still evaluating the possibilities. I will get back to you as soon as possible. Sorry for the inconveniences, Carlos.
  15. Hi, I was able to reproduce the issue with Centos 6.3. If you previously install the following package, you shouldn't face any error with the certificate: sudo yum install ca-certificates Regards, Carlos.
×