title: Jenkins: Don't want to trigger on Git Tag (No Workspace)
body: <p>I have users who need to trigger jenkins jobs on Github (Enterprise) pushes. So all I have access to are Webhooks, and the Git Service hooks.  These hooks push even if the only commit was a tag.</p>
  
  <p>Some users auto-tag their builds if they succeed, this auto-tag causes a new webhook to fire and it triggers their build again.</p>
  
  <p>Typically we were avoiding this by using the git plugins "exclude user" section and setting a list of service accounts on that list that do the tagging.</p>
  
  <p>However with the advent of our new ephemeral build farm, we don't maintain workspaces anymore (we spin nodes up as Docker containers on demand).  So this approach no longer works (see: <a href="https://issues.jenkins-ci.org/browse/JENKINS-29282" rel="nofollow">https://issues.jenkins-ci.org/browse/JENKINS-29282</a>).  </p>
  
  <p>My temporary work around is that I run a shell script as the first build step which now does some git-log compares and aborts the build if the service account was the only committer.</p>
  
  <p>I'm looking for a way to use a git hook to trigger a build that does not even start the build if it was just a tag event.</p>
  
  <p>This would appear to be an a difficult ask, but I feel like this problem has to be pretty common.  Many people must auto-tag Git after a build runs successfully and avoid rebuilding.</p>