 Hello, everybody, and welcome to the Jenkins Pipeline authoring SIG. The date is May 22nd, 2020. We're midway through, or I don't even know if it's midway, but we are somewhere in points of the world pandemic, so hope everybody is safe. This meeting is governed by the Jenkins Code of Conduct, which is amounts to be awesome to one another. Please don't make me have to use that, which I don't think I've ever had to or seen it. So anyway, my name is Marty Jackson. I am one of the SIG leads for the Pipeline authoring. And I see we have some new people on there. I see familiar faces. I see a few names that I haven't, one name that I haven't seen before. If you'd like to introduce yourself, please feel free. Hey, this is King and Odyssey. Just join in and see what this is about. Probably listen in a bit before contributing too much. I work with Stephen. I have a decent amount of, is Alan Hamilton. So, excited to join. Awesome. Well, welcome. Welcome, welcome. We're a rag tag bunch. Try to keep it light, I think. Okay, I am going to share my screen. And we can get started, but unfortunately, see if this works for me. No, because I breathe had to format my system. It is new. Does anybody else want to share the screen for the meeting notes? I can't do it without leaving this meeting so zoom can take my set. I got a market. Thanks. Awesome. Okay. Let's see, let's go ahead and start open items from last meeting. I was unable to attend last meeting due to personal conflict, but I see we did go over a lot of things. I do see, see next steps. I am going to start from the Jenkins runner update. The next steps was integration testimony framework, including pipeline is YAML. Do we know if that, uh, who's action item that was. So, Oleg was saying that he, um, he released 1.0 data 12 of the Jenkins file runner. I mentioned that that might be an opportunity to leverage the Jenkins file runner for integration testing for pipelines. Right, which is an interesting idea. Jenkins file runner lets you sort of do 1 shot Jenkins masters to run a pipeline. So there might be an opportunity to leverage that for for integration testing. I also said he was going to incorporate support for pipeline is YAML into the Jenkins file runner so that he could get some experience with pipeline is YAML and test it out. So I think any, any follow on items for that would be an update from all the next time he's able to join us. Yeah, I will I'll sync with him offline. See if he has an update to that and I will add it to the notes. We usually sync multiple times throughout the day. I'll I'll get him. Let's see pipeline is YAML update. Next steps was integrate the pipeline generator. Do we know who was discussing that? That was a I talk. I don't see him available on the call today. So I apologize on talk if I butchered pronunciation, but he he's currently working on pipeline is YAML didn't get an update last week in regard to the pipeline generator. Okay, we'll go ahead and but the goal for that was to be able to to for the pipeline syntax generator to be able to spit out pipeline is YAML equivalence for for snippets. Okay, we'll punt that until next meeting. Let's see here. Jenkins templating engine for 2.0. I don't see any action items. Did you have anything in regards to that. No, no, actually items. Just, we were pretty light on agenda last week so I figured I'd give an update on the scope for the 2.0 release, since it was, it's on the Jenkins roadmap now. I don't see any action items there. Okay, to choose too easy. Let's see facilitate contribute contributions to plugins. There's really no action items for that. Awesome. I will move on from that to discuss. We have the hack fest, the pipeline documentation. I believe you entered this in Mark, did you want to speak to this. Sure, I just have an idea that what I'm going to do is, well, one, encourage people to contribute. If they're interested in contributing pipeline documentation. There's a piece of pipeline documentation that is complicated. It's complicated because you have to document inside plugins, not just documenting on the Jenkins.io site. We could touch on that in the doc sig office hours if that helps. There's so much to do on the Jenkins.io site that's much more approachable for people much more comfortable than having to find a specific plugin and update its documents that I'm prone to leave it off for now, but it could be an advanced topic that we could consider if, if there is some interest. And it's one that I've learned the hard way manage it maintain the get plugin that I can't just go to an ASCII doc file, write its documentation and be done. I have to think carefully and put it into certain places in the plugin structure to have it visible then in the help in the syntax generator, and in the online Jenkins.io doc. The second proposal there was, I think I'm just going to as part of my hackfest contribution do a blog post and a five minute video highlighting the pipeline snippet generator. I still think we get far too much feedback on the Jenkins.io site which says give me more examples where the people don't realize the examples are already inside the system ready to be used. That would actually be really awesome. I know a lot of I get a lot of questions for that and people actually saw some way to use that. If I can help you in any way doing that, I would be more than happy. Because I know that would stop a lot of questions. Great. Jenkins pipelines on a daily basis and I still use the snippet generator almost every time I need to figure out the particular syntax like I know as well as you can at this point and I use it every day. Right, I am, I am, we should be intentionally lazy in generating things to the simplest way possible and snippet generators one of those simplest way possible to generate it. Absolutely. And that's all we can help you out. Let me know would definitely I'd love to help you out. Okay. I had an item on here tracking roadmap items with Jira stories. So one of the things that we need to do is for the roadmap is really start to dial the drill down into creating stories for those so those can be updated on the actual roadmap that was put forth by Oleg. So I am going to be spending some time this long holiday weekend. Going over what you know what is out there what matches. So you may see see some things from me where I'm you know like with JTE like hey, would this be a good thing to pull into that sort of store with this story be good to pull into the roadmap for JTE and other things like there's things like linting and things like that. So I'm going to be doing that. I'll make a note here. Correct me if I'm wrong, but I think right now if you go to the roadmap Jenkins that project roadmap. So right now are we linking to like epics. Is that so that's what we'll do. Yeah, that's what I'm going to want to do is I'm going to want to take the epics that we have on the roadmap and then start to associate stories with those. So you're able to do a mapping from the roadmap to where all of this exists. So that is what I will be doing. That is all I had for any discussion items does anybody else have anything that they would like to discuss. I will add that has anybody noticed an uptick in conversations in the getter channel for the pipeline offering. I have noticed it's like really increased and I like I'm kind of like excited about that and then also kind of scared like, oh, we've got to get everything together fast because people are now coming to the site. I made a new open source friend and Jerry who is working on some some functionality and sort of starting to dive around the pipeline code base looking for opportunities. So he's been asking a ton of questions and driving conversation. So that's exciting. We, I will encourage him to attend the next time because he has some ideas that might warrant some conversation in the SIG around pipeline visualizations unit testing, some stuff like that. I don't want to go too far into the technical weeds but he has some very, I'll call them niche interests and and how to leverage Jenkins. He's been doing some of that is very interesting conversation. So yeah, that'll be awesome to have more people here. Does anyone have anything else. Keegan you have seen a lot. Oh, I'm sorry like go ahead. I wanted to touch one of the issues regarding heck fast, which is going to happen next week. In previous discussions, we were trying to make decision on the communication channel. This is still the question, but at the same time, I noticed that Gitter channel was established for next week hacker fast. So just wanted to clarify, is it the final decision on communication channel that Gitter will be the channel of communicating. Or it's still not decided yet. So, there's been a lot of conversation about this not only just for the hack fast but prior of what you know Slack versus Gitter. For now, I will say we are going to stay with Gitter. My hope is is that at some point, we'll be able to move that but that's just a hope I don't know how. I don't know that is going to be coming to fruition if you I don't think it's going to happen anytime soon. So Gitter will be of the official key. Keegan, you've heard. This is one of our shorter meetings but did you have any question. No, nothing really specific. I'm still trying to get the speed with everything. Understood. I'll know if if you have any questions were we're in the Gitter channel. So if you're not there definitely join there and if you have any questions and don't be afraid to ask questions that's for sure. Nobody will fall to for asking questions. Thank you. You're welcome and thanks for joining. Please do come back. Well if nobody has anything else we'll call this a short meeting I'll give you the rest of your Friday back. And I will see you all online. Awesome. I'm going to stop recording.