the first time i create a tag on a hash, jenkins will happily trigger a build of matching jobs. but if i create another tag on the same hash,  jenkins will not trigger a build.

i guess this is a feature right now, since the wiki says: "If the job's SCM (git) detects that the remote repository has changes, THEN A full build of the job will be queued"

i would suggest to add an option to skip this check, since otherwise creating tags is not correctly working.

my current workaround is do delete the workspace at the end of the build.