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

Wed Sep 1 13:33:34 EDT 2010

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

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

Problem is stated in summary "Restore the structure" :)

Currently there is no structure anymore so when you get to the http://download.jboss.org/jbosstools/builds/nightly what do you see?

[DIR]	Parent Directory	-
[DIR]	3.1.2.GA/	16-Jul-2010 20:00 	-
[DIR]	3.2.helios/	01-Sep-2010 10:44 	-
[TXT] latestBuild.html	15-Sep-2009 10:10 	66
[DIR]	trunk/	23-Jul-2010 15:40 	- 

where I supposed to get 3.2.0.M2 build?

What was before:

[DIR]	Parent Directory	-
[DIR]	3.1.2.GA/	16-Jul-2010 20:00 	-
[DIR]	3.2.0.M1/	01-Sep-2010 10:44 	-
[DIR]	3.2.0.M2/	01-Sep-2010 10:44 	-
[TXT] latestBuild.html	15-Sep-2009 10:10 	66
[DIR]	trunk/	23-Jul-2010 15:40 	- 

do you have any questions where to get M2 Nightly build in list above?

Currently in http://download.jboss.org/jbosstools/builds/nightly/3.2.helios

[DIR]	jbosstools-3.2.0.Beta1.aggregate/	01-Sep-2010 04:47 	 -
[DIR]	jbosstools-3.2.0.Beta1.continuous/	01-Sep-2010 03:11 	-
[DIR]	jbosstools-3.2.0.M2.aggregate-2010-08-31_11-51-14-H216/	31-Aug-2010 12:41 	-
[DIR]	jbosstools-3.2.0.M2.aggregate-2010-08-31_15-51-52-H217/	31-Aug-2010 17:15 	-
[DIR]	jbosstools-3.2.0.M2.aggregate-2010-09-01_10-17-00-H220/	01-Sep-2010 10:43 	-
[DIR]	jbosstools-3.2.0.M2.aggregate/	20-Aug-2010 16:49 	-
[DIR]	jbosstools-3.2.0.M2.continuous-2010-08-31_19-16-10-H324/	31-Aug-2010 20:36 	-
[DIR]	jbosstools-3.2.0.M2.continuous/	31-Aug-2010 21:12 	-
[DIR]	jbosstools-3.2.0.M2/	16-Jul-2010 10:38 	-
[DIR]	jbosstools-3.2.0.M3.aggregate/	30-Aug-2010 23:35 	-
[DIR]	jbosstools-3.2.0.M3.continuous/	30-Aug-2010 23:40 	-
[DIR]	jbosstools-drools/	10-Aug-2010 12:45 	-
[DIR]	jbosstools-pi4soa/	24-Aug-2010 21:50 	-
[DIR]	jbosstools-teiid-designer-7.2-2010-08-31_15-21-09-H3/	31-Aug-2010 15:44 	-
[DIR]	jbosstools-teiid-designer-7.2/	30-Aug-2010 17:06 	-
[DIR]	jbosstools-teiid-designer-2010-08-31_21-21-09-H226/	31-Aug-2010 22:53 	-
[DIR]	jbosstools-teiid-designer/	25-Aug-2010 04:49 	-
[DIR]	savara/	27-Jul-2010 03:56 	-
[DIR]	scribble-trunk/	19-Jul-2010 08:57 	-
[DIR]	scribble/	10-Aug-2010 15:53 	-
[DIR]	xulrunner-1.9.1.2/	10-Aug-2010 12:33 	-
[DIR]	xulrunner-1.9.2/	30-Jul-2010 18:01 	- 

Wow! where I supposed to get last 3.2.0.M2 build is it in jbosstools-3.2.0.M2 or in 	jbosstools-3.2.0.M2.aggregate or jbosstools-3.2.0.M2.aggregate-2010-09-01_10-17-00-H220 or it might be  .... 
It looks like this list is going to be very long pretty soon.

what we had before in http://download.jboss.org/jbosstools/builds/nightly/3.2.0.M2

20100831115114
20100831155152
20100901101700

There was a script which kept only three last version only.

What we had before in http://download.jboss.org/jbosstools/builds/nightly/3.2.0.M2/lastBuild.html would transfer us to http://download.jboss.org/jbosstools/builds/nightly/3.2.0.M2/20100901101700 which was a build results page with all zips, updates, reports, test results and links to the drivers.

Thats why we have to restore old structure for AGGREGATED JBoss Tools builds and find a place for separated components if we need it.

Because in current condition everything is destroyed, but nothing provided instead of old structure.

> 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