[jbosstools-issues] [JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-24135:
------------------------------------

I suspect your definition of "permanent" and "stable" are not the same as mine. 

If it's a supported release [1] with a lifecycle of customer support and dates when end of service levels occur, then it can go in /static/ because it's permanent & stable.

If it's neither permanent nor stable... it should go somewhere else.

[1] https://access.redhat.com/support/policy/updates/jboss_notes

> Clean up old vscode builds and establish file retention / cleanup policy
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-24135
>                 URL: https://issues.jboss.org/browse/JBIDE-24135
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.4.4.AM2
>            Reporter: Nick Boldt
>            Assignee: Gorkem Ercan
>             Fix For: 4.4.4.AM3
>
>
> Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts.
> * java-server 1.0.x
> * java-server 0.1.x
> * jdt-language-server 0.1 older than 4 weeks ago
> Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as:
> /neon/snapshots/vscode
> /neon/integration/vscode
> etc.
> Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created. 
> Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aerogear_master/ if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aerogear_master/2017-02-02_21-43-56-B953/



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)