I have a GitHub repo where Jenkins service is configured to trigger a Jenkins job for every commit. However, as a part of our build pipeline we also do a mvn release - which is in turn creating a new commit that triggers a new jenkins build, and so on.
I've already looked at - Stop mvn release triggering repeat Jenkins builds
I've already tried polling ignores commits from certain users, as well as, polling ignores commits with certain messages. Neither of them seems to be working. Is there anything else that I can try from jenkins or github side, other than creating an additional job - with a script to check for the commits myself?
Thanks in advance!