...
| Code Block |
|---|
cvs commit setEnv.csh gmaketst common/setup/setEnv.csh gmakedev common/setup/setEnv.csh |
In common/tool/ add the new server to procmanager and warmst, then cvs commit and release them. You have to release all teh way to new, because cddev does not have the "dev" directory in its path. So we can't test warmst until it's all the way to new.
- To procmanager script, add line for AIDA_RDB_NAME
- To warmst script, add line for new server
- cvs commit procmanager and warmst
- gmaketst common/tool, gmakedev common/tool, gmakenew common/tooltest aidamanager for AIDA_RDB_NAME.
Test starting the new server
In a new login on a development host (so as to pick up the additions to the environment released above):
- source /afs/slac/g/cd/soft/dev/script/ENVS.csh
- source !:1:h/aidaSetEnv.csh dev
- kinit (to get a token for the ssh done in the aidamanager step)
- aidamanager $AIDA_RDB_NAME start dev
You may like to have the cmlogviewer running while you do this.
Run the test suite, release it, and clean up
- Run the test suite you created for the server (as yet unreleaed) on the released server.
- aidatest dpRdbTest 1 2 3 etc
...
- Then release
- java/
- cvs add
- cvs commit
- matlab/
- test the array extraction in matlab.
- cvs add
- cvs commit
Compile the test suite in the released area:Code Block > addUserRefWrite > source $AIDASCRIPT/aidaSetEnvDev.csh dev > aidamake testsuite > removeUserRefWrite
Finally, aidamake all, to make the javadoc, zip file for Eclipse etc.
Test from the ref test examples.
Email Jingchen, ask him nicely to
- gmakenew package/aida/common/script, to new the st file
- create the "type I" st. file
Ask Bob nicely to:
- add DpRdb to server check
...
...
- add DpRdb to UWD