I also have similar situation. Each build is creating tag which is created during build (in buildscript) and it pretty hard to push it back to repository. Credentials are removed just after clone and it is not so simple to add them back during build. I've ended with setting remote URL to contain credentials (my repo is using http authentication) to be able to push. However having feature like 'Push all tags to remote' would be very nice

"Post-build Actions" -> "Git publisher"

I don't think it is possible to use Git publisher to publish tags created during build (not using Git publisher).

As Maciej already answered - it is currently not possible to push back arbitrary tags created during the build - you can only create a tags with a fixed name.

I already created a pull request which mate it into git-client-plugin 1.11.1. I also have the changes for git-plugin but didn't have the time to create tests. Maybe I'll have time tomorrow.

"Each build is creating tag which is created during build " - "Additional behavior" -> "tag every build" ?

I do not want to use Git publisher to create tag. I want it only to push tag that I create during build, eg. in Makefile using git tag "build/$my_awesome_variable"

"Git publisher" doesn't create tags, it only publishes.
1) Extend "git publisher" so it will be able to push external tags.
2) Extend "create build tag for every build" with ability to set custom name.

1) make also help with JENKINS-24880

Ok, 2) is not related to this issue, moved to separate JENKINS-25699

The help text for the "Add Tag" section of the "Git Publisher" Post-Build Action states:

Specify tags to push at the completion of the build.

If the "Create Tag" or "Update tag" option is selected, the tag will be created or updated and pushed at the completion of the build, and the push will fail if a tag with the given name already exists. If the "Create Tag" option is not selected, the push will fail if the tag does not already exist.

Environment variables may be used in the tag name - they will be replaced at build time.

The repository name needs to be one of the repositories configured in the SCM section above.

I have found that environment variables can be used in the tag message, but not the name. I don't understand why the plug-in would require the tag name to be hard-coded - who would go configure the job before each build to add a hard-coded tag name?

Hi there,

I'm coming from Node.js community... I use the following command when I finish a build: (https://docs.npmjs.com/cli/version)

• Building Develop Branch:

npm version prerelease -m "Upgrade by CI"

This will create a new commit, with a tag of the version increment for the current version, say, from 1.3.4, to 1.3.4-0. So, that can be ANY tag during the development cycle. Therefore, I also need to have the ability to publish ANY tag created by npm CLI.

thanks!

It was sure easier if this feature would exist.

Using the jgitflow:release-start/finish creates a tag in the build process, but doesn't push it to remote git.

This feature would make it easier instead of configuring git ssh with the jenkins machine + manually call git commands (because git commands requires password, which cannot be done in an automatic job)

This should be a simple call to `git push <remote-name> --tags` Why is this still an open issue 3 years after it was reported? I'm using zest releaser for python and it adds tags to commits it creates but there's no way to push these tags up that I can find.

The git plugin has implemented a git credentials binding in git plugin 4.8.0. The git credentials binding allows a Pipeline step (sh, bat, or powershell) or a freestyle project build step (shell, batch, powershell, XShell) to perform authenticated git operations.

See the blog post, the git plugin Pipeline documentation, and the git plugin freestyle project documentation.

Won't be implemented in the git publisher because it can now be done with the more general purpose git credentials binding.

Hello,

I use freestyle jobs but I access git via SSH.
How can I do that with the bindings?

The GSoC project is currently developing the ssh private key binding to match the username / password binding. We expect to be complete in the next 4-6 weeks. If you'd like to assist with the testing, you're welcome to work with us on PR-1111. You could experiment with the current pre-release build of that pull request to see if it already addresses your need.

Alternately, you could add a username / password credential to your Jenkins job and configure it to push through the https interface using the username / password credential

We have been dealing with this issue for years.

Our workaround has been to have a post build step in the form of the following shell script:

git pull origin master
git push origin master --tags

But with this, we depend on the private key of the machine running the job. It does not scale well with multiple agents.

Even with the added git ssh private key binding, I don't see how this will allow my shell script to keep working as is. I sense that I am gonna need to tweak it some way. If that is the case, the script will probably stop being portable across Linux/Windows.

If I can keep my shell as is, that should be ok. If I could drop the shell for something more framed, that would be a lot better.

One of the freestyle projects that I used for my testing was configured to push tags. I even used the XShell plugin so that I could run the same freestyle project on Windows and on Linux. In that case, the command I used was

git push --tags

That command works in both batch and in shell and keeps the freestyle project simple.

The freestyle usage is described at https://plugins.jenkins.io/git/#git-bindings. It makes the credential available to all the build steps in the freestyle project. I placed my "git push" in an xshell build step that was the last build step of the job.

I suppose the example you are talking about was using git username/password binding.

I suppose it will work the same once https://ci.jenkins.io/job/Plugins/job/git-plugin/view/change-requests/job/PR-1111/ is merged?

Since https://ci.jenkins.io/job/Plugins/job/git-plugin/view/change-requests/job/PR-1111/ is not ready yet, https://github.com/jenkinsci/git-plugin/pull/1126 was rejected and some people may prefer a simple UI to a shell script, I just published https://github.com/jenkinsci/git-push-plugin/ .

https://github.com/jenkinsci/git-push-plugin/ precisely fullfill the need described in this ticket, which is pushing (using the configured scm git credentials) all tags (and commits) created by the build (be it npm, yarn, maven, ...) without knowing their names before the build begins.