Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Project Repository Reports

Hi Eike,

Thank you for the report. Is there an easy way (let's say per Jenkins job) to regenerate compositeArtifacts.jar and compositeContent.jar? The errors I've looked at were all missing old releases which were either archived away without updating the indexes or not correctly deployed (some nightly deployments).

Thanks and regards,

-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx <cross-project-issues-dev-bounces@xxxxxxxxxxx> On Behalf Of Eike Stepper
Sent: Thursday, 5 December, 2019 08:52
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: [cross-project-issues-dev] Project Repository Reports

Hi Committers,

Every once in a while during my work I notice broken p2 repositories, especially composites,  somewhere on Sometimes p2 refuses to load the composites altogether, sometimes it loads them only partially, which often makes it even harder to detect the nature of the problem.

I have created a Jenkins job that finds and analyzes all p2 repos on the downloads server once per day. The job creates per-project reports and an overview page. The reports focus on the parent/child relationships between the ~18,000 existing repos and highlight broken links. During the internal test phase of the report generator some projects could already fix many of their broken repos, so that we're now down to 188 broken repos in total (down from ~550).

Please have a look at the overview page and find the report for your project:

I hope that the reports are helpful for you and that they help to eliminate all broken repos at some point. Your feedback is most welcome ;-)



cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Back to the top