CodeManagement: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:
<br>
<br>
<blockquote>
<blockquote>
''mu2e uses git for all code management.  There is one main repository for code (with BTrk, the Kalman fit, in a separate respository).  The code is primarly c++, with bash scripting, and some perl and python.  The code is distributed worldwide, including remote institutions and the grids by the cvmfs distributed disk system.  The code is built after every commit, and built and validated every night on the Jenkins build platform.''
''mu2e uses git for all code management.  There is one main repository for code (with BTrk, the Kalman fit, in a separate respository).  The code is primarly c++, with bash scripting, and some perl and python.  The code is distributed worldwide, including remote institutions and the grids with the cvmfs distributed disk system.  The code is built after every commit, and built and validated every night on the Jenkins build platform.''
</blockquote>
</blockquote>
<br><br>
<br><br>

Revision as of 23:36, 28 December 2016


mu2e uses git for all code management. There is one main repository for code (with BTrk, the Kalman fit, in a separate respository). The code is primarly c++, with bash scripting, and some perl and python. The code is distributed worldwide, including remote institutions and the grids with the cvmfs distributed disk system. The code is built after every commit, and built and validated every night on the Jenkins build platform.



  • For quick cut and paste...

checking out the main repository, with kerberos authentication for committing:

git clone ssh://p-mu2eofflinesoftwaremu2eoffline@cdcvs.fnal.gov/cvs/projects/mu2eofflinesoftwaremu2eoffline/Offline.git

checking out the main repository, readonly:

git clone http://cdcvs.fnal.gov/projects/mu2eofflinesoftwaremu2eoffline/Offline.git