[
https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15482:
------------------------------------
[~maxandersen] He's saying that because the defaults set in the parent pom [1] point
to URLs like
http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_4.2.l... [2]
by default you get only the latest staged nightly build.
[1]
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
[2]
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
[~dgolovin] We could change the default *jbosstools-site-suffix* to be *all* instead of
all/repo, thus pointing builds at
http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_4.2.l... which is
a composite of
{code}
<child location='../../../staging/jbosstools-base_4.2.luna/all/repo/'/>
<child
location='../../../staging.previous/jbosstools-base_4.2.luna/all/repo/'/>
{code}
Or we can continue down the path of timestamped folders proposed in this JIRA and generate
composite*.xml files FOR EACH PROJECT, similar to the above but with the added complexity
that it's for 17 projects instead of 1 composite site.
Replace staging & staging.previous (two builds w/ reused URLs)
with uniquely timestamped build URLs and auto-regenerated composite*.xml files
---------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-15482
URL:
https://issues.jboss.org/browse/JBIDE-15482
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build, updatesite
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 4.2.x
Be it proposed:
{quote}
that instead of an in-place move which reuses
generic folder names like "staging" and "staging.previous", we
composite build output using unique names like
2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
{quote}
We therefore need:
a) to regenerate the composite site each time there's a new build
published, in order to remove the oldest and add the newest (keeping
only the Nth and N-1rst builds)
(I have a script that might already work for this, or would need
tweaking.)
b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
no longer needed, perhaps simply by assuming no one needs it after
24hrs?
24 hours should be more that enough.
c) a cleanup script which can purge all but the builds which are no
more than 1 day old, keeping at all times at least two builds (N and
N-1)
(I have a script that already does this for folders like
http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
might need to be tweaked to work for a new pattern of
staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira