-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
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
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:
- 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