DAQ release procedure
This page contains notes about the release procedure for the DAQ.
Note:These were generated after the first time I did a release and there were a number of problems. I will revise these notes the next time and verify that it all works as specified. 30nov04 MH.
Updated 15jul05 HM.
- Setup the devonline release to be the same as the base release needed for the new release.
- Log into e907daq as daq
- kinit as yourself
- cd /ppcboot/common/usr/local/mipp/releases/{release you want as base}
- setrel devonline; srt_setup
- run sync-online-rel -rel {tag name for the needed base release don't use the cvs tag format, but the srt format i.e. OLR-04.11.29}
- run mipp-build-rel -rel devonline
- Create a temp test release and populate with the changes for the production release
- log in as yourself
- newrel -t devonline tmprel
- cd tmprel; setrel devonline
- addpkg {packages that you want to add}
- make
- Test your test release and verify that everything is working as expected
- Make the cvs tag for the release
- From you test dir, make-online-rel
- use cvs -nQ rdiff -c -r tag1 -r tag2 -s mipp/online/Detectors... and ro cvsweb to verify that the tag worked correctly
- tag1 and tag2 like OL05-06-20.
- If some packages did not get tag you can tag by hand: cvs tag -b {tag name}
- build the new release
- log in as mippsoft
- mipp-import-rel -rel {new release tag, e.g. OLR-05.06.20}
- cd {to release directory}; setrel {release tag}
- mipp-build-rel -rel {release tag} -log {logfile}
- Build on e907daq and on one of the ppcs, maybe on one e907ana node
- Move configuration files
- Just copy files
- The rcd.xml file has to be edited so the default config dir is correct
- set prepro soft link
- test prepro
Mike Heffner
Last modified: Tue Nov 30 18:26:01 CST 2004