-
Bug
-
Resolution: Fixed
-
Major
If you have some tool constantly pinging jobs/.../build?token=... but the job is stuck in the queue for a long time, you will get a CauseAction with a potentially unbounded number of causes, all identical RemoteCause instances. In a system with tens of thousands of build records loaded, there can be millions of such causes. This is a waste of heap space (and disk space, disk I/O time to load).
- blocks
-
JENKINS-44444 Matrix-project is failing the PCT
-
- Resolved
-
- duplicates
-
JENKINS-33935 Can't rerun a build
-
- Resolved
-
- is blocking
-
JENKINS-4831 Message "Started by an SCM change" repeated many times for a build
-
- Closed
-
- is related to
-
JENKINS-33594 Rebuilding broken in Jenkins ver. 1.653
-
- Resolved
-
-
JENKINS-34117 java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
-
- Resolved
-
-
JENKINS-33591 Manual steps broken in Jenkins ver. 1.653
-
- Closed
-
- links to
Code changed in jenkins
User: Timo Mihaljov
Path:
src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java
http://jenkins-ci.org/commit/build-pipeline-plugin/d56ff03bf4838c541e68f4cfc06f59ba78d12317
Log:
JENKINS-33591Don't modify CauseAction's causesThe cause list is immutable as described in the comments of
JENKINS-33467.