title: How to avoid Jenkins multibranch pipeline job triggering itself
body: <p>I would like my Jenkins multibranch pipeline job to avoid triggering itself.  The job makes a commit because it increments the version file and checks it into source control which causes an endless loop.</p>
  
  <p>In a regular job I can follow <a href="https://liviutudor.com/2015/12/09/jenkins-ci-trick-to-prevent-task-from-triggering-itself-on-scm-commit/#sthash.MbNk0w7n.dpbs" rel="noreferrer">these instructions</a> to avoid this loop (although it's not the cleanest way).</p>
  
  <p>The instructions do not work for a multibranch pipeline (there is no 'ignore commits from certain users' option).  Is there any way in a Jenkins mulitbranch pipeline to prevent a self-triggered commit?</p>