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

[Nick Boldt (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBIDE-6956.
-------------------------------

    Resolution: Done


>> Are you suggesting these be moved somewhere else, like updates/staging/ ?
> yes, I thought that staging folder is going to be used for that 

See JBDS-1336 - in progress.

>> 3.2.helios folder:

http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/README.txt - It'll be removed after Beta1 is done. If you want to open a JIRA reminder assigned to Beta2, feel free.

>> redirect:

http://download.jboss.org/jbosstools/builds/nightly/trunk/latestBuild.html already exists. Others are created as needed automatically for other branches. Note that it's "latestBuild.html", like we had last year, not "lastBuild.html", because the whole point of this jira was to put everything back the way it was. :P

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