If you create a DefaultDeadBranchStrategy with 0 days to live, and 0 builds to keep, you can easily create a situation where a branch can be deleted while a job on it is active.
When branches are re-indexed, the project will be deleted and interrupt active jobs.
I believe a more appropriate course would be to wait for a branch indexing to run while the project is inactive, a state which once entered it shouldn't leave since the branch was deleted (unless it were recreated).
|Field||Original Value||New Value|
|Priority||Minor [ 4 ]||Critical [ 2 ]|
|Assignee||Matthew Moore [ mattmoor ]||Jesse Glick [ jglick ]|
|Component/s||cloudbees-folder-plugin [ 18137 ]|
|Component/s||branch-api-plugin [ 18621 ]|
|Remote Link||This issue links to "PR 44 (Web Link)" [ 14081 ]|
|Remote Link||This issue links to "PR 46 (Web Link)" [ 14113 ]|
|Remote Link||This issue links to "PR 53 (Web Link)" [ 14142 ]|
|Workflow||JNJira [ 159152 ]||JNJira + In-Review [ 196004 ]|