https://srs.slac.stanford.edu/hudson/view/Fermi/job/Fermi/job/GlastRelease-CI/
For GR, we are primarily concerned about the L1 processing and the L1 branch of GR.
Why does seemingly every commit to any package in fermi-lat trigger a GR build? This makes it very difficult to follow the build history
Trigger builds in Jenkins, making sure to specify the L1 branch
There was a problem with the builds since Feb 12th that Brian fixed last night.
His build 858 succeeded last night, I tried again this morning and received another build failure 859
ERROR: Could not find a version that satisfies the requirement gitdb>=4.0.1
While Brian's build did:
Collecting gitdb2<3,>=2 Downloading gitdb2-2.0.6-py2.py3-none-any.whl (63 kB)
Building L1
Grabs (tip?) of L1 branch for those packages with L1 branch defined: INFO:root:Checkout out spec: astro origin/L1
If I tag GlastRelease in GitHub, will that trigger a build in Jenkins? Or do I trigger that manually using the tag name?
Release tags in Github will not trigger a build
Brian will fix up builds so not everything is
start manual build without develop flag in Jenkins using the tag, and the tagged packageList.txt contents will dictate the versions of the packages
We are still installing to u52 NFS - not automated yet from Jenkins - Brian may work on that
New dir structure to update to CVMFS???? Stephen Zimmer's set up?