Re: [DISCUSS] Enable Travis CI?

IMHO we should take this (good) track as an awesome opportunity to "fix" that ;) Le jeu. 17 oct. 2019 à 10:12, Francesco Chicchiriccò 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 mast

Re: [DISCUSS] Enable Travis CI?

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 infr

Re: [DISCUSS] Enable Travis CI?

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. Romain Manni-Bucau @rmannibucau

Re: [DISCUSS] Enable Travis CI?

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

Re: [DISCUSS] Enable Travis CI?

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. Romain Manni-Bucau @rmannibucau | Blog

Re: [DISCUSS] Enable Travis CI?

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 centraliz