ammachado commented on code in PR #24754: URL: https://github.com/apache/camel/pull/24754#discussion_r3600614990
########## Jenkinsfile.deploy: ########## @@ -17,7 +17,7 @@ def AGENT_LABEL = env.AGENT_LABEL ?: 'ubuntu' def JDK_NAME = env.JDK_NAME ?: 'jdk_25_latest' -def MAVEN_PARAMS = "-U -B -e -fae -V -Dnoassembly " +def MAVEN_PARAMS = "-U -B -e -fae -V -Dnoassembly -Dcamel.exe.build=true " Review Comment: One honest caveat on timing, to correct my note above: I can't exercise the native stage on demand. The snapshot-deploy pipeline runs on ASF Jenkins, and the `camel-4.22.x` branch only comes into existence at release time, so the first real run of the toolchain self-provisioning happens in ASF CI as part of the release cycle, not something that can be triggered beforehand. That said, it shouldn't need to block or be deferred: the native stage is inert until that branch exists (older LTS never touches it), and when it does run, the self-provisioning downloads the pinned toolchain if it's missing. The compiler-existence check in the `Setup llvm-mingw` stage is there so that first run fails fast and loud if anything is off, rather than silently producing a broken deploy. _Claude Code on behalf of ammachado_ -- 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]
