IMHO we should take this (good) track as an awesome opportunity to "fix" that ;)
Le jeu. 17 oct. 2019 à 10:12, Francesco Chicchiriccò <ilgro...@apache.org> a écrit : > On 17/10/19 10:05, Romain Manni-Bucau wrote: > > Oki so corrolar point to my initial thought: do we drop jenkins and ask > > infra to also handle master build (+ maintenance branches) with > credentials > > to enable nightly deployments? > > > > I'm +1 while we keep all jobs on the same build platform and infra > manages > > it. > > FYI we are already using Jenkins and Buildbot as CI platforms, hence we > are already not keeping all jobs on the same build platform. > > My proposal is not to replace either, but to add Travis CI. > As said, Infra is fine with Travis CI (and AppVeyor, for example). > > Regards. > > > Le jeu. 17 oct. 2019 à 10:02, Francesco Chicchiriccò < > ilgro...@apache.org> > > a écrit : > > > >> On 17/10/19 10:00, Romain Manni-Bucau wrote: > >>> I understand but I don't want something done without infra being aware > of > >>> it. > >>> Typically who would be admin on the repo to enable travis and update it > >>> when the webhook will be broken? Should be infra, not us IMHO. > >> Of course! Only infra can enable our repo for Travis - and it's plenty > of > >> other ASF projects doing the same BTW. > >> > >> If we can not disagree on Travis CI, next step is to file a request for > >> Infra on JIRA. > >> > >> Regards. > >> > >>> Le jeu. 17 oct. 2019 à 09:24, Francesco Chicchiriccò < > >> ilgro...@apache.org> > >>> a écrit : > >>> > >>>> FYI, we have a working .travis.yml: > >>>> > >>>> https://travis-ci.org/ilgrosso/openjpa/builds/599012496 > >>>> > >>>> Regards. > >>>> > >>>> On 17/10/19 08:45, Francesco Chicchiriccò wrote: > >>>>> On 17/10/19 08:23, Romain Manni-Bucau wrote: > >>>>>> Hi Francesco, > >>>>>> > >>>>>> Cant we do it on jenkins? > >>>>>> Rational being to ensure we rely on a centralized and infra solution > >> and > >>>>>> not something on our own, even for PR. > >>>>> Hi Romain, > >>>>> we already have Jenkins jobs [1], but AFAICT they suffer from chronic > >>>> lack of resources to satisfy all projects' needs, especially when it > >> comes > >>>> to build PRs. > >>>>> Besides this aspect, PRs *are* already managed at GitHub, and Infra > is > >>>> completely fine with this - as we are, since we decided to switch to > >>>> dual-hosted repository a while ago. > >>>>> BTW, I am not proposing to replace Jenkins, only to add Travis CI. > >>>>> > >>>>> Regards. > >>>>> > >>>>> [1] https://builds.apache.org/view/M-R/view/OpenJPA/ > >>>>> > >>>>>> Le jeu. 17 oct. 2019 à 08:21, Francesco Chicchiriccò < > >>>> ilgro...@apache.org> > >>>>>> a écrit : > >>>>>> > >>>>>>> Hi all, > >>>>>>> I think it would be really useful to enable Travis CI for our > GItHub > >>>>>>> repository; besides other benefits, this would also improve our > >>>> ability to > >>>>>>> check PRs. > >>>>>>> > >>>>>>> WDYT? > >>>>>>> Regards. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ > >
