when Jenkins does the checkout it does it keeping the credentials isolated from the actual build, so you might need to use the ssh-agent plugin to inject the credentials that can be used to do the push back into the build's environment
On 18 November 2014 15:26, youhour <[email protected]> wrote: > When I'm using this same id to clone, I was able to create and push the tag > without any issue. Only have issue when trying to do from Jenkins. > > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/Pushing-Git-tags-back-to-origin-tp2274148p4728284.html > Sent from the Jenkins users mailing list archive at Nabble.com. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
