-
Type:
New Feature
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: branch-api-plugin
-
Labels:None
-
Environment:Windows
-
Similar Issues:
I have an organizational project configured which scans repositories for jenkinsfile. One of the repository (https://github.com/VirtoCommerce/vc-module-jenkinssample) has a following Jenkinsfile defined:
node { stage 'Checkout' checkout([ $class: 'GitSCM', branches: [[name: '*/master']], extensions: [[ $class: 'PathRestriction', excludedRegions: 'CommonAssemblyInfo\\.cs', includedRegions: '' ]], userRemoteConfigs: [[ url: 'git@github.com:VirtoCommerce/vc-module-jenkinssample.git']]]) }
As you might see I have an excluded region defined, so changes made to CommonAssemblyInfo.cs don't trigger any builds. However "Branch Indexing" still forces the job to build when I commit changes to "CommonAssemblyInfo.cs". How can I prevent this?
Btw, the above script works fine in a separate/individual Pipeline Job.
- is duplicated by
-
JENKINS-44371 MultibranchPipeline - Ignores SVN Properties
-
- Resolved
-
-
JENKINS-57164 Allow Users to include/exclude paths from Multibranch SCM Triggering
-
- Resolved
-
-
JENKINS-43842 Conditional build trigger on branch indexing
-
- Closed
-
- is related to
-
JENKINS-57474 Ignore committer doesn't work for non-email subversion users
-
- Open
-
-
JENKINS-36195 Pipeline polling ignores special polling rules
-
- Open
-
- relates to
-
JENKINS-27092 create a step to abort the build with a NOT_BUILT status
-
- Reopened
-
- links to
+1 to what Kevin Phillips mentioned above. "Polling ignores commits in certain paths" is available for "normal" Pipelines, just not for Multibranch Pipelines.
Jesse Glick any chance the extension to scm-api you mentioned in https://issues.jenkins-ci.org/browse/JENKINS-35988?focusedCommentId=295310&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-295310 are on the roadmap?
(in my case, it would even be for the bitbucket-branch-source-plugin....)