[tractusx-dev] FW: [eclipse.org-committers] Build service update

["Meyer, Tom" <tom.meyer@xxxxxxxxxxxxxxxxxx>]

Hi all,

 

When clicking on the spreadsheet,  Eclipse-Tractus-X is also affected by Jenkins Jobs. I’ve got no clue which these are and which purpose they serve. For me it feels like we’re not affected, and can take the backup of last year. Thus, we should file a ticket.

 

I’m more concerned about dash + any dependencies making the maven repo running again. These block the release for 25.06. We got the dependency for dash in our backend’s pom – it doesn’t even build. We can comment it out to create a RC and test. But releases are not possible without Dash (we got at least 3 Prs that need a dependencies update). Are you already in contact with Wayne?

 

Thanks in advance

Tom Meyer

 

From: eclipse.org-committers <eclipse.org-committers-bounces@xxxxxxxxxxx> On Behalf Of Denis Roy via eclipse.org-committers
Sent: Wednesday, April 30, 2025 4:10 AM
To: Eclipse Committers <eclipse.org-committers@xxxxxxxxxxx>
Cc: Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx>
Subject: [eclipse.org-committers] Build service update

 

Folks,

 

I was overly optimistic about the recovery process of the storage cluster that is hosting Jenkins data (job configurations, etc). Recovery is likely, but not guaranteed, and the timeline is not certain.

 

Unfortunately, we’ve been relying on this technology to not fail in the manner it has, and the end result is that the availability of Jenkins backup data is not consistent for each hosted instance. While we may be able to recover some (and hopefully most), there are instances for which we don’t have a recent backup.

 

To avoid prolonging the outage any further, we have two options:

1. We can provision a Jenkins instance with the last known version of the Jenkins data. This data is the last snapshot prior to migration to the storage cluster, and, depending on when your instance was migrated, may be weeks, or up to several months old.

2. We can provision a new, bare Jenkins instance for your project. If your build is defined in pipelines alongside your code, recovery may be more straightforward.

 

You can also choose to wait for the storage cluster to recover, so that we can either continue its usage, or extract data from it to provision a new instance. We do not, however, have an ETA for this recovery, nor do we know with any level of certainty that it actually will recover.

 

We recognise that none of these options are ideal, and we will work with your project to restore service as best we can. We’ve compiled a list[1] of Jenkins instances as well as the date of the last-known-good data, to help with your decision. When you’re ready to proceed, please file an issue on HelpDesk[2] with Project Lead +1 and the team will assist as soon as possible. 

 

Once service is restored, we will perform a postmortem and assess the path forward and share that information with you. 

 

Regardless of what we find in the postmortem, we obviously missed in not ensuring backups of these jobs were captured regularly in case of a catastrophic failure such as this one. We sincerely apologize and thank you for your understanding.

 

[1] https://docs.google.com/spreadsheets/d/13zNUbwAHkYacC193HFwgZOd1fqn-N9cyzXf_lHke07s

[2] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/new

 

--

Denis Roy

Director, IT Services | Eclipse Foundation

Eclipse Foundation: The Community for Open Innovation and Collaboration

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature.asc

_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-committers