[jbosstools-dev] latestBuild.html pointing to non-existent build

[Denis Golovin]

Sean Flanigan wrote:
> http://download.jboss.org/jbosstools/builds/nightly/latestBuild.html
>
> is redirecting to
> http://download.jboss.org/jbosstools/builds/nightly/200907071749/
>
> when that build actually lives here:
> http://download.jboss.org/jbosstools/builds/nightly/3.1.0.M3/200907071749/ 
>
>
>
> This makes me wonder: why is the trunk build called "3.1.0.M3"?  Why 
> not just call it "trunk" (and jbosstools-nightly-trunk), instead of 
> renaming/reconfiguring it all the time?  (Along with copying it to 
> 3.1.0.M3 when a new branch build is needed, that is.)
it should be trunk like jbosstools/updates/nightly has trunk for nightly 
updates.

We supposed to have builds and updates sites each has the same structure:

nightly - contains nightly builds/updates
stable - contains stable releases (X.X.X stable releases)
development - development builds (X.X.X.MX releases)

every folder has sub folders each corresponds to built/released version

so nightly should contain several sub folders at the same time. it 
depends on number of builds in development. there is only one exception, 
subfolder for build from trunk called as trunk. That was done to always 
have the same update/build site for nightly versions from trunk.

all builds from other branches have corresponding version. For example 
now we have trunk in development, at the same time there is a branch for 
3.1.0.M2 and release of 3.0.1 build is comming. Every build always comes 
to nightly, even build which build from tag comes to nightly area. Then 
after a dev meeting it can be promoted to stable/development area.

so jbosstools/builds/nightly now should contains
trunk/latestBuild.html
trunk/20090706XX/
trunk/20090707XX/
..
3.1.0.M2/latestBuild.html
3.1.0.M2/20090706XX/
3.1.0.M2/20090707XX/
..
and when work for 3.0.2.GA will started
it will add the same structure for 3.0.2.GA builds

The structure for updates sites is almost the same

jbosstools/updates/nightly/trunk contains update site for builds from trunk
jbosstools/updates/nightly/3.1.0.M2 update site for builds from 3.1.0.M2 
branch
...

after development is finished they can be promoted to development/stable

jbosstools/updates now contains only last version. so for now 
jbosstools/updates/development contains 3.1.0.M1 version, then it will 
be replaced with 3.1.0.M2
jbosstools/updates/stable contains 3.0.1.GA version, which will be 
replaced by 3.0.2.GA.


so if you want to be on edge just use jbosstools/updates/nightly/trunk 
update site and builds from this site will always be picked up because 
they always have older version then from development/stable. When brunch 
created and you want continue updates from branch you have to get 
updates from jbosstools/updates/nightly/3.1.0.M2 update site and so on.

The real situation seems to be different :)

Denis