-
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
[JENKINS-36195] Pipeline polling ignores special polling rules
Link |
New:
This issue is related to |
Assignee | Original: Mark Waite [ markewaite ] |
Assignee | New: Jesse Glick [ jglick ] |
Since the git plugin doesn't read the contents of Jenkinsfile when performing polling, I'm not sure how it would honor the polling settings inside the Jenkinsfile in the repository. It seems like it would be even more challenging in a repository with more than one branch, since the polling settings might differ between branches within the same repository.
I wonder if jglick has any ideas how to handle this case and
JENKINS-35988(and others like it).