...
SVN is a version control system that enables groups of developers to code on the same software project and or files with little to no worries in terms of conflict of code. More importantly, it allows the branching and tagging of projects. Finally it provides a central repositry repository whereby developers can quickly and easily obtain the latest (or not so latest) versions of project code.
...
In order to access the SVN, you must have access to the SLAC machines (instructions for creating an account here). Users must also be part of the 'iepm' group.
The path for the SVN repositry repository is
| Code Block |
|---|
file:///afs/slac.stanford.edu/g/scs/net/netmon/repo/svn/ |
...
| Code Block |
|---|
$ cd /tmp/my_project $ svn update |
Restoring a
...
particular version of code
If you wish to discard your changes to a file, or you wish to 'roll back' to a version of the file/project then you can issue a update with the -r option to revert to the version specified.
| Code Block |
|---|
$ svn update -r version_no my_project Example: $ svn update -r 300 My.pm |
Administrative Details
...
/afs/slac.stanford.edu/g/scs/net/netmon/repo/svn/ + Relative Location <Relative Location>
Project Name | Relative Location | Description |
|---|---|---|
IEPM Base Libraries | iepm | This project contains the base/standard perl libaries that other project may depend upon. This should contain fundamental base classes that may or may not be extended/inherited by project specific modules. |
IEPM-BW | iepm-bw | This contains the iepm-bw related modules and scripts such as that to query for the IEPM-BW database, maintaince scripts etc. |
Netflow Analysis | netflow | For the Terapaths Project, this package contains the libraries, scripts and installation scripts required for the Netflow analysis backend and frontend |
PingER | pinger | PingER related scripts and modules |
topology | Topology analysis tools such as | |
event_diagnosis | This project contains scripts related to event diagnosis. Two types of scripts are present in distributions. Those to be deployed on Central Node and those which should be deployed at Monitoring Node. |