Search FAQ Search FAQ
Search Word(s):
Matching Options:
Search in:

Enabling SVN for an existing addon

1. Open the SVN page



2. Make sure your SVN account has been created

3. Find the project in the list

4. Tick its check box


5. Click "Enable SVN"


Creating an SVN for a new project

1. Open the SVN page



2. Scroll to the bottom

3. Enter new project name


4. Click "Create new SVN"


Checking out and Committing into your SVN

This guide is for command-line based SVN. There are GUI tools like TortoiseSVN which can make your life easier!

1. Open the SVN page



2. Find your SVN URL in the "Current SVN Projects" section at the top of the page


3. cd path/you/want/to/checkout/to

4. svn checkout

5. Create your files

6. svn add filename.lua

7. svn commit
* You will be prompted for username and password to commit, this is NOT the same as your forum login. You can find your SVN login by clicking "Login Info" at the top of the SVN page


You can find more help on how to use SVN at http://svnbook.red-bean.com/. You can also find some nice guides on using SVN and TortoiseSVN on the wowace wiki


Creating a release

1. Open the SVN page



2. Find your project under "Current SVN Projects"

3. Select "Make Zip" from the dropdown on the right


4. Enter in a release number. This is the same as the "File Version" in Upload & Update


* If this is a new repo not associated with a released addon, you will be prompted to select an existing addon or create a new one.


5. Select a release type. "Beta" indicates that your addon may not be stable, use at your own risk. "Stable" indicates that the addon is tested and safe for the mass public to use


6. Enter a description and changelog. These fields are the same as those in Upload & Update



7. Click "Generate Zip"


8. Review the file to ensure it is correct and complete


9. Click "Push Zip Live"


This will package everything in your /trunk and push it out as a release. If you want to put your files directly in /trunk (/trunk/AddonName.toc instead of /trunk/AddonName/AddonName.toc), you can set the "wowi:dirname" svn property on the trunk directory. This will force the packager to put all the files in /trunk into a folder with the name you specified.

1. svn propset wowi:dirname "AddonName" trunk/
2. svn commit


Let the CIA eavesdrop on your repository

1. Open the SVN page



2. Find your project under "Current SVN Projects"


3. Select "Miscellaneous" from the dropdown on the right


4. Enter a project name into the "CIA project name" field


5. Click "Update Options"


CIA.vc will echo your commit details into any IRC channel you want. Many developers have set up CIA bots on FreeNode, in channels like #WoWUIDev-commits.



Activating commit emails

1. Open the SVN page



2. Find your project under "Current SVN Projects"


3. Select "Miscellaneous" from the dropdown on the right


4. Enter an email address into the "Commit email" field


5. Click "Update Options"


An email with details about the commit and diff output will be sent whenever a commit is made.


You should probably use a mailing list like Google Groups to send your commit emails to. This allows any user who wishes to watch your project to subscribe easily.

Commit emails will come from svn@wowinterface.com


Hide your repository from the public

1. Open the SVN page



2. Find your project under "Current SVN Projects"


3. Select "Miscellaneous" from the dropdown on the right


4. Check "Disable public SVN viewing."


5. Click "Update Options"


Activating this option will make your repo private, only project members will be able to view and checkout.


Adding revision numbers automatically to TOC files

The string "wowi:revision" in ANY .toc file in the repository's trunk will be replaced with the current revision number of the entire repo when the files are zipped.


This is similar to the svn:keyword "$", except that the repo's current revision is used. The svn:keyword uses the last revision the file was modified (so to keep it up to date you would have to "touch" the file with every commit). Also note that, unlike the svn:keyword, the string will NOT be replaced for users that checkout your addon directly from your SVN. If for example you test the addon's current version during runtime, you should account for users with svn checkout copies.


Reset zip file generator

1. Open the SVN page



2. Find your project under "Current SVN Projects"


3. Select "Miscellaneous" from the dropdown on the right


4. Click "Reset Lockout"