[JENKINS-39579] Matrix jobs defaullt to "locked"

Hello,

I would like to request feature change about locking matrix build with dependencies to other builds.

Right now it's only possible to delete those builds via console on file system level directly.

A real dependency would mean, if I delete those build for example #42, it should break the dependency to another build #43. This break would mean, it isn't possible to build #43. What doesn't happen in most cases.

In this case it should be possible to allow "delete build" (at least as admin, because he/she knows what he/she does).

Thanks & regards

Gino

---
Originally reported by giat7133, imported from: Matrix jobs defaullt to "locked"

• assignee: kohsuke
  
• status: Open
  
• priority: Minor
  
• component(s): matrix-project-plugin
  
• label(s): build, delete, matrix
  
• resolution: Unresolved
  
• votes: 2
  
• watchers: 5
  
• imported: 2025-12-06
  

Raw content of original issue

Hello,


I would like to request feature change about locking matrix build with dependencies to other builds. 


Right now it's only possible to delete those builds via console on file system level directly. 

A real dependency would mean, if I delete those build for example #42, it should break the dependency to another build #43. This break would mean, it isn't possible to build #43. What doesn't happen in most cases.


In this case it should be possible to allow "delete build" (at least as admin, because he/she knows what he/she does).


Thanks & regards

Gino

environment

```
Jenkins version 2.30

Matrix project plugin version 1.7
```

No source file, entry point, or test is named. Start by tracing matrix build dependency locking and build deletion behavior in the matrix-project-plugin, then determine how administrative deletion should affect dependent builds. Done would require a decided design and tests covering deletion of a dependency and the behavior of the dependent build.

Written by the indexing model from the issue text.