davsclaus commented on code in PR #24754: URL: https://github.com/apache/camel/pull/24754#discussion_r3593061469
########## 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: Adding `-Dcamel.exe.build=true` here means every snapshot deploy will activate the `build-native-exe` profile in `tooling/camel-exe/pom.xml`. The exec-maven-plugin runs at `generate-test-resources` phase, which executes even with `-Dquickly` and `-DskipTests`. If the ASF Jenkins agents don't already have `x86_64-w64-mingw32-clang` and `aarch64-w64-mingw32-clang` on PATH, snapshot deploys for `main`, `camel-4.18.x`, and `camel-4.14.x` will break. The `Verify llvm-mingw` stage (line 58) provides a clear early error, which is good — but the infrastructure needs to be ready before this PR merges. Is llvm-mingw already installed on the Jenkins agents, or should the Jenkinsfile changes be deferred until after provisioning? -- 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]
