Jenkins Platform SIG, 9 Apr 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Platform SIG 2020 04 09

Description

Jenkins Platform Special Interest Group for April, 9, 2020 discussed the Jenkins core release project (INFRA-910), platform roadmap, Windows installer, IBM s390x, IBM PowerPC 64, ARM64, and multi-architecture docker image support

A

Oh 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 system, 390 and PowerPC infrastructure, progress, I guess should we also include there and arm 64, or do you want that? Is that better do done separately, Alex they're, really two different things: yeah.

A

B

Don't really need any special agents for that, so it's kind of a little separate right. Okay,.

A

So I'm sixty-four status report we may do the Java upcoming, not sure that, wouldn't that depends if Matt's able to join us, if not we'll, defer it for two weeks and darker PR status and progress, anything else that needs to be added to the agenda before we start working through it.

A

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 we will then update the text to know what the actual status is so open. A jet for doctor up any system support I still haven't done that windows support policy jet still pending windows, installer code, signing Alex. You want to share with us today, yeah.

B

It's 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.

A

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.

B

I think so excellent.

A

Thanks very much Alex. Thank you. Thank you for your heroics on that all right, then, dr. bill, PR, rework this one I think the the there is still intense interest for it and we'll continue working Alex. Anything you want to report there so.

B

It turns out there are no changes, the Jenkins file, so we didn't need a shadow here. So I just closed it great excellent.

A

Okay and we we do have the three system 390 and the PowerPC equipment- that's been donated or lent to us by IBM and it's ready to go. We just need to get it connected.

A

All right on to Windows, installer, then or Alex anything else on the dr. bill. Fiat rework! We are I need.

B

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 check out into a build and steel, to see how it compares great all right.

A

Thank you, windows, installers next, so.

B

There has been some minimal testing done by Oleg and he found an issue and filed it so that that's what Slayton was referring to for the meeting so I'm just working on fixing that slate. If you, if you are interested, there's a PR on the Jenkins CI packaging repository, it's got a long, there's a branch on that repository. It's like infra, 9 10, it's the start of the branch name and that's where all the changes have been kind of put into a Nepal request made for the new packaging setup.

B

So if you have, if you wanted to look and see what the changes are, you you're welcome to do that.

C

Okay, yeah definitely well.

A

Then there is a there is likewise a PR for that same repository.

A

Jing for tests of Linux install and service checks.

C

Hey Mark, what's what's the general like status of 910, you guys got it working or the concept going. I've been seeing a bunch of ire. She chats about like automation, releases, yeah,.

A

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 9 10 PR. Oh really,.

C

A

Core release project is is looking is making dramatic progress thanks to the availability now of the signing certificates yeah. That.

B

Was holding us.

A

Up quite a bit for a while yeah. So maybe we ought to put that. Let's put that as a separate top-level items Jim just so that we is that's a good one to report on and give some guesses, so Mark Waid and mark and Alex.

C

Now, um well that, like you know once once, the core release is all all good and then I closed out. Well, that affects how we do releases of the docker images. Now.

A

C

A

Does not they are distinct processes, so the core release project is focused on MSI installer, the Jenkins war file and the Debian package and the RPM packages, two different variants of RPM, but it's not touching the docker release project so that that is still yet to be done.

C

B

I think we would want to at some point when a release is done, kick off something within the docker build to build for that new version that has been released, but that.

C

B

Fully discussed at this point, I think yeah.

C

I was thinking someone along the same lines like triggered something off that pipeline, which then triggers our build pipeline or just at PR. That I have open still might help with that, but we're still working on that so yeah.

B

I'm planning on looking at your PR a bit more in depth and doing some local builds stuff like that, just to get a little bit more understanding of the changes. No.

C

No rush, I know a lot of people working on nine ten, so I mean I've been going great.

A

So and Jim I'm gonna I've moved this series three 90 the system, three ninety topic earlier in the list, so that we make sure we get there absolutely anything else. Alex on Windows, installer.

B

A

B

Mean hopefully, we'll just it'll just go out the open and be used more and I'm sure they'll be issues found and so forth. So, looking forward to it's been a long time since I started that work exactly.

A

This o needs more testing, yeah good in particular. Now do you have any concern with regard to the the 32-bit or 64-bit transition, so this is giving us now the ability on Windows to use a 64-bit, JDK correct.

B

So it'll use whatever JDK. 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, it will 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. What a service reference net so it'll run on neither 64-bit or 32-bit, so so II would.

A

Correct in this note that it would allow someone to choose an open, j9 JDK if they wanted. If.

B

That was installed they just they would specify the path. Yes, okay,.

A

So Jim that might be a place where, where your your context may be interested in, oh well, shall we do some exploratory testing on this thing, with open j9 on Windows.

C

Yeah I I never really touched the windows, so that would be really interesting to see. Okay.

A

All right 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 percent or more of the execution environments all right anything else, then Alex, no.

B

I think that's all in Windows the star. Okay,.

A

The core release project then so this is in four nine ten, and this has been. This is the concept here is: let's not require kohsuke kawaguchi as the only person who can release and deliver a release of Jenkins and, and it's been an interesting ride. So the code signing certificate has been received and is deployed, builds test, builds, are running, tests builds, are being tested and being checked.

A

We found some issues in those checks so Alex, you noted a Windows issue detected by Oleg yeah.

B

It wasn't so much part of the Corley's 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.

A

Linux issue that that's alex is working on the issue from oleg and.

A

Linux has been found, Ireland Fisher's been found and Olivia has already fixed it and delivered new code for that work. There are still many compatibility checks that 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.

A

It's looking promising, though, and we'll continue, continue, building and testing until we're done.

A

Any questions there.

A

All right so then, let's the series, 390 assistant, 390 I, keep saying the wrong way and PowerPC. So I've confirmed that the power, the power infrastructure is now directly accessible.

C

Awesome yeah I think we we punched a hole and for you guys for SSH no jump. Oh no.

A

Jump are acquired thanks very much I'm managing my my PowerPC agents, with with the usual SSH agents, plug-in that I used with every other plugin with every other agent. So you've made my life much simpler and scaling the X agents.

A

Agents are also directly accessible and I had, and both of them are running on tests.

A

You don't yet have is need to attach those to CI Jenkins at I/o and Olivier. That will need to likely need to wait. It's currently delayed by the core out of release, automation, project.

A

So my suspicion is we're still a week or two away from touching that: okay.

C

A

I could I could do a spot connection of those you know as a 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, ya.

C

Know and that's why I got from the IRC chats Olivier, it was like hey we're focusing on you, know, 9 10 right now and we'll swing back around for connecting things.

A

A

Anything else on is 390 or the powerpc project nope, okay, so next topic was platform roadmap and here I wanted to show what Olek 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.

A

Here, let's 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 that were working now, docker for PowerPC 64 on a new Windows installer and then docker, forearm and multi-platform docker. Now, actually thinking about it, have I placed the multi-platform, docker images in the wrong location because aren't think required in order to do s/390 and PowerPC.

C

Know you can have standalone images on your.

C

What's the unofficial, Jenkins repository, experimental yeah, you can have them on those or you can just pull down the specific image using 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 architects you're running on and pull down the right and correspond the image.

A

Okay, so so this makes sense, then we could do. We can do docker for s/390 as as a specific tag. First and then later we could do multi-platform, docker images to make it easier to use them. Mm-Hmm yeah, okay got it. Thank you alright!

A

So now what I had done to to express that I created three epochs in the JIRA tracker for s/390 for PowerPC and for arm 64 figuring? We use the FA to to capture the capture related tickets as one of the items there were a number of hopes. It's already here, open j9 bug reports that I thought. Oh, we may need to be aware of these j9 bug.

A

Reports particular on s/390, where j9 is, is the best way to run it with Java 8 with Java 11 I understand that that you can run at full performance with Java 11, even with adopt open JDK, but with JDK 8 you've got to use j9, okay,.

C

Yeah, this is really good, so I can take those had those been sent over to the j9 like bugtracker on. However, anything like that. No.

A

Right now, they're bears and they're just open, they're open, and many of them just need to be evaluated right now, you're, not even sure, if they I'm not sure, if they're still real, if they. If, for instance, this limit, says jobs sitting in the queue waiting for the next available, executors probably just needs somebody to sit down with it and test it see if they can duplicate it and, if not proposed to close it as cannot duplicate it.

A

A

So Alec you were saying something and I interrupted. No.

B

I was just agreeing with you.

C

Mark, do you mind pasting in the.

C

The roadmap URL.

A

Oh, you bet yeah, absolutely yeah. Thank you! Yeah. It's I think it's still Oleg still correctly considers it prototype mm-hmm. You know it's still in under evaluation, so it's not a not being it's not been put into the into the whether you call it into the dashboard right. How embarrassing the Billboard know what is sigmap? No! No! No! It's it's! This thing right here when I go to this page. This scrolling thing at the bottom, forgive my not remembering the word for it. That's really pathetic, withdrawn.

A

Tron 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.

C

A

Right so open je9 issues need investigation and particularly on its 390, that's that's crucial with JDK 8 now. Do you have a sense? Jim is JDK 11 more popular on s/390 or is it is JDK 8 still a popular thing like it is in the the 64-bit Intel world.

C

It seems both of them are still very popular, I couldn't really say either or I mean if the underlying application requires 8 and also go with a so.

A

Yeah, and in our case, we officially support and many of us actively use, JDK 11, for instance, CIO Jenkins, that IO is running on jdk 11 me.

C

A

We're running large installations on Java 11, but but if you've got somebody says no I'm gonna run eight, then they really are they've got open, j9 for sure, then yeah.

C

You mentioned you, didn't you swap the agents from up above to Java 11, actually.

A

You know I'm I'm, running I'm, running open, j9, 8 and 11, and right now my environment Java 8, so they do great with, but that's just agents right so agent on open G on JDK, with s3 90, X and PPC. So.

C

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.

A

Like right exactly and and that may be something that we want to guide people to as we get to the point of documenting it, mm-hmm.

C

A

Okay, so s/390 anything, particularly that you wanted to note. I think I put similar things in the in the PowerPC one, because there were some that are suppose cific powerpc issues that had been previously reported. So you may want to invite your PowerPC team to go exploring yeah.

C

Let me all point to that: I was.

A

I was impressed at the number of issue reports that were there, it's like wow, that's good people are already doing this and it was working for them and.

A

Then likewise, I did something similar with arm 64 there. There were again some interesting things of people who had reported issues on arm.

A

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, go right ahead 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 to edit and adapt.

A

Anything else with regard from roadmap thing.

A

A

Okay, so next topic arm 64 status report I. Think there right now. The answer is, we know that we've got Alex, you had noted, we've got AWS has arm 64 instances. Next.

B

We have, we haven't, set up on NCI Jenkins dot IO for 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 the test and build a plug-in on there or something like that, but we don't really have any workloads right now to run on there. Oh ok.

A

So well, that's I wasn't aware of that. I could have been borrowing capacity. So so, how are they labeled on see? I thought Jenkins thought I. Oh, let.

B

Me look, give me just a minute: I think it's just arm 64, but let me know check so.

A

They're not labeled with docker or all right.

B

No they're not that's correct, okay and.

A

I guess that makes sense, because, right now our docker images are assuming Intel Architecture right, okay, so available. That's interesting, because that means I could do some experiments with with certain certain plugins. They.

B

Are labeled as arm 64.

A

And open JDK installed, they.

B

Should be the exact same as the.

B

The the x86 Linux agents unto you a bunch of 18:04, just like the x86 or AMD 64. They should have the exact same set up.

A

Wonderful! That's really great! Thank you. Okay, good anything else on arm 64.

A

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 the Matt's occur 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.

A

What's coming in Java, he agreed to do it, but I failed to put it on his calendar he's 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 then dr.p our status and progress Alex. Anything you would like to fear there I just.

B

Need to go review it further in depth. I've done some cursory reviews and things look good I I want to go and do some more in debt such as this kind of a bigger change, then than other ones.

A

B

Good off the top of just looking.

A

This is the one that changes us to do multi-platform is that right, that's correct! This is Jim's here.

C

Feel free to hit me up on IRC view any questions, I'm sure we'll do.

A

Well and it's one that I need to get involved in and there it's as one of those where we it's making a major change, and if we make something catastrophic ly, we have hundreds of thousands of people who start telling us. We made a mistake so yeah.

C

Be nice to have more eyes on it too, all right, I'm, not not a god when it comes to programming, I, don't think any of us are exactly.

A

There are plenty plenty of plenty of failures and, in my life to remind me that I make mistakes all the time great, any other topics we need to review here in our platform special interest group, you.

A

You alright, then I'm gonna go ahead and stop the recording thanks very much everyone for being here, and we will see you in two weeks thanks Burke thank.

C