| I just hit this bug. Our jenkins uses some groovy scripting to kill off jobs in flight when new commits come in so as to save resources. So it seems that our script to try to stop the duplicate pipeline might have left git in a bad state. What's the best way to gracefully stop the pipeline? We use lots of tricks but it's not clear the 'best' way to force a pipeline to really stop - usually our attempts just cause an "are you sure" message to pop into the console out. |