This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch ci-issue/deploy-4-22-x-snapshots in repository https://gitbox.apache.org/repos/asf/camel.git
commit 4efab4ddd64ace6b0819bd7d5f6a0a54ecf0a009 Author: Claus Ibsen <[email protected]> AuthorDate: Tue Sep 8 12:07:46 2026 +0200 ci: deploy camel-4.22.x snapshots to the ASF snapshot repository The Build & Deploy stage guard in Jenkinsfile.deploy was never adapted when the camel-4.22.x branch was cut, so the stage is skipped on every build of this branch and no snapshots are published. As a result 4.22.1-SNAPSHOT does not exist in the ASF snapshot repository, while 4.14.x and 4.18.x snapshots are published as expected. This breaks the Camel JBang integration tests on this branch: the jbang-it-test profile passes -Dcamel.jbang.version=${project.version} as a Docker build argument, and the CLI container build cannot resolve org.apache.camel:camel-jbang-core:4.22.1-SNAPSHOT (the local Maven repository is a runtime bind mount, not available at image build time): [jbang] [ERROR] Could not read artifact descriptor for org.apache.camel:camel-jbang-core:jar:4.22.1-SNAPSHOT Add camel-4.22.x to the stage guard. The Setup llvm-mingw stage and the nativeExe check already list this branch, and Jenkinsfile.jbangtest was adapted too - only this guard was missed. camel-4.14.x is dropped to match main; that branch evaluates its own copy of this file, so it is unaffected. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- Jenkinsfile.deploy | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Jenkinsfile.deploy b/Jenkinsfile.deploy index 83fa02bc8388..2d6f564e30c4 100644 --- a/Jenkinsfile.deploy +++ b/Jenkinsfile.deploy @@ -97,8 +97,8 @@ pipeline { when { anyOf { branch 'main' + branch 'camel-4.22.x' branch 'camel-4.18.x' - branch 'camel-4.14.x' } } steps {
