#2692 Allow svn checkout customization - INI UPDATE

v1.0.0
closed
SCM
nobody
2015-08-20
2011-08-25
No

Our SVN checkout URLs always append /trunk since that is a common pattern, but it doesn't work with all projects. Also, it doesn't work on new empty repos.

We could check to see if 'trunk' is present and if not, omit the 'trunk' append. Additionally, it could be nice to let admins customize the checkout path to whatever they want.

Related

Tickets: #2523

Discussion

  • Mark Ramm

    Mark Ramm - 2011-08-31
    • milestone: limbo --> backlog
     
  • Tim Van Steenburgh

    Add SVN config setting for default checkout path, and default it to /trunk. And for new SNV repos, do an initial commit to setup /trunk, /branches, /tags.

    • size: --> 2
     
  • Jenny Steele

    Jenny Steele - 2011-09-07
    • status: open --> in-progress
    • assigned_to: Jenny Steele
     
  • Jenny Steele

    Jenny Steele - 2011-09-09
    • status: in-progress --> code-review
    • assigned_to: Jenny Steele --> Rick Copeland ☕
     
  • Jenny Steele

    Jenny Steele - 2011-09-09

    There isn't a good way to make this configurable since our config options are editable after the tool is created, so I just made this create /trunk /tags and /branches in the repo init step so the checkout url makes sense.

     
  • Dave Brondsema

    Dave Brondsema - 2011-09-12

    I think a config option is still useful, it's not a problem for admins to set that after the repo is created, in case they remove trunk/tags/branches and use something else. E.g. https://sourceforge.net/adobe/cairngorm/code/

     
  • Rick Copeland - 2011-09-14
    • status: code-review --> in-progress
    • assigned_to: Rick Copeland ☕ --> Jenny Steele
     
  • Rick Copeland - 2011-09-14

    Please also add an option to customize what gets displayed for the checkout url in svn. (and hg/git if it makes sense)

     
  • Jenny Steele

    Jenny Steele - 2011-09-26
    • status: in-progress --> code-review
    • assigned_to: Jenny Steele --> Rick Copeland ☕
     
  • Dave Brondsema

    Dave Brondsema - 2011-09-27
    • assigned_to: Rick Copeland ☕ --> Tim Van Steenburgh
     
  • Tim Van Steenburgh

    Seems to work ok, but I'm concerned about the changed asserts in the clone_from method. I think the svnsync calls should return 0 on success, which means the clone_from test is failing for some reason.

    If svnsync returns # of commits on the source repo, we still have a problem, since the code is now asserting that we'll never clone a repo with more than 1 commit.

     
  • Tim Van Steenburgh

    • status: code-review --> in-progress
    • assigned_to: Tim Van Steenburgh --> Jenny Steele
     
  • Jenny Steele

    Jenny Steele - 2011-10-18
    • status: in-progress --> code-review
    • assigned_to: Jenny Steele --> Tim Van Steenburgh
     
  • Jenny Steele

    Jenny Steele - 2011-10-18

    I figured out that svn didn't want to clone into a repo that already had data, so for clones I made it not set up the default dirs.

     
  • Tim Van Steenburgh

    Merged to dev.

     
  • Tim Van Steenburgh

    • summary: Allow svn checkout customization --> Allow svn checkout customization - INI UPDATE
    • status: code-review --> closed
    • assigned_to: Tim Van Steenburgh --> Jenny Steele
     

Log in to post a comment.