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
Hi! Support of buildpacks is not in the near plans as for now.
Buildpacks provide a good way to get reproducible images in your workflow. werf by itself also provides a way to get reproducible images along any step in your workflow, but in a different way, supporting more traditional imperative images declaration. We cannot now surely say that buildpacks will provide better building capabilities than werf currently provides (given that werf has another features, such as incremental images rebuilds, guarantee of images immutability in the distributed builders environment, etc.). So adding buildpacks into werf for now is an open question, which needs more arguments and reasons. We need these because supporting both buildpacks and current way to build images seems redundant and expensive.
The first argument could be: it saves time to write and maintain CI/CD configuration, by automatically generating suitable images. But it works only if buildpacks ecosystem contains suitable instructions.
The text was updated successfully, but these errors were encountered: