Yesterday our corporate Git repo server had an unavailability. The machine was stuck or something, so somehow accepting connections but never responding.
Since then (for 13 hours as of writing), the pipeline multibranch `Branch Indexing` process has been "building" (stuck actually) on the master.
The thing is: I've been unable to kill this build. Looking at the stack trace, it's certainly because of the classical Java IO issue: waiting on a socket, so uninterruptible?...
Anyway, another bad thing is that as there seems to be a shared lock between branch jobs of that multibranch pipeline, I can't even manually start a build on the modified branch.
So my current solution is I'm gonna have to wait for a calmer moment and restart the whole instance. But it's not really possible in the work day.
Maybe a solution/workaround like for the `Hard kill` issue could be introduced to try and workaround that rare, but very annoying since as explained the build won't even start manually triggered.
Gonna attach some thread dumps.
If you need anything else, just let me know.
Thanks for that wonderful tool!