[jbosstools-issues] [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