Project

General

Profile

What Lynn does » History » Version 49

Joe Boyd, 12/10/2019 09:44 AM

1 1 Lynn Garren
h1. What Lynn does
2 1 Lynn Garren
3 30 Lynn Garren
{{TOC}}
4 16 Lynn Garren
5 40 Joe Boyd
h2. Build "third party" ups products as needed for art and larsoft 
6 40 Joe Boyd
7 45 Joe Boyd
<pre>
8 49 Joe Boyd
For immediate term using old methods Chris Green will have to take care of this,  Jim A should be the one to tell 
9 49 Joe Boyd
these people this but in the future using SPACK here are some examples of people that could maybe take these pieces
10 40 Joe Boyd
11 40 Joe Boyd
  * ROOT: Philippe / Physics and Data Simulation.
12 40 Joe Boyd
  * GENIE: Robert Hatcher / Neutrino Simulation.
13 40 Joe Boyd
  * GEANT4: Krzysztof / Physics and Detector Simulation.
14 40 Joe Boyd
  * PostGresQL, Psycopg,  SQLite, MySQL, MariaDB: Scientific Database Applications.
15 40 Joe Boyd
  * nucondb, ifbeam, ifdhc, ifdh-art, etc. (and unique dependencies): Compute
16 1 Lynn Garren
    Services Tools.
17 1 Lynn Garren
  * PyTorch, libtorch, TensorFlow, Eigen, Caffe (legacy): Algorithms for
18 45 Joe Boyd
    Reconstruction and Analysis.
19 45 Joe Boyd
</pre>
20 42 Joe Boyd
21 7 Lynn Garren
* We have a [[build-framework:|defined procedure]] that uses a number of scriptlets found in the ssibuildshims product.
22 5 Lynn Garren
* Each product has a tiny redmine repository for the build and bootstrap scripts.
23 9 Lynn Garren
** Scripts include autobuild.sh, bootstrap.sh, build_xxx.sh, and usually ups/xxx.table, where xxx is the product name.
24 9 Lynn Garren
** We sometimes need patch files.
25 9 Lynn Garren
** Other scripts are occasionally included, such as bootstrap_datasets.sh for geant4.
26 10 Lynn Garren
** We tag these repositories with the product version.
27 5 Lynn Garren
* To ensure reproducible builds, we only build from tagged releases.  In rare cases, we use a commit hash.
28 1 Lynn Garren
* We require that the source code be captured in a source code tarball for reproducible builds.
29 6 Lynn Garren
* We bootstrap and run local test builds for the supported compiler options.  This is a rapid turnaround development step.
30 14 Lynn Garren
** Whenever possible, we run unit tests as part of the build procedure and require that these tests pass.
31 6 Lynn Garren
* Once everything looks good, the source code tarball is uploaded to SciSoft.
32 12 Lynn Garren
* Also provide help to people attempting to make their own ups products.
33 5 Lynn Garren
34 48 Joe Boyd
h2.  Build art releases after they are tagged.
35 48 Joe Boyd
36 48 Joe Boyd
<pre>
37 48 Joe Boyd
SciSoft team would take this over
38 48 Joe Boyd
critic distribution includes everything
39 48 Joe Boyd
</pre>
40 1 Lynn Garren
41 1 Lynn Garren
* Kyle sends around an email to the SciSoft Team when a release is tagged.
42 1 Lynn Garren
* Update information in build-framework/CMakeLists.txt
43 1 Lynn Garren
** There are multiple branches for different product configurations
44 1 Lynn Garren
* Run cmake to get the new build configuration files.
45 1 Lynn Garren
* Check the new config files.
46 1 Lynn Garren
** Always compare against the previous release.
47 3 Lynn Garren
* If they are OK, use copyToSciSoft to install ONLY the appropriate build configuration files on SciSoft.  There are html files for each release that also need to be installed.
48 1 Lynn Garren
** canvas
49 1 Lynn Garren
** art
50 1 Lynn Garren
** gallery
51 1 Lynn Garren
** critic
52 1 Lynn Garren
* Start a Jenkins build
53 1 Lynn Garren
** https://buildmaster.fnal.gov/buildmaster/view/Art/job/critic-all/
54 1 Lynn Garren
** The build needs two iterations.  First for python 2 (the LABEL field is empty) and then a second pass with LABEL set to py3.
55 2 Lynn Garren
* Sometimes there are problems with the build.
56 2 Lynn Garren
** Investigate and fix.
57 2 Lynn Garren
** A local test build is sometimes helpful, depending on the problem.
58 2 Lynn Garren
* Once the build has completed successfully, download the tarballs locally and then upload them to SciSoft.
59 2 Lynn Garren
** Work in an empty directory
60 2 Lynn Garren
** copyFromJenkins -N -q c2 -q c7 -q e17 -q e19 critic-all
61 2 Lynn Garren
** copyToSciSoft *
62 4 Lynn Garren
63 35 Joe Boyd
h2. Update other products to use the appropriate release of art (SciSoft team or experiments, see bullet notes)
64 12 Lynn Garren
65 47 Joe Boyd
* artdaq_core (This should go to the artdaq group -- Eric Flumerfelt, Lynn says we just need a tag)
66 12 Lynn Garren
** Owned by the artdaq group
67 12 Lynn Garren
** This product is designed to build against several different releases of art, as reflected in the generated table file.
68 12 Lynn Garren
** If the head of develop matches the latest tag, then use git flow to tag against the head of develop.  Otherwise make a release branch against the latest tag and edit product deps.
69 12 Lynn Garren
** We only edit ups/product_deps to make a new release.
70 37 Erica Snider
* ifdh_art (SciSoft)
71 12 Lynn Garren
** This is the ifdh service developed by Marc Mengel at the request of the art team.
72 12 Lynn Garren
** ifdh_art can build against several different releases of art.
73 12 Lynn Garren
** ifdh_art is updated when libwda or ifdhc is updated or if it needs to recognize a new release of art.
74 37 Erica Snider
* nutools (Robert Hatcher?)
75 12 Lynn Garren
** This product is owned by NOvA
76 12 Lynn Garren
** However, larsoft uses it extensively and sometimes makes contributions to the code.
77 22 Lynn Garren
** Any changes beyond those required by a new release of art, genie, or geant4 must be approved.
78 12 Lynn Garren
79 36 Joe Boyd
h2. Build mu distributions ( mu2e should take this over)
80 11 Lynn Garren
81 11 Lynn Garren
* The mu distribution is basically an art distribution with a few additional products.
82 12 Lynn Garren
* The distribution is built when requested.
83 11 Lynn Garren
* Found on a branch of build-framework
84 11 Lynn Garren
85 39 Joe Boyd
h2. Build nutools releases and the nu or nulite distributions. (Erica will talk to Laura Fields about Robert Hatcher doing this)
86 1 Lynn Garren
87 1 Lynn Garren
* Both NOvA and LArSoft can drive the need for a new release of nutools.
88 11 Lynn Garren
** NOvA uses the full nu distribution.
89 11 Lynn Garren
** LArSoft now uses the nulite distribution which ignores packages that are NOvA specific.
90 29 Lynn Garren
* nutools has been split into modular components.
91 29 Lynn Garren
** This was a staged deployment.  As of nutools v3_05_00, only the CRY interface remains in nutools.
92 29 Lynn Garren
** The nutools suite now contains nusimdata, nugen, nug4, nuevdb, nurandom, and nutools.
93 29 Lynn Garren
** The build configure scripts are now generated from templates in nutools/bundle.
94 11 Lynn Garren
95 32 Joe Boyd
h2. LArSoft release management (SciSoft team plus experiment activity on patch releases)
96 28 Joe Boyd
97 29 Lynn Garren
* Note that the move to github and pull requests will change this workflow.
98 1 Lynn Garren
* Advise and collect information for each weekly release.
99 22 Lynn Garren
** I am often the first point of contact for code changes.
100 22 Lynn Garren
** Sometimes push back about proposed changes.
101 12 Lynn Garren
* Send notices that the release is about to start.
102 12 Lynn Garren
* Make a test build with larsoft and all the experiment code.
103 12 Lynn Garren
** From long experience, if there is more than one set of feature branches to merge, each set must be tested sequentially.
104 12 Lynn Garren
** While this could be done via CI, it is currently more efficient to test on woof.  Especially since overlapping feature branches must sometimes be tested.
105 12 Lynn Garren
** We do encourage anyone submitting a feature branch to run the CI themselves.
106 12 Lynn Garren
* We work on a temporary release branch.
107 12 Lynn Garren
* Once the tests are complete and successful, update the release versions for those packages which will be changing and then tag.
108 12 Lynn Garren
* The tag is merged with master, but not with develop. 
109 12 Lynn Garren
** Merging with develop before the tagged release is available on cvmfs causes all kinds of problems. 
110 12 Lynn Garren
* Build on Jenkins.  Sometimes we find problems during this step.  We move the tag if necessary when resolving problems.
111 12 Lynn Garren
* Once the build is complete, we finalize the release.
112 12 Lynn Garren
** pull the tarballs from Jenkins and upload them to SciSoft
113 12 Lynn Garren
** install the release on cvmfs
114 12 Lynn Garren
** For macOS building, we install the c2 build on /grid/fermiapp/products/larsoft
115 12 Lynn Garren
** make a cross package tag
116 12 Lynn Garren
** make release notes
117 12 Lynn Garren
** final merge with develop
118 12 Lynn Garren
** send an announcement
119 12 Lynn Garren
* The procedure is described in detail at [[larsoft:How_to_tag_and_build_a_LArSoft_vx_yy_zz_release]]
120 12 Lynn Garren
** Although it is tempting to take shortcuts, the procedure is designed to allow the release manager to recover from various problems that may arise.  Taking shortcuts removes those safeguards.
121 13 Lynn Garren
122 32 Joe Boyd
h2.  support various infrastructure products (SciSoft team)
123 15 Lynn Garren
124 15 Lynn Garren
* cetbuildtools and mrb
125 15 Lynn Garren
** both products were originally developed by me, but have significant contributions from others
126 15 Lynn Garren
** We have provided cetmodules for use within spack and are contemplating a move across the board from cetbuildtools to cetmodules.  Details need to be considered.
127 15 Lynn Garren
* larreltools
128 1 Lynn Garren
** Replaces laradmin
129 16 Lynn Garren
** Contains scripts used to build regular and patch releases of larsoft
130 15 Lynn Garren
* larutils
131 15 Lynn Garren
** The larsoft build scripts used on Jenkins reside in larutils
132 15 Lynn Garren
* artutilscripts
133 15 Lynn Garren
** The build scripts used when building art, nutools, etc. on Jenkins reside in artutilscripts. 
134 18 Lynn Garren
** This is also where buildFW, pullProducts, copyFromJenkins, copyToSciSoft, etc. are found.
135 15 Lynn Garren
* laradmin
136 15 Lynn Garren
** This is now only of archival interest
137 15 Lynn Garren
** It contains the record of various larsoft migrations.
138 15 Lynn Garren
139 21 Lynn Garren
h2. SciSoft
140 21 Lynn Garren
141 21 Lynn Garren
* approve requests for read-write access
142 21 Lynn Garren
** The possibility exists for someone to accidentally remove or overwrite products.
143 21 Lynn Garren
** For this reason, we use nfs4 groups to limit read-write access to necessary directories.
144 21 Lynn Garren
** Some members of the SciSoft team have read-write access to all of SciSoft.
145 21 Lynn Garren
* copy files to pnfs for archiving
146 21 Lynn Garren
** There is a procedure, but it is slow and not automatic.
147 21 Lynn Garren
148 13 Lynn Garren
h2. spack
149 13 Lynn Garren
150 13 Lynn Garren
* I attempt to help with the spack development, but this takes a back seat to the other efforts.
151 19 Lynn Garren
152 32 Joe Boyd
h2. heppdt (mu2e should take this over, Kutschke)
153 19 Lynn Garren
154 19 Lynn Garren
* This is a legacy product that was spun off as a C++ replacement for part of the original stdhep.
155 19 Lynn Garren
* It is still in use by mu2e.
156 20 Lynn Garren
157 23 Lynn Garren
h2. Mailing lists
158 23 Lynn Garren
159 23 Lynn Garren
* owner/manager of several mailing lists
160 23 Lynn Garren
** many are unused and can be retired
161 23 Lynn Garren
162 32 Joe Boyd
h2. CLHEP maintenance and support (someone at CERN)
163 20 Lynn Garren
164 20 Lynn Garren
* I have been the main point person for CLHEP bug fixes.
165 20 Lynn Garren
* Support will be passed to CERN.
166 24 Lynn Garren
167 25 Lynn Garren
h2. system management
168 24 Lynn Garren
169 26 Lynn Garren
* Still provide backup support for oink.  Rare that I do anything.
170 25 Lynn Garren
* detsim.fnal.gov
171 25 Lynn Garren
** Now supported by CCD