jenkinsci / jenkinsci/branch-api-plugin

[JENKINS-65303] Incorrect wording in help text for Orphaned Item Strategy

Open
#760 1 comment 0 reactions 0 assignees View on GitHub
component:branch-api-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
39
Forks
154
PR merge metrics
No merged PRs in 30d

Description

The help text for Orphaned Item Strategy states:



Jobs for removed SCM heads (i.e. deleted branches) can be removed immediately or kept based on a desired retention strategy. By default, jobs will be removed as soon as Jenkins determines their associated SCM head no longer exists.

I've tested with bitbucket-branch-source-plugin and github-branch-source-plugin and this is not true. The strategy doesn't check if the SCM head exists or not, but removes any branch marked as orphaned regardless of if the associated SCM head exists or not.

Preferably, it should keep the job for any branch that still exists. The current behavior cause behavior described in JENKINS-52406">JENKINS-52406.

If this is not possible, the text should be changed to reflect the actual behavior. Not sure what that text would be though as the current behavior is not obvious.

---
Originally reported by ahammar, imported from: Incorrect wording in help text for Orphaned Item Strategy


  • status: Open
  • priority: Minor
  • component(s): branch-api-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 20251211-141027

Raw content of original issue

The help text for Orphaned Item Strategy states:



Jobs for removed SCM heads (i.e. deleted branches) can be removed immediately or kept based on a desired retention strategy. By default, jobs will be removed as soon as Jenkins determines their associated SCM head no longer exists.

I've tested with bitbucket-branch-source-plugin and github-branch-source-plugin and this is not true. The strategy doesn't check if the SCM head exists or not, but removes any branch marked as orphaned regardless of if the associated SCM head exists or not.
Preferably, it should keep the job for any branch that still exists. The current behavior cause behavior described in JENKINS-52406.
If this is not possible, the text should be changed to reflect the actual behavior. Not sure what that text would be though as the current behavior is not obvious.

environment

```
Jenkins 2.263.4

branch-api-plugin 2.6.2
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.