MuseMaintenance: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
(Created page with " ==Publishing Offline tags== When Offline is tagged, it needs to be build and published on cvmfs in Muse format * go to jenkins [https://buildmaster.fnal.gov/bui...")
 
No edit summary
Line 2: Line 2:
==Publishing Offline tags==
==Publishing Offline tags==


When Offline is tagged, it needs to be build and published on cvmfs in Muse format
When Offline is tagged, it needs to be build and published on cvmfs in Muse format.  A [[Jenkins|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|jenkins]] [https://buildmaster.fnal.gov/buildmaster/view/mu2e/job/mu2e-offline-build-muse/ mu2e-offline-build-muse] project.  (Requires an account and a cert in the browser.)
* go to [[Jenkins|jenkins]] [https://buildmaster.fnal.gov/buildmaster/view/mu2e/job/mu2e-offline-build-muse/ mu2e-offline-build-muse] project.  (Requires an account and a cert in the browser.)
Line 16: Line 16:
* cd ~ and publish the transaction
* cd ~ and publish the transaction


The script that this project runs is in the '''codetools''' repos,
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.





Revision as of 21:44, 16 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 "current" link to this new tag
  • cd ~ and publish the transaction

The script that this project runs is in the codetools repos,

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.