MuseMaintenance: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 24: | Line 24: | ||
==Publishing Production tags== | ==Publishing Production tags== | ||
Production contains most of the top-level fcl to use Offline, so is often updated and published at the same time as Offline. | Production contains most of the top-level fcl to use Offline, so is often updated and published at the same time as Offline. To "build" and publish a tag of Production with tag name ''tag'', in a scratch area. | ||
setup mu2e | |||
setup muse | |||
git clone https://github.com/Mu2e/Production | |||
git -C Production checkout -b temp ''tag'' | |||
muse setup | |||
muse build | |||
muse tarball -r Production/''tag'' | |||
You will get an output tarball. In a second window, in the same directory | |||
setup mu2e | |||
setup muse | |||
muse setup -q debug | |||
muse build | |||
muse tarball -r Production/''tag'' | |||
Then on the cvmfs installation machine | |||
* log onto the [[Cvmfs|cvmfs]] machine, and start a transaction | |||
* cd to /cvmfs/mu2e.opensciencegrid.org/Musings/, wget the tarball, extract it (bzipped, use "-j") | |||
* remove tarball | |||
* repeat for the debug tarball | |||
* if needed, repoint the "Production/current" link to this new tag | |||
* cd ~ and publish the transaction | |||
Revision as of 20:11, 17 June 2021
Publishing Offline tags
When Offline is tagged, it needs to be build and published on cvmfs in Muse format. A jenkins build project is used to build prof and debug in parallel. If the build fails, the project will return an error. The output is tarballs that can then be installed on cvmfs.
- go to jenkins mu2e-offline-build-muse project. (Requires an account and a cert in the browser.)
- select "Build with Parameters", enter the tag string, and hit "Build". takes about 45 min.
- When done, select "BUILDTYPE=prof"
- if anything went wrong, select "last build" and look at the console output and the log file
- under artifacts, right click on the tarball and "copy link address"
- log onto the cvmfs machine, and start a transaction
- cd to /cvmfs/mu2e.opensciencegrid.org/Musings/, wget the tarball, extract it (bzipped, use "-j")
- remove tarball
- repeat for the debug tarball
- if needed, repoint the "Offline/current" link to this new tag
- cd ~ and publish the transaction
- once cvmfs is updated, test with
muse setup tag
The script that this project runs is in the codetools repo,
codetools/bin/jenkinsMuseBuild.sh
When the jenkins project is run, it checks out the head of codetools to find the script.
Publishing Production tags
Production contains most of the top-level fcl to use Offline, so is often updated and published at the same time as Offline. To "build" and publish a tag of Production with tag name tag, in a scratch area.
setup mu2e setup muse git clone https://github.com/Mu2e/Production git -C Production checkout -b temp tag muse setup muse build muse tarball -r Production/tag
You will get an output tarball. In a second window, in the same directory
setup mu2e setup muse muse setup -q debug muse build muse tarball -r Production/tag
Then on the cvmfs installation machine
- log onto the cvmfs machine, and start a transaction
- cd to /cvmfs/mu2e.opensciencegrid.org/Musings/, wget the tarball, extract it (bzipped, use "-j")
- remove tarball
- repeat for the debug tarball
- if needed, repoint the "Production/current" link to this new tag
- cd ~ and publish the transaction