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

Mickael Istria (JIRA) issues at jboss.org
Wed Jan 22 05:00:28 EST 2014


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

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

> My thinking on this is to keep it simple 

A script, a new repo, some new UI entries doesn't seem simple to me ;)

>  check which exact commits was used for a build

That's already possible just by looking at the build page. I don't see how adding scripts and so on would make things simpler than looking at a page and using "git tag...; git push...". The only difference with what you suggest is that CI builds are not kept forever.
IMO, the problem to solve here is not that things are technically complicated to do, it's just that people don't think about it.
Tagging or promoting a tag will always require a manual step from devs. If they forget to tag things, they'll also easily forget to promote stuff.


                
> 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


More information about the jbosstools-issues mailing list