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
We should rather be using the Make targets in the release workflow, too, which has several benefits:
Less difference between how images are built for development and for releases. This brings our local development process closer to what's actually released which will prevent bugs that only appear in released artifacts.
Tooling will iteratively get to a better state overall. Right now it's only used for development and not as configurable as it should be (see clean up Docker targets in Makefile #3264 for an example) and what "matters" is that the release process works. If it's all in one, both are maintained at the same time.
A good example of this principle can be seen in the pipeline-controller's tooling here.
The text was updated successfully, but these errors were encountered:
makkes
changed the title
Use Make target for building container images
Use Make target for building and pushuing container images
Jan 24, 2023
makkes
changed the title
Use Make target for building and pushuing container images
Use Make target for building and pushing container images
Jan 24, 2023
We have two different ways how the container images of Weave GitOps are built right:
docker/build-and-push
action hereWe should rather be using the Make targets in the release workflow, too, which has several benefits:
A good example of this principle can be seen in the pipeline-controller's tooling here.
The text was updated successfully, but these errors were encountered: