[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7737) Verify savara jobs

[Gary Brown (JIRA)]

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

Gary Brown commented on JBIDE-7737:
-----------------------------------

One point - savara and jbosstools will have different release lifecycles. So I think it is best that jbosstools-savara have its own set of hudson jobs (as you now have setup) that reflect the lifecycle of jbosstools. As and when jbosstools need stable versions, branches/tags will be created.

Similarly, savara (the separate non-Eclipse based distribution) will have its own release lifecycle, and therefore its own set of jobs. Occasionally, there will be unnecessary duplication (i.e. there will be two jobs building trunk currently). however it means that at any point, the jbosstools jobs can be updated to point to an appropriate branch/tag, without affecting the upstream aggregate job, or affecting the nornal savara distribution build.

Keeping them all in the Savara view is good, as it enables them to be managed side by side. In general it would be good if Nick can manage the jbosstools-savara jobs, and I will manage the standard savara jobs. When approaching a release point, we then just need to decide whether a branch/tag needs to be setup for jbosstools.


> Verify savara jobs
> ------------------
>
>                 Key: JBIDE-7737
>                 URL: https://jira.jboss.org/browse/JBIDE-7737
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Savara
>    Affects Versions: 3.2.0.CR1
>            Reporter: Nick Boldt
>            Assignee: Gary Brown
>            Priority: Trivial
>
> I have two builds for savara right now. One pulls from your 1.1.x branch and builds towards a 1.1 release (JBoss Tools 3.2.0.CR1 from trunk):
> http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-savara-1.1_trunk/configure
>   http://anonsvn.jboss.org/repos/savara/branches/1.1.x
>   http://anonsvn.jboss.org/repos/jbosstools/trunk/build
> The other pulls from a stable branch and builds toward a 3.1 release (JBoss Tools 3.2.0.Beta2 from branch):
> http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-savara-1.1_stable_branch/configure
>   http://anonsvn.jboss.org/repos/savara/tags/jbosstools/1.1.x-jbt3.2.0.beta2
>   http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.Beta2/build
> My question:
> Should there be a savara 1.2 trunk build too, like Teiid has with 7.1/7.2 builds? If so, I can create one for you called jbosstools-savara-1.2_trunk, building from your trunk.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira