Hi. 2020-07-22 21:48 UTC+02:00, Gary Gregory <garydgreg...@gmail.com>: > Hi All: > > There are three build systems available to us: > > - Apache Jenkins > - GitHub Actions > - Travis CI > - Plus, *your *PC (that one does not really count.)
I don't agree: a source distribution assumes that one's own computing resources is essential. This project never discussed departing from the assumption that a contributor should be able to build locally and primarily check that the reports generated comply with the level of quality defined, implicitly and explicitly, over the years. > We have components building here and there, with multiple components > building on multiple systems. > > My main driver is that we already use GitHub for source mirroring and PRs, This also was never agreed as a change of project management; from a convenience, the use of GitHub has become an assumption to which everyone is suddenly requested to adapt to. > so it feels better to me to have builds in the same place. IMHO, we should ensure that components build on Jenkins. > I propose we default to GitHub -1 > while allowing each component to do whatever > it wants. Specifically, I would like to drop Travis CI and use GitHub where > both are used by a component. More automated builds are a nice convenience. But just that. Until the policy is explicitly changed and the process adapted accordingly, what counts is the build performed on the release manager's (and the reviewer's) computer. > A tangential issue is whether to use or keep on using Coveralls and > whether that can be made to play with GitHub or if we should just use > JaCoCo all over even though I am uncertain as to the liveliness of the > JaCoCo project. I don't get why you would want us to have all our eggs in the same basket. Regards, Gilles > > Thank you, > Gary > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
