-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major
-
Component/s: branch-api-plugin
-
None
-
Environment:Windows
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
-
- Resolved
-
-
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