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

Improve CI efficiency #20

Open
4 tasks
forgottosave opened this issue Oct 16, 2024 · 0 comments
Open
4 tasks

Improve CI efficiency #20

forgottosave opened this issue Oct 16, 2024 · 0 comments
Labels
🧱 CI CI run related (bug, new feature,...) priority: 👇 low state: 🛠️work There is work to do here

Comments

@forgottosave
Copy link
Collaborator

forgottosave commented Oct 16, 2024

Description

The CI introduced in #19 can be drastically improved in efficiency, by creating a custom docker/container image based on fedora:latest where all dependencies required in most builds are already installed.

Tasks

  • Create custom container including all dependencies
  • Rebuild image automatically every once in a while so it stays up to date
  • As mentioned by @COM8, maybe it can be hosted inside the GitHub container registry, this needs further investigation (https://github.blog/news-insights/product-news/introducing-github-container-registry/)
  • Another side thing that would also improve "efficiency": Maybe properly define, what CI should run on which event (currently a lot of jobs run twice on a push to a PR)
@forgottosave forgottosave added state: ⏱️ planning is in planning priority: 👇 low 🧱 CI CI run related (bug, new feature,...) labels Oct 16, 2024
@forgottosave forgottosave mentioned this issue Oct 16, 2024
9 tasks
@forgottosave forgottosave added state: 🛠️work There is work to do here and removed state: ⏱️ planning is in planning labels Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧱 CI CI run related (bug, new feature,...) priority: 👇 low state: 🛠️work There is work to do here
Projects
None yet
Development

No branches or pull requests

1 participant