Migrating away from Travis CI

[Mark Thomas <ma...@apache.org>]

Hi all,

Infra have notified us that we need to migrate off Travis CI. The 
recommended replacement is GitHub actions.

We are already using GitHub actions as a smoke test and we also have 
BuiltBot and Gump providing CI.

Travis provides access to ARM64, s390x and ppc64le which do not appear 
to be available in any of our current CI systems.

The ASF Jenkins service does appear to have a ppc64le node. There also 
appears to be an ARM64 node but it is currently unavailable.

We need to remove the configuration for the Travis builds. That is easy 
to do. The question is do we want to replace the builds for these 
additional platforms?

I don't recall any instances of platform specific issues detected by 
these CI systems. Travis has been so unreliable at times, I have 
contemplated removing the Travis builds entirely irrespective of this 
migration request from the infrastructure team. I am therefore leaning 
towards the simple solution of not replacing the Travis builds. Should 
we have a platform specific bug reported then we can, as we have done in 
the past, figure out a way to get access to a suitable test environment.

Thoughts?

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

Re: Migrating away from Travis CI

[Rémy Maucherat <re...@apache.org>]

On Tue, Oct 25, 2022 at 10:01 AM Mark Thomas <ma...@apache.org> wrote:
>
> Hi all,
>
> Infra have notified us that we need to migrate off Travis CI. The
> recommended replacement is GitHub actions.
>
> We are already using GitHub actions as a smoke test and we also have
> BuiltBot and Gump providing CI.
>
> Travis provides access to ARM64, s390x and ppc64le which do not appear
> to be available in any of our current CI systems.
>
> The ASF Jenkins service does appear to have a ppc64le node. There also
> appears to be an ARM64 node but it is currently unavailable.
>
> We need to remove the configuration for the Travis builds. That is easy
> to do. The question is do we want to replace the builds for these
> additional platforms?
>
> I don't recall any instances of platform specific issues detected by
> these CI systems. Travis has been so unreliable at times, I have
> contemplated removing the Travis builds entirely irrespective of this
> migration request from the infrastructure team. I am therefore leaning
> towards the simple solution of not replacing the Travis builds. Should
> we have a platform specific bug reported then we can, as we have done in
> the past, figure out a way to get access to a suitable test environment.
>
> Thoughts?

Given history, we should be fine with only GH actions and the main
Apache CI. Sure having more platforms is always a good bonus, but if
it is no longer easy to have it's likely not worth the effort.

Rémy

> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org