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.Final 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-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer...