Reusing/Caching the Compiled KiBot image

[alextrical]

Good day,
I expect this has been asked before but i cant seem to find the best way.
I'm using KiBot for DRC and ERC checks in a GitHub Action when a Change is submitted, for intergity checking. this looks to take around 3-8 seconds, however it recompiles KiBot every run, that takes ~1:30 to compile. Is there a guide you can point me to, to allow caching and reusing the KiBot container once its built, but be rebuilt if there are any changes coming from the upstream KiBot repo?

Kind regards
Ben J

[set-soft]

Hi @alextrical !
If you run KiBot locally and directly (no docker image) the pre-compiled Python code is automatically stored in __pycache__ subdirs. You don't need to do anything.

[alextrical]

Hi @set-soft
This is a new area of investigation to me, so please forgive my ignorance.

However when running as a GitHub action, the workflows I've been using always compiles the container. The Workflow is based on the github action found here https://cicube.io/workflow-hub/kibot-github-action/

I was hoping to skip the build process on every call. Either by working out how to cache the output to be reused in future GHA workflows, or by building an image to be uploaded to https://ghcr.io that can be reused

Kind regards

[alextrical]

Maybe im just being dumb. Is this the syntax I should be using to pull a pre-compiled image?

https://gitlab.kit.edu/uogxs/ci-config/-/blob/d55f29eeedae0daa438913effa62a8837453a359/kicad-ci.yml

[alextrical]

I suppose the apt question now is, is there a guide on how to setup Github actions to use "image: ghcr.io/inti-cmnb/kicad8_auto_full:latest"?

Is this the correct starting point?

KiBot/docs/GITHUB-ACTIONS-README.md

Line 20 in ff2c6ff

container: ghcr.io/inti-cmnb/kicad7_auto_full:latest # Don't Change, except if needing older version of KiCad.

Many thanks

[set-soft]

Hi @set-soft This is a new area of investigation to me, so please forgive my ignorance.

However when running as a GitHub action, the workflows I've been using always compiles the container. The Workflow is based on the github action found here https://cicube.io/workflow-hub/kibot-github-action/

I was hoping to skip the build process on every call. Either by working out how to cache the output to be reused in future GHA workflows, or by building an image to be uploaded to https://ghcr.io that can be reused

Ok, this is not a compilation, is the image creation.

GitHub actions works this way, if you want to make it faster, by using an already created images just don't use GitHub Actions.
The docs explains how and the workflows here are examples for actions and equivalents without actions.

You can find more examples here

The basic idea is that you specify the docker image you want and then run the commands, like using the command line interface.