On Wed, Jul 22, 2020 at 4:59 PM Olivier Lamy <ol...@apache.org> wrote:
> On Thu, 23 Jul 2020 at 06:45, Gary Gregory <garydgreg...@gmail.com> wrote: > > > On Wed, Jul 22, 2020 at 4:22 PM Olivier Lamy <ol...@apache.org> wrote: > > > > > How do you deploy snapshots automatically? > > > > > > > I don't use snapshots. If I have to have one, I build it locally. > > > > But what about the community who wants to try snapshots build? > > Sigh, did you not read my _entire_ proposal where I clearly state, now with added emphasis: "I propose we default to GitHub *while allowing each component to do whatever it wants*." Gary > > > > Gary > > > > > > > > > > On Thu, 23 Jul 2020 at 05:48, Gary Gregory <garydgreg...@gmail.com> > > wrote: > > > > > > > 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.) > > > > > > > > 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, > > > > so it feels better to me to have builds in the same place. > > > > > > > > I propose we default to GitHub 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. > > > > > > > > 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. > > > > > > > > Thank you, > > > > Gary > > > > > > > > > > > > > -- > > > Olivier Lamy > > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy >
