Would the preclusion of non-committers also prevent us from configuring Jenkins to auto-test on PR independent of who opens it?
One of my current concerns is that we're maintaining 2x the CI for 1x the benefit, and I don't currently see an easy way to unify them (perhaps a lack of imagination?). I know there's a long history behind the choice of CircleCI, so I'm not trying to be hand-wavy about all of the thought that went into that decision, but that decision has costs beyond just a paid CircleCI account. My long term, probably naive, goals for CI would be to: 1. Have a CI system that is *fully* available to *any* contributor, modulo safeguards to prevent abuse 2. Have a CI system that is easy to maintain, with clear instructions and examples for adding a new test suite 3. Have a CI system with reporting that makes it easy to quickly identify test failures, as well as test *stability* over time CI isn't glamorous, is often underfunded, and yet is critical to project velocity and stability. I really appreciate Josh and others driving these discussions! Cheers, Derek On Thu, Oct 20, 2022 at 1:25 PM Ekaterina Dimitrova <e.dimitr...@gmail.com> wrote: > Sounds like great plan to me. > Just wanted to mention one caveat. Non-committers do not have access to > ASF CI. I do not think this will change. While no one of us ever said no to > push a patch for testing, it is good to have a good backup plan people can > do it themselves. Currently this is CircleCI. Maybe we can leave it just as > is at some point and people who want to use it can continue supporting it > themselves? I don’t have a clear answer now. I guess time will show > > On Thu, 20 Oct 2022 at 14:51, Brandon Williams <dri...@gmail.com> wrote: > >> On Thu, Oct 20, 2022 at 1:45 PM Josh McKenzie <jmcken...@apache.org> >> wrote: >> > >> > My high level hope is that we can: >> > >> > 1. Unstick mainline yearly releases (vote to accept circle results, >> make circle more robust <- WE ARE HERE) >> > 2. Invest resources into the ASF CI environment to get it to being a >> viable replacement for circle (requirements for this qualification TBD) >> > 3. Deprecate circle >> > >> > I'm doing my best to help make the above a reality. There's a lot of >> hand-waving in "ASF CI as viable replacement" but it's 2022 and there's a >> lot of modern build and ci system's learning our industry has gained in the >> last decade we're not yet taking advantage of. >> >> I'm a strong +1 on this plan and will do everything I can to assist. >> We should have a discussion on how to get this accomplished and >> delineate the current problems we are facing. >> > -- +---------------------------------------------------------------+ | Derek Chen-Becker | | GPG Key available at https://keybase.io/dchenbecker and | | https://pgp.mit.edu/pks/lookup?search=derek%40chen-becker.org | | Fngrprnt: EB8A 6480 F0A3 C8EB C1E7 7F42 AFC5 AFEE 96E4 6ACC | +---------------------------------------------------------------+
