Announcement

Collapse
No announcement yet.

Cnheckout/update once for all authorized folders under the same repo

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Cnheckout/update once for all authorized folders under the same repo

    I have a MyCompany repo whose folder structure as the following :

    MyCompany/
    └── departments
    ....├── HR
    ....├── Public
    ....│...├── OPS
    ....│...├── QA
    ....│...└── PM
    ....├── IPD
    ....└── develop
    ........├── IAP
    ........├── AM
    ........└── TM


    I have setup path-access:

    [MyCompany:/departments/Public/OPS]
    @g_ops=rw

    [MyCompany:/departments/HR]
    @g_ops=rw

    [MyCompany:/departments/develop/TM]
    @g_ops=rw


    i.e. group g_ops can only access departments/Public/OPS , departments/HR , departments/develop/TM , 3 folders.

    if @g_ops want to access departments/Public/OPS,
    they have to checkout/update from http://svn.mycompany.com/MyCompany/d...nts/Public/OPS
    if @g_ops want to access departments/HR,
    they have to checkout/update from http://svn.mycompany.com/MyCompany/departments/HR

    That is not convenient.

    I wonder that if it is possible that :
    @g_ops only have to checkout /update once from http://svn.mycompany.com/MyCompany/,
    they will "checkout /update" all the data of the folders which they are authorized to under the same repo automatically .
    The folder structure of their workspace may looks like this :

    MyCompany/
    └── departments
    ....├── HR
    ....├── Public
    ....│...└── OPS
    ....└── develop
    ....└── TM



    Thank you!
    Last edited by DougR; 07-27-2018, 07:11 PM. Reason: Another attempt to fix structure.

  • #2
    I call what you described "buried access" for exactly the reason that you must know the path exactly for the URL and the checkouts/updates/checkins can only occur to those paths. And you end up needing 1 working copy for each buried directory where access is enabled.

    You can either live with this OR choose to give them READONLY for the other paths from the root down. If you do the latter then they will be able to see the directory names down to their checkouts. Depending on how you write the rules, they'll either be able to see the other, uninvolved directories (and their contents) - or not.

    NOTE: SVN 1.10 has enabled wildcarding that might be very helpful if you choose to move toward the latter.

    Comment

    Working...
    X