[jbosstools-issues] [JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-16220:
---------------------------------------

This approach could be actually good way to do integration builds once a week or every change in this composite git repo. It would be similar to tag files in eclipse. Not every commit to actual module would trigger it. If module lead wants integration build he/she should go an update submodule in composite repo. 

It also would let us do:
- branches in this composite repo for different streams
- tagging in one place for everything like:
   {code}git foreach 'git tag 4.1.0.GA -m "JBoss Tools 4.1.0.GA"{code}

The name for repo would be jbosstools-releng (similar to what they have in eclipse) or jbosstools-submodules or jbosstools-aggregated or jbosstools-product or e.t.c ... your suggestions are welcome.
                
> create an all-in-one build for JBT projects, using submodules
> -------------------------------------------------------------
>
>                 Key: JBIDE-16220
>                 URL: https://issues.jboss.org/browse/JBIDE-16220
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.2.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.2.x
>
>         Attachments: buildlog_maven311.txt
>
>
> Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs.
> {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188}
>  "git submodule" started learning a new mode to integrate with the
>    tip of the remote branch (as opposed to integrating with the commit
>    recorded in the superproject's gitlink).
> {code}
> Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current.
> If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc.

--
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