On Thu 3 Jan 2019 at 18:03, Enrico Olivelli <[email protected]> wrote:
> Il gio 3 gen 2019, 17:38 Mickael Istria <[email protected]> ha scritto: > > > Hi, > > > > I think this discussion is diverging into "trying TravisCI for some > > plugins" and is loosing focus on the initial question of how to improve > the > > build+test flow to get faster feedback as a contributor or as a reviewer. Travis will get the build+test flow faster for non-committers. > > Can the GitHub PR builder plugin be enabled on Maven Core ? No, it’s not compatible with how we build, as currently we only build from gitbox not from GitHub so there is no link for Jenkins to see Committers > > would be allowed to trigger a test with a single comment once they > checked > > it doesn't cause a security flaw. > > > > It turns out that it is not simple as it could seem because we have custom > Jenkins plugins to scan all the repos and have a common configuration, so > in order to achieve such goal we need to enhance that plugin, please > Stephen correct me if I am wrong. Yep I need to enhance the plugin a little... just trying to clear stuff off my plate > Travis jumped on this train because it is easy to enable and it is very > widespread, and it leaves security problems out of ASF infra. > But a check with Travis won't ever cover all jobs we are actually starting > per-branch. > It can be a good compromise to start, but if we have resources to improve > current integration this will be the best choice for the mid term. > > Enrico > > > > > Cheers, > > > -- > > > -- Enrico Olivelli > -- Sent from my phone
