Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up GitHub Actions to automate output QC/QA & server updates #48

Open
CeresBarros opened this issue Apr 24, 2024 · 0 comments
Open

Comments

@CeresBarros
Copy link
Member

Several CCISS workflow (and subworkflows) outputs need to be checked for consistency with one another and then uploaded to different cloud servers.
Bellow is a "QC workflow" that needs to be triggered everytime one of the objects with checkmarks is changed:

Image

Once the QC workflow completes successfully, it should trigger a second workflow that uploads a target object (not necessarily all the objects with checkmarks above) to cloud server ("uploading workflow"). Bellow is an example of an uploading workflow with feasibility tables:

Image

Notes:

  • Both the QC workflow and uploading workflow are implemented as GHActions.
  • The QC workflow needs to happen across several GH repos (any repo that alters a checkmarked object).
  • The QC will be implemented as an FFEC action (because it's essentially the same across many GH repos) - an FFEC actions repository will need to be created
  • The uploading workflow will happen in repos that host data (e.g. bcgov/SS_feasTable repo).*
  • QC workflow will need to download objects to be checked from where they were uploaded to - objects cannot be large.

* workflows that produce large datasets (e.g. BGC projections) automatically upload them to cloud servers, no GHActions needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant