You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present it seems reviewdog actions have to build the container image on ever (uncached) run.
This significantly increase the time it takes to run and the compute cost for reviewdog based Actions.
Solution
One way to improve this would be to build and publish container images and use those, image hosting for open source projects is free on Github using Github.
This greatly improves performance and cost of Docker based Actions.
Example
If the Actions still want to be a "Docker" type Action, you can simply keep their Dockerfile with that only includes a FROM for the image that's already been built:
FROM ghcr.io/reviewdog/some-cool-action:latest
and rename, build and publish existing Dockerfile which will be used for the builds.
An example of such a workflow might look like:
(assuming the "real" dockerfile is now called prebuild.Dockerfile
Problem
At present it seems reviewdog actions have to build the container image on ever (uncached) run.
This significantly increase the time it takes to run and the compute cost for reviewdog based Actions.
Solution
One way to improve this would be to build and publish container images and use those, image hosting for open source projects is free on Github using Github.
This greatly improves performance and cost of Docker based Actions.
Example
If the Actions still want to be a "Docker" type Action, you can simply keep their Dockerfile with that only includes a FROM for the image that's already been built:
FROM ghcr.io/reviewdog/some-cool-action:latest
and rename, build and publish existing Dockerfile which will be used for the builds.
An example of such a workflow might look like:
(assuming the "real" dockerfile is now called
prebuild.Dockerfile
The text was updated successfully, but these errors were encountered: