I believe my employer also offers free build services for OSS projects via our CodeShip offering. If people are concerned about tying PR validation exclusively to one vendor we should inspect the CloudBees CodeShip capabilities (includes Docker build agents, which can be very nice... though I confess I have not tried CodeShip yet, despite it being a product of my employer)
I think CircleCI also provides some stuff in that line. We could also investigate GitHub Actions for build validation... but further down the road that may require getting Microsoft/GitHub to provide CPU time donations. On Sun 6 Jan 2019 at 20:04, Sylwester Lachiewicz <slachiew...@gmail.com> wrote: > In Maven Resolver we have a sample Travis configuration, so someone can > test with the forked repo. > If we go with Travis CI I would be good to have a common configuration for > all projects (ie to run run-it etc and have .travis.yml excluded from RAT). > I saw in one Apache project (don't remember now name) where they have a > separate script to merge PR but prerequisite was to PR from forked repo has > successful Travis build. > This way we do not use "our" Apache accounts to run builds and developers > are free to configure anything (and be responsible) in its own Travis > accounts. > > BR > Sylwester > > pt., 4 sty 2019 o 19:21 Enrico Olivelli <eolive...@gmail.com> napisał(a): > > > 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
