Oops! It appears that you have disabled your Javascript. In order for you to see this page as it is meant to appear, we ask that you please re-enable your Javascript!
close
Success

SVN Externals and the Command Line

1

Here at 11-Bridges / Staffing Robot we build custom client websites with custom themes and plugins. For version control, we use SVN across different platforms and use Tortiose and Versions as SVN clients to manage it. Lately, we’ve been realizing it will significantly improve our workflow if we use SVN externals. In doing so, we can make singular updates and selectively deploy these updates across an array of client projects.

We are using the CLI to propegate our SVN externals as follows:

Option One:

  1. Use the CLI & move to folder in which you plan to place the SVN external.
  2. Type the following (ignore ‘<’ & ‘>’):
    svn propset svn:externals ‘<new file name> <location of SVN branch>’ .
  3. Commit, then Update

Alternatives:

  • Cap external to a particular revision number (may or may not need a space between the r and the number):
    svn propset -r87 svn:externals ‘<new file name> <location of SVN branch>’ .
  • Also, using ‘–’ may prevent some issues:
    svn propset svn:externals — ‘-r87 <location of SVN branch> <new file name> ‘ .

Option Two:

If option one doesn’t work:

  1. Create txt file that includes:
    <new file name> <location of SVN branch>
  2. Save txt file in the folder in which yhou plan to place the SVN external.
  3. Use the CLI & move to folder in which you plan to place the SVN external.
  4. Type the followin into the CLI:
    svn propset svn:externals . -F <name of text file>.txt
  5. Commit, then Update

We are beginning to implement this process now. Look for an update down the road that further details our process using SVN externals and how it benefits to our workflow.
We would love to hear your comments if you have experience using SVN externals and the process in which you use them.

admin

The author admin