CVSROOT=/afs/usatlas.bnl.gov/software/cvs. This mirror is available for checkouts only. The import and
commit operations should be performed with CERN ATLAS CVS repository
that is accessible by the kserver or ssh methods only. For information on CVS commit history or hyperlinked code browsing please refer to the U.S. ATLAS Software Server and CERN Software Development web page
There is also the local U.S. ATLAS CVS repository for the personal work of U.S. ATLAS members and development projects that might in future go to the ATLAS repository. The personal modules are named with usatlas account usernames. The location is at CVSROOT=/afs/usatlas.bnl.gov/project/localcvs and the web browser is available for this repository.
When working with CERN CVS repository, gserver or ssh access methods can be used (see this page for details). Note that kserver access method is no longer available (since June 1, 2008).
For gserver access method the CERN Kerberos Version 5 ticket is needed. It can be obtained with kinit command:
setenv (or export) CVSROOT :gserver:isscvs.cern.ch:/local/reps/atlas kinit <your CERN account>@CERN.CHAlso the executable
/opt/usatlas/bin/cvs should be used (automatically included in PATH in US ATLAS group environment)
The advantage of ssh method is that it does not require kerberos tickets to access the CERN CVS repository. The setup is:
setenv (or export) CVS_RSH "ssh" setenv (or export) CVSROOT ":ext:<your CERN account>@atlas-sw.cern.ch:/atlascvs"In case of problems with the CERN CVS repository that require administrative rights to the latter, contact
atlas-sw-cvsmanagers@cern.ch.
Note about CMT and CVS. In ATLAS release the packages have additional version directories which do not exist in the CVS repository. It is recommended to use cmt co operation for checkouts since it creates the correct directory hierarchy. See section 12 of CMT manual for details.
atlas-sw-tagapprove@cern.ch mailing list. For opened releases new versions are submitted through the Tag Collector web interface (with the condition that a developer must be in the managers or developers lists for the package). The new package versions appear in the next nightly build of the corresponding release.
Please note that this site is a content mirror of the BNL USATLAS TWiki. To edit the content of this page, click the Edit this page button at the top of the page and log in with your BNL USATLAS account.