Open NicoPrediger opened 4 years ago
In order to make archive automation possible, we might want to think about some manual clean up on archive.eclipse.org, for example https://archive.eclipse.org/modeling/tmf/xtext/updates/releases/ already has content, but it does not look like an update-site.
In order to make this work, our "folder scheme" needs to be stupid simple so that Jenkins can be trusted to handle this.
Might become obsolete by foundation feature
Community ticket: https://bugs.eclipse.org/bugs/show_bug.cgi?id=546528
move to 2.24
move to 2.25
move to 2.26
Unassigning myself due to priorities. Re-assign if priorities change...
Job should take parameters of relative paths to move "stuff" from download.eclipse.org to archive.eclipse.org.
Most "stuff" that's archived will break two composite update-sites (download and archive) and should therefore recreate all relevant XML files.