Hi, > I agree, adding Jenkins is far from ideal. I thought there was some > reminder from INFRA being sent to the PMCs or PMC Chair earlier in the > year but I might be wrong. Kou, do you know if INFRA asked about this > lately?
INFRA just said "ASF Infra has decided to move away from Travis". INFRA doesn't provide any recommended way for s390x. See also: https://lists.apache.org/thread/mzq72rdl9s1xvhjgysykq2ng2ygktr9b (This is an email at private@. So PMC members can only see it.) Another approach is using https://github.com/ursacomputing/crossbow . Recently, we migrated all Travis CI jobs to GitHub Actions: * https://github.com/apache/arrow/pull/34717 * https://github.com/apache/arrow/pull/34835 So Voltron Data can stop a Travis CI contract for https://github.com/ursacomputing/crossbow . If Voltron Data still has a Travis CI contract for https://github.com/ursacomputing/crossbow , we can use https://github.com/ursacomputing/crossbow + Travis CI for s390x. Thanks, -- kou In <cad1rbrrc-c9p5a1uh6bs10ougcbrnejqgusepd9ouvdkjou...@mail.gmail.com> "Re: [DISCUSS] Migrate s390x from Travis to ASF Jenkins" on Fri, 21 Apr 2023 15:45:43 +0200, Raúl Cumplido <rau...@apache.org> wrote: >> > On Thu, Apr 20, 2023 at 4:07 PM Matt Topol <zotthewiz...@gmail.com> wrote: >> >> >> >> I just wanted to add on that there was a Go on s390x job too that needs to >> >> get migrated and wasn't on the list in Raul's original email. > > Thanks! I thought I added the Go one too :) > >> >> On Thu, Apr 20, 2023 at 2:42 PM Benson Muite <benson_mu...@emailplus.org> >> >> wrote: >> >> >> >>> Might also consider testing farm for Centos Stream, Fedora and/or RHEL >> >>> builds[1][2]. >> >>> >> >>> 1) https://docs.testing-farm.io/general/0.1/test-environment.html >> >>> 2) >> >>> >> >>> https://fedoramagazine.org/test-github-projects-with-github-actions-and-testing-farm/ >> >>> > > That looks pretty cool! I am not sure we can use it though as from > their onboarding page it looks like is only opened to: > > Currently Testing Farm is open for: > - any Red Hat employee, team or project > - any Fedora or CentOS Stream contributor, team or SIG > - any public project, service or initiative which Red Hat or Fedora > is maintaining or co-maintaining > - via Packit integration > https://docs.testing-farm.io/general/0.1/onboarding.html > > If someone has any contacts on Red Hat/Fedora maybe this is something > we could explore as it would be like adding GitHub actions. > >> >>> On 4/20/23 19:43, Antoine Pitrou wrote: >> >>>> >> >>>> Hi Raul, >> >>>> >> >>>> I'm a bit lukewarm about this. We currently don't use Jenkins and it's >> >>>> quite different from the CI services we have. Adding Jenkins jobs for >> >>>> s390x sounds like significant additional maintenance for a little-used >> >>>> platform. Has someone been asking for this? > > I agree, adding Jenkins is far from ideal. I thought there was some > reminder from INFRA being sent to the PMCs or PMC Chair earlier in the > year but I might be wrong. Kou, do you know if INFRA asked about this > lately? > >> >>>> Regards >> >>>> >> >>>> Antoine. >> >>>> >> >>>> >> >>>> Le 20/04/2023 à 13:00, Raúl Cumplido a écrit : >> >>>>> Hi, >> >>>>> >> >>>>> As discussed on this mailing list thread [1], one month and a half ago >> >>>>> we migrated the ARM 64 jobs from Travis to self-hosted runners [2]. >> >>>>> >> >>>>> We are still missing to migrate the s390x jobs that we run on Travis >> >>> [3]. >> >>>>> >> >>>>> - name: "Java on s390x" >> >>>>> - name: "C++ on s390x" >> >>>>> - name: "Python on s390x" >> >>>>> >> >>>>> As we don't have other s390x hosts I will try and set up new Jenkins >> >>>>> jobs for those using the ASF provided infrastructure. >> >>>>> From what I can read on the ASF wiki [4] I might require some PMC to >> >>>>> help me get access to Jenkins via the whimsy tool to be added to the >> >>>>> hudson-jobadmin group in order to have access to set up jobs on >> >>>>> Jenkins. >> >>>>> >> >>>>> I wanted to validate that this is ok and would like to ask if someone >> >>>>> can help me with the access. >> >>>>> >> >>>>> As a reminder all Apache projects were supposed to migrate from Travis >> >>>>> CI by the end of 2022 [5]. >> >>>>> >> >>>>> Thanks, >> >>>>> Raúl >> >>>>> >> >>>>> [1] https://lists.apache.org/thread/mskpqwpdq65t1wpj4f5klfq9217ljodw >> >>>>> [2] https://github.com/apache/arrow/pull/34482 >> >>>>> [3] >> >>>>> >> >>> https://github.com/apache/arrow/blob/f2cc0b41fe9fb1d8d2bdb1d2abf676278e273f55/.travis.yml >> >>>>> [4] https://cwiki.apache.org/confluence/display/INFRA/Jenkins >> >>>>> [5] https://github.com/apache/arrow/issues/20496 >> >>> >> >>>
