Details
-
Bug
-
Resolution: Fixed
-
Medium
-
5.9.3
Description
Summary
This is thrown by Bamboo on each poll of an SVN repo that has no changes, so for an active instance this can easily clutter the logs and grow them more than necessary.
Current thought is that
com.atlassian.bamboo.v2.trigger.DefaultChangeDetectionManager.filterExcludedChangesets(DefaultChangeDetectionManager.java:759)
seems to be accepting a null where it shouldn't.
Environment
SVN 1.7
Steps to Reproduce
We have not been able to reproduce this locally yet.
Expected Results
No issue.
Actual Results
[10-BAM::PlanExec:pool-17-thread-2] [DefaultErrorHandler] Recording an error: Unable to detect changes : XXXX-XXXX : java.lang.NullPointerException
Notes
Workarounds
- (May not work in all cases) Remove the linked repository and re-add it