 Welcome, everyone. This is the Jenkins Platform Special Interest Group. Delighted to have everyone here. Let's get started. It's the 9th of April. Proposed topics for our agenda today are Open Action Items, The Windows Installer, Platform Roadmap, Series 390 or System 390 and PowerPC Infrastructure Progress. I guess, should we also include there and arm64 or do you want that? Is that better done separately, Alex? They're really two different things. Yeah. We don't really need any special agents for that. So it's kind of a little separate. Right. Okay. So arm64 status report. We may do the Java upcoming. Not sure that'll, that depends if Matt's able to join us. If not, we'll defer it for two weeks and Docker PR status and progress. Anything else that needs to be added to the agenda before we start working through it. All right, let's go then. So Open Action Items. Oh, this is me hanging my head in shame again. We've got, let's let me copy those and update the text to note what the actual status is. So open a JEP for Docker Operating System Support. I still haven't done that. Windows Support Policy JEP still pending. Windows Installer Code Signing. Alex, you want to share with us today? Yeah, it's working. The automated release process that Olivia has been working on is signing the installer. They're working on the final stuff to make everything available through that process. Excellent. Thank you. Very good. All right. So certificate has been received and deployed. So should we just mark this one as done? Big victory? Yeah, I think so. Excellent. Thanks very much, Alex. Thank you. Thank you for your heroics on that. All right, then Docker build PR rework. This one I think the, there is still intense interest for it and we'll continue working. Alex, anything you want to report there? So it turns out there are no changes at the Jenkins file, so we didn't need a shadow PR. So I just closed it. Great. Excellent. Okay. And we do have the system 390 and the power PC equipment that's been donated or lent to us by IBM and it's ready to go. We just need to get it connected. All right. On to Windows installer then. Or Alex, anything else on the Docker build PR, rework PR? I need to go back and review it some more. I mean, it's a, some of the build scripts are fairly large changes. So I just want to do it local checkout and do a build and see how it compares. Great. All right. Thank you. Windows installer is next. So there has been some minimal testing done by Oleg. He found an issue and filed it. So that's what Sladen was referring to for the meeting. So I'm just working on fixing that. Sladen, if you are interested, there is a PR on the Jenkins CI packaging repository. It's got a long, there's a branch on that repository. It's like infra 910 is the start of the branch name. And that's where all the changes have been kind of put into in a pull request made for the new packaging setups. If you want to go look and see what the changes are, you're welcome to do that. Okay. Yeah, definitely. And there is a, there is likewise a PR to that same repository. Jing for tests of Linux install and service checks. Okay. Hey, Mark. What's, what's the general like status of 910? You guys got a working or like a proof of concept going? I've been seeing a bunch of IRC chats about like automation, automated releases. Yeah, it's, well, it's, it's making really great progress actually. So what we, what Alex had reported earlier is the Windows installer code that is in the context of the infra 910 PR. Oh, really? Okay. So the core release project is, is looking is making dramatic progress thanks to the availability now the signing certificates. Yeah, that was holding us up quite a bit for a while. Yeah. So maybe we ought to put that let's put that as a separate top level item Jim just so that we, because that's a good one to report on and give some guesses. So, Mark, wait, and Mark, and Alex. Well, that, like, you know, once once the core release is all, all good and closed out. Well that affects how we do releases of the Docker images. Now we have it does not they are distinct processes so release project is focused on MSI installer, the Jenkins war file and the Debian package and the RPM packages to different variants of RPM, but it's not touching the Docker release project so that that is still yet to be done. Okay. I think we would want to at some point what when it releases done kick off something within the Docker build to build for that new version that has been released, but that has been fully discussed at this point I think. Okay, yeah, I was thinking something along the same lines like trigger something off that pipeline, which then triggers our build pipeline, which that PR that I have open still might help with that. But we're still working on that so. Yeah, I'm planning on looking at your PR a bit more in depth and doing some local builds and stuff like that just to get a little bit more understanding of the changes. Yeah, no no no rush I know a lot of people working on 910 so getting that up and going. Great. So and Jim I'm going to I've moved the series 390 the system 390 topic earlier in the list so that we make sure we get there. Anything else Alex on Windows installer. I mean, hopefully we'll just it'll just get out of the open and be used more and I'm sure there'll be issues found and so forth so looking forward to it's been a long time since I started that work. Exactly. So needs more testing. Yeah, good. In particular. Now, do you have any concern with regard to the 32 bit versus 64 bit transition so this is giving us now the ability on Windows to use a 64 bit JDK. Correct, so it'll use whatever JD so if the person wants to use a 32 bit JDK they're welcome to. They can put in the path to that JDK if they if they want to use a 64 bit. So it'll allow that as well. I mean there's nothing within. It's basically just setting up to run the Jenkins dot war file from the Windows service wrapper Windows service wrapper is net so it'll run on either 64 bit or 32 bit so. So, so it would am I correct in this note that it would allow someone to choose an open J9 JDK if they wanted. If that was installed, they just do it specify the path yes. So, Jim that might be a place where where your, your contacts may be interested in oh well shall we do some exploratory testing on this thing with open J9 on Windows. Yeah, I, I never never really touched the windows so that'll be really interesting to see. Alright, so, and right now it's, we're not testing that as far as I know I'm my focus is on adopt open JDK and 64 bit and we'll continue that way because that's, that'll be the 90% or more of the execution environments. Alright, anything else then Alex. No, I think that's all in Windows installer. Okay, the core release project then so this is in for 910. And this has been this is the concept here is, let's not require Koseki Kawaguchi as the only person who can release deliver release of Jenkins. And, and it's been an interesting ride so the code signing certificate has been received and is deployed. Test builds, test builds are running test builds are being tested and being checked. We found some issues in those checks so Alex you noted a Windows issue detected by Oleg. Yeah, it wasn't so much part of the core release projects, but he was able to test the installer and found the issue so. Right, which is part of this transition and I found a Linux issue that that's Alex is working on the issue from Oleg and Linux issue has been found our Linux issues been found and Olivia has already fixed it and delivered new new code for that work. There are still many compatibility checks. They are needed. You know packaging compatibility weird. We're changing a bunch of things and therefore we got to check all sorts of things aren't broken. It's looking promising though and we'll continue, continue building and testing until we're done. Any questions there. All right, so then let's go on to series 390 assistant 390. I keep saying the wrong way, and power PC. I've confirmed that the power, the power infrastructure is now directly accessible. Awesome. Yeah, I think we we punched a hole and for you guys for SSH so no jumpers right. No jump post required thanks. I'm managing my my power PC agents with with the usual SSH agents plug in that I use with every other plug in with every other agent. So you've made my life much simpler. And sdx agents agents are also directly accessible. And, and, and both of them are running on test. Don't yet have is need to attach those to see I got Jenkins.io. Yeah, that will need to likely need to wait. It's currently delayed by the core out of release automation project. So my suspicion is we're still a week or two away from touching that. Okay. Now I could, I could do a spot connection of those. One off rather than systematically connecting them with the automation, but my thought was better to do it the right way and, and be sure that Olivier's involved so I'm not the single point of failure. Yeah, no, and that's what I got from the IRC chats, Olivia. It was like, Hey, we're focusing on, you know, 910 right now and we'll swing back around for connecting things. All right. Anything else on s390 or the power PC project. No. Okay, so next topic was platform roadmap and here I wanted to show what Oleg has created for us. Thanks very much by the way I think it looks gorgeous. If we look, go down to governance and structure. Project roadmap. I'm going to make this big enough to actually read. What you'll see is a working draft of the Jenkins roadmap visualized. And if we look at packaging and platform support. Here's how we phrased it Docker for 390 Docker for arm as the columns here are current things we're working now Docker for power PC 64 and a new windows installer. Arm and multi platform Docker now actually thinking about it. Have I placed the multi platform Docker images in the wrong location because aren't they required in order to do s390 and power PC. No, you can have standalone images on your. What's the unofficial Jenkins repository experimental. You can have them on those, or you can just pull down the specific images and tags. The multi platform kind of manifests will allow you to be like Jenkins LTS right, which then it will know and look up what architecture running on and pull down the right corresponding image. Okay, so, so this makes sense that we could do we can do Docker for s390 as as a specific tag first and then later we could do multi platform Docker images to make it easier to use them. Yeah, okay, got it. Thank you. Great. So now what I had done to to express that I created three epics in the JIRA tracker for s390 for power PC and for arm 64 figuring we'll use the epics to to capture the capture related tickets. And one of the items, there were a number of opops, it's already here, open Jane nine bug reports that I thought, oh, we may need to be aware of these Jane nine bug reports particularly on s390 where Jane nine is is the best way to run it with Java eight with Java 11 I understand that that you can run it full performance with Java 11, even with adopt open JDK but with JDK eight you've got to use Jane nine. Yeah, this is really good. So I can take those others been sent over to the Jane nine like bug tracker on GitHub or anything like that. No, right now they're, they're just open, they're open, and many of them just need to be evaluated. I'm not even sure if they, I'm not sure if they're still real. If they, for instance, this one that says job sitting in the queue waiting for the next available executor probably just need somebody to sit down with it and test it. See if they can duplicate it and if not propose to close it as cannot duplicate it. Okay. So Alex you were saying something and I interrupted. No, I was just agreeing with you. Do you mind pasting in the roadmap URL. Oh, you bet. Yeah, absolutely. Yeah, thank you. Yeah, it's, I think it's still. Oleg still correctly considers it prototype. Yeah, you know it's still in under evaluation so it's not a not being it's not been put into the into the, what do you call it into the dashboard. What the hell embarrassing the billboard know what is. No, no, no, it's, it's this thing right here when I go to this page, this scrolly thing at the bottom. You might not remembering the word for it. That's really pathetic. John John. Oh, bless you. Who said that that was excellent. Thank you. Yes, it's not in the jumbotron yet when as it becomes more, more clear, I suspect we will add it to the jumbotron. Thank you. Thank you very much. All right, so open j9 issues need investigation and particularly on s390. That's that's crucial with JDK eight. Now do you have a sense Jim is JDK 11 more popular on s390 or is it is JDK eight still a popular thing like it is in the 64 bit Intel world. I think both of them are still very popular. I couldn't really say either or. I mean, if the underlying application requires eight and obviously go with eight. Yeah, and in our case we officially support and many of us actively use JDK 11 for instance ci.jankins.io is running on JDK 11. So we're running large installations on Java 11, but, but if you've got somebody says no I'm going to run eight, then they really are, they've got open j9 for sure then. You mentioned you didn't you swap the agents from up above to Java 11. Actually, you know, I'm, I'm running, I'm running open j9, eight and 11 and right now my environment j Java eight so JDK eight with, but that's just agents right so agents on open j on JDK eight with s390 x and ppc. So I know we talked about was like, you just totally eliminate all this confusion. If you just went to 11 and just to pull down hotspot or whatever you usually use. Right exactly. And that may be something that we want to guide people to as we get to the point of documenting it. Good. Okay, so s390. So anything particular that you wanted to note, I think I put similar things in the, in the power PC one because there were some that are specific power PC issues that have been previously reported. So you may want to invite your power PC team to go exploring. Yeah, let me all point to that. I was, I was impressed at the number of issue reports that were there, like, wow, that's good people are already doing this and it was working for them. And as I did something similar with arm 64 there, there were, again, some interesting things of people who had reported issues on arm. All right, so now, those epics, I had, I had framed them with my phrasing, Jim you should feel free if you feel like hey marks phrase this badly it needs to be phrased differently smarter better. And make those corrections, or if you would like to put some priorities on hey we should do this first rather than that. Those are, this is freely editable and you are welcome to edit and adapt anything else with regard to platform roadmap then. So next topic arm 64 status report. I think there right now the answer is, we know that we've got Alex, you noted we've got AWS has arm 64 instances. We have, we have them set up on, on ci dot Jenkins.io for it under AWS for virtual machine agents. So, we just don't have anything to run on there right now. So we could come up with a test and build a plugin on there, or something like that but we don't really have any workloads right now to run on there. Okay, so, well, that's, I wasn't aware of that I could have been borrowing capacity so, so how are they labeled on ci dot Jenkins.io. Let me look give me just a minute. I think it's just arm 64 but let me double check. So they're not labeled with Docker out war. Right now they're not that's correct. Okay, and I guess that makes sense because right now our Docker images are assuming Intel architecture. Okay, so available. That's interesting because that means I could do some experiments with with certain certain plugins. They are labeled as arm 64. Okay. And open JDK installed. They should be the exact same as the the x86 Linux agents. Excellent. Okay. You've been to 1804 just like the x86 or AMD 64. They should have the exact same setup. Wonderful. Oh, that's really great. Thank you. Okay, good. Anything else on arm 64. Okay. So, let's see Matt, have you joined us. I haven't looked at participants recently, but no he hasn't. No, okay, so we will defer this one for another time. The reason that Matt sicker is a is a Java or is a an Apache, I believe, board member and active participant in Apache projects and therefore follows Java release plans quite closely so we wanted to leverage his and he's also a developer on Jenkins. So we wanted to use use his knowledge and his experience to have him share with us. What's coming in Java. He agreed to do it, but I failed to put it on his calendar is based in Chicago in the United States and therefore this is a little early for him yet. So we'll defer that for another week. And Docker PR status in progress. Alex, anything you would like to share there. I just need to go review it further in depth I have done some cursory reviews and things that good but I want to go and do some more in depth stuff since this kind of a bigger change than the other ones. It's a good off the top of just looking. This is the one that changes us to do multi platform is that right. This is Jim's PR. So, feel free to hit me up on IRC if you have any questions. Sure, we'll do. Well, and it's one that I need to get involved in and that it's one of those where we, we, it's making a major change. And if we break something catastrophically we have hundreds of thousands of people who start telling us we made a mistake. So, yeah. It'd be nice to have more eyes on it too. I'm not, not a God when it comes to programming. I don't think any of us are exactly there are plenty of plenty of failures in my life to remind me that I make mistakes all the time. Great. Any other topics that we need to review here in our platform special interest group. Alright, then I'm going to go ahead and stop the recording. Thanks very much everyone for being here, and we will see you in two weeks. Thanks, Mark. Thank you, mom. Thank you. Bye.