[ ] Add everyone to the role accounts (Guillaume, Cory, Russ, David, Dan)
[ ] Establish cron script running under the role account on each machine that periodically checks the hashes of the current JEDI repos in GDASapp and builds those hashes if an existing build of those hashes does not exist.
GDASapp
[ ] Separate the part of the script that build JEDI repos and the part that build the gdas.x, oops-based code and Ctests. JEDI bundle build should be one step and GDAS build another step that points to JEDI bundle build somehow.
[ ] Append GDAS build script to optionally look for existing build under the role account of that machine. If appropriate build is found, link to that instead of building JEDI again. Note: it might be sensible to keep the default mode to build JEDI from scratch. If always linking people could run into trouble if they then pull from a develop that has moved onto to a newer version of JEDI. There would be no mechanism to let them know to recreate the link.
global-workflow
[ ] Fork g-w to someone's GitHub and set autoupdating. Establish protected branch that will serve as the GDASapp develop.
[ ] Establish a minimal CI algorithm that tests what Russ is running manually, e.g. GFS17/18 runs. This should be quick(ish) to run and using the fixed JEDI builds. Maybe one half and one full cycle at coarsest possible res.
Offline JEDI build
GDASapp
global-workflow