thedavidweng opened a new pull request, #6641: URL: https://github.com/apache/camel-k/pull/6641
## What Propagate builder trait configuration failures into `IntegrationKit.Status.Failure` when the kit is moved to `Error`. This keeps the existing `IntegrationKit` condition and lets the `Integration` status include the concrete failure reason instead of only reporting that the kit is in `Error`. Fixes #6637 ## Why Custom builder tasks are only supported with the `pod` build strategy. The builder trait already marks the `IntegrationKit` with an `IntegrationKitTasksValid` condition when `builder.tasks` is used with `routine`, but the related `Integration` only appends detailed kit errors from `IntegrationKit.Status.Failure`. Without setting `Status.Failure`, users only see the generic kit error state from the `Integration`. ## Test Plan - [x] `go test ./pkg/apis/camel/v1 ./pkg/trait ./pkg/controller/integration -count=1` - [x] `git diff --check` ## Notes `make test` was also attempted locally after installing Maven. It still fails in unrelated tests: - `pkg/builder/TestGitCloneCommit` with `worktree contains unstaged changes` - `pkg/util/jvm/TestGenerateKeystore` because the local JDK/keytool error text differs from the test assertion --- _Codex on behalf of David Weng (@thedavidweng)._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
