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

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

[~maxandersen] I don't understand what you mean. Permanent file? These are FOLDERS of many files, not just a single file. Where would you put this file? Are you talking about sticking an update site zip in Nexus again? Remember, the update site zip is only PART of what's housed in a build folder - we have a lot of metadata associated w/ each update site build, too.

[~mmalina]: If you need a static URL for "the latest build's update site", that's being generated. For example, 

http://download.jboss.org/jbosstools/builds/staging/CI/jbosstools-birt_master/
http://download.jboss.org/jbosstools/builds/staging/CI/jbosstools-livereload_master/
_Note that content is not yet up to date - I just copied stuff over for testing._

If you need a static URL for "the latest build folder w/ metadata" (eg., logs, git rev, etc.) I can provide that -- it's not being generated right now so you'd have to browse for the correct subfolder each time.
                
> 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