 Hello everybody and welcome to the Jenkins pipeline authoring sig United States meeting it is Friday March 13th Welcome, uh, I will start with saying that the Jenkins does have a code of conduct which essentially amounts to don't be a jerk to one another Just be kind I Am going to share my screen to bring up the meeting. Oh, no Don't tell me I can't share my screen I can share mine if you'd like If you can because I need to I'd have to leave this meeting and restart it Because I'm on a new laptop and it's not letting me share and because I just updated Not here. So let's do a share this screen And there's probably a way to open up the google doc now and here we go Beautiful. Thank you so very very much. I appreciate that to make it readable size Okay, and if you could just drop your name in the attendees list for March 13th Uh, I will go ahead and start off with open items the personas, uh Questions if everybody has entered their questions, which I believe they have That's great. If you have it, please do I will link the doc D link to the doc in here But uh, I think most everybody has answered their personas questions and those are going to be what we decide How our roadmap is going to look in the features that we want to work on Uh, do anybody have anything to add to that anybody mark? I won't refer to you as there's more people here Uh, nothing nothing for me. I added my questions. Awesome. I thought I could help with Uh, okay, I will move over into the discussion Uh gdsl support. There has been some chatter in the getter channel Uh in regards to doing getting that back up to speed And uh, well I the the the chatter I agree with is extremely relevant and it is something that Liam and I have talked about adding this to our roadmap So we definitely will be Thinking about that and and how we want to get that done My idea initially in conversation with Liam was that we just do this initially for IntelliJ And then we start working out for eclipse and and all of that stuff later on but initially for IntelliJ and uh, so that is that The final thing with uh, open discussion is we need to start finalizing our roadmap For those that are watching this video one of the things that the pipeline Authoring sig is going to do is we want to set out a roadmap for what We will be wanting to accomplish as a you know from a high level And then what we're going to accomplish this year may be quarter by quarter This also sort of rolls up into for those that have seen Oleg's email in regards to the overall Jenkins Roadmap we want to start rolling sig Roadmaps into that. I will add a link to What we have for the initial roadmap as well as to Oleg's mailing list Item for the overall Jenkins project roadmap Do you have anything to add to that mark? Just one point Just like real maps of real roads don't have dates on them It is perfectly okay that the real map that the map of this road does not have dates on it So you you referenced quarters and for me It I think it was Oleg's phrasing was something like Now near and a long ways out or something like that there he had three three buckets in his proposal And and none of them are particularly time constrained Agreed I get into the concept of doing things by quarters, but being that this is an open source project I have to sort of change my agile mindset to a more oss mine frame So thank you for clarifying that If you don't have anything else mark I think we can go to the open floor and you do have some items that you wanted to discuss So I will turn it over to you I do okay, so I've been I've been funded to replace the D zone Jenkins pipeline ref card. It's a PDF formatted ref card eight or ten pages based coming from 2015 that's heavily on scripted pipeline And I think we can given that it's a funded effort We can shift its content to use it to do some things with declarative There is already a declarative pipeline ref card from D zone But none of none of those have anything about matrix Or milestones or retry For me, I think we should deprecate scripted from we should not mention scripted in the ref card The ref card should be a a marketing concept It should be something that people look at very quickly and realize The preferred way to do things and I don't think putting scripted in front of people today Is a preferred way I agree with that Okay, cool So matrix milestone and retry are three that look to me. Oh, I guess and there's one more lock Right that are if I remember right not mentioned in the existing declarative pipeline ref card Any other recommendations of oh, here's a cool feature That we ought to highlight it already does have for instance post when That's that are already covered Okay I don't have anything off the top of my head to add I will I do have a question In in regards to this body of work. Is this something that you are doing? Yourself, are you looking to maybe get help on this from the community? Uh, no, it's this is just me. I'll do it myself. I'm not looking for help from the community I do think That I would I I hope that I can As part of this use it to generate a declarative pipeline tutorial on jankins.io Um, that was the the reason for coming to the pipeline authoring sake was I think this could also be used to generate We have today on jankins.io tutorials on how to do a maven based job application how to do a python application and how to do a a No j s application This would be Somewhat orthogonal to those those three things which are application centered this would be feature highlight centered Show the pieces and let let a reader Choose which piece they wanted to look at Instead of a linear flow through the tutorial. It would be Choose your adventure. Oh, I want to know about post conditions. I want to know about when I want to know about matrix or milestone And put tutorials segments there question was Does that seem reasonable for a tutorial or should I look at another another delivery form? No, I think that seems perfect as a tutorial I would even take it To say I wonder where this could fit like in looking from a personas perspective How this like oh this addresses david or this addresses linda Uh, that would that would be very good Well, and I like that. That's a good point. Um, uh, which persona Or personas will this Will this updated document address because You've got a good point. I I should be very clear With the people i'm working that are helping with it Which personas we're trying to address and which ones we are not trying to address with this Agreed and I think when we have the overall document that gets put out there in terms of personas and somebody says Oh, i'm david and then they see that they could say oh, okay Well, that that doesn't apply to me or then they look at it and they're like wait that does apply to me I'm not david. I'm linda So I do think that would be good if we could sort of somehow incorporate that Good. All right. Yeah, so I'll I'll that's a good good point. I hadn't thought of using the personas. Thanks That was what I needed Awesome. That is uh, that'll be great. I'd love to see that and if you need any help Please by all means let me know and uh, I can help but I think you've got it well under control But please don't hesitate to reach out if you do Great. Thank you That is all that I had Uh I don't think there's anything else. Do you have anything else you wanted to add mark? I don't thanks very much for letting you take the time to talk through that ref card question Well, that is beautiful. Then I will give you back. Uh, the rest of your hour I will thank uh anybody that uh is watching this for watching it And if you do have any questions, please don't hesitate to reach out to us via the uh pipeline authoring mailing list or directly in the getter channel with that I will thank everybody and have a great weekend Thanks Bye. Bye