Skip to content

[BUG] Build Remains "unregistered" After Git Clone Secret is Created #1725

@adambkaplan

Description

@adambkaplan

Is there an existing issue for this?

  • I have searched the existing issues

Kubernetes Version

1.29

Shipwright Version

v0.13.0

Current Behavior

If we create a build requiring git credential before creating the secret and we create the secret after build creation, the build cannot start.

Expected Behavior

We should be able to run a build after the referenced secret.git.cloneSecret has been created.

Steps To Reproduce

  1. Create a Build object that references a git clone secret that does not exist yet.
  2. Create the referenced source clone secret.
  3. Attempt to execute a BuildRun from this Build.

Build cannot run because the parent Build has the "unregistered" status.

Anything else?

Reported in Red Hat JIRA - https://issues.redhat.com/browse/BUILD-1160

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions