-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
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
[JENKINS-35988] Equivalent to polling commit exclusions for branch indexing
Description |
Original:
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. |
New:
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. |
Assignee | Original: Mark Waite [ markewaite ] |
Component/s | New: github-organization-folder-plugin [ 21427 ] | |
Component/s | Original: git-plugin [ 15543 ] |
Component/s | Original: workflow-multibranch-plugin [ 21465 ] |
Component/s | New: workflow-multibranch-plugin [ 21465 ] |
Link | New: This issue is related to JENKINS-36195 [ JENKINS-36195 ] |
Workflow | Original: JNJira [ 172625 ] | New: JNJira + In-Review [ 184698 ] |
Description |
Original:
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. |
New:
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: {code} 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']]]) } {code} 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. |
Component/s | New: branch-api-plugin [ 18621 ] | |
Component/s | Original: github-organization-folder-plugin [ 21427 ] | |
Component/s | Original: workflow-multibranch-plugin [ 21465 ] |