Jenkins Cloud Native SIG, 30 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Cloud-Native SIG Meeting for 20201030

Description

Jenkins Cloud-Native SIG Meeting for 20201030

A

All righty we are recording, welcome everybody. This is the jenkins cloud native sig meeting. This is a sort of impromptu meeting because we don't have an official meeting time. Yet my name is marky jackson, I'm one of the sig leads and uh before we get started just a couple house cleaning items. This is a recorded meeting, uh so it is available on the internet and we do follow the jenkins code of conduct, which essentially amounts to be nice to one another.

A

uh So we have I'm gonna go ahead and share my.

A

Screen and we have two topics on the roadmap- the first topic is uh meeting cadence, so we started this impromptu meeting uh today, friday october 30th at 8 00 a.m, pacific standard time, and what I wanted to do is set a meeting. Cadence. Does this time work for everybody.

B

On my side, yeah, it's uh this this time is good.

A

B

C

A

C

Yeah, this works okay. For me, the other the previous times, weren't possible.

A

Okay, so team bibhav, so what I will do, uh I am going to add an action item.

A

Give me just a moment.

A

I will add the meeting to the community calendar.

A

There will be a new zoom link and I will update that in the.

A

Chat so that is it. Does anybody have anything else regards to that for meeting cadence.

A

Okay, moving on.

B

I just wanted to ask like uh how did these meetings like go? Go on before this kind of re-initialization.

A

Wait, can you repeat that again, how do these meetings, what.

B

Yeah, so how did these meetings go before like we before right now,.

A

uh So previously uh the meetings kind of were they're much like every other uh sig meeting. uh There's a note taking they'll be we'll talk about. You know, items that are up for discussion items for road mapping and things like that.

A

Really what we want to try to do, uh I would think, in the first few meetings is: try to start thinking about what we're looking to accomplish with this sig as well as start getting a road map together for the things that we'd like to accomplish in the next year.

A

Does that answer your question.

B

Yeah yeah it does so. uh If uh can, if it's okay, can I ask another question just related to this one.

A

B

Yeah uh so well before, before uh this reinitialization like uh what? What were the goals that were set for the sick.

A

So if you go back at that meeting doc, I gave you there there weren't, really the goals that were set need to be, we sort of need to revisit them and make sure are they still the same? So if you look back at some of these previous meeting notes here, you'll be able to see some of the things that were being worked on and that's kind of once. We, uh I think, with this meeting.

A

What we want to do is make sure we set the meeting cadence and then what we want to accompl what we want to start doing next weekend, which probably will be everybody, reviewing these notes and seeing if there were things that were left open if those are still of value and uh if we can accomplish those and then start to build out the road map.

A

Does that answer your question.

B

Yes, yes, it does. Thank you more awesome.

A

You're welcome uh so the next topic is, uh they have you've entered that and that's the jenkins operator roadmap. So I would like to just touch on this. This topic, just a real quick bit. The jenkins operator is, is handled by another uh entity like they're, an actual company that handles it, and uh so we don't. I know they did publish their roadmap.

A

uh If we wanted to try to bring that into the cloud native sig, then we're probably gonna want to reach out to them and get them involved here.

A

But please take it away. What were your questions.

B

So it's uh it's! My questions were so I just wanted to kind of go over what is happening with the operator right now and then uh on our side. So I so I'll just give a little introduction of myself, so my name is, and I work for red hat in the openshift jenkins team.

B

So we have an instance of like a jenkins image and a few plugins that we maintain and we've been giving it to our customers and supporting it, and now that we are in our main product has like moved away from the jenkins image itself. We are slowly uh getting into like the kubern, like the jenkins operator and for the last, uh like, I think it's it's been a little more than a year since we have uh kind of been looking at the jenkins operator and have been working on it.

B

So, apart from that, uh like right now uh with the governance stuff that is going on what we've done right now. Is we folk the jenkins operator repo and we have? uh We are working on it uh actively.

B

So uh I uh so in in this I'm basically going to discuss like what we have as uh uh in the fork like like doing with the jenkins operator, and if for the it would be possible to get the you know, uh people from workers lab involved with this, and you know, get discussions going on and how we can really. You know, uh move the operator forward.

A

Yeah, so uh I know that there is an email chain that uh has been going back and forth in regards to getting that. I have personally reached out uh to the the team that is handling the jenkins operator to get some feedback. I know some other people have also done the same thing I think before we can have discussions about the jenkins operator roadmap. We definitely need to get them involved in the sig.

A

So I'm going to reach out again to see if we can have them attend next week's meeting and see if there's something we can do, but I definitely think that before we have any discussion about that, we need to have them here as well. Would you agree.

B

Yes, I agree so uh yeah that that's all that's uh that's it from my side, then for the roadmap. Guess uh if, if we need uh voter slap to be in this meeting, yeah I'm, I agree with that as well.

D

Yeah, so what is the current state about that? um We got a request response from management.

D

They said that they are about writing back to the developer. My link list never happened, but they also declared the intent to start contributions in november.

D

Well, jenkins, both tries to get the response. If it doesn't come, maybe we will consider other options because, right now the situation is not the the product just doesn't evolve, but there are private forks which are being evolved, which is not exactly what is expected uh from our open source project building hosted within the junkie serbian exhibition and yeah. If it gets stuck further, I think we will have to open that.

A

Okay, so let me just make a note here, because I can't spell.

A

Okay, so basically, what we're doing is we're reaching out we're going to wait and see we'll wait until once the jenkins elections are done to see where we stand and then we'll decide. The next course of action once that's done is that okay, bibhav.

B

Yes, that sounds cool.

D

B

Not really dependent.

D

On jenkins selections per se, but uh yeah, it's also a matter of the bandwidth because advantages both was quite busy this month. It will be a bit better in november because he did the most of the leg work until the elections are over, but still right. Now. I would give another chance uh with this drop to this.

A

Does anybody house have anything to add to that.

D

Just sorry that it takes so long because yeah it's something to think about in our processes, so that we can introduce another escape hatch to prevent it in the future.

A

Okay, does anybody else have any other topics that they would like to discuss.

A

Okay, so I'm going to go ahead and just cover what the uh what the action items are for next week, everybody uh oleg everyone has agreed to this meeting cadence meeting this day and time. I know that this may not always work for you, uh but.

D

This time is actually quite good, especially now in the wintertime.

A

Okay, awesome I'll, add you as a plus one.

D

Yeah for me, the biggest problem this time after 6 p.m, especially that's why it uh pipeline other training seek was a problem, but now this uh meeting is four pm and pipeline multiple ps5. So it's basically just uh my availability is not the timing.

A

Awesome, okay, uh so the action items that are for next uh between now and next meeting will be. I will be adding the meeting to the community calendar. I will set up a new zoom uh and then I'll update uh everybody in the cloud native sig getter. Once that's done uh an action item for everybody.

A

Everybody on this call will be to review the previous meeting notes and see if there's any areas of interest that we would like to extract from these previous meetings and resurface them, and we will go over that next meeting, which will be next friday. At the same time,.

D

Yeah, I will pull a couple of additional meetings which are not listed here because they happened in a limited group and not in this document. I guess and yeah. There are a few other action items I took in may june, which still remain on me. One is updating basic pages.

D

We also had an agreement on things like moving gcask to another speaker de facto and yeah refactoring. What is actually on the page, so it reflects this data on the roadmap.

D

It still remains on my list. Unless somebody else wants to take it in short term, you can uh basically keep it as this.

A

Can I assign that to you oleg for moving the j caps, or at least okay, I've? Also, I've also assigned updating the landing page to you if you'd like I can take to do that, but I think that we should maybe uh sync on the verbiage that we want on there.

D

There is a half updated page somewhere in my four, my branches, oh jump inside so yeah. I like to start doing that, but yeah anyway, there will be a pull request.

A

Awesome, okay, so it looks like we have our uh action items. Does anybody else have anything they want to add.

B

Yeah, if you don't mind, I had I had a question to you: marky, especially uh you're part of the cd foundation. uh If I'm not wrong like cd foundation, interoperability, so uh are there any things that are overlapping between what cloud native sick uh might do forward? And you know uh the cd for uh the interoperability sake of cd foundation uh would be doing.

A

uh I think so the way the interoperability sig is working is a much larger sort of scope and that's for all of the projects that fall under the uh under the cdf. I do think there will be times that we will go and update the interoperability sig, but I don't think the uh the existence of this sig, as well as the interoperability sig overlap with each other, because what the cdf sort of guidance is is larger to every project under the cdf, where the guidance for this sig is specific just to jenkins.

A

So there may be times when we update them, but uh but there's going to be no overlap.

A

B

Answer your question: yes, uh it it does uh partially. I think, uh because uh what about then now plugins such as uh the one that I've been working on uh tecton plant, plug-in and if there are on others like you know uh the kubernetes plug-in, not kubernetes, uh maybe openshift plug-ins, which uh you know, do builds and stuff for jenkins.

B

So are. Would these be considered overlaps or just no? No.

A

Those would not be considered overlaps. I think those would be considered specific to this sig. However, we can update the interoperability sig from time to time about the presence of these plugins. So, for example, oleg uh recently gave a demo of what was it the the file runner, which one was it all like that.

B

It was the file runner and I watched it as well.

A

Right so there are interoperability, things that we can update them on, but the work that goes on within those plugins would be more specific to the jenkins sig and not the cdf interoperability.

A

Does that does that answer your question.

B

Yeah, it does make things clear. Yes,.

D

Awesome, yes, basically, how it's supposed to work in foundations, so yeah. We will have a lot of uh jenkins internal things, even if they contribute uh to communication with other projects at some point but yeah. At the same time, you have a lot of opioid things so, for example, health charts for jenkins. It's definitely something we may want to discuss at the cloud native seek, but it's unlikely an interest for interoperability seek at the moment.

A

Okay, awesome: well, if nobody has anything else, we will close this meeting out and I'll give you 10 minutes back, and I will see you next week, so you want uh meetings every week right.

A

uh I think we can start every week, but then once we start to get going and we have the sort of roadmap laid out, then we can move it to bi-weekly, I'm fine with that, but for now I think we should keep them every week until we get everything ironed out.

D

And especially, if we keep them short.

A

Yeah alrighty, everybody have a good weekend and I will see you all online.

B

See you all, it was nice uh catch and go.

A

B

A