build icon indicating copy to clipboard operation
build copied to clipboard

Shipwright - a framework for building container images on Kubernetes

Results 121 build issues
Sort by recently updated
recently updated
newest added

# Changes Bumps docker.io/aquasec/trivy from 0.51.1 to 0.51.4. You can trigger a rebase manually by commenting `/rebase` and resolve any conflicts with this PR. # Submitter Checklist - [ ]...

size/XS
kind/dependency-change
release-note-none

# Changes Move out @otaviof to Emeritus Add @apoorvajagtap to approvers and reviewers. Add @karanibm6 to approvers Congrats @apoorvajagtap and @karanibm6 ! # Submitter Checklist - [ ] Includes tests...

size/XS
kind/cleanup
release-note-none

Related to #1116 We never actually tried to clone source from BitBucket. We should do that and especially try out their access tokens that are explained in https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/#Cloning-a-repository-with-an-access-token. Today, when...

lifecycle/stale

In [Enable dependabot updates #1044](https://github.com/shipwright-io/build/pull/1044), we enabled Dependabot updates for this repository. As part of that we changed the release notes linter to ignore Dependabot PRs because the Dependabot configuration...

lifecycle/stale

# Bug Report **Description** If the `TaskRun` for the associated `BuildRun` cannot be created, the listed failure reason is `CouldntGetTask`. This failure reason is misleading if the underlying `TaskRun` can't...

lifecycle/stale

The community wants to keep docs close to the code, and implement a sync process to add the documentation to the shipwright.io website. See https://github.com/shipwright-io/website/issues/29. Today the sync is a...

lifecycle/stale

With the `bundle` end to end tests, a prototype style build and buildrun spec definition was introduced: https://github.com/shipwright-io/build/blob/main/test/e2e/e2e_bundle_test.go#L60-L69 Migrate the existing YAML files in `test/data` into the prototype definitions so...

lifecycle/stale

_Story_ As a Shipwright contributor I want a container image with all the tools needed to develop the Build project So that I can run test scripts on any computer...

lifecycle/stale

We should have a `make` target which generates the content that needs to be PR'd to https://github.com/operator-framework/community-operators/tree/master/community-operators/buildv2-operator Prior art: https://github.com/redhat-developer/service-binding-operator/pull/794/files

delivery
lifecycle/stale

_Idea_: This is considering the scenario of advance users. We should document the process of building an strategy. _Acceptance_Criteria_: PR a doc enhancement around this for advance users.

help wanted
kind/documentation
lifecycle/stale