Difference between revisions of "NECI-testcode"
Jump to navigation
Jump to search
import>Js615 |
import>Js615 |
||
| Line 9: | Line 9: | ||
#!/bin/bash -x |
#!/bin/bash -x |
||
SVN=https://wwmm.ch.cam.ac.uk/svn2/groups/alavi |
SVN=https://wwmm.ch.cam.ac.uk/svn2/groups/alavi |
||
| − | |||
mkdir CLEAN |
mkdir CLEAN |
||
chgrp alavi CLEAN |
chgrp alavi CLEAN |
||
chmod 2775 CLEAN |
chmod 2775 CLEAN |
||
| − | |||
cd CLEAN |
cd CLEAN |
||
svn co $SVN/NECI/trunk NECI |
svn co $SVN/NECI/trunk NECI |
||
Revision as of 15:16, 12 October 2009
This is a new page to post info on how to migrate the test code between machines, as was done between discovery and scepter recently. I will be adding to this as and when I have spare time. --js615 12:52, 12 October 2009 (BST)
Setting up the testcode
1. Check out the components
This script written by JSS sets the correct permissions for the CLEAN directory, including the "2" sticky. To take advantage of these permissions, all group members need to add umask 2 to their .bashrc files.
#!/bin/bash -x SVN=https://wwmm.ch.cam.ac.uk/svn2/groups/alavi mkdir CLEAN chgrp alavi CLEAN chmod 2775 CLEAN cd CLEAN svn co $SVN/NECI/trunk NECI svn co $SVN/CPMD/branches/QMC/trunk CPMD svn co $SVN/testcode testcode
Although this example uses svn, other version control software can be used. Currently, svn and git are supported by the testcode.