[jbosstools-issues] [JBoss JIRA] (JBDS-2741) 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/JBDS-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803642#comment-12803642 ] 

Nick Boldt edited comment on JBDS-2741 at 9/11/13 6:13 PM:
-----------------------------------------------------------

PR to switch from using\ {JOB_NAME}/all/repo to \{JOB_NAME}/\{BUILD_ID}/all/repo, and do subsequent cleanup & composite site metadata generation:

https://github.com/jbosstools/jbosstools-build-ci/pull/63

DO NOT APPLY THIS PR YET. Testing here:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master_JBDS2741

using 

https://raw.github.com/nickboldt/jbosstools-build-ci/JBDS-2741/publish/publish.sh
                
      was (Author: nickboldt):
    PR to switch from using\ {JOB_NAME}/all/repo to \{JOB_NAME}/\{BUILD_ID}/all/repo, and do subsequent cleanup & composite site metadata generation:

https://github.com/jbosstools/jbosstools-build-ci/pull/63

DO NOT APPLY THIS PR YET. Testing here:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master_JBDS2741
                  
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-2741
>                 URL: https://issues.jboss.org/browse/JBDS-2741
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: build, requirements, updatesite
>    Affects Versions: 7.0.0.GA
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 7.1.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 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