[jbosstools-issues] [JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051459#comment-13051459 ] 

Nick Boldt commented on JBIDE-15482:
------------------------------------

Progress made here as part of JBDS-3208. 

Old composite sites:
https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/builds/staging/_composite_/core/master/compositeArtifacts.xml (uses staging and staging.previous - 2 sites composited)
https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/builds/staging/_composite_/core/4.3.mars/compositeArtifacts.xml (uses only staging - single site)

New, simpler ones:
https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/mars/snapshots/builds/_composite_/core/master/compositeArtifacts.xml (does not use latest/all/repo - 2+ sites composited)
https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/mars/snapshots/builds/_composite_/core/4.3.mars/compositeArtifacts.xml (uses latest/all/repo - single 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
>    Affects Versions: 4.2.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>              Labels: f2f2014
>             Fix For: 4.3.0.Alpha2
>
>
> 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 was sent by Atlassian JIRA
(v6.3.11#6341)