That's the only way I know to do it. The plugin does not have a concept of pushing tags to a different repository than the repository from which the work was cloned.
Is it intentional that you're recording tags in a repository that is not the origin repository from which the Jenkins workspace was originally cloned? Mark Waite On Tue, Nov 12, 2013 at 6:16 AM, Max Rydahl Andersen <max.ander...@gmail.com > wrote: > Hey, > > I'm trying to figure out the easiest way to have jenkins push tags for > each build for a master repository to a "ci" repository but for now it > seems to me like the SCM plugins and Git Publisher plugin does not allow > for such setup. > > Is the only option to do a shell script at the end which pushes "manually" > ? > > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
