Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
Jenkins LTS Latest
Windows 7 x64
Description
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
For example:
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://git@bitbucket.org/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:
Attachments
Issue Links
- is duplicated by
-
JENKINS-36836 Git path polling ignores do not work in Pipeline jobs
-
- Closed
-
-
JENKINS-46059 Multiple Git polling causes build to be triggered when all commits are excluded
-
- Closed
-
- is related to
-
JENKINS-35988 Equivalent to polling commit exclusions for branch indexing
-
- Resolved
-
-
JENKINS-44611 Any way to restrict build for non-whitelisted users?
-
- Open
-
- links to
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:
https://github.com/jenkinsci/git-plugin/pull/1046
https://issues.jenkins.io/browse/JENKINS-64902
so hopefully this issue will soon be fixed upstream