Difference between revisions of "HOWTO Create a New Hall D Software Release"

Revision as of 16:29, 7 April 2022

Instructions updated 04/07/2022

This should only be done by the Hall D software coordinator

1) Start with the previous release, usually linked to version.xml. Increment one of the numbers (main, update, bugfix), e.g.:

cp version_5.5.0.xml version_5.6.0.xml

2) Edit file, date and description of the xml file:

<gversions file="version_5.6.0.xml" date="2022-04-07">
<description>Update releases of amptools, halld_recon, halld_sim, gluex_root_analysis, and hd_utilities.</description>

3) Create new releases of the relevant packages on github. The simplest way is to go through this link:
https://halldweb.jlab.org/halld_versions/version.xml

4) Substitute new releases in xml file, removing eventual dirtags

<package name="halld_recon" version="4.36.0"/>

5) Source new xml file, e.g.

gxenv version_5.6.0.xml

6) Add dirtags for each "version mismatch found"

<package name="hdgeant4" version="2.33.0" dirtag="hdr4360"/>

7) Log into sandd1 as gluex

ssh gluex@sandd1

8) Change into the directory where you want to save the build logs

cd ~/chore/log_archive

9) Launch the build on 4 different machines: CentOS7, RHEL7, RHEL8 and in singularity container (also CentOS7)

~/bin/build_version_set_all.sh version_5.6.0.xml

10) Check log files. If one build fails, relaunch 9) after all processes finish.

11) Update the soft link to version.xml in the halld_versions repository on github. A cronjob on sandd1 will synchronize the group disk at midnight.