[jbosstools-issues] [JBoss JIRA] (JBIDE-15918) Could Jenkins perform tagging of its own repo?

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922728#comment-12922728 ] 

Max Rydahl Andersen commented on JBIDE-15918:
---------------------------------------------

I looked and there actually is a Git Publisher plugin that does this exact thing *but* it does not work with "multiple SCM" option which we for some reason uses (https://issues.jenkins-ci.org/browse/JENKINS-13779)

Any idea why we use multiple SCM option when afaics there only are just one repository listed in builds like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Trunk/job/jbosstools-livereload_master/ ?
                
> Could Jenkins perform tagging of its own repo?
> ----------------------------------------------
>
>                 Key: JBIDE-15918
>                 URL: https://issues.jboss.org/browse/JBIDE-15918
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.1.1.Beta1
>            Reporter: Nick Boldt
>            Priority: Minor
>
> [~maxandersen] said:
> {quote}
> Project leads, please tag your projects!
> {code}
>   co jbosstools-4.1.1.Beta1x
>   git tag jbosstools-4.1.1.Beta1
>   git push origin jbosstools-4.1.1.Beta1
> {code}
> {quote}
> Then asked:
> {quote}
> Really would be nice if jenkins could just make such tags in its own repository and we could move the exact commit over from the "build" repository to the master repository.
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira