 This is the She Clouds Africa Monday status meeting today is April 2021. We are recording this and it's time to begin. Present are all of our SheCold Africa participants, plus me and Meg McRoberts and I'm mentoring today's meetings. And you're all muted so I guess well you'll, if you want to say something unmute yourself. Does anybody have any issues they need to discuss I know you just went over status at the end of the day Friday with Mark so I'm kind of going to assume that everybody's at the same spot right. Okay silence is a scent. Um, so what I thought we might do, I looked, and it looks to me like. On yinye is sailed through everything. It looks like Esther and Lucy are ready to define a pipeline. And that Sharon and Cynthia are ready to view the steps reference the next step. Is this true. Yeah. Yeah. So, um, are we blocked on defining a pipeline just haven't gotten to it do you think you know how to do that. I looked at the instructions and they are a little dicey so that's what I'm. What I thought we might do is do true open source status that maybe one of you would like to. To open up your work area and, and the group can help can work you through doing the next steps is that work. On yinye. Um, did you use blue ocean to create your pipeline or did you go do it through the Jenkins stage board and then a text editor. I use blue ocean. You use blue ocean. Okay. Yeah, I was was trying to figure out when I went looking at the detailed instructions. We have you install blue ocean. And then he gives you links to videos on how to do it. Outside of which is my, my personal opinion, there's, there's a lot of arguments going on right now. I think blue ocean is wonderful for getting started because it's, it's kind of easy. You can't make many mistakes or it'll stop you. And you quickly get to see the structure of the pipeline, etc. I mean, I, what I also see is if I was writing pipelines all day long blue ocean would get very slow and tedious very quickly. I'd much rather be working in a regular editor I could do it a lot faster, but to get a basic pipeline going. So Esther Lucy who wants to share draw lots. Well Lucy do you want to try it. Stop sharing. And whoops. Oh chat chat chat. Lucy, are you sharing your screen. I think Lucy has some, I don't know internet connection was, she wrote something in the chat pattern please. Oh, okay, let's see. Okay. Esther, do you want to share. Okay, I, I can't share my screen right now. Okay. Okay. Cynthia and Sharon, we you've already created a. Um, do you want to share and do it or I can pull up a lab and do it but be nice if one of you guys did her own in yay. What are we meant to show so I missed that. Oh, I'm going to share your screen and let's just define a little pipeline with blue ocean and see how that's done and then we can look at the steps reference. And if we still have time we can look at the snippet generator. We can share and then work together. Okay. Yeah. I'm not seeing any of you. I don't know what I'm doing here. Since I should I share. Okay, so this is basically to do a little bit of demonstration on how to create a pipeline. For those of you that haven't done yet. Okay. I can't see what you're sharing. I just got some connection issues. Can everybody. Oh, there it is. Now I see nevermind. Good. Good. Yeah. Yeah, so it should be something. Okay. Excellent. Yeah. Create. Can you guys see this? Yes. Yes. Yeah. So then it's create a new pipeline. And then we choose kids. I'll have to look for something on my kick. Yeah. Good work. Then now I can create a pipeline. Those are understand what this is. I don't, I'm not an expert here, but you did use HTTP and I, I've always used SSH for blue ocean. I don't know if that's necessary. Oh, you mean I should have used. Go back to your GitHub and see, I think it gives you an SSC option. Oh, so this, this one I should have used this one. Yeah. Okay. Let me try to. Yeah. I should check and see for sure. But everybody I know prefers the SSH. We never tried the HTTP. Giving it the SSH for the repository works. Did you use SSH or HTTP? I use SSH. Hi Henry. Hello Cynthia. Your screen is not moving anymore. Can anybody hear me? I can hear you. Yes. I think Cynthia is having network issues. I apologize. My internet is not really good. Yeah. Yeah. Yeah. Yeah. Mark warned me. He said, take, keep my video off the, that it does stress your internet. But I'm trying to use also the URL. The SSH URL, but I'm still getting. You want to show. Yeah. Yes. Yeah. Yeah. Can I see my screen? Yes. Okay. Oh, I think I've used that before. I have to choose another project. Okay. So here's it. So. Well, I did basically is to add them. Stages that I did. Follow the declarative tutorial. So I added them. I think the first thing to use. Yeah. Can you just do a print message if you want? Yeah. Okay. I'm going to save yet. Then I added the test. And different message. And to play. So after. So if I say. Then commit to master. Or I could actually commit to the. The first, the first time you do it, you get that branch indexing message. I don't know why, but after that you'll get, you'll see your commit message there. Okay. And there you saw how it ran. It's done. Yes. Does that make sense to everybody? Yes. Yes. Have you all found the control S in blue ocean also? But on me. Control S. You've seen that. He actually pops a code editor for you. I'm not sure you may have to. Try. You may have to go back into the edit. Click the little pencil up at the top. Towards one. Towards the right end. One, two, three. The fifth thing. Yeah. Now try now do a control S. There. And there you can see your pipeline code. Yes. You can make. Yeah. Right. That's what the Jenkins file actually looks like. So. And that's what I could see, you know, in real, if I were really trying to develop a pipeline, I would go this far or, you know, get your stages in and then just copy paste this into my other file or just go in and, you know, grab it out. But you can edit this. And you can make changes. Yeah. Yeah. Also generated Jenkins file. Right. That's what the Jenkins file actually looks like. So. Okay. And then you can make changes. And then update. Oh, okay. Kind of nice. It's not a nice editor. I wish they let me use the editor I wanted. That's cool. So you can click update. I'll get out of there and get you out of there. Okay. Okay. So that makes sense. Esther and Lucy, you haven't done this before. You think that'll help you get going. Yeah. Okay. Then, can you go back to your Jenkins dashboard? Okay. And there you should find. Where are your objects? There we go. And bonka, that's the one we were just working on, right? Yes. If you click that little arrow there that shows next, just to the right of bonka. Get a drop down. Okay. Okay. No. Yeah. See that arrow. Yeah. And then next to the bottom, see where it says pipeline syntax. Yeah, click that. Okay. And this gives you, this is wonderful thing. And this is the stuff that you guys are actually working on. So there's your snippet generator. Okay. And you see, you can choose something there. And it will tell you what fields it needs. For this one, it needs a project to build in the quiet period parameters. There are the question mark is the help stuff. And I think you will find that some of it is excellent. And some of it is worthless. But that's what you're here for. Yeah. So there was a question. I was thinking Mark will be. Available this morning. I needed to. So ask him some questions regarding some parameters. No, he's not here. Maybe I would, I would ask the question on this lecture now later. Right. Yeah, Mark, it's, it's two 30 in the morning where Mark is. Yeah. Yeah. But yeah, but posted into Slack and he'll, he's usually online pretty early. He should, he's probably be online in three or four hours. So yeah, post questions. Yeah. He would know that. You have that. And then you can click, you've got the steps. It gives you a weird view of the steps reference. I'm not sure what that is, but over in the. I think it's useful if your job we're trying to write a pipeline, especially if the information was good. Okay. You can also, if you just Google, there's a doc page that has the steps reference. And yeah, and there you see what it does. And then you'd have that little bit that you could just copy into your pipeline. If you needed it. I also wanted to ask this particular view. And then there is another view here. It's. What's what's basically the difference between the two screens. This year. Okay. What do you mean the, the snippet generator is actually a tool. Whereas, and the steps reference is the documentation. Okay. Okay. Okay. So you could, you actually could look. If you Google, um, Jenkins steps reference, you'll find the doc page, which on that this one, this one, it seems like if you click on one of them, it just opens the information right on the screen. The other one. Yeah. Okay. So the question. Yeah. I'm still asked only below me just give a little. So these parameters here. Okay. These arguments, you understand them and we know how to create help for them. But then this next step tries of objects. This Boolean, I tried looking for each of them in the projects, but I couldn't find them. So I don't know if we're supposed to also add documentation for each of them. If you can, yes, I think that would be nice. Figuring out what they are is more of a challenge. It's how to go about adding them cost. I would ask Mark the question. I would just organize the question and action. Okay. Okay. And you can, we're recording this so he can look at the recording and see exactly where you were. So can I stop sharing? Pardon. Can I stop sharing my screen? Are we cool? Yes, I think so. Does anybody have any questions? Does this make sense? Is it helpful for you guys to get to the next steps? Yeah, it's helpful. Okay. Always if you're looking for one, I think one of the better documented plugins is get, because Mark's the maintainer of it. So when he's gotten very conscious of this stuff, every, every time we sit down to talk about, he goes, Oh, I should add that to my get reference. So. And of course I get the feeling, I don't know that any of you want to grow up to be tech writers, but you see the silent effort from my end is I want to make sure that when you write your stuff, you understand how important it is to do this sort of documentation when you write your stuff. But that's the tech writers. Tech writers are obnoxious that way. So. Okay. Okay. Does anybody else have any questions or. Want to do anything else? Or should we call it a meeting? Do you want to get to work? Yeah, I'm cool. You're good. Yeah. Okay. Well, then let us end this meeting. And I thank you very much. Thank you too.