Jenkins build deleted all content in GEF Classic release page

Summary

The build for GEF Classic release generation failed and somehow deleted all directories from https://download.eclipse.org/tools/gef/classic/releases/

I could trigger the build for 3.18.0M1 so that at least one release is back. Could you please restore the others from backup.

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

People depending on our

I noticed it this morning thanks to the GMF Runtime nightly builds and opened https://github.com/eclipse/gef-classic/issues/272. Sirius is probably impacted too, all our target platforms reference GEF Classic 3.17.0.

added IT-priorityhigh IT-severitymajor ~26502 team:infra labels

assigned to @jmazanek4ep

@jmazanek4ep can you take a look?

Wow, you guys really need to be using a better (and safer) promotion mechanism like the one that JustJ provides. I most recently updated Xpect to use that.

For reference, I think Ed is refering to: https://github.com/eclipse/Xpect/blob/master/org.eclipse.xpect.releng/promotion/pom.xml

I noticed it recently, and hope to be able to use it for EMF Services and GMF Runtime (when time permits). Shouldn't something like this be available from CBI?

If I waited for it to come from CBI, I'd still be waiting.

@emerks the promotion job that @vogella established is in general quite good. I don't yet know how I broke it twice in the last 3 months. But I definitely need to add a safety net to protect us from my clumsiness.

It doesn't maintain a proper composite that references the latest release but rather creates a copy of the repository which is horrible for mirrors and for disk footprint in general. But then it doesn't provide support for mirror URLs either, which is poor for the download server. So none of that seems quite so good to me.

Moreover, one need only look at this

https://download.eclipse.org/tools/gef/classic/releases/

versus this

https://download.eclipse.org/xpect/updates/

to determine what is quite good and what is not really quite so good.

In any case, I and the community and I are very grateful that you do provide support for GEF classic!

I totally see that and was anyhow not happy with our current setup. However I fear this goes way beyond my current knowledge. My first step would be to secure the current state that this can not happen with the current setup. In addition I hope I can find someone in the GEF Classic community to support us here.

Perhaps I can find time in the future to help enable such a thing. Certainly there is no good documentation and that's 100% my own fault...

@azoitl what's the exact time stamp when this happened?

Jenkins reports the build failure at with Oct 25 2023, 12:59pm

directory is marked for restore from backup

Any idea when this will be restored?

restores of the directory end up in error, I am troubleshooting it

@jmazanek4ep a full restore is IMHO not necessary if we can get directory for the latest releases: 3.17.0, 3.16.0 most users should be happy.

Maybe as a first step, but a full restore is required IMO. Releases are supposed to be forever. We (and probably many others) support/maintain versions of our software which still use "older" versions of Eclipse and GEF than 3.16.

GEF Classic 3.15 itself is not old by any means, it's from less than a year ago: https://github.com/eclipse/gef-classic/tags

@azoitl @pdavid directory is restored with the latest available backup (16.10.2023). Please take a look and let me know, if anything else is needed

Thanks! I just launched a GMF Runtime build to check (at least for the versions it references).

Thanks! I had a quick look on the dates of the folders. This looks good to me.

I confirm the GMF Runtime build are OK now.

Since everything seems to be OK, I am closing this issue

closed