build
build copied to clipboard
Shipwright - a framework for building container images on Kubernetes
My builder image has a jboss:root user. When doing a source-to-image strategy (https://github.com/shipwright-io/build/blob/main/samples/buildstrategy/source-to-image/buildstrategy_source-to-image_cr.yaml) I am getting: error building image: error building stage: failed to execute command: credentials: get uid/gid: user:...
As decided in the community meeting from [2021/11/22](https://github.com/shipwright-io/community/issues/42#issuecomment-975581815), we want to scan for problematic dependencies. Candidate tool is [go-licenses](https://github.com/google/go-licenses). Maybe there is also something in golangci-lint. We should define the...
_Idea_: The build controller should emit Kubernetes events for BuildRun objects. These should reflect the important state transitions for the BuildRun's lifecycle - namely if it started, if it succeeded,...
today the https://github.com/tektoncd/triggers project provides github/gitlab styled webhook trigger support for creating tekton API object to trigger their CI/CD pipelines. This is akin to the webhook support in openshift build...
Modify name of literals to "automatically" have Tekton Chains push signatures and attestation. See [format](https://github.com/tektoncd/chains/blob/main/docs/config.md#chains-type-hinting). * Modify `shp-output-image` to `*IMAGE_URL` * write out `IMAGE_URL` to a `result` ( update to...
_Idea_: This is coming as an outcome of https://github.com/shipwright-io/build/issues/662. We want this issue as a way to understand the implication of stopping using serviceAccount and referencing that in Tekton TaskRun,...
The `Build` API includes a `spec.builder` field, which lets users specify the "builder image" for a particular build strategy. This field was initially added to support build strategies like `source-to-image`,...
Although somewhat analogous to [optional image push step](https://github.com/shipwright-io/build/issues/165 ) there is also the concept of allowing the [Build output image](https://github.com/shipwright-io/build/blob/fc3975da9fafb1f1525c8856ada78a4e5ab17c6b/pkg/apis/build/v1alpha1/build_types.go#L108-L109) to be an optional field. Reminder, it is already optional...
[cosign](https://github.com/sigstore/cosign) maintained by [sigstore](https://sigstore.dev/) community is a new standard that allows the signature and verification of container images and OCI artifacts. we (w/@dentrax @erkanzileli) thought that we can add this...
In strategies like source-to-image, it would be cool to verify the signature and provenance information of the builder image before proceeding with its execution.