 Welcome, this is the Jenkins platform special interest group. It's the 8th of April 2022. Today's agenda items we have open action items. Docker agent support additions being considered. Linux Linux packages on system D requiring Java 11 for core Java 17 support. Changes in the Docker image exit lifecycle and the she code Africa pipeline help project that we're starting any other topics we need to put on the agenda. Okay, then let's go ahead. So by way of open action items. I've still got one open action item which is that the plugin installation manager tool documentation needs to be improved we have an outdated pull request that propose some changes. It needs to be go through a major revision and then be applied as a pull request to the tool repository rather than to the Jenkins.io doc site. And that's one that it's just going to have to wait, I don't have time to do it right now. We'll work on it when time allows. So this is just a status report we've had a request from Jenkins users to please support Docker on Windows Server 2022 LTSC. And we're interested in that but the Kubernetes version that first supports it is not available in the Jenkins in for yet. So it will be a while before we get to this one. The info team is aware aware and they've put it into their list of work to do. Then another piece of news Linux packages switched in Jenkins in the most recent Jenkins long term support release from using system five in it the old style of doing package initialization to the new style using system D. Jenkins had a few minor fixes in the most recent LTS and it's looking good. Last topic, our next topic was Java 11 or newer for Jenkins core or any sorry I should ask any questions from anyone on topics we've addressed so far. Okay, require Java 11 or newer is in progress. And the topic for discussion is we think we're ready for to say that September 2022 should be the release and mark to open the discussion, or to continue the discussion in the mailing list and the poll requests. We have it in several locations. It's a matter of getting everyone to agree. Yes, September 2022 is the right time to do this on the Java 17 topic. We've got tooling improvements that are in progress. Thanks to Basel Crow for his work on those plugins will need to perform updates and users can already begin testing it with Jenkins 2.339 and 339 and later. We're currently at 2.342. So, can test and experiment already. Any questions on those topics. All right, last item. This one Kevin may maybe relevant to you. So, in the Docker images that the Jenkins project provides will be using a new technique to handle what happens when the Jenkins process exits. So what this is is when the Jenkins project process is asked to restart itself. Okay, it uses some complicated Linux specific logic to to end the process and restart it. Next weekly release will simplify that dramatically. Instead of the complicated logic Jenkins will just exit, and it will then rely on the Docker container on the Docker container runtime to restart the process. So that makes it easier for us to maintain the Jenkins core code and gives better control over Docker. However, that is a behavior change that needs more explanation may need a blog post, etc. Any questions on that one. Okay, then we can spend some significant time on the next topic. Welcome to the Sophia and to Afi. Sophia, could you tell us something about yourself first and then Afi will ask you to so that the she code Africa contribute on is starting now. And these are two new participants to the Jenkins project who are part of she code Africa contribute on. They'll be helping us with pipeline help Sophie can you Sophia do you want to go first. I'll go Kevin and Michael. Thank you. So, um, I'm Sophia Kito, I am a Java back in developer at a startup in Nigeria called quality. I started programming just a few years back. And although I don't necessarily have a software engineer background, I actually did study professional engineering, but I was able to creep into the tech term into software. Due to personal studies, and today I'm actually a Java developer. So it's really exciting fun. I do hope to actually explore other aspects of software, like engineering team engineer lead. And software architectures and the rest but for now I'm just aiming to be a Java rock star. This happens to be my first open source projects that I am really excited. And I just can't wait to start. Thank you for the opportunity. Thanks very much Sophia. It's great to have you with us. And I think you'll find your Java experience quite helpful. We look forward to working with you. So, Sophia, would you like to be next. Oh, and Sophia, Sophia, you said you're from Nigeria right so I'll be sure you tell everyone where you're from, etc. Okay, hi everyone, my name is Afi I'm from Ghana. I am a software engineer with 10 table and also contingent for more custody. With my stack I don't really have a stack I've worked on Java spring. I really love string goods. So I've had experience with that in react. But currently I'm more on a Python flags project. Yes. So I'm also happy to be here. I'm excited to work on like this, this project is Jenkins pipeline project. Funny thing is, I have, like, I have failed builds with like after building with Jenkins so I really love to like go in and like learn how to contribute more in order to understand what happens under the hood. Yeah, and hopefully solve my, my build issues. Yeah, so I'm happy to be here. I'm happy to learn more. Great. Thank you. Well, and, and I think that's a that's the kind of mutual benefit that we hope all of us receive right is by you helping open source open source also helps you. We like that. We like both of those. Great. Excellent. So, so while we're here Kevin would you be willing to introduce yourself. Hi, my name is Kevin Martin. I'm just recently joined cloudbies as a technical documentation writer. I've joined the community team so I'll be working really closely with Mark to help get the documentation maintained updated and just constantly looking towards ways to help everyone out through Jenkins documentation. I'm really excited to be getting to work with everyone and I'm really looking forward to helping out with these projects and she code Africa and everything I just found out about this from Mark recently and I honestly got goosebumps hearing about it because it's really really cool really really inspirational. And I was able to talk to my girlfriend about it because it's it's something very close to her and which she does so she was really excited about as well so just really really cool really really awesome and I'm so excited to have you come here and join us up. So, welcome. Excellent. Thank you. Thanks very very much thanks to all of you. So what I wanted to do was give, give an overview of how this particular specific project will work, and I'd like to spend as much as 15 minutes on it the idea being, if I say something that causes you to have a question, please just unmute and ask the question interrupt me don't, don't delay don't feel shy about oh that's I didn't understand that Mark just ask right out. That way we've, if there's some surprise. So I think what we should first talk about is timeline, so that we've got a framework. And then we should talk about pipeline help or initial setup. And then the pipeline help specifics. And when do we meet next to talk about pipeline help or pipeline help pipeline. Yeah, talk about pipeline help. Does that seem reasonable to everyone. It does. Okay, so timeline, April five through I think it's about April 19 is the two weeks of. I put that in question mark because I don't remember the exact date. What, what we're calling community bonding. This is a chance to get started. To get to know each other understand how how we work together. How we submit pull requests, experiment and get to get our development environments ready. Learn a little bit about Jenkins. Those sorts of things in this two weeks because this is where we sort of warm up to each other be sure that we understand okay this is how we're going to tell each other how we're doing and this is. We're doing some problems together let's fix those problems, that kind of thing. Then we'll have a four week period from April something to I think it's April. Let's call it 19 again I don't remember the exact date I'll have to look it up to May 19. Where we actually do the project work. This is four weeks of four weeks of working on on the specific tasks. And then we've got a two week conclusion a wrap up period. And that's where right final reports submit final details, etc. Any questions on the timeline. Okay, so then in the initial setup, the community bonding period. This is where we have each of the each of our contributors so Afi and Sophia get started, right. And the get started, the best way that it has worked for me in the past to do the get started is each of you will create your own copy of the document that we use as a base, and you'll start making your notes in that copy. Making notes in that copy as you make progress. The idea is, make that document public. So that mentors can see it. And when there's a question you encounter a question noted in the document. Ask it in the slack channel as well. Now, it brings me to a good question, Kevin, I don't know that we've gotten you subscribed to the slack channel yet. So, Kevin, are you hooked into the CDF, the continuous delivery foundation slack I would bet not. No, I'm currently not a member of that slack channel. Okay, so I am going to do the invite. I think I can figure out how to do this so on my screen you should see it and somewhere here there's a way to add a member so Kevin I assume you're interested in this so I'm going to add K Martins at cloud these calm and invite. So you should get an email. This person looks. Yes, so you are a co worker. Good. As a member. Yes. Okay, so Kevin, could you check your email and confirm that you've received that invite Sophia and and Afi I believe this is how you were invited wasn't it, or did you have to register some other way. I got an email. Yeah, go to email. Okay, good. So this, then, oh yes, and Kevin, very good. Alright, so Kevin has joined. Welcome to the CDF slack workspace. And now that Kevin's joined, I think that should have put you in the list. And it did, Kevin. No, oh yes, there we are. Good. Okay. So very good. Great. Thank you. All right, so. All right, so we've got we've talked through a little bit of initials initial setup now a piece of this is this pipeline help document. And for that, I've got a drive folder that I've been using. This is fat fingers. She code Africa here. And so in this folder. Okay. Fold she code Africa folder contribute on folder. And Sophie and Afi, Sophia and Afi you both have access to that right. Yes, I do. Okay, so and then in the folder. There is the project document. Let's get a copy of this. And what you do is each of you should make a copy of that document. And it would be easiest for me if you put that copy or a link to that copy into the people folder here for you. So Sophia, you would put yours here in this people folder so that I can find it easily. If you if you'll share it with me even if you don't put it there, I'll put a link to it there. You know, Sophia and Afi have you have you each copied this document, if not, would you be willing to do it now. Okay. Oh good. All right, so here I'm going to, I'm going to paste a link to this document into the chat into the. I'm going to do this chat system where is the chat chat. Here we go. Okay, so here's the Google Doc in the chat. If you could open that and then do a file, make a copy. And then after you've made the copy, do the share to share it to me so that I can then put it into the right location. I'm going to put a link to it in the right location. And it would be best if we could do that now are you okay doing that now Sophia and Afi. Great. All right now I need to check my emails I should see a an invitation. Okay I'm not seeing invitations to your document yet. Be sure that what you do is you click the share here at the top right and add mark dot Earl dot wait at Gmail.com. Okay I see yours. Great. All right so open it. So here is the copy and I'm going to do file, add shortcut to drive, put it into my drive here. Jenkins, she code Africa, contribute on 2022. Boom, mentees. And this is office. Okay, so there we go. All right, so now what I'll see when I look at that folder is I will see there's a link of two office copy. Good. All right. And Sophia I see yours now. Perfect. So this is the same exercise. I'm going to make a I'm going to add a shortcut. Excellent thank you so what this will do is this gives you a structured place to start through a series of tasks in this startup phase and, and if you hit a problem, raise a note a note a question in the document and raise a question on Slack, and we'll discuss it, we'll talk through it. And Sophia. Great. All right, so now I should see the same thing here. When I look at Sophia's copy. Ah, good. Okay, so Sophia you put, you put yours actually in your folder. Is that right. Yes, I did. Ah, very good. Okay, so then I can just delete that because I can see the original copy perfect. Thank you. All right. Okay, so then what you'll do is go through those steps. And, and this is this is the place where the steps are imperfect. They are, I'm sure there are mistakes in them. I'm sure there are things that I just didn't capture. But what what helps is if you've when you've completed something, paste a screenshot right here. And, and that way it's okay I did it. And that's that makes it easier for the mentors to see all case progress is being made. And if we go through it then we'll, we'll get you these experiences and this this actually takes through quite a number of steps on how to do this exercise. Ultimately, we'll need to next week meet together to talk about which plugins, each of you should work on, and what your experience will be there. And now I think there's enough here for you to get started without us assigning you a specific plugin, are the two of you okay taking that approach where you'll just get started and, and let us know how you're how you're feeling. Okay. I think I've already started, but I just had some issues, so I had to post for a while. That's the problem that and and this is, we know that you're employed full time at other places and that you've got other things going on. This is not a pressure generating effort, this is just a let's help you get started and if there are things that surprise you share with us what surprised you so we can make this better. Right. Are there any other questions for me I think that covered all the topics that I wanted to add except when do we meet next. What, what would work for the two of you in terms of a next meeting if we met middle of next week. Would that be okay and our is this time okay or it'd be better for you if we met two or three hours earlier, or an hour or two later what times work for you. For me, from 3pm GMT that's like you CC. That's that works for me. Okay, great. And if we went sometime between 3pm and say six or seven UTC is that okay or is that too late. That's also okay. Okay. Sophia how about you. I think for me, I think from six UTC, 6pm UTC is okay anytime from, from, yeah, okay. Okay. That also works for me so from three or four or five, six is also not bad so I could just like quickly, like get home and then just like log in from here. So that also works for me. Okay. And Kevin for you. 6pm UTC okay. Yeah, that should work perfectly for me. I don't really have too much. Yeah, that should be perfect. Okay, let me, let me I'm going to stop sharing briefly while I look at my, my personal calendar be right back just a minute. Okay, so calendar here. That's not the right one. Okay, so 6pm UTC. Oh, that works well for me almost any day. That's great. Okay, so, so if we were to meet Wednesday at 6pm UTC or Tuesday at 6pm PM UTC. So Tuesday. Let's see. I need to look at the right week. Okay, Tuesday. Yeah, Tuesday or Wednesday, Wednesday. Do you have, do you have preference which of those two days is better. Tuesday. Wednesday is better. Okay. Well, so now, now challenge with Thursday be a better one for either of you Tuesday Wednesday or Thursday. Tell me, tell me which ones. Okay. And let me double check my schedule for Thursday so it's complicated there are four of us here of course it's going to be complicated scheduling so let's see. Let me look at my calendar again. Okay, Thursday at. Oh, okay Thursday at 6pm is documentation office hours Europe. If you're willing to join that meeting, I could just extend that meeting and we would talk about documentation in the in the first part of it. Or, or you could we could say we'll do our meeting at 630pm UTC. What's your preference. It's 630 be okay. Sorry, say again. Yes, it's that you be okay for me. And Sophia with 630 on Thursday be okay for you. Yes, it will be. Okay. All right, so let's let's put it then as. So Thursday at 630pm UTC. And I will schedule the session in the Jenkins calendar. I would normally invite each of you to that meeting from the Jenkins calendar that means your email address will be put in the calendar are you okay with that. Okay, so invite. All. Now that session time is a little is complicated for our, our project manager, nothing. Oh dear. I'm forgetting her name how embarrassing that is really sad. Oh dear. I forget, but our project manager is, is unavailable after sunset. And so we'll go without her for that session. And we may do a, an every couple of weeks a sync session with her, where I'll talk with her separately during her her daylight hours. All right. Okay. I think that covered all the topics I had anything else before we end for today. I don't know. Do we actually have like a direct mentor or you are a direct mentor. I'm, I am your direct mentor. Okay. So, so on this particular project, we use this, this, this project technique last year, and we mentored we may have if I, if I'm able to recruit additional mentors I'll be delighted but right now I know it's me. And I've been through this particular project, and it's techniques we found some mistakes we found some problems. And so I'm looking forward this year to learning having learned from those problems we're going to have a good experience together. All right, any other questions. None for me. Okay. Thanks everybody recording will be available on community dot Jenkins.io in about 24 hours. It should be 24 hours or less if I'm if I get all my work done for it. Thanks everybody have a great day and enjoy your weekend. Thank you. Thank you so much.