Skip to content

Conversation

AnomalRoil
Copy link
Contributor

Fixes #40

Comment on lines +93 to +95
type=registry,ref=${{ env.DOCKER_REGISTRY }}/${{ matrix.target.image }}-cache:${{ steps.meta.outputs.version }}
type=registry,ref=${{ env.DOCKER_REGISTRY }}/${{ matrix.target.image }}-cache:main-latest
cache-to: type=registry,ref=${{ env.DOCKER_REGISTRY }}/${{ matrix.target.image }}-cache:${{ steps.meta.outputs.version }},mode=max
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could reuse the same cache for all the images I guess, but for now we have different caches for each image. Note that this is a non-issue anyway, since the caches are stored in our Google docker registry and not in Github caches.

@GlacierWalrus
Copy link
Contributor

This is the kiss of death for our CI, you'll instigate the same ci flooding effect as we had for marshomono. There's a better way building this which I think I did somewhere... I'll see if I can dig it up

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

Successfully merging this pull request may close these issues.

matrixify the docker builds
2 participants