Tag a new argoneutcode release » History » Version 4
Tag a new argoneutcode release¶
argoneutcode depends on larsoft and larbatch. Whenever there is a new version of larsoft or larbatch (normally happens weekly), we need to tag a new argoneutcode release to depend on the latest larsoft and larbatch. To find the current dependence on larsoft and larbatch, one can check srcs/argoneutcode/ups/product_deps and examine the following block:
# Add the dependent product and version product version larsoft v05_11_01 larbatch v01_21_04 cetbuildtools v4_19_04 - only_for_build end_product_list
To find out the latest larsoft and larbatch versions, do
ups list -aK+ larsoft
ups list -aK+ larbatch
Suppose the latest larsoft is v05_12_00 and the latest larbatch is v01_22_00, we need to tag argoneutcode v05_12_00.
First cd to the local argoneutcode directory:
Make sure you are on develop branch and get all the updates:
git checkout develop git pull
Start a release branch:
git flow release start v05_12_00
parent argoneutcode v05_12_00 larsoft v05_12_00 larbatch v01_22_00
Sometimes larsoft updates cetbuildtools version and if that's the case you should do this same here.
Commit your changes:
commit -a -m'v05_12_00'
Finish the release:
git flow release finish -m'v05_12_00'
and create the new tag and push the changes to origin develop and master:
git push --tags git push origin develop master
The tagging is done. A new tag v05_12_00 has been created and both remote develop and master have been updated to this new tag.
The next step is to start a Jenkins build:
You need to register and get a certificate. Click argoneut-release-build then click rebuild last from the left. Change the version of argoneutcode you want to build (v05_12_00 in this example) and start building. Unpack the tarballs (debug and prof) to /grid/fermiapp/products/argoneut/.