-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
-
1283.v9ddb_0284a_00c
In some environments, and whether anonymization is enabled or not, the bundle generation might take a long time but collecting thread dumps is not always pointing to the culprit, especially when Support Core is writing / anonymizing a specific content.
I can be hard to identify which component / content is causing a slowness in the bundle generation.
https://issues.jenkins.io/browse/JENKINS-61815 should eventually help solve that problem but in the meantime, I cheap improvement can simply be to add some logging of what content and component t is being processes.
- relates to
-
JENKINS-61815 Display per-component size / time estimation
-
- Open
-
- links to
[JENKINS-71226] Add logging to help identify faulty and slow components / contents
Summary | Original: Add logging to help identify faulty components | New: Add logging to help identify faulty and slow components / contents |
Link | New: This issue relates to JENKINS-35344 [ JENKINS-35344 ] |
Link | Original: This issue relates to JENKINS-35344 [ JENKINS-35344 ] |
Assignee | Original: Emilio Escobar [ escoem ] | New: Allan BURDAJEWICZ [ allan_burdajewicz ] |
Link | New: This issue relates to JENKINS-61815 [ JENKINS-61815 ] |
Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "support-core #464 (Web Link)" [ 28696 ] |