[jbosstools-issues] [JBoss JIRA] (JBIDE-18899) symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18899:
------------------------------------

Yes, I realized that I was confusing issues after I saw your second comment. 

The process for cleanup and regen is this:

1. delete ALL folders that are more than [date] old, keeping exactly [number] builds
2. regen ALL metadata in that folder

So while a cleanup is happening, you may experience stale metadata. Even if I moved to a model where we:

1. delete A folder and regen
2. delete B folder and regen
3. ...
4. delete N folder and regen

... you'd still see stale metadata *while* a folder is being deleted. And then you'd probably get errors about incomplete XML files due to more frequently changed composite*.xml files.

I don't have a good solution for this other than the simple one:

"if you hit a composite and it refers to old builds which have been / are being deleted, wait a couple mins and try again."

If you can propose a better solution than the equivalent of https://www.youtube.com/watch?v=p85xwZ_OLX0 I'm open to ideas. But sometimes the best *technical* solution is in fact a human process one. :D





> symlink http://download.jboss.org/jbosstools/updates/nightly/luna/latest points to content which has moved into /staging/ folder
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18899
>                 URL: https://issues.jboss.org/browse/JBIDE-18899
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: updatesite
>    Affects Versions: 4.2.1.CR1
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>
> http://download.jboss.org/jbosstools/updates/nightly/luna/ says last folder published is B14 but http://download.jboss.org/jbosstools/updates/nightly/luna/compositeArtifacts.xml contains the following:
> {{{
> <?compositeArtifactRepository version='1.0.0'?><repository name="JBoss Tools Builds - builds/nightly/core/4.2.luna" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"><properties size="2"><property name="p2.timestamp" value="1417970049000"/><property name="p2.compressed" value="true"/></properties><children size="9">
> <child location="2014-12-06_19-43-15-B315/all/repo/"/>
> <child location="2014-12-06_01-42-39-B314/all/repo/"/>
> <child location="2014-12-05_16-52-33-B313/all/repo/"/><child location="2014-12-05_13-48-06-B312/all/repo/"/><child location="2014-12-04_19-55-14-B311/all/repo/"/><child location="2014-12-04_14-48-07-B310/all/repo/"/><child location="2014-12-03_17-44-02-B309/all/repo/"/><child location="2014-12-02_13-44-05-B308/all/repo/"/><child location="2014-12-01_16-57-02-B307/all/repo/"/></children></repository>
> }}}
> Indicating that http://download.jboss.org/jbosstools/updates/nightly/luna/2014-12-06_19-43-15-B315/all/repo/ should exist - but it does not.
> I assume this is due to a nightly being used for publishing results to staging - thus it might just be cleanup step that is missing ? 



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)