On Fri 4 Jan 2019 at 22:00, Tibor Digana <tibordig...@apache.org> wrote:
> @Stephen Connolly <steph...@apache.org> > After such a big investment, especially made on your side, in Jenkins > plugin you developed you do not want to support the GitHub PRs and you just > let be to go with TravisCI just like that? I do not think so! I want to add GitHub support to ASF Jenkins too, but PR verification should be layers. No harm in having one layer provided by Travis/Codeship/etc and the second layer by Jenkins. The other point is even if I add PR support to the ASF Jenkins, it’s not going to be automatic build for non-committers (which is the group of PRs that need the CI feedback most, and with least delay... ie before they walk away) as we simply do not have throw-away infra for building PRs that could contain bitcoin miners triggered by a unit test, etc. Now if infra wants to set up a dedicated “safe space” for untrusted PRs to be built... super... but until that happens, we’ll need something like Travis to take that risk for us. > T > > > On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > +1 from me > > > > On Fri 4 Jan 2019 at 18:21, Enrico Olivelli <eolive...@gmail.com> wrote: > > > > > Hi, > > > I would like to try out Travis on this small plugin: > > > https://github.com/apache/maven-scripting-plugin > > > > > > I have pushed a minimal configuration file > > > I need to ask to Infra, but I need approval from the community and > > PMCs... > > > > > > Can I proceed ? > > > > > > Enrico > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > -- > > Sent from my phone > > > -- Sent from my phone
