[FEATURE] Publish Container Image with `shp` CLI

[adambkaplan]

Is there an existing feature request for this?

• I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

Integrating Shipwright with other CI systems is currently a challenge. The community does not currently have native integrations with tools like Jenkins, Argo Workflows, or even Tekton itself 🙀. The latter has experimental support through the triggers sub-project

Describe the solution that you would like.

Release the shp CLI as a container image, in addition to the CLI binaries that are released today. This provides a flexible path to integrate Shipwright with tools like Jenkins, Argo Workflows, or even Kubernetes itself (ex: run builds on a schedule with a CronJob).

Describe alternatives you have considered.

Triggers promises to provide more native integrations with Tekton and potentially other tools/frameworks. However this is currently experimental and may not support every anticipated scenario. A container image provides significantly more flexibility for integrators.

Anything else?

No response

[SaschaSchwarze0]

@adambkaplan have you thought about which base image should be used and which tools should be in there ?

[adambkaplan]

Sticking with ubi9/ubi-minimal makes the most sense, since we are using it as the base for the build project images: https://github.com/shipwright-io/build/blob/main/.ko.yaml#L1.

In terms of other tools...I'd rather keep this image minimal to reduce any potential attack surface. The only thing on the top of my head that needs "extras" are the local source upload features. We need to do a quick check to ensure this logic is self-contained in the go binary (no os/exec calls).