Re: priority list

2022-11-21 Thread Kirk Lund
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
> > > > >
> > > >
> > >
> >
>


rewrite CI pipeline

2022-11-21 Thread Sai Boorlagadda
Hello devs,

I started a parallel activity to tease out CI work on using ASF jenkins and
also Github actions (though GHA has several issues). I wanted to provide
some updates on these efforts and seek if others are interested to
collaborate.

Jenkins - Was waiting for INFRA to create a high level folder[1] to host
all Geode jobs and have a basic unit test pipeline[2] that runs tests on
Ubuntu using Oracle JDK 8. While there are failing tests[3] that need some
help, I am still exploring ways to write pipelines and include multiple
JDKs into a single JOB, so we can build using 8 while we test using 11.

GHA - While it is super quick and easy to start writing a pipeline[4] using
"matrix and strategy", There are few tests[5] failing consistently using
Adopt JDK 8 on Ubuntu.

[1] https://ci-builds.apache.org/job/Geode/
[2]
https://github.com/apache/geode/blob/4abcdc06af536e1188e0f8c432e9b768c175d8c0/.jenkins/Jenkinsfile
[3] https://ci-builds.apache.org/job/Geode/job/geode-develop/11/console
[4] https://github.com/apache/geode/pull/7870/files
[5] https://github.com/apache/geode/actions/runs/3515795079


Re: priority list

2022-11-21 Thread Sai Boorlagadda
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: rewrite CI pipeline

2022-11-21 Thread Kirk Lund
Looks like membership errors. Membership went through extensive changes to
be modularized as geode-membership, and VMware was still fixing some bugs
in it when I left. These could be really difficult to solve for those of us
who have no experience with the new membership.

I wonder if we could engage VMware for a little more help on these failures
before they depart entirely?

Last I heard there were also problems with using OpenJDK 8 but I don't know
the details. VMware was using Liberica JDK 8 from Bellsoft. We may also
need VMware to explain what the issue was with OpenJDK 8 so we can figure
out what to do about it.

On Mon, Nov 21, 2022 at 3:29 PM Sai Boorlagadda 
wrote:

> Hello devs,
>
> I started a parallel activity to tease out CI work on using ASF jenkins and
> also Github actions (though GHA has several issues). I wanted to provide
> some updates on these efforts and seek if others are interested to
> collaborate.
>
> Jenkins - Was waiting for INFRA to create a high level folder[1] to host
> all Geode jobs and have a basic unit test pipeline[2] that runs tests on
> Ubuntu using Oracle JDK 8. While there are failing tests[3] that need some
> help, I am still exploring ways to write pipelines and include multiple
> JDKs into a single JOB, so we can build using 8 while we test using 11.
>
> GHA - While it is super quick and easy to start writing a pipeline[4] using
> "matrix and strategy", There are few tests[5] failing consistently using
> Adopt JDK 8 on Ubuntu.
>
> [1] https://ci-builds.apache.org/job/Geode/
> [2]
>
> https://github.com/apache/geode/blob/4abcdc06af536e1188e0f8c432e9b768c175d8c0/.jenkins/Jenkinsfile
> [3] https://ci-builds.apache.org/job/Geode/job/geode-develop/11/console
> [4] https://github.com/apache/geode/pull/7870/files
> [5] https://github.com/apache/geode/actions/runs/3515795079
>


Re: rewrite CI pipeline

2022-11-21 Thread Kirk Lund
It's also possible that these issues are specific to using OpenJDK 8 or
Ubuntu. I thought we were building and testing with CentOS before.

On Mon, Nov 21, 2022 at 4:20 PM Kirk Lund  wrote:

> Looks like membership errors. Membership went through extensive changes to
> be modularized as geode-membership, and VMware was still fixing some bugs
> in it when I left. These could be really difficult to solve for those of us
> who have no experience with the new membership.
>
> I wonder if we could engage VMware for a little more help on these
> failures before they depart entirely?
>
> Last I heard there were also problems with using OpenJDK 8 but I don't
> know the details. VMware was using Liberica JDK 8 from Bellsoft. We may
> also need VMware to explain what the issue was with OpenJDK 8 so we can
> figure out what to do about it.
>
> On Mon, Nov 21, 2022 at 3:29 PM Sai Boorlagadda 
> wrote:
>
>> Hello devs,
>>
>> I started a parallel activity to tease out CI work on using ASF jenkins
>> and
>> also Github actions (though GHA has several issues). I wanted to provide
>> some updates on these efforts and seek if others are interested to
>> collaborate.
>>
>> Jenkins - Was waiting for INFRA to create a high level folder[1] to host
>> all Geode jobs and have a basic unit test pipeline[2] that runs tests on
>> Ubuntu using Oracle JDK 8. While there are failing tests[3] that need some
>> help, I am still exploring ways to write pipelines and include multiple
>> JDKs into a single JOB, so we can build using 8 while we test using 11.
>>
>> GHA - While it is super quick and easy to start writing a pipeline[4]
>> using
>> "matrix and strategy", There are few tests[5] failing consistently using
>> Adopt JDK 8 on Ubuntu.
>>
>> [1] https://ci-builds.apache.org/job/Geode/
>> [2]
>>
>> https://github.com/apache/geode/blob/4abcdc06af536e1188e0f8c432e9b768c175d8c0/.jenkins/Jenkinsfile
>> [3] https://ci-builds.apache.org/job/Geode/job/geode-develop/11/console
>> [4] https://github.com/apache/geode/pull/7870/files
>> [5] https://github.com/apache/geode/actions/runs/3515795079
>>
>


Re: rewrite CI pipeline

2022-11-21 Thread Sai Boorlagadda
I was thinking it has to do with either JDK or ubuntu. I also tried
'temurin'
and there were different sets of errors. So to see if the devs can shed
some light on JDK dependency or any prior knowledge on choosing
bellsoft distribution.

Sai

On Mon, 21 Nov 2022 at 16:25, Kirk Lund  wrote:

> It's also possible that these issues are specific to using OpenJDK 8 or
> Ubuntu. I thought we were building and testing with CentOS before.
>
> On Mon, Nov 21, 2022 at 4:20 PM Kirk Lund  wrote:
>
> > Looks like membership errors. Membership went through extensive changes
> to
> > be modularized as geode-membership, and VMware was still fixing some bugs
> > in it when I left. These could be really difficult to solve for those of
> us
> > who have no experience with the new membership.
> >
> > I wonder if we could engage VMware for a little more help on these
> > failures before they depart entirely?
> >
> > Last I heard there were also problems with using OpenJDK 8 but I don't
> > know the details. VMware was using Liberica JDK 8 from Bellsoft. We may
> > also need VMware to explain what the issue was with OpenJDK 8 so we can
> > figure out what to do about it.
> >
> > On Mon, Nov 21, 2022 at 3:29 PM Sai Boorlagadda <
> sai.boorlaga...@gmail.com>
> > wrote:
> >
> >> Hello devs,
> >>
> >> I started a parallel activity to tease out CI work on using ASF jenkins
> >> and
> >> also Github actions (though GHA has several issues). I wanted to provide
> >> some updates on these efforts and seek if others are interested to
> >> collaborate.
> >>
> >> Jenkins - Was waiting for INFRA to create a high level folder[1] to host
> >> all Geode jobs and have a basic unit test pipeline[2] that runs tests on
> >> Ubuntu using Oracle JDK 8. While there are failing tests[3] that need
> some
> >> help, I am still exploring ways to write pipelines and include multiple
> >> JDKs into a single JOB, so we can build using 8 while we test using 11.
> >>
> >> GHA - While it is super quick and easy to start writing a pipeline[4]
> >> using
> >> "matrix and strategy", There are few tests[5] failing consistently using
> >> Adopt JDK 8 on Ubuntu.
> >>
> >> [1] https://ci-builds.apache.org/job/Geode/
> >> [2]
> >>
> >>
> https://github.com/apache/geode/blob/4abcdc06af536e1188e0f8c432e9b768c175d8c0/.jenkins/Jenkinsfile
> >> [3] https://ci-builds.apache.org/job/Geode/job/geode-develop/11/console
> >> [4] https://github.com/apache/geode/pull/7870/files
> >> [5] https://github.com/apache/geode/actions/runs/3515795079
> >>
> >
>


Re: rewrite CI pipeline

2022-11-21 Thread Anthony Baker
I would not expect to see any differences between openjdk distributions.

Anthony


> On Nov 21, 2022, at 4:34 PM, Sai Boorlagadda  
> wrote:
> 
> !! External Email
> 
> I was thinking it has to do with either JDK or ubuntu. I also tried
> 'temurin'
> and there were different sets of errors. So to see if the devs can shed
> some light on JDK dependency or any prior knowledge on choosing
> bellsoft distribution.
> 
> Sai
> 
> On Mon, 21 Nov 2022 at 16:25, Kirk Lund  wrote:
> 
>> It's also possible that these issues are specific to using OpenJDK 8 or
>> Ubuntu. I thought we were building and testing with CentOS before.
>> 
>> On Mon, Nov 21, 2022 at 4:20 PM Kirk Lund  wrote:
>> 
>>> Looks like membership errors. Membership went through extensive changes
>> to
>>> be modularized as geode-membership, and VMware was still fixing some bugs
>>> in it when I left. These could be really difficult to solve for those of
>> us
>>> who have no experience with the new membership.
>>> 
>>> I wonder if we could engage VMware for a little more help on these
>>> failures before they depart entirely?
>>> 
>>> Last I heard there were also problems with using OpenJDK 8 but I don't
>>> know the details. VMware was using Liberica JDK 8 from Bellsoft. We may
>>> also need VMware to explain what the issue was with OpenJDK 8 so we can
>>> figure out what to do about it.
>>> 
>>> On Mon, Nov 21, 2022 at 3:29 PM Sai Boorlagadda <
>> sai.boorlaga...@gmail.com>
>>> wrote:
>>> 
 Hello devs,
 
 I started a parallel activity to tease out CI work on using ASF jenkins
 and
 also Github actions (though GHA has several issues). I wanted to provide
 some updates on these efforts and seek if others are interested to
 collaborate.
 
 Jenkins - Was waiting for INFRA to create a high level folder[1] to host
 all Geode jobs and have a basic unit test pipeline[2] that runs tests on
 Ubuntu using Oracle JDK 8. While there are failing tests[3] that need
>> some
 help, I am still exploring ways to write pipelines and include multiple
 JDKs into a single JOB, so we can build using 8 while we test using 11.
 
 GHA - While it is super quick and easy to start writing a pipeline[4]
 using
 "matrix and strategy", There are few tests[5] failing consistently using
 Adopt JDK 8 on Ubuntu.
 
 [1] 
 https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci-builds.apache.org%2Fjob%2FGeode%2F&data=05%7C01%7Cbakera%40vmware.com%7C313885015e604ec0189c08dacc217432%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638046741303111474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BcOk3bhLThh21s0iQAZmes4gab%2B8YpdIlnoVgTIlsb4%3D&reserved=0
 [2]
 
 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fblob%2F4abcdc06af536e1188e0f8c432e9b768c175d8c0%2F.jenkins%2FJenkinsfile&data=05%7C01%7Cbakera%40vmware.com%7C313885015e604ec0189c08dacc217432%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638046741303111474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9UvAI7RIV1caJJz70958WqyHNgkkN%2FMihHqONxUKiiw%3D&reserved=0
 [3] 
 https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci-builds.apache.org%2Fjob%2FGeode%2Fjob%2Fgeode-develop%2F11%2Fconsole&data=05%7C01%7Cbakera%40vmware.com%7C313885015e604ec0189c08dacc217432%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638046741303111474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Kk1Nj%2FfusbTjMnBLQdpYoJk1mFSGNv0DaLYTmnrNUQE%3D&reserved=0
 [4] 
 https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fpull%2F7870%2Ffiles&data=05%7C01%7Cbakera%40vmware.com%7C313885015e604ec0189c08dacc217432%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638046741303267691%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=psIl5Jj%2BZHWXfuv1LBj5V5GKbzoy%2FnN9AQFrIjks9Bo%3D&reserved=0
 [5] 
 https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Factions%2Fruns%2F3515795079&data=05%7C01%7Cbakera%40vmware.com%7C313885015e604ec0189c08dacc217432%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C638046741303267691%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JJXdJ%2BQoGOtTdRw7kl8AoFCrilQ7KtCcXS7E6xUJBfU%3D&reserved=0
 
>>> 
>> 
> 
> !! External Email: This email originated from outside of the organization. Do 
> not click links or open attachments unless you recognize the sender.