Instructions for Boole release

First check the number of the previous Boole release (e.g. v45r0) and then checkout which projects were used. (e.g. Boole v45r0 used Lbcom v34r20, LHCb v54r20, Detector v1r23, Gaudi v36r16 and LCG 103 with ROOT 6.28.00.)

How do we decide the new Boole release name

We will increment the version number if it has a Gaudi/LHCb not compatible with the previous one otherwise we will increment the release number. Last time it was v46r0. What about the milestone name? These are called Digi# If the raw data did not change the name is fine and the convention is year.month.day Digi17/2024.04.22 If the readout map changed (last time they did for FT and UT) we can add a letter to the name and therefore Digi17a/2024.04.22

Create a new Boole issue

In this issue all MR to be included in the new release will be listed. Depending on the projects involved in the Boole MRs we will decide weather we need a new version of Detector, LHCb, Lbcom and also if we need new tags for the conditions in DDDB, SIMCOND and if we need to merge requests in LHCb Conditions.

Create a milestone

If the new release includes Boole MRs only this can be within the Boole project otherwise we have to create it in Boole and then promote the milestone to the upper level. By doing so we can associate the milestone the MRs of other projects. Add the milestone to all the MR related to the new Boole release, by doing so it will be much easier to follow the progress of the preparation of the new Boole release

Follow the MR we would like to include in the new Boole release and interact with the sub-detector contacts and with the responsible for the new releases of the other needed projects. For Detector refer to Menglin, for SIMCOND to Sajan and for the rest ask Gloria.

Update Boole reference for required platforms

Once all of the needed MRs have been merged, we can update Boole references. For the selected compiler and platform check the outcome of the nightly build for Sim11

Log on lxplus and then get your Boole local version

• git clone https://gitlab.cern.ch/lhcb/Boole.git

• cd Boole

• git checkout -b edelucia_updaterefs

To update the refs for the new release of Boole with DetDesc:

• lbn-get-new-refs -c x86_64_v2-el9-gcc13+detdesc-opt lhcb-sim11 233 Boole

looking for slot: lhcb-sim11, build_id: 233, app: Boole, platform: x86_64_v2-el9-gcc13+detdesc-opt

Getting data from: https://lhcb-nightlies-artifacts.web.cern.ch/lhcb-nightlies-artifacts/nightly/lhcb-sim11/233/tests/x86_64_v2-el9-gcc13+detdesc-opt/newrefs/Boole.zip

Extracting specific refs…

Digi/Boole/tests/refs/boole-upgrade-baseline.ref.detdesc.new

Digi/Boole/tests/refs/boole-write-xdigi.ref.detdesc.new

Digi/Boole/tests/refs/boole-dump-raw.ref.detdesc.new

Digi/Boole/tests/refs/boole-VP.ref.detdesc.new

Digi/Boole/tests/refs/boole-reprocess-xdigi.ref.detdesc.new

Digi/Boole/tests/refs/boole-spillover.ref.detdesc.new

• cd Digi/Boole/tests/refs

After having cross checked the files name.new with the reference nightly build, rename the files and then create the MR for updating the refs

• git status

• git add -u

• git commit -m “update DetDesc refs”

• git push -u origin edelucia_updaterefs

Once the MR is created, we perform a test with respect to lhcb-sim11 with the following command

/ci-test –model lhcb-sim11

We can merge the MR with updated refs if the test is successful

Proceed with the new release of Boole and related projects if any

We need to release the whole stack and we use a codimd prepared by Rosen https://codimd.web.cern.ch/0uhnPEfwQD-7Waoj2M5Qqw

Log on lxplus

Use your Gitlab personal token (create a new one here https://gitlab.cern.ch/-/user_settings/personal_access_tokens)

export GITLAB_TOKEN=your_token

curl https://gitlab.cern.ch/rmatev/lb-stack-setup/raw/master/setup.py | python3 - stack

cd stack

make Boole/checkout lhcb-sim11

git clone https://git@gitlab.cern.ch/lhcb-core/lhcbstacks.git

ls lhcbstacks/data/stacks/Digi*

Copy the last yml file into the new one:

cp lhcbstacks/data/stacks/Digi17/2023.10.31.yml lhcbstacks/data/stacks/Digi17/2024.05.14.yml

Edit the file according to nightly build for Sim11.

name: Digi17/2024.05.14 (has to match the yml file name) type: lhcbcmake

projects:

Gaudi: v38r1 Detector: v2r6 LHCb: v56r0 Lbcom: v36r0 Boole: v46r0

toolchain:

type: LCG version: 105c

platforms:

• x86_64_v2-el9-gcc13-opt

• x86_64_v2-el9-gcc13-dbg

• x86_64_v2-el9-gcc13+detdesc-opt

• x86_64_v2-el9-gcc13+detdesc-dbg

tags:

• Run3

• Digi17

• Digi17b

Now we need to create a file release_config.yml with a content such as:

release: lhcbstacks/data/stacks/Digi17/2025.05.15.yml

base: lhcbstacks/data/stacks/Digi17/2024.05.14.yml

branches:

default: master

custom_project_deps:

LCG:

105c: “LCG [105a](http://lcginfo.cern.ch/release/105c/) with ROOT 6.30.08”

Then

Checkout the modified/extra scripts from LbDevTools/rm-release-tools

git clone https://gitlab.cern.ch/lhcb-core/LbDevTools.git

git -C LbDevTools checkout rm-release-tools

Generate, edit and open a MR with the release notes for every project

cd Detector

• python ../LbDevTools/LbDevTools/ReleaseNotes.py vlastrlast vnewrnew

• edit the release notes and add the branch name

• git checkout -b release-vnewrnew

• git status

• emacs CMakeLists.txt and change the project version

• Then edit DetectorDependencies.cmake in the cmake directory and check it.

• git add needed files

• git commit -m “prepare Detector vnewrnew”

git push -u origin release-vnewrnew

Then we are going to do the same thing for all other projects used by Boole

cd LHCb

python ../LbDevTools/LbDevTools/ReleaseNotes.py vlastrlast vnewrnew

git checkout -b release-vnewrnew

git status

emacs CMakeLists.txt and change the project version

Then edit LHCbDependencies.cmake in the cmake directory and put required Detector version and release.

git add needed files

git commit -m “prepare LHCb vnewrnew”

git push -u origin release-vnewrnew

cd Lbcom

python ../LbDevTools/LbDevTools/ReleaseNotes.py vlastrlast vnewrnew

git checkout -b release-vnewrnew

emacs CMakeList.txt and change the project version

Then change in directory cmake editare LbcomDependencies.cmake

git add needed files

git commit -m “prepare Lbcom vnewrnew”

git push -u origin release-vnewrnew

cd Boole and we do the same

We can proceed to tag and merge

1a. Merge in LHCb/Detector Prepare Detector release v2r0 adding the milestone of the Boole project and as label we put Simulation

2a. Go on Deploy releases => new release, search and create a tag name => we put new v2r0 for both tag name and release title.

The release date is the milestone Digi17a/2024.5. For the release notes we copy them from the file using Open raw. Then create release.

Then we can do the same for all the other projects (LHCb, Lbcom and Boole)

Commit push and open a MR in lhcbstack

If we go in our stack we have a file in /data/stacks/Digi17/2024.05.15.yml

Be sure to have a CR as last Line of the file

Git checkout -b Boole-run3-digi17a

git add /data/stacks/Digi17/2024.05.15.yml

git commit -m “ Add Digi17/2024.05.15 stack for run3 improve simulation“

git push -u origin HEAD -o merge_request.create

This creates a MR in lhcbstacks https://gitlab.cern.ch/lhcb-core/lhcbstacks and this starts a pipeline and then runs a test in the nightly https://lhcb-nightlies.web.cern.ch/releases/

In our case the MR is https://gitlab.cern.ch/lhcb-core/lhcbstacks/-/merge_requests/238

We can then close the Issue related to the Boole release and the associated Milestone

We just check the result of the release build outcome.

If everything is ok we put the tick and then to merge the request for the new release in lhcbstacks we go on the shifters database and find out who is on shift today for the software releases