fix: Properly collect Python dependencies during image build. Next attempt at build cache #47
Conversation
…tempt to build cache * `Dockerfile`: fixed installing Python package dependencies (should use same `pip install --root...`) * Github Actions: switched to `registry` cache for Docker build, as `gha` one didn't result in any hits
|
Please retry analysis of this Pull-Request directly on SonarCloud |
1 similar comment
|
Please retry analysis of this Pull-Request directly on SonarCloud |
platform, utilizing separate build cache - previously a single step build all target platform didn't use the cache resulting in very long build time
|
|
Please retry analysis of this Pull-Request directly on SonarCloud |
potentially it could lead to build cache not being utilized
|
Please retry analysis of this Pull-Request directly on SonarCloud |
1 similar comment
|
Please retry analysis of this Pull-Request directly on SonarCloud |
since there is a known issue it might prevent utilizing the cache
|
Please retry analysis of this Pull-Request directly on SonarCloud |
|
`build-push-action`, since version couldn't be determined when using default Git context for the action
|
version for `setuptools_scm`
|
Please retry analysis of this Pull-Request directly on SonarCloud |
* Github Actions: pass version override via `VERSION` build arg instead of environment variable when building the Docker image
|
Please retry analysis of this Pull-Request directly on SonarCloud |
|
Please retry analysis of this Pull-Request directly on SonarCloud |
the platform name doesn't pass Docker Buildx requirements to cache ref
|
Please retry analysis of this Pull-Request directly on SonarCloud |
|
the image tag being built, the prefix will be the version
name to the `build-push-action`
|
Please retry analysis of this Pull-Request directly on SonarCloud |
1 similar comment
|
Please retry analysis of this Pull-Request directly on SonarCloud |
|
Please retry analysis of this Pull-Request directly on SonarCloud |
produced by `docker/metadata-action` as JSON, so they could be handled by `github-action-matrix-outputs-write`
|
for tags and annotations via JSON representation (`docker/metadata-action`, `json` output)
tags/annotations/digests considering nested JSON structure
|
Docker image metadata has been moved to separate jobs, since those don't need to be matrix ones
|
in `{value: <digest>}` object each, so later
those could be dereferenced using `.*.value` syntax
|
Please retry analysis of this Pull-Request directly on SonarCloud |
|
construct arguments for `docker buildx imagetools create` command - should be easier compared to `jq` and alike
|
Please retry analysis of this Pull-Request directly on SonarCloud |
`docker buildx imagetools create` command - should use `tag` and `annotation` instead of `tags` and `annotations`
|
Please retry analysis of this Pull-Request directly on SonarCloud |
|
manufest, as annotations aren't supported there - instead, there are added to each image built
|
operation at a time, otherwise GHCR responds with 403 when multiple tags are provided to `buildx imagetools create`.
|
Please retry analysis of this Pull-Request directly on SonarCloud |
|
Dockerfile: fixed installing Python package dependenciesDockerfile: restructured to minimize chances of cache invalidationregistrycache for Docker build, asghamight reduce hit ratio (see Best way to cache multi-stage + multi-platform image builds docker/buildx#1382 for details)buildxinvocation with multiple platforms doesn't result in proper caching (see the link above for details)