jenkinsci / jenkinsci/git-plugin
[JENKINS-49434] Multibranch pipeline doesn't trigger on Git submodule changes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 694
- Forks
- 1.1k
- Avg merge
- 1h 29m
- Merged PRs (30d)
- 3
Description
Currently, the multibranch pipeline does not trigger builds if the pipeline is pointed to a Git repo with submodules and one of the submodules changes. This is different from the SCM polling behavior of a single-branch pipeline, which does trigger rebuilds on a change to a submodule. I categorize this as a bug because I would expect the multibranch pipeline to poll for changes in the same way as a single-branch pipeline.
Originally reported by chris_reffett, imported from: Multibranch pipeline doesn't trigger on Git submodule changes
- status: Open
- priority: Minor
- component(s): git-plugin, workflow-multibranch-plugin
- label(s): multibranch, pipeline, scm, triaged-2018-11
- resolution: Unresolved
- votes: 4
- watchers: 7
- imported: 2025-12-02
Raw content of original issue
Currently, the multibranch pipeline does not trigger builds if the pipeline is pointed to a Git repo with submodules and one of the submodules changes. This is different from the SCM polling behavior of a single-branch pipeline, which does trigger rebuilds on a change to a submodule. I categorize this as a bug because I would expect the multibranch pipeline to poll for changes in the same way as a single-branch pipeline.
- environment:
Jenkins 2.89.2, git-plugin 3.7.0, pipeline-multibranch 2.17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the git-plugin and workflow-multibranch-plugin SCM polling paths described in the issue, comparing multibranch behavior with the single-branch pipeline case. Reproduce the scenario using a repository with a changed Git submodule; done means the multibranch pipeline detects that change and triggers a build consistently with single-branch polling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100