jenkinsci / jenkinsci/git-plugin

[JENKINS-48296] Multibranch pipeline - ignore commits from certain user

Open
#3,237 31 comments 0 reactions 0 assignees View on GitHub
component:git-plugin component:pipeline-multibranch-defaults-plugin enhancement imported-jira-issue priority:critical resolution:unresolved
Dominant language
Java
Stars
694
Forks
1.1k
Avg merge
1h 29m
Merged PRs (30d)
3

Description

I would like my Jenkins multibranch pipeline job to avoid triggering itself. The job makes a commit because it increments the version file and checks it into source control which causes an endless loop.

In a regular Jenkins job I was able to avoid this loop by using additional behaviors configuration.( I set Polling ignores commits from certain users option to "Jenkins automation server" ).

This functionality does not work for multibranch pipeline (there is no 'ignore commits from certain users' option). Is there any way in a Jenkins mulitbranch pipeline to prevent a self-triggered commit?

---
Originally reported by ajit425, imported from: Multibranch pipeline - ignore commits from certain user


  • status: Open
  • priority: Critical
  • component(s): git-plugin, pipeline-multibranch-defaults-plugin
  • resolution: Unresolved
  • votes: 25
  • watchers: 34
  • imported: 2025-12-02

Raw content of original issue

I would like my Jenkins multibranch pipeline job to avoid triggering itself. The job makes a commit because it increments the version file and checks it into source control which causes an endless loop.

In a regular Jenkins job I was able to avoid this loop by using additional behaviors configuration.( I set Polling ignores commits from certain users option to "Jenkins automation server" ).

This functionality does not work for multibranch pipeline (there is no 'ignore commits from certain users' option). Is there any way in a Jenkins mulitbranch pipeline to prevent a self-triggered commit?

  • environment: Jenkins 2.82, Plugins - git, gitHub, pipeline-multibranch,

4 attachments

- [Screen Shot 2019-04-05 at 12.31.24 AM.png](https://issues.jenkins.io/secure/attachment/46639/Screen%20Shot%202019-04-05%20at%2012.31.24%20AM.png)
> ![Screen Shot 2019-04-05 at 12.31.24 AM.png](https://issues.jenkins.io/secure/attachment/46639/Screen%20Shot%202019-04-05%20at%2012.31.24%20AM.png)
- [Screen Shot 2019-04-05 at 8.12.46 PM.png](https://issues.jenkins.io/secure/attachment/46649/Screen%20Shot%202019-04-05%20at%208.12.46%20PM.png)
> ![Screen Shot 2019-04-05 at 8.12.46 PM.png](https://issues.jenkins.io/secure/attachment/46649/Screen%20Shot%202019-04-05%20at%208.12.46%20PM.png)
- [image-2019-04-05-08-14-52-491.png](https://issues.jenkins.io/secure/attachment/46642/image-2019-04-05-08-14-52-491.png)
> ![image-2019-04-05-08-14-52-491.png](https://issues.jenkins.io/secure/attachment/46642/image-2019-04-05-08-14-52-491.png)
- [screenshot-1.png](https://issues.jenkins.io/secure/attachment/46638/screenshot-1.png)
> ![screenshot-1.png](https://issues.jenkins.io/secure/attachment/46638/screenshot-1.png)

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.