marking as "blocker" because it's impossible to use this plugin with Jenkins unless you configure your build machine to tag all builds (which may be impossible or very undesirable for many projects)

what's worse, the build fails in a way that does not really tell "Failed" to the Jenkins, so it keeps restarting the build job every 15 minutes even though there are no changes in GIT (instead of waiting for the manual restart).
(I don't have "build periodically", I use "poll periodically" instead)

+1. This is a high-priority blocker. This is seen when building a read-only github repo like git://github.com/user/project.git

sanitized build log

Barry - your issue isn't the read-only github URL. It's that you don't have the git config user.name and user.email configured for the Jenkins user. You can do that through Jenkins, either in the advanced Git config for an individual job, or globally in Manage Jenkins.

@abayer: You're correct. Interesting, it tries to tag the build without a user.

but it does try to tag without it configured.

is there a workaround I can use to disable tagging builds?

can I at least download the older version of this plugin somewhere (1.1.12, without the build tags)?

btw, build tags are useless in general because all builds already have the changeset/commit info and you can recreate the build using that.

I noticed this default behavior also. I was able to turn it off in the project-level configuration.

Jenkins 1.448

Configure | Source Code Management

under Branches to build, click Advnaced

Check the "Skip internal tag" checkbox and Save.

thank you very much, Dan. this worked.

Can't find this checkbox in Jenkins 1.459.

Where did it went to?

I agree that this behavior is annoying and should not be on by default. All of my repos now have tens or hundreds of jenkins tags that I don't care about, and running 'git tag' on them produces a pretty useless output. Can this be off by default?

Agreed with other commenters. This should be off by default and exposed in project configuration.

There is now a checkbox to make tagging optional.

This is not resolved - the request is for the internal tag to be disabled by default. Since this feature was introduced, anyone who doesn't want it has to manually edit ALL their build jobs and disable it.

@owenmehegan is correct, the git plugin should not dictate a tagging philosophy unless the user opts into it. with lots of jenkins projects this is tedious to disable. The checkbox currently requires you to hit the 'Advanced' button under the 'Branches to build' section and then checking 'Skip internal tag'

The git-plugin 2.0.1 and git-client-plugin 1.6.2 do not create a tag for every build. The default setting for the "Create a tag for every build" is now off.

Verified that "off" is the current default for git tagging of each build.

I'm using git-plugin 2.2.5 and git-client-plugin 1.10.1 and this thing is still creating tags. It doesn't push them to the remote, but it still creates them locally.

Patrick Hemmer I don't see this result on any of my 100+ jobs, on multiple machines.

I use many combinations of authentication (read only, read/write, ssh keys, username/password, etc.), transport (git, ssh, https) and servers (bitbucket, github, assembla, local git server). I'm not seeing a tag per build on any of my jobs, unless the "Additional Behaviours" has been enabled to "Create a tag for every build".

Is this happening on every job, including newly created jobs, or only on jobs which were defined prior to your upgrade to git plugin version 2 ?

Is "Create a tag for every build" enabled in the job configuration?

Is there anything else which might be unique or different about your configuration?

I noticed after I submitted that comment that it doesn't happen unless the git-publisher is enabled (post-build action). As soon as it's enabled, it starts generating tags of the form "jenkins-${project}-${build_number}-SUCCESS"

Looks like it's from this: https://github.com/jenkinsci/git-plugin/blob/e384fbff87fec3473f7032760dfd0f4ec5285896/src/main/java/hudson/plugins/git/GitPublisher.java#L215
The code does have a conditional gitSCM.getSkipTag, but I have no clue what controls that.

1. I think if you previously used a version of the git plugin which DID enable tags on builds by default, then simply upgrading to the version where tags are disabled by default would not change that setting in your existing builds. You would need to manually do that.
2. In either case, I think the tags are only created in your local checkout of the repo. They would not be pushed to the remote repo unless you happened to do a 'git push' or 'git push --tags' as part of your build job, or used the git-publisher action as Patrick points out. In my case we create our own tags for builds, in certain cases, and push those. Each time we did that we would also end up with the superfluous Jenkins tags crapping up the remote repo. I think this is why not everyone saw this auto-tag behavior as such a big deal.

Adding the Git Publisher step was the magic for me. Once that is added, then the jenkins-job_name-job_number-SUCCESS tag is written for each successful job.

As far as I can tell, Owen Mehegan is correct that the tags are entirely local to the repository, unless you specifically choose to push the tag. Can you further describe the cause of your concern for those extra tags in the repository?

The problem this causes is with things that use the tags. A good example would be git describe --tags. A build job might use this command to generate a version for the build. However with the jenkins tags getting added in, this breaks as the command returns the wrong tag.

I've ended up just adding git tag d $(git tag --list 'jenkins*') to my build jobs. It's dirty, but it works.