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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-15918:
----------------------------------------

How would a job know it is the jbosstools-4.1.1.Beta1 tag? There is nothing in pom files nor job config that can tell that. What would be the rule to have jenkins tagging? If it is changing a system property or something like that which require a human action, then I don't see the benefit of a manual action to command something upon a manual action to do something.

However, I think that Jenkins could create a tag for each build. Those tags would help to track the commit (1) <-> build (N) association easily. It would be useful.
                
> 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