 Awesome. All right, welcome. It's the 7th of June. This is documentation office hours. Remember, we abide by the Jenkins code of conduct. So, dear Raj, one of the things that I was hoping for was that you'd be willing to try another time to create the weekly changelog. Oh, I'm going to turn off my camera. We don't need to watch me. Are you interested in doing that again? Or is there something else that was more important to you for us to do tonight? From my side, I'm comfortable with anything that you think should be of more priority. Well, so I would love to do one more time to run the weekly changelog and have you be the person who submits it. Because that way, if I'm not available next week, or the weeks after that, we could still get a weekly changelog. I, when I brought this to, when I brought this to the Jenkins governing board, there was some skepticism while we're not sure that a, someone who's not an experienced Jenkins core developer can actually maintain the create the weekly changelog. And you were great proof last week that yes, somebody can. Yes, definitely. Very good. I'll drive a risk. Definitely. Okay. So if anybody could do it, somebody with some talent. Well, thanks. So should I share my screen? Yes, please. If you could. And is there any background noise? Even if there is, it's worth it. Let's just go ahead. That's great. You just leave your, your, your microphone on and we'll, we'll talk to you and ask you questions and let you know while you're sharing your screen. Awesome. So I think you can see my screen. I'll just find this right now. So we are at Jenkins core directory and we want to run the Docker command but before that last time we were. So are you, are you up to date with the current version that's remote on that's on the, on Jenkins? Exactly. So last time we did that, we ran into some problems. So you said that there's a file in which you need to change the version, the latest version. So from that, it will be fetching all the PRs. Right. Well, actually, even before that your Jenkins core, the, the, I think the directory in right now is the Jenkins directory. Right. So here, if you could do a Git log. Let's see what, where, where it's at and let me double check to compare that it's at the correct location. So when I look at mine, Jenkins core is. Okay, so you are. So you, it looks like your copy, your local copy of Jenkins core needs to be updated. And so what you're going to need to do is quit out of the, quit log and do a Git pull minus, minus all. Okay. Now you need to do a Git merge upstream slash master. And there's actually another command you could use instead, but this one will now bring your local copy current with what's on upstream. And now if you do the Git log, you can do something about SSHD core. Yes, it does. Good. Okay. So your, so Jenkins, Jenkins core is up to date. Now, if you'll, if you'll do it one more step, do a Git space push. This will push your merged master branch to your fork. You don't strictly have to do it, but it's, I like to do it just to make sure that you do it. Now you have to remember you're using the password. Super. Okay. So, so now your local copy of Jenkins core shows all the latest changes. So now you should be ready to run that Docker command. Let's see. This one. So this will take up all the PRs that has been. Right. It should. Oh, no. What's it saying? Okay. No. Interesting. Okay. That seems like the correct, that is the correct version. So why is it saying no URL specified. Docker run. Curl no URL specified. Okay, we may have to have you stop sharing. Let's have you stop sharing your screen so that you don't show us something we shouldn't see. And then show. Now on your local command line, instead of just the Docker run, put the word echo in front of it. And see what it's outputting as your GitHub underscore off. It should be a username. I think it usually a username, a colon and a passphrase or a token. You know, so it should look like it looked like a username password. Does it. Dash V and then a location of the workspace. Dash dash. And then location. Okay, so let me. You may not have a value assigned yet for GitHub underscore off. But we ran this last week. So I mean, it worked last week. Hmm. So you may need to define the GitHub underscore off environment variable. And let me double check while you're doing that. I'm going to double check just to be sure that GitHub isn't down. Because there actually are times when, okay, it's, it's working okay for me. So I think it may just be that you don't have a value for GitHub off. Okay, great. So now you can start sharing your screen again. I clear your screen so that we don't see your GitHub credentials. We don't want to record those. That's none of our business. So I cannot even go up now. Oh, okay. So, well, so the, if you look in the, if you look in the read me file of the, of the, the generator, it's got the exact Docker command you need. Yeah. In core changelog generator in the read me.md. Just exactly that one. Well, or, or the one above it, you need the one. That one is fine. You just have to remove the number off the end. The one that your icon is over right now is the one. Yeah. Yes, that's what we're looking for. Good. Okay. Okay, now that's a fun one. A parse error. Hey, could you do an echo? Dollar sign Lang. Space dollar sign LC underscore all it's capital. It's all uppercase. Dollar sign LC LC underscore all. And I think that's it. Yeah. Those two enter. Ah, yes. Okay. So, and they might be okay. But could you instead do. Export space Lang equals. En underscore. Capital I am dot. UTF dash eight, or the UTF dot eight days. That's eight is all caps. Yeah. And let's see if that helps. English has spoken in India using UTF eight characters. Let's try it. So I'll run the command once again. Yeah. And now your arrow key should work. Okay, that's better. So one of the problems I had found in the past. Was that that Docker image for some reason. Wanted did not have UTF eight as its character set. And so I think that's what you just did is you've now used the correct character character set. Good. Okay. So we have the template. Yes. So now we go to the site. Mm hmm. And open up there. Right. Let's edit here. What do you think using nano? We had some problems last week. Yeah, VS code really surprised us. So you're welcome to experiment with VS code, but I think, I think it's more aggressive with its formatting of YAML than we're ready for. So what do you suggest? Where should we get the files? Yeah. So, so nano is great if you're comfortable with nano, whatever editor you're comfortable with. This is change log file that we just generated. Right. We move forward. Yes. And this is the retail file that we want to generate. So, so, yes, please. Now, I am not, I am not a nano power user. So this will be a very interesting experience. So I would assume you move down one line and drew, do a control K a bunch of lines to cut the text. And then you go paste it into the other file and then we'll edit it in the other file. Oh, you won't let you, you probably won't let you cut will it? Oh, no meta a, there it is. Yeah, look meta a mark text. Oh, this one or meta six. Yeah. So meta six is copy text. Right. So meta a to market and then meta six to copy it. What is this meta? Oh, meta means the alt key. Sorry. Yeah, that's a, that's an Emax damage. Yeah, but, but your technique that you're using now should be great. Now, if you can switch to the other, the other buffer and copy that with your editor. We're going to paste it. Yeah, I think so. Now, where are we in this editor? This, this is okay. So there should be a very long file. There should and there isn't. Okay. So maybe it's time to close this. Let's go back to VS code. You're comfortable with that. Let's use VS code and we'll figure it out. I mean, let's not put you into some strange and bizarre editor. Let's get you into, into something that's comfortable. We are not able to catch the difference. Yeah. Yes, good. Well, but, but I think let's just see if we can figure it out because ultimately you're, you're comfortable using VS code, right? And lots of lots, many, many users edit with VS code. So if VS code is going to do damage, we want to know how, what we need to do to make it work. This is the. Yeah, this looks great. Now we'll probably even after you get the file in the editor, we'll probably want to go check your Jenkins.io that it is current. And yeah, you can, yeah, you don't need to save that modified buffer. So here from your shell, we want to go to the Jenkins.io directory. I'm sorry. Yeah, so do a get pull minus minus all. And get space status, we'll probably want to just throw away local changes for the moment. Yeah. So I think what you want to do is say get space merge minus minus abort abort a B or T. All right. So now get space reset space upstream slash master. Oh, now that's interesting. Why would it have a stage change? Okay. Get get status. This is interesting. Okay. So get check out dash dash dot space dot. Okay. So I'm sorry. You need a space after the dash. Yeah. Enter. Now do the get status. So what we're trying to do is get this to, to match with upstream. Now we want to check out a different branch. Let's check out master. Get space check out space master. Okay. So get reset. Minus minus hard space upstream slash master. So what we're going to do here is make your local copy of the master branch exactly match upstream. And now do a get log. Okay. And yes, okay, that's good. So now. And now if you just say. What this is going to do is make your, your private, your, your personal copy, your fork match with upstream. Good. Okay. All right. So now we need a new working branch. So get check out minus B. And change log dash two dot 297. All right. Now we're ready to go back to VS code. Okay. So there's this is the prototype. This is the weekly dot YAML that's on its left also. Oh yeah. Very good. Yeah. So what we want to do now is take the, the text that's in the top and do the same edit we did last week to, to transform it into the bottom. Oops. That you just move the comments. You want to put it after those comments because it's a new one. Exactly. Right. Right. And because that looks like a number, it needs to be in quotes. So it needs to be either single or double quoted. Yeah, double quotes are great. And then the release date will be it's tomorrow is the eighth, isn't it? Yes. Yeah. So today is the eighth for you. Yeah. So, so the eighth is the release date. All that work is that now we need to start working on making these messages, right? Exactly. Right. Very good. Okay. So it says, is ignoring this. Post change one. Raise conditioning class loading. And for me, that's a good enough description. Yeah, I would take that. Again, this is me that, that admitting, I know who Jesse Glick is J Glick is a very, very frequent author and he writes very, very well. So whenever I see Jesse Glick and Daniel, I just need to close my eyes and just. Exactly. That's, that's been my approach anyway is when I see anything from Daniel or from Jesse, I just close my eyes and accept what they've got. Now this one does have something to teach us here. You see the characters surrounding the word linkage error? Yes. That sort of backwards quote. Those need to be transformed into an HTML code tag. So a less than code greater than. Similarly, how we did last week for more method. Yes. Yeah, you're right. I didn't remember we've done that last week. Yes. That's right. Hey, ready to go to the next entry. So this is a bug. And first one was also a bug. We should be at the top above RFA. Yeah, I don't remember which order. That's a good question. I'm going to have to look at the style guide to see which order the style guide says. You keep going and I'll look up the style guide. Yeah, okay. So this is one where we may want to beg for mega Kristen's help. I actually like the PR title better than the, better than the proposed changelog. It says do not change fonts when artifacts are shown as, I might say it as a tree. I almost like the PR title better too. Yeah. So, so I would keep the R title. It's more of a sentence. Yeah. And it's also, I think it's not. Yeah. Just like, it feels weird to say fix here, but yeah, I don't know. I kind of like it. Yeah. And now one of the things you need to do, there's be sure you end with a hard stop. With a period. Great. So there's two. The style guide. While we're picking at pros in the previous one, remove of comments, digester from core. I think the of could go. Oh, yes. Yes. Okay. Yes. So which one I suggest. She's, she's saying, keep the, keep the proposed changelog, remove comments, digester wrapper, and delete the PR title. Oh, now whoops, there was one item there. Did you see the developer colon? We want to retain the developer colon because this is a developer specific fix. And that's the end users won't perceive. Is this. Right. And that one you can tell because the category RFE. Or the category is developer. Now there's an indentation change there, dear eyes that you may need to correct. No, it's, oh, yes, it's different in your destination buffer than in the source. Interesting. Is that visual studio code doing that for us? Yes. Yes. Okay. And then. Ah, okay. So there you have a block indent and outdent facility in visual studio code. Nice. That looks right to me. Okay. So developer remove comments, digester wrapper from core and dependent. Yeah. So this is bumping. And for this, you suggested that some of the details regarding bumping from this version to that need not to be shown to the users. So we need to search in the file, whether this specific thing was previously added as a comment or not. If it was added as a comment, then we put it as a comment again as well. Right. Exactly. So look, look for this one. I think this one was mentioned. I think SSHD has been mentioned very prominently recently. And so I think this one will need to be mentioned. Yeah. It has been mentioned. Well, keep looking because that one is actually, I think different. Yeah. Bumping. No. This is the recent one. Oops there. Yeah. So, so we've done one case where we didn't mention it. And scroll down, down one. Oh, there it is. So this is, I would keep this one because it's been a source of a number of recent changes. So I think we should keep it. That's what I would take it as is just take the PR title. Let me double check just to be sure that. That's PR 5547. Yes. Okay. Let's take a look at it. Yes, we've got several approvals. So let's include it. Okay. Good. Okay. Okay. So I think that's a good one. So syntax. Would it be better to say bump SSH, or SSH decor from 2.5 to 1 to 2.70 in Jake and CLI? Oh yeah, good. Yes. I think in Jake and CLI should come after the release numbers. Right. Do you agree? This looks good, right? Yes. Okay. Just copy the comments. Now we have to do the investigation. It's, it's, they've used bump before that's a, a generated word used by dependabot. And so we've usually just left the word bump in there. Okay. All right. Now the challenge. I know some people that probably bothered by it. But I think that's a good one. Do you realize the challenge now is to figure out what the diffs look like to see if it has changed the file dramatically. Can you save that file and let's go out to a command line. And do some, some differencing. So do I get space diff? I think I need to do this. That looks good. Yeah. So we would, it would be nice to get rid of that trailing white space, but it doesn't. Yeah. That's a good file. So that's a, that looks like a big win. Suggesting to. There's no extra space. Interesting. There's no extra space, but it's, have you saved the file? Yes. Huh. Try to get diff again. Let's see. Oh, okay. Now it did the rewrite. Okay. So now how do we teach visual studio code. How do we do that kind of massive rewrite of the file? Any, let's see, maybe you do some searching. I'm going to do some searching. There's probably some configuration. VS code. Not rewrite YAML files. Oh, wait a sec. There was, it said something about turn off. Avoid reformatting. Save. Oh, oh, look, there it is. Command shift P save without. Command is probably alt save without formatting control KS. Okay. Now that it's saved it, let's try that diff again. Well, I guess I guess we could always save just the say is copy the file to a separate location, right? Okay. Reopen a fresh copy of the file and copy just the last block. And then save without form. Sorry, what about using what? Control instead of all. Control instead of all for command. I think it's usually control. Ah, could be. But I thought that when, when Deraj did it, it was just trying to do that save without formatting again. It may be that the files already been modified in, in memory. So it was. One shift. Right, that one. Because what did it say command alt P. Usually it's control. Well, and Deraj is running. Mark said to do all. Yeah, that's so am I. So my proposal. Let's have you copy the changelogs weekly.yaml to a temporary location. And reset it. And we'll just bring it in from the copy. Yeah, put it someplace safe. On your desktop or wherever's comfortable. And now you'll go to your command line and we're going to, or you could use VS. VS code as well. We're just going to ask gift to reset the file. So from the command line, it would be get checkout. Dash dash space dot. So do you want me to do it? Yeah, terminals easiest for me. I know it can be done with this VS code as well. I just don't know how to do it. So get checkout. Space dash dash. Space dot. So what that says is please check out any files that are currently modified and make them match what's on the room on the, in the repository. So this is basically a reset. Now, if you do a get status, it should says tell us that nothing has changed. Now we go back to VS code. Reopen that file. It may have already detected that it's changed. So you want to open the same file on VS code. Right. Open the copy and we'll paste its contents into the, into the original. And then, then when we save the original, we will be sure we have you save it with file save without formatting. Hey, now let's try that file save without formatting. Oh, yes. Okay. Now there's still maybe a formatting problem here because I think so now let's do a make run and see what it says. Because I think the indentation there is still a little surprising to me. Sorry D Raj that this is so complicated. Thank you for being willing to do it. Yes, that's my pleasure. Last time, she said to me that there should be some, there should be RFEs between major bug and another type of change, which was like there has to be some great colored changes between the two red color changes for visual easiness. So let's see if there are any available. Yes. This one, I'm not sure there will actually be any available. So that's, that's why we want to look at it visually here. So open it up in your browser and let's see what it shows. Okay. Go back to the terminal window. Let's see if it's reporting an error or some surprise. You can still hear me. Can hear you. Yes. Well, it's certainly, it's doing a lot of work generating this, the website. So, okay. And here comes the site. I was ready to go through the last week's video on YouTube, but I don't think you uploaded that, right? Oh, didn't I? I thought I had. I apologize. I will, I will get that uploaded. I should have done that. I uploaded two videos earlier today and must have missed the, that one. I will get it done. Yes. I was trying to practice on time. So that's why I was looking for it. Right. Well, and that would have been a great help if I'd done what I should have done and, and had it available for you. Oh, there it is. Nope. You're right. I had not uploaded it. I see it right there. Okay. And this one is showing us that we need to make that change to that file. Okay. Notice that it says 2.296 when you click the change log, I bet it will show us a change log for two, only 2.296 and we just wrote 2.297. Yeah. So now it's generating the change log. Or did it fail? So switch. Oh no, it's coming still. Okay. Right. So it's showing us. 2.296 and we need, because that's the most recent actual release. So we need to. Trick it by show having it show us the next one by changing one of the files on the disc. You remember which file that is there's a file named. Version something or other in the content underscore data. I think it's underscore temp directory. Yes. It's very slow. Right. Would it help if I just stop generating the website for now? It will because we'll need to stop it anyway. We'll have to regenerate it after we update that, that value. Time has also stopped. Well, but it's still, it's still delivering audio for you. It's still seeing the screen. So. No, the file that you're saying is. Yeah, I thought it was, let's see. So. Then data. Just a minute and I can, I can get you the exact name. It is content slash underscore temp, not underscore data. So content slash underscore TMP slash latest core. It's T X T and it's T M P rather than T E M P. And the core there will be, has a capital C in it. Well, and you could do, there's another way you could do it. We can, you can just say echo space. 2.206 202.297. Was that what it was? Was the number version we're working on? Yes. And it's not slash content, but dot slash content. And now if you press tab there, it should complete it for you. Okay. Now do the make run again. And let's see if it. If it will, let's show it to us this time. Go ahead and type make run. Oh, okay. It's very slow now. Maybe you want to stop sharing your screen. That may make your computer much faster. Why don't we, let's have you just stop sharing. Because you know what to do now. Yes. So let's just have you stop sharing your screen. Okay. Let's go ahead and type make run. I'm having some delay. Oh, okay. I'll type make them now. It's very slow now. Maybe you want to stop sharing your screen. That may make your computer much faster. Why don't we let's have you just stop sharing. Okay. I'm going to stop sharing your screen and. That way you get. Your computer performance back. Stop. Let's see. I'm going to stop your sharing. Yes. Okay. And then I'll stop my share. Oops. I still see your screen shared. So it didn't appear to have stopped your sharing. Okay. You should see a blank screen for me. That's weird. It keeps going back to showing your screen. Stop participant sharing. There we go. Yeah, I have a, I have a control on my side that tries to do it. Okay. Hopefully soon you'll get, you'll get your computer will be faster now. Do you Raj? It is a little bit slow. It tried. Okay. Okay. Right. So is it, is it not arriving yet? Okay. Well, let's, let's wait. Okay. I've got another meeting scheduled to start in just two minutes, but I hope we'll be able to finish this. And I may just tell the other people that I'm going to be a little late for their meeting. Because we're so close. Yes. But just in case it doesn't happen. It takes a long time. Should I submit the PR and. The photo. On the PR message. And then you can review it. Right. You could, you could submit the PR. If you submit the PR, even without us having seen it, you've already done quite a bit of help. And, and I can look at the PR. And do some reviews online after this other meeting finishes. So absolutely. I mean, you submitted the last PR, no problem. So I think you Raj, if you, if you're willing to do that submit, we could call this meeting done and I will. I'll review the PR asynchronously with you after, after you've submitted it. Mark, what about the minutes for this meeting? We didn't open those up. Oh, we did not. You're right. Meg, I should have made some notes. Yes. Would you be willing to do this? Good. We could just know who was here and what we did. Exactly. Yeah. If you could. Would you like me to do. If you could, that would be wonderful. The links not in the calendar. Yeah. I thought it was, but here I'll paste it into the, here is the, the, I'll paste the link to the minutes into the chat here. So there are the meeting notes. Can you open those notes? Okay. Yes. Great. There we go. I got it. Excellent. So even if all you can do is propose a revision there. I can then accept the change and, and we'll have notes. Okay. So Deraj, you're okay submitting the pull request on your own. Yes, definitely. That would be actually better considering everyone's time. All right. Thank you everyone. Deraj. Thanks again for being willing to work through this. You are heroic. Thank you very, very much. Great work, Deraj. My pleasure. Okay. I'm going to end the call and I'll upload. I promise this time I will open upload to meeting.