 Okay. And welcome to Jenkins documentation officers. This is the February 2nd edition of 2023. Big welcome to Mark and Mark and Breva Rockton joining as I thankfully have usually myself. For the agenda. We have a little bit longer agenda than usual, but mostly to facilitate some discussion action items we've got a new blog post from john mark miss and that we want to highlight. We've got our weekly release this week and next week we have our next LTS release. We have the FOSM event happening this weekend in Brussels, if I'm not mistaken. And cool. Thank you for confirming Bruno, and just want to highlight that for a second. We've got about Debian 12 and the release of it which will include and only include open JDK 17 as opposed to 11 so the future of Jenkins documentation and that couple updates for a Google summer of code and where we're at with the Jenkins participation and not. And like I mentioned previously, most of this is pull requests that I wanted to just share and bring up mention, maybe discuss depending on how much time we had and what which one we're looking at. And it mostly a lot of new contributions from new contributors and just a lot of amazing work that should not go on noticed. So, is there anything else on the agenda or anything that I missed that we want to add. Bruno, was there anything from the platform sick that's not already represented here. I thought we covered it all but if, if not, I'll, while we're going through this agenda I'm going to watch the sick notes just to be sure. Thank you more. Yeah, that works. Thank you very much Mark appreciate it. So let's get started. The first item on our list is, we have a brand new blog post from john mark that was published yesterday, regarding the Jenkins application for Google summer code. The application, the, it's the organizer application specifically. This is something that we need to submit as the Jenkins project. And this is to hopefully get us into Google summer of code. And specifically, yes, but this is still something we need to apply for and get approval from Google. But John Marks done a really nice review and write up of all the things that have been going on since we started and what things are going to be coming up and going on and what the application entails, and provides a lot of nice interactive links that help with the number of code info mentor info, and just the general ideas of continuing community discourse throughout getter in the community forum so just a really lovely blog post that provides necessary insight into where we're at with our Google summer application and what to expect. Next up on the agenda, we had our weekly release just on Tuesday of 2.389, which has gone out successfully. So, hooray for that and next week we'll be at 2.390. And next week we will also be at our next LTS release which is going to be 2.375.3. Great guide have been created everything's up to date with all back ports there was one that came after my initial submission of the change login upgrade guide but that's been since added so we should be good to go on that and everything seems to be ready for the release. So, barring any unforeseen circumstances we should be smooth sailing on that. But the change login upgrade guide or request has not been merged yet right so we've, that is correct. Okay so we've definitely got that auction item still it's, it's got two approvals. And, and you did add the backport right I see it. Yes. Okay, good so I think, actually, I'm going to go ahead and merge it, because I think we're ready. It's, it's coming out there's no reason for us to delay its availability until next. Let's delay the merge. Let's get it merged now so it's ready. Okay, sounds great. Thank you very much Mark. And, yeah, and so this will occur next Wednesday, February 8. So, be able to go for that and Mark, we'll be doing a live stream for this release as well. Will be, yes. So, Thursday, then it's typically when you and Darren do the live stream so, again, this release will be happening and then that will be the next day. Next up on this. Again, just want to mention that FOSDEM is this weekend in Brussels, we have some wonderful, wonderful, wonderful folks going and representing Jenkins. Bruno is actually one of those from not mistaken a lot. Keep an eye on, go look for him, bother him with any questions you have, say hi. Yeah, I look like that if you ever, yeah, you know, big guy with no hair. It's me. Welcome. Sorry, Kevin, and while I have the mic, I have this contraption with me. So, if you see something looking weird on the table, it's maybe Jenkins booth. Come and say hi. Me. I don't want to spoil what that is for everyone, but I'm curious to know what it is. Oh, you don't have to spoil it. I've just finished a live on YouTube about that thing that I used to call mini-gem. It's a small instance of Jenkins with one controller and three agents, but that's not the subject of this meeting. Oh, cool. Me. That's for you. Well, but it is a subject of this meeting when we'll get a blog post about that. Oh, yeah, of course. More stories about that. So, it certainly is a subject of this meeting just not yet. I nicely don't get you to pause them. I will forget. Very far in the future preview. Great. Cool. Thank you very much, Bruno. And yeah, and just again, thank you to all the people that are all the folks that are going to represent Jenkins and interact and engage with the community at large. This is a really great opportunity to just get to connect with people directly as opposed to, you know, we're online. This is mostly remote. So it's a great time just to be able to talk face-to-face. And get stickers. Sorry to interrupt once more. Or buy a t-shirt. We have some. Hey, all right. We've got swag. Cool. Sticker t-shirt. What else could you want? Nothing. Anything else on Foss and Bruno? No, no, I'm done. Thank you. Sorry. No, no, no worries. Just making sure. I realized I was starting to cut off a little bit and I want to do that again. Cool. All right. Debian 12. So this is something that will be releasing in April, May of this year. What's going to happen is Debian 12, aka Bookworm is going to launch with open JDK 17 as opposed to JDK 11. What this means for Jenkins documentation is that we will need to move forward and start using Java 17 as in our documentation as opposed to Java 11. This makes sure that not only is the Jenkins information up to date, but also usable by anyone who is moving on to Java 17. The Java 11 support will not be dropped until 2024. That is something that I want to make very clear right now. Mark put that note in here. Even though the Debian 12 release is not coming with it, it's still supportive. Very, very important to note. There's no cut off for anyone at this point in time. And sorry for interrupting you once more. On the latest platform sigmark, we talked about tamering quite a lot. When we talk about Bookworm, because yes, for our containers we are using tamering open JDK builds. And maybe we should tell something somewhere in the documentation about our choice of tamering. I agree. I think well, there's there's this other question even before that. Should we also change the windows instructions at the same time so Kevin, I'd lobby yes we should because Jenkins Java 17 is fully supported already. There is no shame in us in April or May, deciding that we're going to document Java 17 as our de facto documentation. And note that yes we also support Java 11. It's it's not this is not abandonment of Java 11 but rather beginning the process of shifting people's mental model so that they know that Java 17 is, is the preferred choice, and is very well supported. I know that that was recently pushed to full availability for functionality with 2.361.1. So that is something that people might not know about yet or might not may not have adjusted to just yet so making sure that we clarify and provide this guidance will just make sure that the adoption rate is higher than if it were so well and and by April May we will now have been a 2.361 was the the the LTS that gave us full support of and mandatory Java 11 Java and full support of Java 17 absolutely. We've already released 2.375 it's concluding release will be next week will then be to 2.387. That series will go for three months and by if it's all the way into May before Debian releases will be even one more LTS beyond that so so really the story for Java 17 is is cemented clearly we could. So, and that's great so I'm glad that you're okay with the idea let's let's make that Java 17 story stronger and stronger and stronger. Definitely. Now we go on to Bruno's question of what about Timurin. Yeah, what about it. No, yeah, I know that Timurin is the one the what we use for Jenkins and as far as development goes but beyond that mark what. What would you have to share or I don't even have to share Bruno you can describe it you know very well the places where we use Timurin. Oh, well, I have a real no I'm not so sure I know all of them but also, of course, for the containers for the docker containers of the input one the docker agent and the last one. I forgot to name it don't know why Mark, the third one is. Yeah, so SSH agents inbound agents and the controller all three of those absolutely are using eclipse Timurin any all Jenkins container agents use all Jenkins containers use eclipse Timurin as it's JDK. And that's, I think we said one exception right arch Linux, if I remember right was the one. Nonetheless, it's, it's very much a thing for us, but it's nowhere mentioned in our documentation on www.jankins.io. Good to include that documentation then. Yeah, and it may be that that we owe a blog post it might be that the best way to put it is in the installation document for docker containers where we describe there that we are intentionally using eclipse Timurin. I don't know which of those, or maybe both of them because no harm in saying, yes, we have we like our relationship with eclipse Timurin they support the platforms we want, want supported. And they do a good job of delivering all the Java versions we need on all the platforms we need. Yes, and maybe we should read that in the documentation that will explain how to install JDK 11 on book war, for example, that could be our choice because the JDK open JDK built by Debian won't be available if I'm correct. Well, that may be the right time to say, hey, by the way, we can install with Timurin. Why not. I just don't know how it's done by the way, I know you can download directly on the terminal in release this page. I know we are doing it differently with Docker because we are downloading a Docker image and putting it inside our images, but I don't know if they are PPA for Debian you went to or whatever for Timurin. Actually, I don't know them directly from their GitHub releases page. So we'll have to find out. Yeah, good, good question and as far as I know there are dev based and RPM based installers for Timurin. So you can use your standard package manager there. And I'm, I'm a little hesitant to put that in the docs but I might say hey let's put it in a blog post. I don't want to deemphasize JDK seven in the docs was my thinking that let's keep the story centered around Java 17 there but they certainly do provide packages in operating system package manager format for those for those those platforms that matter to us. Yeah. And if we're going to share a blog post or any kind of documentation it sounds like it might make more sense to include that as a blog post when the W12 actually is releasing just to provide an alternative for people who want to use an alternative. Well, and it's a good excuse in that that blog post to say that we in this is intentional right we have switched to describing Java 17 it's a thoughtfully done thing. Yeah, I like that. Nice. So, more to come on that then. Cool. Have a firm of honor quickly again I just want to make sure Mark any other questions or statements on this. I think for me. Nothing for me. Okay, thank you. What's up is the Google summer of code. Just a quick update here. Our organization application will be submitted in a couple days. So, even though that is happening mentor applications are still open project idea proposals are, for the most part, published but again, still optional to, you know, if you want to submit a proposal or sign up, do any or anything like that. I mean, the information there. We have all the information in our Google summer of code and Jenkins page. And we are now getting to the point where we're starting to organize the mentor meetings and project meetings to start and getting ready for the initial push and the start of the social and community building aspect of Google summer of code. The project ideas were just recently went pushed from draft to publish so that is something that has happened in the last couple hours today. Thank you to john mark for doing so. And just thank you to all the mentors and participants that have signed up already. We've got a great handful of participants and people that have signed up to be mentors. The contributor applications are going to be open soon and open for quite a while if I'm not mistaken at least a month or two. So, the idea is that we'll get plenty more folks joining in and signing up there. It's not just students it's anyone who's interested. It's always by any means if you find that one of the ideas seems interesting. So contribute, you can show up, be there, get what you want out of it and learn. You don't have to be constantly doing something, but you can do anything in this case and any, you know, any contributions would be that much more. Any more contributions would be great. And we can, it can foster discussion, it can encourage others. Even if it's not a huge life changing change submission. Yeah, these are the kind of things that help encourage and expand the community so anyone is welcome to join out. And then the last few items I have on here and be mindful of time. Some pull requests of note that I wanted to share. The first one here is in progress about adding content to the updating Jenkins documentation. Vandy has gone and added a ton of content. And being a new contributor, this is a lot of content to take on, not markers a good first issue but still they decided to take it on and just the fact that they were able to create all this content add this in and just provide a lot of context is amazing and super appreciated. I think I had there was a question I had on here about the copies Jenkins platform, because we did discuss it's coming into life in documentation but that's been removed so I think the only thing here is Mark I think requested changes so it. If there's anything that still needs to be taken care of. We can definitely take care of that but outside of that, would you be able to check out the updated version of this. And yeah today today does not look good for me but I would hope tomorrow that I can get to it. Okay, and, and yeah I think this needs more work before I'm ready to say yes I've got to do another review of it and I want to be sure that it looks and feels the same as the install guide and and on the earlier reviews. It felt like I could make those kind of changes, much faster myself than trying to do it as pull request comments and Vandit's work and Vandit's willing to accept pushes from me and from others so he won't object or Vandit won't object. So I think that's fair to just let me make proposal or let me make things push things to it and if any of them cause him angst or frustration, we can revert those pull requests, or we can revert those commits. Yeah, no definitely. Cool. And I have to go through now that it's got I keep forgetting to go through and review the updated updates. So I need to do review on that as well. So, thank you for reminding. Next up, the light TPD reverse proxy info again this just needs to be tested and verified. I've gone through and reviewed it from documentation standpoint so it's just a matter of making sure that works properly in the way that they're describing it. The, we had a pull request and a, this is for this is for the Docker repo and this is specifically for uninstalling a plugin with from Docker. And this information is not crucial to the Jenkins documentation right now but is something that we want to include at a later point in time. This will require some conversation and discussion with Docker experts. So nothing has happened too much here yet just something to be aware of and that this will be something that we discuss again down the line. And the next thing that I had added on to the list is a submission from a newer, or actually not a user this is a returning Google Summer of Code participant who submitted a tutorial on the Jenkins file runner GitHub actions. And this is one of the 2022 Google Summer of Code projects. This person participated in the project and has submitted a tutorial for it. I've gone through reviewed in terms of the documentation. I still need to go through and do a functional test to make sure everything's okay and works properly but it's been great and John Marks also gone through and reviewed, or at least read through and yeah. So, there's been some action on here if anyone wants to check it out try it out. The Jenkins file runner GitHub action is a newer functionality for me to experience and I think in the grand scheme things and GitHub actions are newer in general. So this is awesome and again it's another piece of Jenkins that we can that expands to another area and another functionality that we can use to increase Jenkins presence and functionality. So Kevin sorry for interrupting but I haven't read the PR yet, but what is it about it's with an add Jenkins file runner GitHub action. Is it GitHub calling Jenkins or Jenkins calling GitHub I guess it's the other way around GitHub Jenkins calling GitHub actions. It's the other direction it is. So Jenkins file runner allows me to define a pipeline and have an ephemeral Jenkins that starts just long enough to run the pipeline and then stops. So the entire Jenkins controller becomes ephemeral. The entire Jenkins controller and so this the project idea from last year's Google Summer of Code was allow a GitHub action to invoke a process that starts a full Jenkins controller executes a defined Jenkins pipeline and then exits the entire Jenkins controller. Mind blowing. I love that. I, it's, it is, it is certainly a significant thing and you can imagine the level of complexity that involves because a Jenkins controller has all sorts of interesting things going on right in terms of. Well I actually on my Jenkins controller need 50 agents, because I need five different operating systems and three different hardware platforms and blah blah blah blah. And with all that, putting me into a Jenkins file runner condition wouldn't wouldn't save me much. Right. So, so it's, it's an interesting idea for certain use cases. Yeah, I thought I was a could kill cool kid on the block, you know, because I was able to start a Jenkins instance with all its agent just thanks to a darker compose within Gitpod but no. Okay, got it. That's cool. I love it. Thank you. Yeah, thank you very much Mark for providing that additional context, I was not there last so that helps me a lot too. Yeah, so yeah if you have a chance you can check that out, maybe learn something new about Jenkins file runner GitHub actions. It's all there. But yeah, there's more to it than that they have their own documentation for the Jenkins file runner GitHub action so we might be able to add some information from there. We'll work with. Now I'm completely blanking. No, no, no, it's okay. I just forgot. Mark, do you happen to know this, this person's name by any chance. Yes, Yiming Yiming is first name and gong, I think his last name student at Carnegie Mellon University in Pittsburgh, Pennsylvania, United States. So thank you for that and just putting that together appreciate it. Next up, there was a pull request to update the viewing logs page. This was something that CJ had reviewed and submitted a update for when we looked into the update submitted though we found that there could be a lot of updates on this page. Specifically, there are instructions for Linux Mac, but Mac OS X specifically. And so, this is a little outdated, but we've been able to acknowledge that and point that out. CJ has been working on this updating things. It's gone through and worked on updating the Mac OS information of Linux information. There is still a question about other systems and this is something that I wanted to bring up here because I know that we've talked about things like Kubernetes and the other systems that are available for installation purposes, which is where I kind of leaned on. But what other systems should we be potentially calling out here specifically mark. So on the installing page under other systems we mentioned free BSD and what was the other one I forget which other one so if you look for other systems, free BSD and open Indiana yeah I'm not sure you need to mention. I'm not sure we need to mention that one or even any of these others so so truly if other systems were completely empty, that's also okay. But for me the, the open Indiana free BSD when I have installed and I know it puts its log files in a place that matters to free BSD package maintainers. Okay, I'll make sure to comment that and that in there if that's not already put in the documentation. And once again, thank you to Jeff for doing this creating this. Again, this is a new is a lot of updating to do because the some of the systems are a little behind but thank you again to starting working on this and contributing this. So, real quickly just to finish up since I know we're at time. The second and last pull request here is about managing users page content. Bush Wadi has been working on this and has added a lot of information, since we didn't have any before on this page. And I'm working with them now to go through and get some specifics going on some explanations for some of the fields going on we've got some screenshots a little bit more added to that. And we need to also recognize stuff like security permissions, other aspects of managing users in Jenkins besides just managing users directly. And then the last pull request here is, we've been talking a lot about adding information for detached plugins and implied dependencies. This is something that has been started now. Again, thanks to I'm pretty sure about it's been the yeah that it has been going on a tear lately and submitting a bunch of stuff but he added some information about implied dependencies and detached plugins to the managing plugins page. I've been able to go through a review provide some suggestions and feedback, and we're working on this as we speak to get a really nice visual and contextual representation of this information. So that we can address detached plugins we have the list of them here in the documentation office our notes. But we have. But at this point in time Vandy has focused on the windows WMI agents so we are using that as an example. Great. Other ones we can always discuss later on and as we go. But with this being so recent, this is a good place to start. And with that we've reached the end of the agenda is there anything anyone else wants to share comment on. Nothing else for me. Okay. All right. Well thank you very much. The video will be available 24 to 48 hours, and I'm going to go ahead and stop the recording.