[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-6956:
--------------------------------------

All above is about aggregated builds what we need to do next is to find place to put bits build/updates for sepate components aggregated into JBT Update site like: teiid, drools, pi4soa and etc.

Even jbosstools continuous build could be treated like separate component included in aggregated build/update site.

Lets say we have for jbosstools aggregated builds:

    * jbosstools/builds
    * jbosstools/updates

Then we can have for separate components only for nightly builds:

jbosstools/${component}/builds/nightly
jbosstools/${component}/builds/nightly/${version/branch}/${timestamp}
jbosstools/${component}/updates/nightly/
jbosstools/${component}/updates/nightly/${version/branch}

another option is to have them under current nightly folder

jbosstools/builds/nightly/${component}/${branch/tag}/${timestamp}
jbosstools/updates/nightly/${component}/${branch/tag}

> Restore structure of http://download.jboss.org/jbosstools
> ---------------------------------------------------------
>
>                 Key: JBIDE-6956
>                 URL: https://jira.jboss.org/browse/JBIDE-6956
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Build/Releng
>    Affects Versions: 3.2.0.M2
>            Reporter: Denis Golovin
>            Assignee: Nick Boldt
>            Priority: Critical
>             Fix For: 3.2.0.Beta
>
>         Attachments: jbosstools-structure.png
>
>
> Before aggregation was introduced which is building final aggregated repo we used to have simple hierarchical stucture (see attached picture)
> jbosstools/builds/${type}/${branch/tag}/${timestamp}
> jbosstools/updates/${type}/${branch/tag}
> where ${type} is nightly, stable, development
> nightly for nightly builds
> stable for GA releases
> development for M's, betas and CR's releases
> ${branch/tag} was used to separate builds made from different branch tags
> ${timestamp} time stamp YYYYMMDDHHMMSS
> for example in jbosstools/builds/nightly
> jbosstools/builds/nightly/trunk would contains last three nightly builds from trunk
> jbosstools/builds/nightly/3.1.X would contains last three nightly builds from 3.1.X branch
> jbosstools/builds/nightly/3.1.1 would contains last several builds from 3.1.1 tag depends on what kind of problems was found in release candidate build
> for example jbosstools/updates/nightly would contains last update sites for tags/branches like
> jbosstools/updates/nightly/trunk - last update site built from trunk
> jbosstools/updates/nightly/3.1.X last update site built from 3.1.X branch
> jbosstools/updates/nightly/3.1.1 last update site built from 3.1.1 tag

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira