Status: Open (View Workflow)
Jenkins LTS Latest
Windows 7 x64
The git plugin currently offers several special rules on polling:
- Polling ignores commits from certain users
- Polling ignores commits from certain paths (Included/Excluded regions)
- Polling ignores commits with certain messages
- Branch specifier
checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'UserExclusion', excludedUsers: 'dvader'], [$class: 'PathRestriction', excludedRegions: 'One/.*', includedRegions: 'Test/.*'], [$class: 'MessageExclusion', excludedMessage: '.\\[maven-release-plugin
].']], gitTool: 'Default', submoduleCfg: , userRemoteConfigs: [[credentialsId: '...', url: 'ssh://email@example.com/test.git']]])
If a commit is committed to bitbucket.org/test.git, regardless of the user, location, branch or message, the step that includes the checkout will be run.
Similar issue has been reported in:
- is duplicated by
JENKINS-36836 Git path polling ignores do not work in Pipeline jobs
JENKINS-46059 Multiple Git polling causes build to be triggered when all commits are excluded
- is related to
JENKINS-35988 Equivalent to polling commit exclusions for branch indexing
JENKINS-44611 Any way to restrict build for non-whitelisted users?
- links to
Please start work on it. Thank you for fixing this issue, it's pending still.
stanislaw_kodzis I don't plan to start work on this issue.
If you'd like to continue the work that was started by schlitzered, you can use the code that was shared in https://github.com/jenkinsci/git-plugin/pull/1046 . If those changes resolve the issue for you, that would be a great reason to submit a pull request containing the changes. If those changes do not resolve the issue for you, the experience working with those changes may guide you to an improvement that will resolve the issue for you.
don´t use my pull request, i have no clue about java, and just tried something, this pull request never worked.
I myself, in the meantime, switched to Github Actions. the plugin situation with jenkins is a mess. way too much unmaintained code everywhere, and bugs that never get fixed :-/
Thanks for the info Mark and Stephan.
So the GIT plugin needs to be rewritten from scratch? Becase now it too messy to refactor?
markewaite i am not using a Multibranch Pipeline, i am using a normal pipeline. and afaik this should work, it is just a bug, also normal pipeline jobs are not deprecated, so i do not see why i should switch.
never the less, me and a colleague took a look at the problem, and we found the issue, and created a pull request & a another ticket:
so hopefully this issue will soon be fixed upstream