CodeManagement: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 4: | Line 4: | ||
''mu2e uses git for all code management. There is one main repository for code (with BTrk, the Kalman fit, in a separate respository) and a few smaller repositories for tools. Built releases are 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.'' | ''mu2e uses git for all code management. There is one main repository for code (with BTrk, the Kalman fit, in a separate respository) and a few smaller repositories for tools. Built releases are 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> | |||
* [[GitMu2e|The Mu2e git page]] | * [[GitMu2e|The Mu2e git page]] | ||
Revision as of 17:14, 29 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) and a few smaller repositories for tools. Built releases are 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.
- The Mu2e git page
- Jenkins - a central build platform
- CVMFS - a distributed disk system to serve tagged, static code builds and products
- Download - pull a local copy to remote institutions or laptops
- BTrk - the KalMan fitter code is in this non-standard product