-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major
-
Component/s: core
-
None
-
Environment:Jenkins: 2.452.2
OS: Windows 10 - 10.0
Java: 21.0.2 - Oracle Corporation (OpenJDK 64-Bit Server VM)
---
bouncycastle-api:2.30.1.78.1-233.vfdcdeb_0a_08a_a_
gson-api:2.10.1-15.v0d99f670e0a_7
instance-identity:185.v303dc7c645f9
javax-activation-api:1.2.0-6
javax-mail-api:1.6.2-9
jaxb:2.3.9-1
mina-sshd-api-common:2.12.1-101.v85b_e08b_780dd
mina-sshd-api-core:2.12.1-101.v85b_e08b_780dd
sshd:3.322.v159e91f6a_550
trilead-api:2.142.v748523a_76693Jenkins: 2.452.2 OS: Windows 10 - 10.0 Java: 21.0.2 - Oracle Corporation (OpenJDK 64-Bit Server VM) --- bouncycastle-api:2.30.1.78.1-233.vfdcdeb_0a_08a_a_ gson-api:2.10.1-15.v0d99f670e0a_7 instance-identity:185.v303dc7c645f9 javax-activation-api:1.2.0-6 javax-mail-api:1.6.2-9 jaxb:2.3.9-1 mina-sshd-api-common:2.12.1-101.v85b_e08b_780dd mina-sshd-api-core:2.12.1-101.v85b_e08b_780dd sshd:3.322.v159e91f6a_550 trilead-api:2.142.v748523a_76693
-
2.452.3 Wednesday 10 Jul 2024
After two recent Jenkins updates, there is an issue with build history, that is not displayed correctly (as shown in a screenshot).
This issue only occurs if parameter in a job uses another parameter. E.g.
COMBINED_PARAM=${WORKSPACE}_abc
This combination uses WORKSPACE parameter inside COMBINED_PARAMETER value.
If such build with this value waits in a queue, then the whole build history panel is bugged. As soon as the build starts executing and there is no other build with similar parameter in a queue, then the problem stops.
Plugins listed in environment are installed on my Jenkins instance, but after disabling them, the problem still exists.
- duplicates
-
-
- Closed
-
