-
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
-
-
-
- Resolved
-
-
JENKINS-43842 Conditional build trigger on branch indexing
-
- Closed
-
- is related to
-
-
- Open
-
-
-
- Open
-
- relates to
-
-
- Reopened
-
- links to
Joshua Noble
Ignore by commiter: https://github.com/jenkinsci/ignore-committer-strategy-plugin
Torben Knerr Andreas Sieferlinger Alexander Siniouguine Nathan Lowe Nate Faerber Kevin Phillips
I think this does what is being requested here:
https://wiki.jenkins.io/display/JENKINS/Multibranch+Build+Strategy+Extension+Plugin
Resolving for now based on existing plugin. Please comment if not done.
Liam Newman Note that the ignore-committer-strategy plugin doesn't support simple (non-email) subversion usernames, and at least superficially (at least in its UI wording) only supports Git. See also JENKINS-57474.
Bryce Schober
Thanks for filing a new JIRA for that issue.
+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....)