[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=12814033#comment-12814033 ] 

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

{quote}use of a composite site is bad and causing issues{quote}

The reason it's "bad" is that contents of {code}staging/<job_name>{code} {code}staging.previous/<job_name>{code} are subject to change w/ each new published build. So the statically coded composite site [1] contents may point to different content unexpectedly DURING a build, resulting in unresolved IUs.

[1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/compositeArtifacts.xml

The solution, as outlined in this JIRA (before all the comments began), is to avoid that issue by instead generating the composite*.xml files to point to the ACTUAL build folders, eg., in this example [2].

[2] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.x.kepler/compositeArtifacts.xml

If this is not the solution you want, please suggest an alternative approach. I'm coding based on the spec that [~dgolovin] put forth, documented above in the *Description* field. 

{quote}that is why I suggested doing that as part of those other issues.{quote}

Which other issues?

                
> 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: Nick Boldt
>             Fix For: 4.1.1.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 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