LArSoft Release Official Build - LArSoft/larsoft_docs GitHub Wiki
{{TOC}}
See the _Supported_platforms_ list for full details.
Builds:
- SLF6 on Jenkins
- SLF7 on Jenkins
- OSX Mojave on Jenkins with SIP disabled
- OSX High Sierra on Jenkins with SIP disabled
- Ubuntu LTS 16 on a vagrant box (build by request only)
- This step does not use mrb
- run build-larsoft from https://buildmaster.fnal.gov/view/LArSoft/
- change larsoft and larsoftobj version parameters as needed
- This will initiate debug and prof builds for the supported platforms.
- The build runs larutils/buildScripts/build-larsoft.sh from the head of larutils.
- If the build fails for a single platform, you can use the matrix option to rebuild just that piece.
- However, it sometimes works better to start a new “recover-larsoft” job. Edit the node list so you build on just the machine(s) that failed.
- use copyFromJenkins
- create a temporary directory on some local scratch disk
- cd to that directory
- …/copyFromJenkins -N -q s86-e17 -q s86-c2 build-larsoft
- this will pull all artifacts from the last successful build
- check carefully before proceeding
- artifacts of interest are tarballs and _MANIFEST.txt files
- At this time, Ubuntu builds are done from a vagrant box on woof or cluck
- It turns out that vbox instances work best when not shared
- Instructions for settting up an Ubuntu vagrant box: ubuntu-vm:Ubuntu_VM
- We use the same procedures that are used by the Jenkins build
- install larutils
vagrant ssh
mkdir devel
cd devel
git clone http://cdcvs.fnal.gov/projects/larutils - build in a working directory
vagrant ssh
mkdir build
cd build
git clone http://cdcvs.fnal.gov/projects/artutilscripts
env WORKSPACE=`pwd` LARVER= LAROBJ= QUAL= BUILDTYPE=debug ../devel/larutils/buildScripts/build-larsoft.sh
mv copyBack/ /vagrant/ldbg
env WORKSPACE=`pwd` LARVER= LAROBJ= QUAL= BUILDTYPE=prof ../devel/larutils/buildScripts/build-larsoft.sh
mv copyBack/ /vagrant/lprof
- use copyToSciSoft
- from the temporary directory
- …/copyToSciSoft *.bz2
- only files which are not already on SciSoft will be copied
- …/copyToSciSoft *.txt
- only files which are not already on SciSoft will be copied
- copyToSciSoft automatically puts the tarballs and manifests in the proper directories