jenkinsci / jenkinsci/github-branch-source-plugin

[JENKINS-76201] Pushes to target do not trigger build of other change requests

Open
#1,479 0 comments 0 reactions 0 assignees View on GitHub
component:github-branch-source-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
217
Forks
398
Avg merge
30m
Merged PRs (30d)
1

Description

We recently migrated from Bitbucket Server to GitHub and therefore changed the multibranch pipeline jobs of our projects. The migration just involved the exchange of Bitbucket branch source with GitHub branch source, we left the rest of the job configuration untouched. Everything works well so far but for some reason a push to a target branch like main does not trigger a build of all change requests with the same target. While working with Bitbucket we always saw new builds for branches that have the main branch as target when merging into main. That's expected behaviour as we configured the `Discover pull requests from origin` strategy to be `Merging the pull request with the current target branch revision` and this behaviour is also described in the docs. Does anyone know if there is more to it with this plugin or anything we can try to change?

---
Originally reported by seros, imported from: Pushes to target do not trigger build of other change requests


  • status: Open
  • priority: Minor
  • component(s): github-branch-source-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-12-02

Raw content of original issue

We recently migrated from Bitbucket Server to GitHub and therefore changed the multibranch pipeline jobs of our projects. The migration just involved the exchange of Bitbucket branch source with GitHub branch source, we left the rest of the job configuration untouched. Everything works well so far but for some reason a push to a target branch like main does not trigger a build of all change requests with the same target. While working with Bitbucket we always saw new builds for branches that have the main branch as target when merging into main. That's expected behaviour as we configured the `Discover pull requests from origin` strategy to be `Merging the pull request with the current target branch revision` and this behaviour is also described in the docs. Does anyone know if there is more to it with this plugin or anything we can try to change?

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.