2020-08-15 22:51 UTC+02:00, Geoffrey Blake <geoffrey.w.bl...@gmail.com>: > Not familiar with Apache CI, but github actions do not support Arm builds. > Arm should be recognized as a first class build target these days. Travis > allows Arm builds so not sure about the reasoning for moving off.
Also, is Travis computing time a donation to the ASF? If so, we could continue using it for providing "convenience" builds for various architectures and thus spare some load on the Jenkins cluster, using the latter only for ensuring an independent build in a stable environment, and the generation of snapshots. Regards, Gilles > > -Geoff > > On Sat, Aug 15, 2020 at 1:11 PM Matt Sicker <boa...@gmail.com> wrote: > >> Agreed on the GitHub Actions. Neutral about how snapshot sites are >> >> published since there are multiple methods of doing the same thing, >> >> though if that's also simple to set up via the action to commit the >> >> output to the gh-pages branch, I'd say go for it! >> >> >> >> On Sat, 15 Aug 2020 at 13:07, Gary Gregory <garydgreg...@gmail.com> >> wrote: >> >> > >> >> > Hi All, >> >> > >> >> > In order to ease maintenance, I propose that we drop Travis CI in favor >> of >> >> > Apache CI and GitHub Actions. 2 CI systems instead of 3 seems like >> > plenty >> >> > to me. The exception would be a component with an existing complex >> > Travis >> >> > build that was not or cannot be reproduced in GitHub Actions. >> >> > >> >> > Looking ahead, I think we should consider publishing SNAPSHOT sites to >> >> > GitHub.io. >> >> > >> >> > Gary >> >> >> >> >> >> >> >> -- >> >> Matt Sicker <boa...@gmail.com> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
