Hi, About GitHub actions, there are currently some limitations you I pointed out previously in the devlist. Even tho, I was stuck in the process of migrating geode-native CI to GH actions, mostly since I didn't have the necessary permissions. If you want to have further info about GH actions, you can check Apache BUILDS list.
And as for Geode repository, considering the number of resources its CI requires, I'd say GH actions is a no go... Also, I think it was Dan Smith, the one that pointed out that Apache has a Jenkins instance available, so every Apache project can use its resources. My guess is that Apache Jenkins infra would be a better fit for Geode repository. Still, it remains to be seen, since resource requirements on that repository are really high. Sorry I couldn't be of more help, but at least I hope these pointers are useful. /Mario ________________________________ From: Niall Pemberton <niall.pember...@gmail.com> Sent: Saturday, November 12, 2022 10:46 AM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: priority list On Sat, Nov 12, 2022 at 3:24 AM Sai Boorlagadda <sai.boorlaga...@gmail.com> wrote: > Hello Devs, > > I would like to understand some of the top priority items that we should > focus and spend our time on while we ramp up with new community members. > > Any pointers to the scope of the next release or a list of items we should > do as part of this transition. While going through the mailing list what > immediately caught my eye is CI/CD migration to Github actions. > I would say the number one priority is getting a CI instance setup. I guess you've seen what Mario said about his efforts on GitHub actions? Niall > > Sai >
