Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #9272 Order of tags/branches permissions matters
    Actions
    Infos
    #9272
    Manuel Vacelet (vaceletm)
    2016-06-23 09:39
    2016-06-22 18:53
    9556
    Details
    Order of tags/branches permissions matters

    As of today, when I define:

    * RW:Developers
OFFICIAL/* RW:Integrators

    Developers will be allowed to write in "OFFICIAL" namespace, the rule should be written the other way aroud:

    OFFICIAL/* RW:Integrators
* RW:Developers

    To avoid un-necessary understanding by end users, we should:

    • Only allow '*' or '.../*' as supported pattern
    • Automatically order the rules according to
      • the fact that they have '*' in their definitions
      • the rule with more / should appear before the rule with less /
    SCM/Git
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Yannis ROSSETTO (rossettoy)
    Closed
    2016-06-23
    Attachments
    Artifact links
    Empty
    Empty
    References
    Referencing request #9272

    Artifact Tracker v5

    rel #8983 8.16
    story #8419 have permissions per tags/branches

    Release

    release #126
    Referenced by request #9272

    Other

    gerrit #6031
    gerrit #6032
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2016-06-22 18:54
    • Summary
      -Order of tags/branches permissions matter 
      +Order of tags/branches permissions matters