0

I'm currently trying to replace our old cascading builds with an Multibranch Pipeline.

My Target is an Environment where our whole Project is driven by Jenkinsfiles and Branches or Tags can run as an Continuous Integration / Delivery Pipeline.

We are using SVN which defined an Webhook to trigger Builds on commit, and here results my question:

How can I Ignore commits from specific Users when I'm using Multibranch Pipeline in Jenkins?

Edit:

I was trying to reproduce the behavior pointed here. But I can't get it running with the SubversionSCM.

checkout(
[
    $class: 'SubversionSCM',
    additionalCredentials: scm.additionalCredentials,
    excludedCommitMessages: scm.excludedCommitMessages,
    excludedRegions: scm.excludedRegions,
    excludedRevprop: scm.excludedRevprop,
    excludedUsers: 'batch',  // <<-- this is what I want
    filterChangelog: scm.filterChangelog ,
    ignoreDirPropChanges: scm.ignoreDirPropChanges,
    includedRegions: scm.includedRegions,
    locations: scm.locations,
    workspaceUpdater: scm.workspaceUpdater
]
)
Jason Aller
  • 3,541
  • 28
  • 38
  • 38
42tg
  • 695
  • 6
  • 12

1 Answers1

0

Based on this Post I tried to adapt the way to extract the scm.locations and create the same checkout only with an user exception. But sadly the build continues and ignores the second checkout limitations.

Currently im solving this with manuall adding branches to the pipeline and waiting for further additions to the multipipeline or subversion -plugin.

42tg
  • 695
  • 6
  • 12