Closed MichaelRoeder closed 7 years ago
The problem is caused by the Gitlab library that seems to envelope the original GitlabAPIException
into an java.lang.Error
which is not catched by the current implementation of our usage of the Gitlab library.
Fixed in v1.0.4
Problem
If the crawling of gitlab crashes because of a problem, the platform does not get any updates regarding the benchmark or system definitions.
A crash might occur because of communication problems like
Solution
The Runnable executed by the timer needs to be more robust. A regular checking of the timer or printage of its status might be helpful for monitoring.