1:59 p.m.
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
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
2:01 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin updated JBIDE-6956:
---------------------------------
Attachment: jbosstools-structure.png
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
2:01 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-6956:
--------------------------------------
All above is about aggregated builds what we need to do next is to find place to put bits
build/updates for sepate components aggregated into JBT Update site like: teiid, drools,
pi4soa and etc.
Even jbosstools continuous build could be treated like separate component included in
aggregated build/update site.
Lets say we have for jbosstools aggregated builds:
* jbosstools/builds
* jbosstools/updates
Then we can have for separate components only for nightly builds:
jbosstools/${component}/builds/nightly
jbosstools/${component}/builds/nightly/${version/branch}/${timestamp}
jbosstools/${component}/updates/nightly/
jbosstools/${component}/updates/nightly/${version/branch}
another option is to have them under current nightly folder
jbosstools/builds/nightly/${component}/${branch/tag}/${timestamp}
jbosstools/updates/nightly/${component}/${branch/tag}
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
2:44 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
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...,
http://download.jboss.org/jbosstools/builds/nightly/3.1.2.GA/201007161501...,
etc.
NEW:
http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools...
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...
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
12:33 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
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
1:52 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6956:
-----------------------------------
where I supposed to get 3.2.0.M2 build?
Did you look in the 3.2-named folder? Seems straightforward enough.
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.
The unstamped folder == the most recent timestamped folder. Same bits. I wanted to do
symlinks but the server doesn't support it. So, it's a copy. I would have used a
pure yyyymmddhhmmss timestamp but it was MUCH easier to just use the timestamp that Hudson
provides, and save the confusion around international date formats. Is 2010-09-01_10-17-00
harder to read than 20100901101700? Does the incrementin H## build number not show you
which is the newest? (larger build ID == newer)
I agree that the missing index.html w/ test results is a problem, but that's in JIRA
JBIDE-6958.
Would it be simpler for you if instead of having everything in 3.2.helios/, I put
components' job results in nightly/3.2.helios/* and put the aggregate builds in
nightly/3.2.0.M2.aggregate/ ?
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
12:06 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6956:
-----------------------------------
New version of publish script puts latest aggregate build here:
http://download.jboss.org/jbosstools/builds/nightly/trunk/2010-09-02_10-4...
Still need to update the latestBuild.html file...
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
3:48 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-6956:
--------------------------------------
agreed to have staging folder on the same level with nightly/stable/development to have
place to keep temporary builds for subcomponents aggregated to jbt update site.
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
3:50 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-6956:
--------------------------------------
I'm fine to have 2010-09-01_10-17-00 instead of pure timestamps. I agree, it is
reading better.
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
3:52 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-6956:
--------------------------------------
we might have intellectual latestBuild.html that would pull
http://download.jboss.org/jbosstools/builds/nightly/trunk index page and find latest
timestamp. It's just an idea to consider.
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
10:03 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6956:
-----------------------------------
Intellectual?? Sorry, don't understand. What's wrong with generating it every time
we publish, like we used to?
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
11:58 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-6956:
--------------------------------------
no problem to have this file generated old way, it was just an idea
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
3:56 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6956:
-----------------------------------
I just don't understand the idea. Intellectual?
http://www.google.ca/search?hl=en&client=firefox-a&hs=o2m&rls...
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
9:17 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6956:
-----------------------------------
These builds have been moved or copied into builds/staging/, and scripts that aggregate
them (and publish.sh) have been updated to point at/from the new location.
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/jbosstools-3.2.0.Beta1.aggregate
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/jbosstools-3.2.0.Beta1.nightly
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/jbosstools-drools
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/jbosstools-jbpm
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/jbosstools-pi4soa
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/jbosstools-teiid-designer
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/jbosstools-teiid-designer-7.2
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/savara
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/scribble
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/scribble-trunk
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/xulrunner-1.9.1.2
sftp://tools@filemgmt.jboss.org/downloads_htdocs/tools/builds/staging/xulrunner-1.9.2
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
11:35 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Nick Boldt resolved JBIDE-6956.
-------------------------------
Resolution: Done
Structure restored.
Please open a sub-issue or new issue if you have more things that need to be changed to
improve usability / ease of access.
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
2:22 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-6956:
--------------------------------------
http://www.thefreedictionary.com/intellectual (see 3.a - which means this page would
decide on its own what subfolder in nightly folder is latest build without generation this
page after each build)
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
5:29 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-6956:
--------------------------------------
jbosstools/updates is supposed to have nightly, stable, development and staging
sub-folders now it contains component's update sites. Here is an example from log:
http://download.jboss.org/jbosstools/updates/JBossTools-JBPM//jbosstools-...
[java] [download aggregateRepos] To:
/mnt/hudson_workspace/workspace/devstudio-nightly-4.0.0.M2/jbds-build/requirements/aggregateRepos/jbosstools-jbpm-Update-3.2.0.M2.zip
[java] [echo] Get repo drools
[java] [download aggregateRepos] Getting:
http://download.jboss.org/jbosstools/updates/JBossTools-Drools//jbosstool...
[java] [download aggregateRepos] To:
/mnt/hudson_workspace/workspace/devstudio-nightly-4.0.0.M2/jbds-build/requirements/aggregateRepos/jbosstools-drools-Update-5.1.zip
[java] [echo] Get repo teiid
[java] [download aggregateRepos] Getting:
http://download.jboss.org/jbosstools/updates/JBossTools-TeiidDesigner//jb...
[java] [download aggregateRepos] To:
/mnt/hudson_workspace/workspace/devstudio-nightly-4.0.0.M2/jbds-build/requirements/aggregateRepos/jbosstools-teiid-designer-Update-7
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
1:03 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6956:
-----------------------------------
It contains THREE components' update sites which need to be aggregated into the agg
build (for both uberbuilder and tycho).
Are you suggesting these be moved somewhere else, like updates/staging/ ?
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
1:37 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6956:
-----------------------------------
Denis:
re: "intellectual" index page in nightly/builds/trunk -- we currently have a
latestBuild.html which always points at the latest build. While I think the word you want
here is "intelligent", I think I grok the point you're making. Do you
perhaps instead want a 'latest build across all branches' in nightly/builds/
rather than in nightly/builds/trunk/ ?
re: removing the 3.2.helios folder -- I want to wait until we're safely along into
Beta1 release before doing so, but YES it will be removed in future.
re: updates/{something that needs to be aggregated by JBDS}/ I can move these if you'd
like but I'm not sure it's required. Convince me (and suggest a better layout for
them) and I'll move them and update all the script touchpoints
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: Denis Golovin
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
12:34 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-6956:
--------------------------------------
> Are you suggesting these be moved somewhere else, like
updates/staging/ ?
yes, I thought that staging folder is going to be used for that
> re: removing the 3.2.helios folder -- I want to wait until
we're safely along into Beta1 release before doing so, but YES it will be removed in
future.
"it will be removed in future" could last forever :) Why do you
need this folder it should be moved to staging?
nightly/builds/lastBuild.html is not required. I was thinking about having lastBuild.html
in each folder under nightly/builds like:
nightly/builds/trunk/lastBuild.html
nightly/builds/3.2.0.Beta1/lastBuild.html
and etc.
it is the same file that can check timestamps and redirect you to latest one.
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: Denis Golovin
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
12:34 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
Denis Golovin updated JBIDE-6956:
---------------------------------
Assignee: Nick Boldt (was: Denis Golovin)
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
5:10 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6956) Restore structure of http://download.jboss.org/jbosstools
[
https://jira.jboss.org/browse/JBIDE-6956?page=com.atlassian.jira.plugin.s...
]
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
5677
days inactive
5700
days old
jbosstools-issues@lists.jboss.org
21 comments
2 participants
participants (2)
-
Denis Golovin (JIRA) -
Nick Boldt (JIRA)