 Welcome, it's Jenkins office hours. This is the 20th of December be reminded that we follow the Jenkins code of conduct. So, did I was were there any particular questions you had or topics we should visit. Yes, so just a small question I had, I came here just to ask for the changes I did in my recent pull request as a part of my blog. So, I was asked by Tim that I'm missing an instruction where I'm supposed to tell the readers that where the Jenkins.yamlify is supposed to be and how you will use to configure it by changing the system message property of it. So, if I'm not wrong, if you want to check the changes that I've sent as a PR, you would have to build the website locally right. I, I, and I'm that's easy for me to do it takes just seconds. So let's let's look at that together and okay so it says missing where to put the Jenkins yaml file. Okay, so hang on just a minute while I start up the system to evaluate your pull request, and then we will look at it together if that's okay. Because part of it is I think we need to change the date of your of your blog posts because we've now will post it, we would post it today so we need to date it for the 20th. Yes, I think. Okay, yeah, and I can actually see just the Jenkins logo on the screen. Is that intentional. Okay, just a minute so let me, let me get the site running in development mode and okay the site is running I'm going to go ahead and share my screen. I'm going to put away some things that are here, and I am going to share my screen and show you what I see and then we can walk through it together. Okay, so sharing screen now. Okay. And here is the site. Quick blog, configure plugins with jcasc. Okay, so if you're a beginner at jcasc good good documentation link works, the overview link works, manage jcasc that works good. Okay. All right now the the introduction. Whoops, whoops, wait a second brief introduction. That was odd. Okay. All right so brief here's what an YAML file looks like. Now the and the change that Tim wanted was he wanted to alter in the load. Well so tell me where I should navigate to next to see the change. Okay, so the the suggestion is section is the latest change. Can I say that again? The brief introduction that I've added in this request. Okay so so all right so that now that surprises me then because I'm looking at what I think is the most recent code just a minute maybe I've made a mistake so let's go look. So what I see in the poll requests is. Okay, so add hyperlinks and small corrections, add info about the Jenkins YAML file. And so here is the text brief introduction to the Jenkins YAML file and brief introduction to Jenkins. So there it's added. Okay, so you're sorry. So is this the section you wanted to review? Yes, exactly. Okay. All right, so it says the Jenkins YAML file contains configuration of the Jenkins instance. All right, so there's a change. We like to use. Okay, let's see your blog post is in content. I'll just put the comments here. Okay, so we like Jenkins to be capitalized because it's a product name now where did that go. Where is my link that will let me make a comment. I'm missing something here. Huh. Okay, just a minute. Oh, because I'm in the commits view. I know I see. We want to approve that to run workflow. I need to go to files changed. And here we're looking for Jenkins space. Ah, there we go. Okay, this was the one I wanted to make a comment on. Okay, so prefer to have uppercase J there. And we generally prefer to do sentence per oh, yeah, sentence per line. Just to make it easier for us as reviewers. Okay, then the default location of Jenkins YAML is. So let's just capitalize Jenkins. Hello Zenab. Okay, so capitalize Jenkins. All right, then the default look. Okay, here it is. And this is the text that you are adding. The default location is Jenkins home Jenkins dot YAML from where it can be fetched. This right. Okay, so download your manage Jenkins make sure this file is saved there right and then let's change the system message field. Okay, and here you show a picture. All right now let's take a look at this. There it is. And the picture shows exactly what you were saying Jenkins system message. This Jenkins it. Okay, that looks reasonable. And now, now do you need the width of 700 pixels. What happens if that width is not there. If it is not there, then the image is a bit smaller in size and it becomes quite bloody, I think. Okay, got it. Alright, so, and it's the reason I ask is because I just shrunk my window to whoops, let me bring this up, I think I just shrunk my window to a rather common width. And it, it gives me a horizontal scroll bar. And I think that's because of that 700 pixel width. Just a minute let's go to 800. Yeah, so if I'm at 800 pixels wide, I've absolutely got a horizontal scroll bar there. Now why do I have. Oh, and that's because of the video here. Okay, that's probably then unavoidable, whereas at 1024 it's okay. Great. All right. I'm just checking I'm I'm I've learned that I need to check horizontal scroll bars. Okay, I think you should always avoid horizontal scroll scrolls, right. Well, always is is a little too strong just because the technique used here I like very much embedding a video that is so valuable and, and people understand it's a video by being large enough for them to realize that. So, so I think in this case you did exactly the right thing this this is a video and people need to know it's a video. Yes, yes understood. Okay, let's change the system message field, and there's the change. Oh, whoops. Now there's a, okay, so I think here maybe what you're referring to is we you tell them change the system message field but you didn't tell them to reload the configuration, which is a step that they need to do after updating the file isn't it. Yes, that's. Yes, that's a good point. So I'm going to just put a comment in here. I want to reload the existing configuration to apply the system message change, and then the next bullet now go back to the dashboard and you will see the system updated system message. Yes. So does does that make sense to you does that seem okay. I actually forgot to recheck it again and again because I was just working on it on just before the time of the starting of this meeting. And, and that I certainly I most certainly understand. Good for you for for doing this that's wonderful. Yes, I'll make that change for sure. So, so now you've extended your blog post that instead of just doing one change it also shows them where to what the YAML file is, how to change the system message. I like it that's great. Yes, so I'm not sure but I hope that this is exactly what Tim was pointing out. I was suggesting right. I'm going to read his comment again together just to be sure. Okay, so, and let's make the text big enough that my eyes can read it. So, Tim said the field. Okay, so here's one he say he's suggesting this note could be removed. Do you mind if I remove that note. Actually removed it already in this current PR. Oh, you did. Okay, so then I should be able to see that I should be able to see that that's. Oh, it says outdated got it. Okay, very good. All right, and then this blog is missing where to put the Jenkins YAML file, and there it is and you've got it so I think you've done it. I'm going to mark this conversation as resolved. I think you're ready if, well actually before I do that let's cancel out of that. Cancel. So, if we want me to do the review still okay. Would you be okay. Just a comment. If I applied these changes because I think I have permission to do it if you don't mind that I apply them. Or would you like to be the one who applies them, and then you can do the step to rename the files from five dash 15 to five dash 20 because I think we're ready to publish this blog. If you don't have any problem. If you don't have any problem to do a change that's fine for me. Oh, and I certainly do not if you don't mind I'll just go ahead and here and here's what we'll do is we'll, we'll use go to files changed. And we will add those suggestions to a batch. And then we're going to commit those two suggestions. Okay. So the next step is we need to do a rename and now I could do that or you could do it. Do you have a preference. Um, so here I'll, one of the complications here is, oops, just a minute so get poll. Oops, not possible. Okay, 361. Okay, so if we look at the files that changed, we see that the file name has five dash 15 in it. And that was correct when we were at about the 15th of May what we need to do is rename them to be for today because we would like to publish today. Yes, exactly. And so what I would suggest is we do this, do a get move of those two files. Let's see that was the a doc we also need to move the image. And then we'll need to go inside the file to change those images, such file. Oh, those were deleted. So it's the one that I need is. Okay, now let me do that merge just a minute. Okay, and the get log thing. Okay, so what we have here, minus N. Yeah, I think that actually maybe enough we could just leave the other images exactly as they are. Let's see if it works. Okay, it's ready. I won't help because it's no longer at 515 log. Note that the date shows May 20th there that's correct. And here we go, and it has that picture in it and that picture in it. Very good. So this looks reasonable now one of the things we didn't check was we didn't check the open graph image. We had added an open graph image right. Yes, I have added now we need to find that so that's this file right here. So if I paste that file. There it is. Oh, nice. I like that. Excellent. Okay, good choice of image well done. I don't know why you up. I'm not even. Yes, I can see it now. Okay, how is it. Great. Okay, COVID-19 configuration as code and you excellent. Because you said you should have some human face in it to attract more attention. That's right. Right. Exactly. And I think I think that is exactly what what we want is we need. It's clearly Jenkins. And it's clearly got a human being who's working on it and welcome to COVID-19. I love us. We feel so lucky. Okay, so. So for me this, this looks, this looks like we're ready. Everything seems to be rendering correctly and your biography here is correct. And okay your GitHub link works. Yep. And your LinkedIn link. Let's see how it works. Good. Okay. I think we're ready to publish. Yes. So, so I'm going to push this one last change. And we'll see if, if it will allow me to publish push it to your branch. Do I have to also do that change of reloading it? Yeah. Yeah. Yeah. You told me that the, in the recent PR, I'm missing that step in which I need to read out to users. Oh, and I thought we had merged that. Let's double check. So let me see. So is my feedback visible here. Actually, if we look at the commits. Okay. So here is minor updates. So it included. The. Awesome. So that's, that's already done. And, and now. The one change that hasn't been done is. This one. But it appears. Oh, nope. It rejected it. Update deny updating. Okay. So we're going to have to do it a little different way. We're going to have to do this. We're going to have a branch minus, minus delete. Sorry that you're having to watch me do get things. That's not, not very interesting. Okay. For me, it's interesting. Okay. Honestly. Mark, when are you going to take me on a lesson on kids? Well, I'm happy to give lessons on get any time. I'm just not sure how useful they are. Oh my God. Okay. That's, that's. Well, and certainly I admit that I find them very helpful. There are things that for me are just, oh wow, why did I know about that so long ago? Okay. So get log. Okay. So dirage if we're lucky. I will now be okay. Yes, there it is. This shows us the rename from 15 to 20. So now if we say. Get push. Maybe not. So you may have to do this dirage. Oh no, it's. No, it won't, it won't let me do it. So sometimes I'm given permission on, on people's repositories and sometimes not. So you'll need to do the rename. Of that. That file. Do you have access to a, could a computer so that you could do it now we could, we could watch you go through it and then we could get this merged. Sure. So what exactly do I need to rename? Yeah. So what we need to do is we need to rename. Let's see. Let me do it this way. I can push the branch. Origin. I'll push the branch to my, my repository. And that way you can see it if you need to look at it separately. It is where, where'd it go? Where's the branch? Oh, there it is. Okay. So. All right. So I'm going to paste this. Into our slack chat channel here. So that branch. If we click the, no, that's the poll request. You silly thing. Okay. That's not quite what I need. I want, no, I do not need to open a poll request. I want my fork. And in my fork, there should be a configure plugins with JCASC. And there is the commit and there. Okay. There is the change. So this is the thing that you need to do for yourself. And I could give you commands to do it so you could pull it from mine, or you can just do it yourself. It's, it's a pretty easy change. Yes. I'm going to, I'm going to stop sharing. If you want to share your screen and you don't mind being coached by me remotely, I am happy to happy to help you do it. Yes. I would love to get, love to get coached by you. So can you see my screen? Yes. So from your terminal window, you'll need to go into that repository, do a get poll so that you, so you, you receive the latest changes. So what this does is brings all of the changes that are on, we're on GitHub down to you. And now, oh, that's very nice because right on your screen, two lines up from where your cursor is blinking is exactly the text you need to, to, to copy. So if you, yeah, double click that, the path of that file. So what we're going to do is a get space MV. So a get move space that file. And then we're going to, we're going to paste that file name again. And then we're going to edit it to have a different name. So instead of the 15th, it's going to be the 20th. Exactly. Now hit enter. It was that easy. Now get commit. Yes. So, prepare to publish 20th of May. Yeah, perfect. Yeah, that's great. Yes. Now get push. Yeah. I'm a heroically patient person using username and password authentication. That's very, very. I much prefer private keys. Yes, definitely. Okay. Great. And so we see on your screen that the, your push happened, right? Because there it is prepared to publish. And if you open that, you'll see what it, that it shows I moved a file from one, a file from one name to another. From 15 to 20. Yes. And now about five minutes from now, we can come back here and check and see that the, the continuous integration job completed evaluated it. And, and then I'll be able to go ahead and merge it. Sure. So let's wait for that and continue with the meeting. Excellent. And congratulations. This is great. Thank you so much. Thank you. Thank you. Thank you. So can you hear me? I can hear you just fine. So are you okay if I take over sharing? Yes. So I'll just stop sharing now. Great. All right. So. Okay. So, so let's, I guess we should, what we should probably do is let's get the, the continuous integration job visible so that we know when it's done and we can merge. Okay. So here they are latest pull requests. And there's the one building. Okay. Okay. So I guess it's probably got. Five. It's got at least seven or eight more minutes to go. So it's six minutes in of 12 minutes. All right. So we'll, we'll come back and check this pretty soon. Very good. Now I apologize. I failed to make any notes in our office hours today. So I have to go for just a minute and let's make some notes on this. Okay. And today is. 20. Also highs in up. How are you? Hi, I'm fine. Thank you. And you. I'm doing really great. Thanks. Great job. I can't wait to go and read your blog post. Yes. Please don't tell me if any improvements are needed or not. Thanks. Sure. Thank you. Yes. And also please watch the video. Okay. I'm going to go ahead and do it. Mark is also put it on the YouTube channel. That would be really great as well. All right. So, so one topic then we had today was reviewed. Deer. Log post and merged it. And that's that set. I think we're ready. Zina, are there any topics you wanted to bring? I have one more topic. Let's call it Mark's news. Okay. Great. Until the end. Anything else? Anything that you wanted to bring Zina. I just wanted to ask about. Currents. Documentation. Task for Jenkins. What is it? What are the currents? Work that we need to do on Jenkins. Don't give there's anything I could pick up or probably link. Where I could see. Yes. Excellent. So, so how about, how about let's take a look at. Let's take a look at some different candidates together just to see what we've got available. So if we look in the issues list. Let's look at first. First one is well, let's see if we look here at. This one might be a very good one. I don't know if you're willing to make. Guesses on. What the terminology this one would probably be quite. Quite controversial and take some time to get it all the way to done because the discussions are still happening. So maybe this, maybe it's a little early yet for that one. Okay. So let's keep looking here. This one is in progress now. Just a minute. This one is 43 69. And that should have already closed it then. Okay. So thanks to Cynthia for, for doing that now. Okay, so here's a good choice. Now this one. Have you been able to successfully. Build the site on your computer. I think you have, right? Yes, I have. Okay, good. All right. So then, then here's, here's one that, that will take some more thinking, but would be quite a help. It's, it's. Okay, Josh Soroff here had the question. Hey, what is a Jenkins long-term support release? And what he went looking for was, oh, here's the change log and the LTS upgrade guide. The glossary doesn't mention it and user. So he thinks that this is the right place to put it and describe. Oh, he doesn't think this is a, this is the only place to put it. So then it's, he's looking for, okay, where should it go? And it's all like suggestion is, hey, we should reference it from the installing section, Jenkins section release lines or downloads. So if you want to take this one, this would certainly be helpful. Okay. I'm going to go through it. Could you drop the link to the issue? Yes. There's, and, and let's, let's look, and pretty much any issue in this list that looks interesting to you, you're welcome to do. If you've got any experience with, with engine X as a reverse proxy, this one, but this is engine X as a reverse proxy is relatively complicated. So, so, but, but it certainly if you've got access to a Linux computer, it's an interesting way to learn about reverse proxying, or do we have good first? Oh yes, here we go. There are also these that are called good first issue that we would love to have help on. So pages that need migration. Wow. There's a lot. Yeah, so good first issues. At this location. Oh, that's so hard to read. Let's just do it like that. Those are our excellent candidates to, to help us out. And especially these redirects are relatively quick to do the migrate ones are not, there's a lot of work hiding in, in these migrate ones. Yeah, I could tell because I worked on some of them before I said it. Jenkins one is perfect. Exactly. Updates and done. Now this, yeah, this one, if you want to do a little bit of work in code and layout. This one is certainly an interesting one. You can see what, what Oleg's describing here. You see over here on the far right. It does the layout wrong. Right. And now, and yeah, so, and there's a suggestion that. Well, it says that it's resolved it. I don't know if it has. I don't, I'm not persuaded it has. So let's. Are there any Jenkins events that are multi-day right now. No, all the events are single day. So you'd have to fake it. You'd have to create a multi-day event to see if it's actually fixed. So. Zina did that is, is that enough help or would you like further? Okay, great. Thank you. Okay. Then also there's something I wanted to discuss with you. There is an upcoming event. Oh, sorry. Let me just get a little bit more information. It's on open source day by. Sorry. Open source day is just a one day workshop. And they're looking for it's to encourage women in tech to contribute to open source, small women to contribute to open source also. So it's a one day event and they're looking for mentors. These are engineers that have open source experience that could take hands on session. And that one day event to show. New contributors, how they can contribute to open source, probably how to submit a pull request and things like that. Maybe solve a minor issue on Jenkins. They're also looking for projects that it could use for the workshop during that one day. So if Jenkins is open to. Probably have some issues that you could work on. And Jenkins would like to be part of the project that you could use for the one day. Jenkins would like to be part of the project that it could use for the workshop that they also. And if they are. People within the Jenkins community also that would like to take on session. And that the workshop, even new mark, because I can see how good you are with it. And I know that's like a very, very important topic. When it comes to contributing to open source. So I just wanted to raise that. The we've not been fully finalized. They actually just sent an invitation to us also. And asked if. We had organizations. If we could refer organizations that would be. Interested in participating. I'm not sure of the date of the event yet also. We'll need to have a meeting with them to finalize, but if it is something that Jenkins would be interested in participating. I don't know. I don't know. I don't know if it's for any member of the community. I could share more information once I get. Info on it. I'm confident that the Jenkins project would love to present. If you don't mind a present. Thinking like a 30 minute or a one hour presentation. More than happy. We've got several people who could do that. Me. Kara Delamar. We've got a number of us who could show, Hey, this is how you do this. Now, now the. The, yeah, the date will date will matter. So, yes. I thought so too. So I'll try to communicate with them as soon as possible to get the date. Hopefully there's enough time to prepare. Because I actually just got the information also yesterday. So once I get more information. I'll communicate to that course. Great. Yeah, there, there was a session that Oleg presented. At code for cause India. On, let's see if I can find it now code for cause. Maybe it was the deli meetup. Just a minute. Where they did past events. See all. Okay. Let's see if I can find the link. I can just paste it there. And you could see how Oleg did it contributing to falsely contributing to open mainframe. Yes. So this is. Contributing to. Where is contributing to Jenkins. Come on. Well, that's why we have source engines contributing to Jenkins. Video. For cause. So this would give you something you can look at. See, here we go. All right. So this is it. And if I just stop that and I'll paste that in here. This is a one hour, one hour session that Oleg Nanashiv did. And, and he's, I can't speak for him, but I've done those kinds of sessions before and happy to do them again. All right. Thank you. All right. Details as they arrive. Oleg's contributing to Jenkins. Session for code for cause. An example. Okay. Thank you. Anything, anything else. No, nothing else. Okay. All right. So the last item, and we're about to reach our end of time. I have some news to share. So I on June 9, or June, yeah, June 9, 2021, I will be donating a kidney. Wow. To my nephew. All right. So I'll be out for up to eight weeks. Recovering. I'm looking for this is the place where the two of you. Help. To cover. My responsibilities in Jenkins. In various ways. So Zenab, for instance, I hadn't thought of this before, but if you or if Deraj were interested in. For instance, creating the weekly change log. For Jenkins. That's a, that's a task that I do that I think could be. Could we, I could show one of the two of you next Thursday, for instance, how to do that if you're interested or both of you, because we need more people who are able to do it. Okay. And, and it's, yes, it's, oh, Deraj, you're interested as well. Yes. Yes. Great. Okay. So plan for a demo next week then. Excellent. Because. We need to, we need to do it and it's, it's really great to have, have help people to do it. There are other, there are other things like that where we've got the Jenkins contributors summit. Coming June 25th. And I would normally coordinate the documentation track. But I won't be available. So we need someone else to coordinate the documentation track. Okay. If you, if you could share, I don't know, probably in, I don't know if there's going to be time in the next meeting, more details on what will be required for someone coordinating the track. Yes. Great. That's, I would, I would love to do that. So I'm happy to share it next, I'm happy to do that. Thank you. Next session and we'll, we'll discuss. I'll be discussing these also during the next, the next. Asia and Australia office hours. So next Tuesday, India time. That's, that's the middle of your night. So there is no expectation you'll be there. There's no expectation you'll be there. There's no expectation you'll be there. So no, no assumption that anyone in Africa would ever attend it or in Europe. It's, it's really much too late. That is. Yeah. All right. So, and I will be sending marks, sending email messages. Soon to the docs mailing list. That described this so that others will be aware of it as well. Thank you both of you for the interest. Any other topics? No, that's it for me. Just a small thing. That is how are we going to. Analyze the videos that we have added on YouTube. Oh, oh yes. So that's a, that's a very good question. Let's, I can show you how I do it. I switched to the, well, actually let's even do it without switching. Let's just go look at the Jenkins playlists. And here, let's see where it was, what was it called? It was. I'll have to look at. Maybe I do have to switch to the Jenkins account because I, I certainly will, I know what I can do. I can find it in your poll request. Can't I. I just need the URL for the video and then we can look at its data. So the URL for the video is right here. Yeah, that's the wrong one. The URL for the down, down, down. Oh, there it is. Thank you. That's the one. Okay. So now let's go here. And stop that and replace it with. This. Okay. So what we see. Oh, this is great. I haven't even published this thing yet. No blog post and it's already 231 views. Yay. We've, we've done no promotion of this. And it's already 231 views. Well done. Thank you. So that that's actually quite impressive. So okay. It's only been published for five days. And nothing promoting it. And still people, people have viewed it. Well done. Very well done. Wow. Okay. So. Any, any other questions before we call this session done. I'm sorry, just one quick one. I just wanted to ask if any of the mentees. For contributor and reached out to you. They did. Yes. Absolutely. I've, I've had a, I had a mentoring session with Esther, a JDK afterwards, and I talked with Lucy Karimi afterwards. So very, very glad to hear from both of them. That was, that was wonderful. Thank you for referring them to me. Okay. Cause Lucy Karimi had some complaints. I just wanted to make sure there was no. Yeah. Yes. And, and Lucy and at least she asked me clarifying questions and I gave her answers and she said, okay. I didn't attempt to resolve her concerns any further. I left that. I figured you'll, you'll decide how you want to handle those things. But I gave her my, my thoughts and shared my, my comments. Okay. Thank you. All right. And, and dear Raj, I think we're ready to publish your blog post. Yeah. So CI job is complete. Now I'm going to do something different here because of this. Squash merge me and the number of commits on it. What I'm going to do is instead of merge poll requests, I'm going to drop down this list and do squash and merge. This will turn the 15 commits that were used to create this into a single commit. And one of that is then the image we will only get it once in the, in the net instead of having it several times at different sizes. So squash and merge. And now we get to decide what text. Yeah, I think we're just going to do it like, I assume you're okay if we just have the commit message be like that. That looks great. All right. Confirm squash and merge. Oh, and Tim just approved them. So that's great. Yeah, just few minutes ago. Excellent. So live development, very good. Anything else. Nothing for me. Nothing from my side as well. All right, recording will be posted in probably half a day or so. Thank you to both of you. Bye. Bye.