gnodet opened a new pull request, #29483:
URL: https://github.com/apache/camel/pull/29483

   ## Summary
   
   Fixes https://issues.apache.org/jira/browse/CAMEL-23710
   
   ## Problem
   
   In `.mvn/develocity.xml`, the expression:
   
   ```xml
   
<backgroundBuildScanUpload>#{isFalse(env['GITHUB_ACTIONS'])}</backgroundBuildScanUpload>
   ```
   
   only disables background scan upload on GitHub Actions. On Jenkins, the 
`GITHUB_ACTIONS` environment variable is unset, so `isFalse(null)` evaluates to 
`true`, leaving background upload enabled.
   
   When `develocity.apache.org` is slow or unreachable, the background upload 
thread hangs indefinitely, blocking the Jenkins JVM from exiting. This was 
observed blocking Jenkins builds on both ppc64le and ubuntu agents (see 
attached screenshots in the JIRA).
   
   ## Fix
   
   Add a check for `JENKINS_URL`, which is always set by Jenkins:
   
   ```xml
   <backgroundBuildScanUpload>#{isFalse(env['GITHUB_ACTIONS']) and 
isFalse(env['JENKINS_URL'])}</backgroundBuildScanUpload>
   ```
   
   This disables background upload on both GitHub Actions 
(`GITHUB_ACTIONS=true`) and Jenkins (`JENKINS_URL` set), while keeping it 
enabled for local developer builds.
   
   ## Testing
   
   This is a build configuration change. The logic can be verified by checking 
the `JENKINS_URL` environment variable behaviour:
   - Jenkins: `JENKINS_URL` is always set → `isFalse(env['JENKINS_URL'])` = 
`false` → background upload disabled
   - GitHub Actions: `GITHUB_ACTIONS=true` → `isFalse(env['GITHUB_ACTIONS'])` = 
`false` → background upload disabled
   - Local dev: neither env var set → both are `true` → background upload 
enabled (foreground avoided)
   
   ---
   _This PR was opened by an AI coding agent (Hermes/Claude) on behalf of 
gnodet._


-- 
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]

Reply via email to