...
We have agreed that the build log parser logic will be pulled out of RM and added to Jenkins, so that we can continue to pull out the most pertinent parts of the extensive build log which includes output for all packages not just the one subpackage a developer might be interested in.
Alternate workflow proposal: GlastTools SuperRepo
An alternate proposal was discussed and did not receive consensus. In this model all package repositories would be collapsed into 1 git repository containing the union of ScienceTools and GlastRelease packages. The two products would be considered different build targets for the build system. SCons would continue to be responsible for building the requisite packages for each target, and differentiating between external dependency versions. This would greatly simplify the Continuous Integration model as Jenkins.
Developers raised objections that moving to this model would be too disruptive to their current workflow, one based on CVS tags shared between distinct repositories.
GlastRelease
Matt asked who is going to be taking over GlastRelease. That is apparently Tom Stephens. Heather showed Tom the version that L1 is currently using.
...