Re: [servlet-dev] Jenkins restoration

[Olivier Lamy <olamy@xxxxxxxxxxx>]

Hi,

Agree with the approach.

This makes me think we should modify Jenkins builds to use Jenkinsfile(s) script(s) with sources in git, so starting from a fresh clean instance would not be a problem.

If this is restored to transform into a Jenkinsfile pipeline file, I can look at it.

Otherwise, create them from scratch. 

On Wed, Apr 30, 2025 at 8:54 PM Mark Thomas via servlet-dev <servlet-dev@xxxxxxxxxxx> wrote:

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 (14 Jan 2025)

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

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

--

Olivier