•  
     
    story #8308 generic tag path specification
Summary
subversion admin
generic tag path specification
I'm not limited to the 2 options currently supported by Tuleap

In Subversion administration, management of the immutable tags is now in a dedicated section.

In this page, instead of the 3 options (no immutable tags, tags per modules, tags at root) the svn admin can enter the paths where tags stands:

  • /tags
  • /*/tags
  • /repository/projects/tags
  • ...

There is support for:

  • wildcards (only match one level of hiercharchy) but sevral possibles eg: /project/*/*/tags
  • whitelists (not limited to "tags at root" as it was done in story #8089).

This configuration is inherited from templates.

 

Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?

Configuration

  1. ForgeUpgrade -> transform existing values into textarea (Immutable tags in modules -> /*/tags/ && Immutable tags at root -> /tags/ + whitelist) + remove svn option
  2. No more option -> immutables tags are activated if there is at least one value in the textarea
  3. Remove methods in Project
  4. Adapt regexp
Details
#8308
Manuel Vacelet (vaceletm)
2016-06-24 15:17
2015-08-06 10:56
3216

References

Follow-ups

User avatar
Extracted the live preview in dedicated story #8316

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Attachments svn_live.png removed
  • Technical informations
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Technical informations
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Technical informations
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Attachments svn_live.png added
User avatar

* will it be possible to use multiple wildcards in one line : component/*/*/tags ?

Yes.

* in case of wild-cards, is it still possible to use white-list as well ? 

We didn' think about this case but I don't think it's an issue. Do you foresee a problem here ?

User avatar
Nouha Terzi (terzino)2015-08-07 09:28
Hello Manuel,

Just some questions to be sure we understand properly:
* will it be possible to use multiple wildcards in one line : component/*/*/tags ?
* in case of wild-cards, is it still possible to use white-list as well ?


thank you for your answers.

regards,
Nouha

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • CC list cleared values: None
  • Permissions set to