Avoid Recursive Building When Jenkins Pushes

[greg.f...@goodautomation.com]

Currently I have a build that creates and updates a bunch of files which are loaded into our IDE to customize it to display all our internal libraries. This build is triggered on commits. After the build completes, I commit and push these files back to my git repo on bitbucket via a Jenkins step. Trust me, I would rather the files not be in the repo, but they have to be for reasons I'm not going to get into. The problem is, this commit and push triggers another build, so I get in a loop where I continually build. I found the ci skip plugin which skips builds based on a string in the commit message. This is fine and works, but it's really brutal in that it requires a build to start before it knows whether or not to keep running. So, now for every build that executes and pushes back to bitbucket, I have a second build start that ends with "NOT_BUILT." This is making my build history unnecessarily large. What I really need is something that won't even start the build if the previous commit was by the Jenkins user. The git plugin has this ability if the build is triggered by polling, but I can't figure out what to do when I am triggering a build from a commit using the bitbucket plugin. Thoughts?