jenkinsci
[JENKINS-48395] Force push does not trigger Multibranch Pipeline build
I have manually added a webhook to the repo.
According to both GitHub and Jenkins logs event is triggere and received. However, the multibranch pipeline configured to include only one branch is not triggered.
Originally reported by 
kentzo, imported from: Force push does not trigger Multibranch Pipeline build
- assignee:
lanwen
- status: Open
- priority: Minor
- component(s): github-plugin
- resolution: Unresolved
- votes: 3
- watchers: 2
- imported: 2025-12-08
Raw content of original issue
I have manually added a webhook to the repo.
According to both GitHub and Jenkins logs event is triggere and received. However, the multibranch pipeline configured to include only one branch is not triggered.
environment
Jenkins 2.73.3<br/>
GitHub Plugin 1.28.1<br/>
Pipeline 2.5<br/>
Pipeline: Multibranch 2.15
kentzo:
- Original comment link
Raw content of original comment:
There is no option in "Scan Multibranch Pipeline Triggers" to enable Github triggers.
Configurations of jobs created for each branch do not have the "GitHub hook trigger for GITScm polling" option checked.
There is no option in "Scan Multibranch Pipeline Triggers" to enable Github triggers.
Configurations of jobs created for each branch do not have the "GitHub hook trigger for GITScm polling" option checked.
quilicicf:
- Original comment link
Raw content of original comment:
Stumbled on that issue too.
I work with a GitHub source that's supposed to detect all branches and no PRs.
The GitHub repo's hook is set to send the events `push, branch created, branch deleted` and delivers them properly.
The multi-branch pipeline job strikes out the branch I'm force-pushing to and does not build it.
The event is obviously received because the branch is stroked-out but i'd expect the branch to be built instead.
That's a shame in our workflow because rebases tend to happen and in this case, the commits are not built and the branch is not built again until someone triggers a scan manually which is not the point of automated testing :-S.
The plugin's version is 2.20, Jenkins version 2.138.1.
Anything you can do?
Stumbled on that issue too.
I work with a GitHub source that's supposed to detect all branches and no PRs.
The GitHub repo's hook is set to send the events `push, branch created, branch deleted` and delivers them properly.
The multi-branch pipeline job strikes out the branch I'm force-pushing to and does not build it.
The event is obviously received because the branch is stroked-out but i'd expect the branch to be built instead.
That's a shame in our workflow because rebases tend to happen and in this case, the commits are not built and the branch is not built again until someone triggers a scan manually which is not the point of automated testing :-S.
The plugin's version is 2.20, Jenkins version 2.138.1.
Anything you can do?