 Okay, it's on. Welcome. This is the Jenkins Docs office hours European edition for August 17. Today on our agenda, we have some action items. If behind behind just showed up so we'll be able to check in on the Google server code. Just some updates about the September LTS release, which is 2.361.1. Small update on certain improvements for Jenkins IO. Discuss the commercial short support page. The blue ocean status statement. Change log entries from multiple repositories. And the hacktoberfest documentation contributions. First things first, just to touch base on the action items and Mark is not here this week. He's on vacation. So we have Alyssa here helping us out today with the recording. So thank you very much to Alyssa. And all the action items are in the same status as previously where Mark still needs to complete the blog post and such. However, the she code Africa contribute on results. The post has. So that is a victory in this case. So, I just want to check in. Would you be willing to share what you've got. Since our last update on the Google summer code. Yeah, sure. Hi Kevin. Hey, so do you want to share your screen. Yes, I do that. Basically, maybe share the data that I've done just a minute. Sure. No worries. So we know how to talk about the progress so we've created the full request for the separation of parameters on the new page so the draft is ready. And in that pure we plan to not only separate, not only include the processing layer but also include the engine configuration. Maybe the read me for that. And also some tests for the processing layer. So that will also be included. And other than that, we are also investigating on one of the anomalies that we saw in the documentation of So we were basically seeing some deprecated steps that inside the documentation. And that also led us to seeing some pages that that were actually not linked from the main base so let me just share my screen and show it to you. All right, so this. Let me know if my screen is visible. Yeah, you can see it. Okay, great. So I basically just search for the issue that Mark had created in the five steps documentation repository. And yeah, so it was about the ignoring experimental plugin releases and for that I saw that the page that is mentioned by Mark was already fixed, but the old plugin link was still leading us to that ASCII doc. And this indicates only one thing that the cleanup of the ASCII docs is not folder is not yet done. So I wanted to maybe create an action item for one of the maintainers for this to run a clean ASCII docs for this so that whenever the next build of the five steps documentation happens, we can feed the new ASCII docs onto the folder so that we get rid of these old lang links. And in this way we'll also ensure that not the older document or older documentation sits on our pages. Any of our pages so for example, the one that we saw was rated to a bit bucket server inside the patent groovy libraries. And so we also posted a query on the pipeline authoring special interest group channel on guitar, and it was basically about the snippet generation of this bit bucket server. And inside that, we were not able to get the extensions choice to be filled by entering different choices. I'll maybe open up modern SCM and in this side from the standard SCM that we have everywhere. We also have a bit bucket server sitting outside. And in this, the name of this field is trades. And according to Christian, they should be extensions because we tested it using the snippet generator and it is supposed to be free name to extensions. So this was that point that we thought that this might be some of the older documentation which is not yet removed. But we have to see basically that clean up is required anyways because the old links which are no longer linked from anywhere but those ASCII docs are still there. And basically I found that link using one of the tickets that that was created the original ticket behind the experimental coming releases. So I picked that link from there. So, yeah, basically should be named the extensions that is what you're working on. And the snippet generation also not happening in the way we expect. So we posted a very on a pipeline of things again, let's see what happens to that. But other than that, I have basically worked. I've also figured out some criteria for setting up the configuration file. And that I have updated in the enemy of this simple request. So I did some tasks for this and that basically contains that extra set of information that we want for the parameter configuration. So they meant to go through this file. So yeah this was the progress for the week. Thanks a lot. Thank you very much. Now I have to admit since Mark's not here I don't know that will have such lovely questions as he normally would provide. But I can see what's going on and I really I know we all appreciate the work that you're doing on getting this cleaned up and looking really nice for with for the Jenkins project so thank you again for all your continuous work. Thanks a lot. And just updates about the Jenkins September LTS release which is going to be version 2.361.1. Faith has asked for a blog post about the Java 11 requirement and really just an overview of Jenkins historically that they can share in the CD foundation blog so I'll be coming up with that we have fossils post from when Java 11 was in the weekly release as a great piece to work from and all the information that we've got since then as well on any releases so lots of material to work with, and I'll be working on that. Once I'm able to finish up the upgrade guide and change log, which are in initial draft stages right now, but have been submitted as a draft PR. The baseline for this release is going to be 2.361. So we're mailing list thread, and it, again, it does require Java 11 so Java 8 supports being dropped completely. We've been doing everything we can to let people know about this ahead of time though. So we've done a great job of making sure that everyone's aware. And then the other thing that is coming along with this is Java 17 support will be it is available for that. And people can start previewing that and testing that if they want to. Change log are is here and available if anyone wants to take a look, share feedback. There's a lot that has been added already we've got a lot of changes coming so there's still more to be done there, but I'll be working on that and getting that taken care of. Search improvements for Jenkins. So this is something that Marcus mentioned in weeks past that the Algolia search is out of date for Jenkins as it stands right now. So we need to update from the legacy scraper to the new version and make sure that the search results are get are appearing as they are expected to right now if you search for upgrade, for example, you won't find the upgrade guide so easily. This is something that has to be taken care of by either Mark or Gavin Mogan since it requires specific credentials. So they will have to take care of that or at least work on that. And Mark's already created an issue in GitHub for this. So we do have something to track with any work can be done associated with that. We also have brought this up in the past but just again the commercial support page proposal that was brought by Gavin Mogan. So we have a support, a vendor support page right now that is could be better and Gavin's could been looking for feedback ideas any kind of proposals that might help build a better support page for vendors. Direct communications links directly to help what kind of offerings they have. Any and in various other topics that would be great to capture in these situations. If there's any vendors or even commercial vendors that you can think of. Feel free to comment and in here. There is. We had discussion recently about including commercial vendors as well as support vendors since it's still going to be cloud. And then. Yeah, there has been a proposal to ask the outreach group to contact potential vendors as well. I think Mark was supposed to check in on that I have not heard as far as what the progress is on that goes. And of course, again this is for the community by the community so as much discussion if you back is available is the best. Moving on the blue ocean status statement that we've added to the blue ocean documentation has been added to more pages and the plugin page. The Docker hub page itself needs to be updated but that's a specific set of credentials again. And we're not sure if we have those to make that update ourselves we might have to check in with some other teams. But the idea is that we'll have the status statement aligned in there as well. And then the tutorial page for creating a pipeline that means the status added. That's something I'm going to take care of as well. We do occasionally get change long entries from multiple repositories. And the issue there is that if they're all coming to multiple repositories, something to fall off along the way, or just not make it to someone's eyes someone's list. I'm going to ask the Jenkins developer list about something we can do about fixing that putting them all combining them all into one entry or, you know, that's still to be discussed so again any ideas any feedback any proposals will be great to share. And then the last thing that I had on my list on our list today was October fest, which is coming up in October. So we've got some things that we can work on for October fest and try to submit, such as the docs need to be converted from wiki pages to markdown. There's still a lot of older pages that need this update. This was actually the project one of the projects that we hosted mentored last year, and we were in the docs team was able to help get a good amount of stuff converted which was great. There's some things that we were discussing but can't be included just because they require too much knowledge of Jenkins to be really helpful. It would take more time to learn and understand what it all means that it would be to do something like inclusive naming. So we're going to keep working on that something I'm going to discuss with Mark as we go along and get closer to see what other docs options we might have. And again, this is something that we'd be happy to discuss here if there's any ideas. This is just something that it's new for me and I'm really excited about being a participant of, and I would love to just expand all my skill sets and relationships within the Jenkins community through it so Yeah, any help is welcome. That is all I had on the agenda for for today. The Han Bruno did you have anything that you'd like to add or throw out there today. Not for me thank you Kevin. Okay. Okay, great. Thank you so much for letting me know and with that, I think we can wrap up a little early today. The video will be available. Once Mark has a chance to upload it again since he's out this week it will probably be next week sometime, hopefully earlier but you'll it'll be shared regardless.