[JENKINS-75690] multibranch job delete branch jobs immidately after branch deleted

[jenkins-infra-bot]

I would like to delete the branch job immediately after the branch is deleted. currently, even after setting the orphanedItemStrategy like this,

 

false
-1
-1
true

 

The branch job is disabled first and only after the next scan it is removed. This causes some resource consumption and cost. we are using https://github.com/jenkinsci/multibranch-action-triggers-plugin/ to trigger other jobs to remove the resources.  

---

Originally reported by krishgcek, imported from: multibranch job delete branch jobs immidately after branch deleted

• status: Open
• priority: Critical
• component(s): workflow-multibranch-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20251212-090250

Raw content of original issue

I would like to delete the branch job immediately after the branch is deleted. currently, even after setting the orphanedItemStrategy like this,

 

<abortBuilds>false</abortBuilds>
<daysToKeep>-1</daysToKeep>
<numToKeep>-1</numToKeep>
<pruneDeadBranches>true</pruneDeadBranches>
</orphanedItemStrategy>

 

The branch job is disabled first and only after the next scan it is removed. This causes some resource consumption and cost. we are using https://github.com/jenkinsci/multibranch-action-triggers-plugin/ to trigger other jobs to remove the resources.  

• environment: ubuntu jenkins Version 2.492.2

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  krishgcek the Multi-Branch Project plugin is deprecated.  Is that the plugin that you are using?  If so, then you should switch to Jenkins Pipeline.
  
  I don't understand the concern about resource consumption.  What issue results from the resources required by a disabled job?
  

krishgcek the Multi-Branch Project plugin is deprecated. Is that the plugin that you are using? If so, then you should switch to Jenkins Pipeline.

I don't understand the concern about resource consumption. What issue results from the resources required by a disabled job?

[jenkins-infra-bot]

krishgcek:

• Original comment link
• Raw content of original comment:

  I am using multibranch pipeline plugin. Since the official plugin only support one Jenkins file, and we need some nightly builds I have used job dsl to create additional jobs when new branch is created. Some of them are cron jobs and they start and fail since the branch nis removed and also uses some azure vms. Currently I am using branch indexing every 10 minutes so that orphaned jobs also get deleted. On branch delete the branch job is disabled and only in the next indexing it it removed. Since the  action trigger only support on delete event ( no event for disabled), until the cron based indexing is done , other jobs are failing.
  

I am using multibranch pipeline plugin. Since the official plugin only support one Jenkins file, and we need some nightly builds I have used job dsl to create additional jobs when new branch is created. Some of them are cron jobs and they start and fail since the branch nis removed and also uses some azure vms. Currently I am using branch indexing every 10 minutes so that orphaned jobs also get deleted. On branch delete the branch job is disabled and only in the next indexing it it removed. Since the  action trigger only support on delete event ( no event for disabled), until the cron based indexing is done , other jobs are failing.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I've reassigned the issue to the workflow-multibranch component.  However, I believe this is more of a request for help with a configuration than it is a bug report.  We use the Jenkins issue tracker for bugs and enhancements.  We use https://community.jenkins.io for configuration and user help.  More people read https://community.jenkins.io than read individual bug reports, so you are more likely to receive an answer there.
  

I've reassigned the issue to the workflow-multibranch component. However, I believe this is more of a request for help with a configuration than it is a bug report. We use the Jenkins issue tracker for bugs and enhancements. We use https://community.jenkins.io for configuration and user help. More people read https://community.jenkins.io than read individual bug reports, so you are more likely to receive an answer there.