Under Advanced Features in https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin, the docs talk about pre-build branch merging. You can specify the merge type as well - ff, or no-ff. By default, the plugin makes a new tag. As a post-build tag, you can then push the branch and tag back to the repository.
You can provide the url as a parameter to the job and then use that variable as the repository url. A warning though, a non-ff merge is done as (git merge --no-ff $GIT_SHA) and you can't customize the tag name. This method might not be flexible enough for your needs. Typically, I do manually merging and tagging as build steps. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6c78aead-506a-435f-9aa6-488f266d6329%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
