> On Sep 1, 2022, at 2:52 AM, P. Ottlinger <pottlin...@apache.org> wrote:
> over the years Travis seems to have degraded: builds fail regularly due to
> technical issues or the inability to download artifacts from Maven central
> that are mirrored onto Travis resources.
>
> Does any other project have stable Travis builds?
>
...
>
> GithubAction builds are green, so is ASF Jenkins and local builds ....
>
> Thanks for any opinions, links or hints ....
>
Apache Yetus still has Travis builds and Github Actions running from
the project's repo. I also run the other Apache Yetus-supported CIs from my
personal account regularly so that the project doesn't expose the rest of the
ASF projects to them. (See 'Automation' at
https://yetus.apache.org/documentation/in-progress/precommit/#optional-plug-ins
for current list.) The different CIs run nearly the same pipeline
Anecdotally, Travis is generally the worst performing and most
unreliable out of all of them, on some days by a fairly large factor. To the
point that I've thought about raising a PR to remove support. So no, it isn't
just Creadur.
Travis has also been wildly unpredictable with changes. (e.g., limits
on log sizes just got introduced in the past year or so, I seem to recall a
lower memory limit added, etc) It might be a new one triggering if these
failures are recent. But honestly: unless the project _really_ needs Travis,
I'd recommend migrating off of it. While it sits somewhere in between Jenkins
and Github Actions on the complexity scale, one is probably better off either
dumbing down the build for GHA or going full bore into Jenkins for the heavier
needs. (full disclosure: I haven't kept up with the ASF jenkins config since I
run my own instance for Yetus testing, but I'm assuming it is still more stable
than Travis given there has been little squawking on builds@ lately. Haha.)
