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.
In a regular Jenkins job I was able to avoid this loop by using additional behaviors configuration.( I set Polling ignores commits from certain users option to "Jenkins automation server" ).
This functionality does not work for 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?