Jakarta EE Platform TCK restoration plan

Summary

As per the below CI disaster recovery email options, we have questions that we need answered before indicated our preferred option:

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.
3. 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.

For now, we prefer to start with option 1, please restore https://ci.eclipse.org/jakartaee-tck/ from backup. If we later can access the (recovered) storage cluster files, please make our Jenkins job definition (config.xml files) available to us.

Question one: Can you copy files off of the storage cluster machine for us to view to help us make a decision? We just need the (recent) Jenkins job config.xml files from this year so we can understand if we can use those to recreate recent jobs with option 1 (recovery from last fall backup).

Question two: On the storage node that we hope to recover from, can you copy the Jenkins job config.xml https://ci.eclipse.org/jakartaee-tck/ files to a place on https://github.com/eclipse-cbi/jiro that we can access so we can see what the Jenkins job definitions look like to help us make a decision on whether to wait for the storage cluster recovery or revert to the backup from last fall.

Question three: If we find that the cluster recovery works how does that impact what we do now in terms of combining (e.g. merging) the recovered job config.xml files with Jenkins jobs that we create in some way? Is that something could coordinate as users?

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

We need to release the Jakarta EE 11 Platform Specification for which we need the CI restored asap so we can start recreating jobs.