-
Bug
-
Resolution: Unresolved
-
Major
In 1.480.3 if you create an external monitor job, and do three builds, then go the the latest (#3), you will see a Previous Build link as expected. But in newer cores you will not see this link, even though all three builds appear in Build History.
The reason is that there is nothing actually writing to the previousBuild or nextBuild fields, contrary to their Javadoc: RunMap does not touch them. (dropLinks would update them after deleting a build, if they were not null to begin with, but they are.)
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/java/hudson/model/AbstractBuild.java
core/src/main/java/hudson/model/Run.java
core/src/main/java/hudson/model/RunMap.java
http://jenkins-ci.org/commit/jenkins/f024f59058fd8475b78fbb09b23a121e695a1ae1
Log:
Making RunMap work properly for non-AbstractProject-based jobs using lazy loading.
JENKINS-22052 is not fixed by this for existing Job types like ExternalJob which still do not use lazy loading.