Re: priority list
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 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 > > 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 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 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 > > > > 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 > > > > > Sent: Saturday, November 12, 2022 10:46 AM > > > > > To: 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 > > > > > > > > > > > > > > > > > > > > >
Re: priority list
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 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 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 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 > > > 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 > > > > Sent: Saturday, November 12, 2022 10:46 AM > > > > To: 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 > > > > > > > > > > > > > > >
Re: priority list
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 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 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 > > 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 > > > Sent: Saturday, November 12, 2022 10:46 AM > > > To: 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 > > > > > > > > > >
Re: priority list
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 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 > 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 > > Sent: Saturday, November 12, 2022 10:46 AM > > To: 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 > > > > > >
Re: priority list
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 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 > Sent: Saturday, November 12, 2022 10:46 AM > To: dev@geode.apache.org > Subject: Re: priority list > > On Sat, Nov 12, 2022 at 3:24 AM Sai Boorlagadda > > 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 > > >
Re: priority list
I added you to that group Sai, good luck! -Dan From: Sai Boorlagadda Sent: Saturday, November 12, 2022 8:11 AM To: dev@geode.apache.org Subject: Re: priority list !! External Email Dan, Could you add me to this ldap group 'hudson-jobadmin' to get administrative account for Jenkins? [1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fplugins%2Fservlet%2Fmobile%3FcontentId%3D65147535%23Jenkins-HowdoIgetanaccountdata=05%7C01%7Cdasmith%40vmware.com%7C39d2a3a41511414c985708dac4c89793%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638038663080305552%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=L4eRMo0%2BdqW8%2F6nDKzRuzZME846WcGSgpCXsY1SMI9Y%3Dreserved=0 ? Sai On Sat, Nov 12, 2022, 7:33 AM Sai Boorlagadda wrote: > Thanks, Mario for the context. > > I am also reading about GA performance/scalability issues[1] from other > apache project migration efforts, so it seems Jenkins would be the better > option for Geode. Let me read about getting started with Jenkins. > > [1] > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FBUILDS%2FGitHub%2BActions%2Bstatusdata=05%7C01%7Cdasmith%40vmware.com%7C39d2a3a41511414c985708dac4c89793%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638038663080305552%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=FUBkLgzZ2gDE01NUpkuC4Lymn3Zq5jBp%2BX9KhPaEhbs%3Dreserved=0 > > On Sat, 12 Nov 2022 at 04:42, Mario Salazar de Torres > 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 >> Sent: Saturday, November 12, 2022 10:46 AM >> To: 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 >> > >> > !! External Email: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender.
Re: priority list
Dan, Could you add me to this ldap group 'hudson-jobadmin' to get administrative account for Jenkins? [1] https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=65147535#Jenkins-HowdoIgetanaccount ? Sai On Sat, Nov 12, 2022, 7:33 AM Sai Boorlagadda wrote: > Thanks, Mario for the context. > > I am also reading about GA performance/scalability issues[1] from other > apache project migration efforts, so it seems Jenkins would be the better > option for Geode. Let me read about getting started with Jenkins. > > [1] > https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status > > On Sat, 12 Nov 2022 at 04:42, Mario Salazar de Torres > 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 >> Sent: Saturday, November 12, 2022 10:46 AM >> To: 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 >> > >> >
Re: priority list
Thanks, Mario for the context. I am also reading about GA performance/scalability issues[1] from other apache project migration efforts, so it seems Jenkins would be the better option for Geode. Let me read about getting started with Jenkins. [1] https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status On Sat, 12 Nov 2022 at 04:42, Mario Salazar de Torres 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 > Sent: Saturday, November 12, 2022 10:46 AM > To: dev@geode.apache.org > Subject: Re: priority list > > On Sat, Nov 12, 2022 at 3:24 AM Sai Boorlagadda > > 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 > > >
Re: priority list
On Sat, 12 Nov 2022 at 12:42, Mario Salazar de Torres 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. Thanks Mario, that was helpful Niall > > /Mario > > > From: Niall Pemberton > Sent: Saturday, November 12, 2022 10:46 AM > To: dev@geode.apache.org > Subject: Re: priority list > > On Sat, Nov 12, 2022 at 3:24 AM Sai Boorlagadda > > 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 > > >
Re: priority list
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 Sent: Saturday, November 12, 2022 10:46 AM To: dev@geode.apache.org Subject: Re: priority list On Sat, Nov 12, 2022 at 3:24 AM Sai Boorlagadda 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 >
Re: priority list
On Sat, Nov 12, 2022 at 3:24 AM Sai Boorlagadda 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 >
priority list
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. Sai
