[
https://issues.apache.org/jira/browse/CAMEL-23710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18141269#comment-18141269
]
Guillaume Nodet commented on CAMEL-23710:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
Initial triage confirmed the bug: in `.mvn/develocity.xml` line 28, the
expression
`<backgroundBuildScanUpload>#{isFalse(env['GITHUB_ACTIONS'])}</backgroundBuildScanUpload>`
only disables background uploading on GitHub Actions. On Jenkins (where
`GITHUB_ACTIONS` is unset), `isFalse(null)` evaluates to `true`, leaving
background upload enabled. When the Develocity server is unreachable or slow,
the upload thread hangs indefinitely, blocking the Jenkins JVM from exiting.
Proposed fix: change the expression to also detect Jenkins, e.g. `#{env['CI']
== null}` or `#{isFalse(env['GITHUB_ACTIONS']) and
isFalse(env['JENKINS_URL'])}`, or simply hardcode `false` since all Camel
builds run in CI.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> Jenkins job can stay blocked indefinitely on publishing build scan to
> develocity
> --------------------------------------------------------------------------------
>
> Key: CAMEL-23710
> URL: https://issues.apache.org/jira/browse/CAMEL-23710
> Project: Camel
> Issue Type: Task
> Components: build system
> Affects Versions: 4.20.0
> Reporter: Aurélien Pupier
> Assignee: Guillaume Nodet
> Priority: Major
> Attachments: image-2026-06-08-09-10-37-709.png, screenshot-1.png
>
>
> !image-2026-06-08-09-10-37-709.png!
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
