The https://download.eclipse.org/eclipse/updates/4.32-I-builds don't have a content.jar/content.xml.xz

[merks]

All the builds https://download.eclipse.org/eclipse/updates/4.32-I-builds have only a content.xml

The same is also true for the release build:

https://download.eclipse.org/eclipse/updates/4.31/R-4.31-202402290520/

This is one of the most heavily uses sites so that's pretty nasty for the server.

This is the size the files should be:

Perhaps this is lingering effect from this ongoing manual processing of the file:

#509

[MohananRahul]

For R-4.31-202402290520, during the promotion, it appears that the generation of content.jar and content.xml.xz did not take place as anticipated. let me compress the content.

[merks]

@MohananRahul

I suspect that if we don't fix this in the I-builds then this problem will happen again when we publish the release...

[merks]

@MohananRahul @akurtakov

This continues to be a problem for 4.33-I-builds and like my previous comment, I'm concerned that we better be sure this isn't also a problem for the 4.33 release repository that we will soon publish.

[MohananRahul]

@akurtakov ,removal of delete should suffice I think for IBuilds.

for 4.33 release , It will be take care during promotion.

[akurtakov]

Please do it.

[akurtakov]

Should this one be closed?

[merks]

It's not fixed yet:

[akurtakov]

@MohananRahul what is your plan here?

[MohananRahul]

@MohananRahul what is your plan here?

I'll check it once I'm back. Currently, I'm traveling.

[HannesWell]

This still happens for 4.36-I-builds and there is even a job that @MohananRahul manually runs for promoted repos:
https://ci.eclipse.org/releng/job/updateXZ/ (admittedly the display name is misleading but I updated the description)

Does someone remember what exactly the issue is? If not I'll try to figure it out from

• IBuilds should not manipulate content.xml (and remove content.jar/content.xml.xz ) #509
• Removing unjar of content.jar #2518

But ideally we should make the initially produced content.jar work and if that's not possible, at least the I-build should rebuild the content.jar and content.xml.xz. The latter shouldn't be a problem (what https://ci.eclipse.org/releng/job/updateXZ/ proves).