[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[el-dev] Jenkins restoration
|
I assume everyone reading this is aware that the Jenkins CI instance we
use is currently unavailable due the failure of the underlying storage
cluster.
We have been asked how we want to proceed. The options are:
1. Jenkins instance restored with last available backup (26 Nov 2024)
2. Clean Jenkins instance
3. Wait to see if the storage cluster can be recovered and a more recent
configuration restored.
Personally, I don't need Jenkins to make progress. It is nice to have
but I can run all the builds locally and I can test Tomcat with the TCK
that way too.
It does mean Tomcat's automated TCK snapshot testing will start to fail
if the API changes as it won't be able to download the updated TCK with
new signature test. That is primarily a Tomcat project issue though and
one I'm happy to live with for now.
I am currently thinking that we give option 3 some more time but if we
reach a point where we need access to the CI system (to publish API
and/or TCK snapshots) then we switch to option 1.
I don't think option 2 is realistic as there is a lot of configuration
in the CI jobs I don't think I could recreate from scratch.
Any objections to me updating the Eclipse IT team along the above lines
in ~ 24 hours from now?
Mark
