Kirk, I started playing around both ASF jenkins and GHA to tease out the differences between what features are available between the two solutions and how easy it is to write the pipelines with what level of control. Eg: I haven't figured out yet how to write dockerized builds with ASF jenkins.
Rather than migrating existing pipelines as-is, we should define the MVP of a pipeline that we should focus on first. I like your idea on having a collaborative setup, let me find some time. Sai On Mon, 21 Nov 2022 at 12:31, Kirk Lund <kl...@apache.org> wrote: > I have next to no experience with Jenkins but I'd be happy to get on some > sort of zoom or google or other screen sharing conference call to offer > what little help I can. > > -Kirk > > On Tue, Nov 15, 2022 at 2:19 PM Sai Boorlagadda <sai.boorlaga...@gmail.com > > > wrote: > > > Thanks Mark. > > > > Dan added me required permissions. So I will try to get a simple build > step > > and configure the job. > > > > Will reach out for specific questions or issues. Do you or anyone have > any > > project reference that uses Jenkins? > > > > Sai > > > > On Mon, 14 Nov 2022 at 07:01, Mark Bretl <mbr...@apache.org> wrote: > > > > > Jenkins CI in 2014 was limited to say the least, now Jenkins has actual > > > pipelines and stages, with parallel functionality, so it will be much > > > better this time around if we go that route. I think we could go back > to > > > the basics, do a compile build and then add unit/basic/BVT tests on top > > > without too much trouble. I would say if we can get CI running for the > > main > > > Geode project with a compile in Jenkins, it would be a great first > step. > > I > > > do have quite a bit of Jenkins experience, so I can definitely help > out. > > > > > > --Mark > > > > > > On Sat, Nov 12, 2022 at 10:24 PM Kirk Lund <kl...@apache.org> wrote: > > > > > > > Do we know why Geode has such a large CI resource requirement? > > > > > > > > I would guess that it was partially due to trying to run as many > tests > > in > > > > parallel as possible to shorten the feedback cycle. The recent CI > > > pipelines > > > > were also built on Pivotal's Concourse which seems to promote a > greater > > > > number of smaller CI jobs (or at least that's my impression). > > > > > > > > This code base did successfully use a Jenkins CI prior to 2014 even > > > though > > > > it took more hours to complete than the more recent Concourse CI. I > > think > > > > Mark Bretl was involved in that Jenkins CI so he might remember some > > > > details or tips or even possible challenges to watch out for. > > > > > > > > -Kirk > > > > > > > > On Sat, Nov 12, 2022 at 4:42 AM Mario Salazar de Torres > > > > <mario.salazar.de.tor...@est.tech> wrote: > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > >
