 Welcome, it's documentation office hours the 31st of August 2023 topics on the agenda for today blog posts. Choosing a plugin bill of materials version Java 1117 and 21 Google summer of code and I think we should move this one much higher on the list because it's actually got real action. Existing requirements document, then some bookkeeping items and DevOps world anything else Bruno. No, thank you more. Okay, so let's look at the blog post first and see what we've got an impressive array of blog posts that arrived over the course of the last few days. So we've got exactly we've got the risk five blog post from Bruno. We've got Docker base quick start examples summary from Ashutosh. Okay, we've got get lab plugin modernization. Modernization from harsh. Then we've got summer internship and security which I think was also before no no this was before our last. Yeah, 23rd. So that was eight days ago right so that that was not in our lab that was already there. Good. Okay. That's a victory. Nice. Yeah. Do Google summer of code so Bruno you want to share with us how Docker compose for tutorials is going. So we are almost at the end we are in the last week of call some of code for this project so the goal was to modify the existing documentation for the tutorials and to simplify them. Quite a lot and to get rid also of Docker and Docker in these tutorials because it was very intimidating for first time users. We are at the end of the project and we haven't been able to integrate the new documentation into Jenkins.io yet. And we haven't been able to insert our Docker images for these tutorials in the Jenkins Docker Hub repo either but we all we have all the material to do so the thing is the time frame was kind of short to get all of this done. And we can't integrate the documentation as long as we're not using the Jenkins Infra Hub though it's a chicken egg problem but only there and we do hope to be able to integrate everything into Jenkins.io and the Jenkins TI Infra by So by the end of September if all planets get aligned correctly. We'll see but now we have now four or five five tutorials working with just one command which I find beautiful it just Docker compose up in the name of the tutorial and bam you've got a working Jenkins instance with an agent and ready to go. So if you want to start with node you're we've got you covered with Python also with Maven and it's working thanks to the huge work of Ashutosh and it was a joy to work on this project and I do hope we'll be able to integrate that into the Jenkins.io website soon. Excellent thank you. You're welcome. Docker compose up that's and and what that does then is that downloads from a downloads a container image that we maintain right and that has current versions with current plugin versions. Yes. In fact we try to get it as up to date as possible so you're we're using the Jenkins LTS version of course but as for the plugins we have something that runs every day and proposes a new plugin versions if ever they exist so you're Guaranteed that you're using the latest versions of plugins and officer Jenkins LTS that's pretty cool but yes. The problem is it's still on Ashutosh Docker Hub repo and not on Jenkins and that's why people could be afraid of using that and that's why we can put that in the official documentation yet. But the PRs should arrive you know for Jenkins.io website should arrive next week hopefully and we won't be able to merge them of course but they will be there we can discuss for a few weeks and then hopefully integrate them into the website one of the Jenkins info has our images in there Docker Hub repo. Very good. And do the have you found that the tutorials when using this run it with a single argument. Which tutorial you want to do they collide with each other or is it okay that they I can can I run. Both the Python tutorial and the Maven tutorial on the same machine or do I have to destroy something to make them work together. To make the same machine yeah on the same machine at the same time I'm afraid it's not possible yet. But can I run them on the same machine at different times with one torn down. Yes. The trick is you have to do a Docker compose down minus V if I'm not mistaken between the two. And that's all and if ever you had forgotten about that you know if you run Docker compose up without shutting down the first one you will get a newer message that tells you oh it looks like you have forgotten to do the Docker compose down minus V so that's pretty much self explanatory that should be easy for the end user hopefully. Very good okay so well and and it gets them the experience of hey compose compose really is doing things on your system you've got to take action when while it's running it's running if you want to stop it you need to stop it. Yes because if ever you reboot it will still be there right stop it right Docker compose is very good at persisting things right that's part of its job. All right. Excellent. Thank you. Anything else you want to share. No except the time proud of progress. That's okay. Very good. Thank you. Well actually there is something more to share right which is that the demonstration, the final presentation will be September 14 is that right. You're right. Yeah, we'll have a 10 minutes presentation and five minutes for the question and September the 14 for all the projects which are for. Yeah. Very good. Congratulations. All right. Thank you. So the second documentation for Jenkins Vandit continues to progress. We've extended the the project has been extended for a little bit extended a few weeks for a few weeks for Vandit's benefit he was able to continue the additional work and moving forward. He's been struggling with Gatsby, I think. But gave in Morgan came to the rescue and I think they will solve the issue. In a few days. Yeah. Very good. All right. Anything else on Google summer of code. No, thank you. Okay, so we have an open one on how to describe the process of choosing a plug in bill of materials version I made no progress this week as a reminder. The question was raised by a Jenkins contributor from I think sales force. Yes, Kyle Leonard. And the question was how do I choose the bomb version. And there are a number of comments there. We discussed it in Docs office hours Asia came to some conclusions and now it just needs to be implemented. And yeah, there were some additional ideas we could consider using update CLI to update the documentation. We could static reference older versions in addition to the most recent release, etc, and a blog post was a suggestion that we had. And the Java next topic Java 11 Java 17 and Java 21. There's more work needed there and that work continues I've got it scribbled on my whiteboard behind me, but haven't yet turned it into something I can discuss with the Jenkins community. We've got interesting challenges hiding there. More more happening hopefully later this week. Any questions on Java 11 Java 17 and Java 21. The first time you explained that in that I listen, I thought it was pretty straightforward, but then you discovered some hidden things and you had to, yeah. Right, it is definitely not straightforward. And so if there's that's why the diagrams are, I think so crucial here is to show, look, here's what we've done in the past. We're doing what we think we should do now and here's where I think we should go in the in the future say two years from now. And each of those is a step on this progression process so I'll I'll get those together and start sharing them. Thank you for that. The next topic was, we had had a discussion with Kevin about possibly embedding the so we've got a document here. When we look at installing Jenkins and we look on Linux for instance there's a section here called software requirements. It links to separate pages related to Java requirements to web browser compatibility to windows support policy Linux. All all very useful things but only available through links embedded inside these pages it's never visible over here on the left hand navigation contents. And Kevin, Kevin observed really it should probably be on the left hand in a separate section. So he's creating a poll request that will create a new, a new chapter here on the left and this chapter. I think has he's even given we discussed a possible name for it and I think it was platform information. I mean the previous meeting notes. Yeah, right and Kevin's Kevin sent me a link to a prototype in his working repository and I was able to do some tweaks to it. I don't think that he has yet submitted a poll request so more work needed there but it is looking promising. So what I ultimately proposed was what if we renamed Java requirements to Java support policy and then had four pages for support policies in the chapter. No actually five, all five of these as support policies. Then there was one additional topic that was related to upgrade and I think that he's been persuaded by my arguments that we probably want an entirely separate chapter on upgrading Jenkins, because it's, it's there are lots of things to consider when upgrading Jenkins. Even there are already a section somewhere about upgrading Jenkins or is it just blog posts. I don't see in my searching and I may have to do more searching I know that Vandit had started work on a an upgrading Jenkins but I'm not sure it was ever merged so needs more looking if it if it does exist it's not as a top level chapter. Oh, maybe it should because we have some questions on Community Jenkins are you regarding that exactly how do I questions like how do I upgrade across multiple major versions of LTS. Right, I'm going from 2.387 all the way to 2.414 how do I do that. What are my choices and why that kind of thing. Yeah, I'm always tempted to answer. Oh, you should have done it earlier. Goodbye. Thank you. Good luck. That sir is a very bad attitude. I know. Yes, very good. So discussion and refinement will continue. Anything else on the support policy document. No, but that's an important thing. Yeah, that's something interesting and that may we may discover it on that some other things are missing. Right. We have to. Yeah, we have to start somewhere. That's cool. Thanks. Excellent. Then next was I've got an action item that I'm giving myself to archive the Docs Office hours notes because what you'll see here if we look at the table of contents is getting Yeah, it's 25 pages of 56 pages right now. So it's it's too long. And what we did before was create archives of multiple months that we can reference for history when we need it. So it's the same kind of document, except it's show exactly just all we do is truncate this copy this create a copy of this document then truncate this document. Yeah. And that's all that I had for one more is devops world tour I owe a blog post. And I hope to get that done today. Because you will be the star on stage. I will be one of the speakers. Yes, one of the speakers. Anything else for today. It's for today, but it's for tomorrow. I think you will see Ashutosh tomorrow in the Asia Docs Office hours. Oh, I don't think you will do a demo but you could maybe discuss what's going on in the very last straight line of the project. Very good. All right. About 12 hours from now. Yeah. Super. Look forward to seeing him. Anything else. No, thank you, Mark. All right, thanks recording will be available whenever I make it available.