I'm exactly in the same configuration:
Our jenkins instance hosts some jobs typed as "Continuous delivery".
Those jobs are triggered by github with this plugin.
So it means we compile, package execute some test and then release it automatically
At some point, release means changing version inside the pom.xml and pushing into the remote repository in order to share the new version (snapshot) across all developers.
... and there we enter in a loop because after pushing, github detect a change and call back again jenkins
So it could be nice in the admin section of the plugin (or maybe per project) to be able to enter a "blacklist/ignore) username.
In case where this username field is set, the plugin ignore commit done by this user
Do you think possible to do this type of enhancement ?
Thx
Christophe
I'm not sure what a good way to upvote an issue here would be but I would like this feature too. Same reason, to avoid build loops with automatic commits.