search

PNNL-CompBio / CONCERTO

Continuous integration and validation for genome-scale metabolic model consortia
Apache License 2.0
3 stars 3 forks source link

Updating model procedure #2

Closed JamesPino closed 1 year ago

JamesPino commented 1 year ago

For the gh-actions, we can specify when to trigger a build (and model update to memote tracking) based on branch. Right now I set it up to track any push at all, which is wasteful since a majority of pushes won't be modifying models. If we make 3 branches specifically used to update models update_av, update_rt, update_se, or a single branch for all update_models, then we can tag the workflow for changes in that(those) branch(es).

It's also possible to leverage the 'matrix' function in gh-action, so we can use a single workflow for all models instead of three. Just found this today.

JamesPino commented 1 year ago

For my second comment (using single gh-action instead of 3), it turns out that if the 3 workflows run at the same time there is a race to see which one commits the updated gh-page branch. The other 2 will fail because it sees there was an update in the middle of a commit. Looking at triggering them sequentially. If we did have a branch per model, this wouldn't be a concern.