<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 09/01/2010 11:34 AM, Nick Boldt wrote:
<blockquote cite="mid:4C7E9CB0.8030208@redhat.com" type="cite">
<blockquote type="cite">structure
<br>
</blockquote>
<br>
More or less the same. Labels changed a little, but the idea is the
same.
<br>
</blockquote>
<br>
To visualize you words structure on the left is almost the same as on
the right, but they are not, are they?<br>
<br>
<img src="cid:part1.01050302.03060107@exadel.com" alt=""><br>
<br>
<blockquote cite="mid:4C7E9CB0.8030208@redhat.com" type="cite"><br>
<blockquote type="cite">links to the last builds
<br>
</blockquote>
<br>
Instead of a static URL (file) you have a static URL (folder) that
doesn't change.
<br>
</blockquote>
Yes, and you can point to that folders from
<a class="moz-txt-link-freetext" href="http://www.jboss.org/tools/download.html">http://www.jboss.org/tools/download.html</a> now some links just confusing<br>
<blockquote cite="mid:4C7E9CB0.8030208@redhat.com" type="cite"><br>
<blockquote type="cite">build result pages,
<br>
</blockquote>
<br>
Yes, that's missing. Instead we have the .target file. And test results
are in Hudson.
<br>
<br>
<blockquote type="cite">automatic nightly builds clean ups.
<br>
</blockquote>
<br>
The goal was to have one folder per build job which was self-cleaning
with every promotion. Therefore rather than needing to clean up
nightly, we'd get cleanup w/ every build published.
<br>
<br>
For nightly snapshots, this is working. For the "release" builds I have
to do manual cleanup from time to time.
<br>
</blockquote>
<br>
Until we have structure like shown above on the left it is not working.<br>
<br>
<blockquote cite="mid:4C7E9CB0.8030208@redhat.com" type="cite"><br>
<blockquote type="cite">On 09/01/2010 08:40 AM, Nick Boldt wrote:
<br>
<blockquote type="cite">See comments in
<a class="moz-txt-link-freetext" href="https://jira.jboss.org/browse/JBIDE-6956">https://jira.jboss.org/browse/JBIDE-6956</a> and
<br>
<a class="moz-txt-link-freetext" href="https://jira.jboss.org/browse/JBIDE-6958">https://jira.jboss.org/browse/JBIDE-6958</a>
<br>
<br>
On 08/31/2010 03:09 PM, Denis Golovin wrote:
<br>
<blockquote type="cite">Max, Nick,
<br>
<br>
I've also opened issue for download site structure
<br>
<a class="moz-txt-link-freetext" href="https://jira.jboss.org/browse/JBIDE-6956">https://jira.jboss.org/browse/JBIDE-6956</a>
<br>
<br>
Before aggregation was introduced which is building final repowith
<br>
everything included we used to have simple hierarchical stucture
<br>
<br>
<br>
jbosstools/builds/${type}/${branch/tag}/${timestamp}
<br>
jbosstools/updates/${type}/${branch/tag}
<br>
<br>
where ${type} is *nightly, stable, development *
<br>
<br>
nightly for nightly builds
<br>
stable for GA releases
<br>
development for M's, betas and CR's releases
<br>
<br>
${branch/tag} was used to separate builds made from different branch
<br>
tags
<br>
<br>
${timestamp} time stamp YYYYMMDDHHMMSS
<br>
<br>
for example in jbosstools/builds/nightly
<br>
<br>
jbosstools/builds/nightly/trunk would contains last three nightly
builds
<br>
from trunk
<br>
jbosstools/builds/nightly/3.1.X would contains last three nightly
builds
<br>
from 3.1.X branch
<br>
jbosstools/builds/nightly/3.1.1 would contains last several builds from
<br>
3.1.1 tag depends on what kind of problems was found in release
<br>
candidate build
<br>
<br>
for example jbosstools/updates/nightly would contains last update sites
<br>
for tags/branches like
<br>
<br>
jbosstools/updates/nightly/trunk - last update site built from trunk
<br>
jbosstools/updates/nightly/3.1.X last update site built from 3.1.X
<br>
branch
<br>
jbosstools/updates/nightly/3.1.1 last update site built from 3.1.1 tag
<br>
<br>
All above is about aggregated builds what we need to do next is to find
<br>
place to put bits build/updates for sepate components aggregated into
<br>
JBT Update site like: teiid, drools, pi4soa and etc.
<br>
<br>
Even jbosstools continuous build could be treated like separate
<br>
component included in aggregated build/update site.
<br>
<br>
Lets say we have for aggregated builds:
<br>
<br>
* jbosstools/builds
<br>
* jbosstools/updates
<br>
<br>
Then we can have for separate components only for nightly builds:
<br>
<br>
jbosstools/${component}/builds/nightly
<br>
jbosstools/${component}/builds/nightly/${version/branch}/${timestamp}
<br>
jbosstools/${component}/updates/nightly/
<br>
jbosstools/${component}/updates/nightly/${version/branch}
<br>
<br>
another option is to have them under current nightly folder
<br>
<br>
jbosstools/builds/nightly/${component}/${branch/tag}/${timestamp}
<br>
jbosstools/updates/nightly/${component}/${branch/tag}
<br>
<br>
Sure we have to restore build index.html with links to update
<br>
sites/drivers and zipped update sites
<br>
<a class="moz-txt-link-freetext" href="https://jira.jboss.org/browse/JBIDE-6958">https://jira.jboss.org/browse/JBIDE-6958</a>.
<br>
<br>
WDYT?
<br>
<br>
Thanks
<br>
Denis
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>