[jbosstools-issues] [JBoss JIRA] (JBIDE-15356) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auo-regenerated composite*.xml files
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Mon Aug 19 22:25:25 EDT 2013
Nick Boldt created JBIDE-15356:
----------------------------------
Summary: Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auo-regenerated composite*.xml files
Key: JBIDE-15356
URL: https://issues.jboss.org/browse/JBIDE-15356
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 4.1.0.Final
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.2.0.Alpha1
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
More information about the jbosstools-issues
mailing list