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

Refactor out common bits of CI pipeline? #702

Open
dc-mak opened this issue Nov 6, 2024 · 0 comments
Open

Refactor out common bits of CI pipeline? #702

dc-mak opened this issue Nov 6, 2024 · 0 comments
Labels
CI Related to CI infrastructure

Comments

@dc-mak
Copy link
Contributor

dc-mak commented Nov 6, 2024

#701 split up the CI into different pipelines, but there is a lot of common code between them. It's worth looking into whether or not using composite actions could reduce the duplication, and also how the opam cache works across the different workflows (presumably one per workflow right now?).

Especially because building cerberus and CN repeatedly seems unnecessary.

"Multiple workflow runs in a repository can share caches. A cache created for a branch in a workflow run can be accessed and restored from another workflow run for the same repository and branch." from here

Also this https://docs.github.com/en/actions/sharing-automations/reusing-workflows

Also this https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/passing-information-between-jobs

I think this means the current workflows are sharing a cache for opam? https://github.com/rems-project/cerberus/actions/caches

@dc-mak dc-mak added the CI Related to CI infrastructure label Nov 6, 2024
@dc-mak dc-mak changed the title Refactor out common bits of CI pipeline Refactor out common bits of CI pipeline? Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Related to CI infrastructure
Projects
None yet
Development

No branches or pull requests

1 participant