 Welcome to the European Jenkins Docs Office Hours. Today is July 7th. And today we have a little bit more of an agenda than we have lately. We have a couple of action items that Mark will share. Just quick status update on. We have some exciting news, a lot of stuff going on. We had our 2.358 release this week, which now is requiring at least Java 11. We have the Jenkins 2.346.2 LTS release coming out. That's going to include the change log in upgrade guide. If we'll be able to share with the Google Summer Code progress updates that he has. We have some additional improvements and enhancements that we're going to be working on for Java 11. It's not a one and done situation. There are still other pieces that need to be updated. And Basil Crow is working on that for us. And then we also have a proposal by Gavin Mogan, who is one of the Jenkins Governance Board members about enhancing and creating a new commercial support site. The current one is out of date and not necessarily the best resource for users. So creating an updated one based on the stories.Jenkins.io will go a long way in helping to improve that experience. And then there was a pull request submitted recently that suggested some changes to the navigation banners, headers, and then we'll be able to share our sales actions, pretty much any part of the background on the Jenkins site. And they're looking for feedback. We've got some, Mark and other folks have already responded, let them know about recent font changes and other pieces that are important in that case. But we'll go over that in time. So first things first. Mark, if you want to just give us a quick update on the first two items there interaction items. Sure. Still no progress. Sorry. Yep. No worries. Okay. Great. And so then again the 2.358 weekly release line was released this week. So now that requires at least Java 11. It also offers Java 17 support. Java is no longer supported. And that will be reflected by the LTS in September, when it catches up and matches the weekly release line requirements. I'm actually, I've also gone through and added some context to the documentation regarding that letting folks know that there is that distinction between the week release and LTS releases. So hopefully everyone's very clear on that and they have if they have questions they can direct them properly. But that should be fairly clear. We have the Jenkins June, the July LTS coming up the 2.346.2 change log enough great guide which the pull request has been submitted. Mark and I have been working on the content reviewing and just making sure that everything looks solid and clear for the release itself. And the updates that I made a suggestion that's been applied. So, but everything else looks great so that should be pretty straightforward at this point. Would you like to show us or take us through the Google son or code and what's what you've been up to since last we spoke. I'm sure so a couple of pull requests to Jenkins that I got much this week and the first one being about the data type details so that has been merged and we can see the reflected changes on the website now. So, everything has been very successfully and all the documentation has been updated accordingly, all the ASCII docs. Then this week I also created a pull request to add a search filter on the pipeline steps efforts page. So basically this steps filter filter out the content on the page dynamically and like yeah if you could demonstrate that something that so all the content would get filter accordingly and basically the advantages of this over a normal browser like this would be if for example you search it and you want to see the related plugins of the steps. When you search that on the browser you get the results, but the other things which are not relevant don't get removed. So you have to navigate between those things top down and it's quite tedious. So now I think this makes it slightly easier to understand to find the piece of information that user wants. So this was the pull request that was merged on Wednesday, I guess, yesterday. And you have to show the mark weight thing. All right, the one that the one that caused me pain and anguish and that VHANA has made my life better. Search for the word checkout. No, no, go back to that. That pipeline steps reference search for the word checkout. Okay, so in order to find things about checkout checkout is one of the most commonly used operations in the pipeline, one of the most common. I would search for the word checkout in the old days, I would press control F, I would enter the word checkout, and it would find the bit bucket server integration first which is not relevant. It would find plastic SCM second which is also not relevant to what I was trying to do. Finally would show me pipeline SCM step I am now for for keyboard interactions in and a little frustrated. What VHANA has done is I type one word checkout and there it is right on my screen, I didn't have to scroll and navigate VHANA really thank you. This is great. Yeah, this looks incredible. I'm glad it came back to me so yeah. Thank you. Yeah, it's great. I was actually checking it out to earlier myself beyond it's really nice really smooth it's very responsive and absolutely makes it a much nicer experience trying to find anything on the steps reference page so that that's that's terrific. Thank you. Thank you. Did you have anything else on the projects you were going to be on or is that cover everything for us today. Yeah, one more thing that the release of the pipeline material titles has been complete so John Mark helped me with that. And now we can see the artifact on the artifact agent is artifact and perhaps the next thing would include VHANA is not as high as Mark showed us last week. So John Mark said that he'll take care of that. So the CD part is like yet to be done. But since there are not many releases that are happening for that repository right now I think that becomes low priority for us and adding some tests to it are some things imagined right now for it. For my clarity, do you intend to replace some capabilities that are some classes that are currently inside the pipeline steps doc generator with references to this library is that how you're envisioning will work. Yes. So we can replace the mock Jenkins or Java mock extension list or Java and the hyper local plugin manager the main body of the from which we can actually execute the reactor inquiry, the plugin manager to get the results so these three classes will not be required in the main repository any longer. So yeah, that was it from my side. This was the week's progress. Awesome. Thank you so much. Looks like there's been a lot. So that's very exciting. And yeah, very much kudos to you. Thank you. Next on the agenda, just some Java 11 further improvements that we're working on the jetty upgrade from version nine X to 10 X and a few other dependencies necessities that are being that need to be upgraded so that's some of the pros helping us and working on those upgraded enhancements. Again, this is not something that can be done very easily or in one go is over time so it's a marathon not a sprint network yard. And then. While Mark's typing out that information or mark if you want to, would you be able to share a little insight on that. This was a fun improvement that comes as a result of the Java 11 work. The jetty project announced the end of community support for jetty nine about a month ago. Our timing is really good to get off jetty nine, they were willing to support us. We're not, we're a little higher on their list than just a community project, but getting off jetty nine and onto jetty 10 is a real positive. Unfortunately, in this case, our automated tests were testing a particular aspect of Web sockets, but weren't testing in a production like environment. We discovered that there was this test gap, Jesse Glick and Basel Crow have been working together to close that test gap, and to get ready to do the upgrade we hope that by 2.359 next week will be on jetty 10, but if not a week or two later. And so nice benefit and getting us on to more modern version of a very important core library. And this is the burden on the maintainers of the jetty library so that they don't have to worry about Jenkins continuing to use just jetty nine. Thank you. And is there anything else that we should know about the Java 11 language extensions. Yeah, in this. Well and this one may impact us in ways that that are documentation related. What Basel's discovered is a leading Jenkins user Steve Hill has implemented a thing with a tool called open rewrite. Open rewrite is an automation system that will do apply code refactorings. And the reason this matters to documentation is we've got a pending pull request for a tutorial on how to modernize a Jenkins plugin. And this user Steve created an open rewrite rule to express one of those modernization steps through automation. And it doesn't do automated evaluation of the quality of the of the change but it does perform the change. And so it gives the user the contributor a jumpstart on Oh, I ran this open rewrite rule, and it performed these code transformations for me now I should focus on testing to be sure it works to be sure it's well behaved. And then I submit a pull request. So it's it's taken away or it's read has the potential to reduce the complexity of some of these modernization steps by letting a machine do it for us. That's pretty awesome. Definitely sounds like it can be very useful for us. If we can get that kind of standardized or something. Well, and, and Steve Hill has done some other cool things around Jenkins automation and in for automation so yes very grateful to him for his work. Fantastic. Thank you, Mark. So just a couple days ago, or within the last week, Gavin mogen, who's part of the Jenkins government's board had made a suggestion about revamping and creating a new commercial support page for vendors vendor support page. We're hoping to make sure that if we're going to have a page like this for support that it's up to date offers something that the user can filter through navigate a bit more cleanly. And more importantly, things like direct links to the support. And what the users are looking for understanding what the makeup of the user base is who's looking for help what they're looking for help with, and is looking for just general feedback on anything else that might be worth tracking. As you can see there's already been a few suggestions and comments about the direction that we can take as far as the support page goes, and Gavin's really receptive to any ideas so by all means feel free to share. If you have any questions, any experiences, anything that might be worth noting that hasn't been put down already, even if it is that's fine. But this is something that's really, it's going to be nice to have after the stories dot Jenkins that I have pages finish up. And would go a long way in helping just reassure and reaffirm a lot of the Jenkins resources and functionalities with those external partners. This is, like I said, this is just something that we've just started working on and I've been working with I've been chance to get some of the Gavin as well. So yeah, that's something that's where we have to look forward to in the future. And then the other item that came up this week is a PR that I've been submitted request, looking for some changes to the navigation and some other parts of the actual Jenkins pages. So the preview site. So this is the background that is set up in the preview the fonts change there are some other items. However, there's been some other recent changes to the system fonts for instance with Jenkins, and with wake things are currently going in the world and with Jenkins. So make sure that everything's on point and aligned for messaging for branding, everything else. So mark, and some others have commented on the post and shared their insights and recommendations suggestions for what can be done. There's definitely some merit to talking about this and discussing the image usage and just overall branding color scheme, etc. So this is another thing that any feedback any suggestions that can be shared will be much appreciated. And we'll go a long way in helping to determine what sorts of improvements we can make in the future, or sooner than later, if there's something that we can agree on now. Mark, I did get a chance to look through these a little bit. Is there anything that you wanted to point out or make note of on these in any specifics or I'm just looking for community feedback. I am. I am notoriously bad at assessing quality of design, and others may feel similarly inadequate. So those who are good in design like you've been a connection who is whose comments are later on. He's very, very good at design and he's very so I give great weight to, to his opinions, and, and his observations. Likewise, Tim Jacome and Jan Farachik are also very, very good in this kind of thing, whereas I'm really bad. So I am unwilling to merge it without getting feedback from other people encourage other people to give their feedback. That's fair. I'm not so great with design either so I feel you're entirely on that. Thank you very much Mark. So that covers the agenda that we have written down for today. Did anyone have any other points topics or items that they'd like to add to or bring up. Yeah, as a side note, the community brown bag was earlier today and was a really lovely experience Bruno actually gave a wonderful talk about the coffee papers and how to really enhance your abilities and chances with how you can Yeah, of course I thought it was really nice and I think that that's a lovely resource for anyone to have so Mark I think that's going to be available somewhere for I don't know because that that was Cloudby's internal Kevin. But it was an excellent presentation where you should want to. And I think I think we may consider that Bruno is having to do it publicly because I think it's a great, a great concept and how to get accepted at talks is a good idea. Yeah, and I think I also just appreciated a lot of the kind of the self affirmations that you're sharing and how to take care of yourself when you're also trying to share all your excitement and knowledge with everyone else so it was really nice. Thank you. I think that covers everything for today, and we made it to the agenda. I think that we could stop the video recording.