-
Bug
-
Resolution: Fixed
-
Major
JENKINS-18065 introduced a layer of caching which caused stale data to be reported under some conditions.
- is blocking
-
JENKINS-18065 AbstractLazyLoadRunMap.iterator() calls .all()
-
- Resolved
-
[JENKINS-25655] AbstractLazyLoadRunMap.entrySet improperly cached
Link |
New:
This issue is blocking |
Assignee | New: Jesse Glick [ jglick ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Labels | Original: lazy-loading regression | New: lazy-loading lts-candidate regression |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | Original: lazy-loading lts-candidate regression | New: 1.580.3-fixed lazy-loading regression |
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
core/src/main/java/jenkins/model/lazy/LazyLoadRunMapEntrySet.java
core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java
http://jenkins-ci.org/commit/jenkins/b76e7bf9988ebf5b3b7e2c5e588d5ce6dbde957e
Log:
[FIXED JENKINS-25655] Incorrect caching from entrySet sometimes caused incorrect results.
Caused a failure in hudson.plugins.promoted_builds.conditions.ManualConditionTest.testManualPromotionProcessViaWebClient when run against 1.580.1.