Won't fix, since there are alternatives in Pipeline like using the ssh-agent wrapper around a git push

Still quite confusing. The help text for "Create a tag for every build" of the Jenkins Git Plugin says this:

Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository.

But the Git publisher has no option to push all tags. After a long internet search, I decided to go with just the Git publisher plug in.

Please reconsider this issue in light of my earlier comment.

This isn't really fixed in my opinion - the plugin page still mentions the non-existent option, and the GitPublisher plugin doesn't have a way to push all tags - it can only push tags that can be explicitly named, so it's not useful for dynamically named tags that Jenkins doesn't know about.

Integrated in plugins_hudson-git-plugin #8
JENKINS-5371 Final part of rewrite of GitPublisher, adding support for pushing tags and branches

Andrew Bayer :
Files :

• src/main/resources/hudson/plugins/git/GitPublisher/help-pushMerge.html
• src/main/webapp/gitPublisher.html
• src/main/resources/hudson/plugins/git/GitPublisher/help-branchesToPush.html
• src/main/resources/hudson/plugins/git/GitPublisher/help-tagsToPush.html

About to make a run at this, with the intent of including an expanded GitPublisher in the next release.

I'd say the right approach here would be to add a post-build action for pushing tags back, or better yet, to expand the "push merges" action to be more configurable, so that you can push back just tags, or merges, or changes without there having been merges, etc. I'll take a look.

http://github.com/bruyeron/Hudson-GIT-plugin/commit/7cd28e8f854507037cc333097016f6ea44aaa289 would resolve this issue. How do you go about getting that change merged into the next release of git hudson plugin?