[jbosstools-issues] [JBoss JIRA] Commented: (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:comment-tabpanel&focusedCommentId=12548116#action_12548116 ] 

Nick Boldt commented on JBIDE-6956:
-----------------------------------

Currently, builds appear in build/niightly/; updates in updates/nightly/. 

Once ready to be published, I copy from nightly to development or release - as we did for the past couple releases.Nothing new here - still a manual process.

--

As to components, they're all available in the aggregate build folder, just as old nightlies used to:

OLD: http://download.jboss.org/jbosstools/builds/nightly/3.1.2.GA/201007161501/hibernate-tools/, http://download.jboss.org/jbosstools/builds/nightly/3.1.2.GA/201007161501/richfaces/, etc.
NEW: http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools-3.2.0.Beta1.aggregate/components/

Instead of having a timestamp folder inside the vanity name of the build (3.1.2.GA/201007161501), I've moved to the actual job name, optionally suffixed w/ a timestamp and build ID, eg:

http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools-3.2.0.M2.aggregate-2010-08-31_11-51-14-H216/

Inside these are still the all-in-one, sources, component zips, and logs. Only thing missing is the prettier index.html and test results (https://jira.jboss.org/browse/JBIDE-6958).

--

And, for every aggregate build, I also create an updates/ folder, just like we did before:

OLD: http://download.jboss.org/jbosstools/updates/nightly/3.1.2.GA/
NEW: http://download.jboss.org/jbosstools/updates/nightly/jbosstools-3.2.0.M2/, http://download.jboss.org/jbosstools/updates/nightly/trunk/

The only real rethink from 3.1 to 3.2 has been that before, JBT was a single build, and now it's a collection of builds + an aggregation. Therefore the 3.2.helios/ folder contains numerous builds which contribute to the overall aggregation, rather than being a single build output.

So... what's the problem, exactly? Updates are still in the same place; builds are still in the same place. 



> 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