Jenkins Platform SIG, 29 Aug 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Platform SIG 2019 08 29

Description

Jenkins platform special interest group from August 29, 2019. Topics include multi-architecture Docker image support, Windows installer progress, and DevOps World | Jenkins World 2019

A

A

Thanks everybody welcome to the platform special interest group meeting. Let's take a look at our agenda today.

A

You share my screen and here we go make it big enough that I can read it with my poor eyes, how's that okay, so just to review the agenda topics first and then we'll actually run through the will actually do the agenda so open action items. We had an item from last time on Natasha talking about the plug-in installation manager since I don't see her yet in the meeting. I assume will delay this. When she's back to school now, release drafter progress. Oleg won't be able to attend, so we will delay that one.

A

So that's prolly defer and Natasha's. We will also defer I assume since she's on the East Coast now again that this may be a workable time for her Oleg had a topic asking if we should move the configuration as code plug-in work from the cloud native special interest group to the platform special interest group I propose we defer it. While we wait for him to arrive, then we had Alex docker multi arch status, you okay with that on the agenda. Alex yeah.

B

A

Thank you, then Windows installer status, Alex, also, okay, on the agenda. Yes, I'm, good, okay and then a brief report on Jenkins world DevOps world from me, Marquis anything that you need to get onto the agenda.

C

Nothing for me right. They got me mostly watching this time and then I'm sure. Next, one I will great.

A

All right, no problem great to have you here super. So let's take a look at the open action items and if I'm really smart I can make that so we don't have a title bar great, so I still and I apologize. This is getting embarrassing. I have not opened the for the proposed rules: du docker operating system, support and platform selection rules. We have already adopted the CentOS and my apologies for the noise. In the background my hotel room air conditioner just switched on, so we have adopted CentOS as a supported platform. It's now delivered.

A

We did it without following any particular approval process. So Oleg has an action item to open a for Windows support policy, same issue Alex your ongoing discussions with only only be able to mean on code signing anything you'd like to report there. Yeah.

B

So we found out that it's basically as easy as opening a issue on the github repository in the PDF. So he did that and George's waiting for that to occur. We're not sure how long it'll take, but the process is fairly easy. So we'll try and document that in this case, meaning in the future great.

A

Thanks very much so that is, that is that action is done waiting for them super okay. We had the new meeting time proposal action item and that is now done and we're meeting at the new time I'm going to put a new action items now meeting at new time. Mark.

A

To announce more widely, so that others are aware of the change I had announced that in the Gitter channel, but did not send it to the mailing list, did not send it to the dev list or anywhere else all right. So then we're gonna defer the topic for plugin installation manager and for a release. Drafter moving the java configuration is code, plug-in maintenance effort and the project to the platform.

A

Sig feels good to me personally, because I like getting more information from the meeting, rather than less they're, currently in the cloud native sig, that is kind of quiet, but let's wait until Oleg is able to attend before we actually make that have that discussion in further depth.

A

Alex, you want to give us a report on darker multi, arch and I'm gonna mute, my phone, so that are my source so that you don't have to hear my loud obnoxious, sound.

B

So the update on the multi arch- that's theirs, I, believe it is complete in terms of being merged in the Jenkins eval branch. So that is current. That branch it's currently building and publishing it all the images for the different architectures on Jenkins that IO the next step is going to be getting feedback on those images from various people and then merging that experimental publish into the normal publish script so that it's done on trusted and in the Dinkin organization on docker hub.

C

Alex I started doing some work. I have not gotten the PRS and I'm hoping to do that next week. In changing some of the naming, so I've had a conversation with Oleg to remove some of the sort of legacy naming like the word slave, so I plan to get that work in there and I think you'll, recall Oleg said a while ago, Oh Marc, you may be interested in the work that you're doing.

B

With often that's definitely needed for sure yeah.

C

There's a lot of changes, though, that go that once I started peeling back that that the layers of that it I realized the actual extent of that so it'll be definitely a large, a large body of work. Yeah.

B

I know the the window stuffs I've done for the difference like dr. Slavin, dr. ssh slave and dr. jane LP slave repositories at all use the word agent. So hopefully there's something, there's an easy fix, cool.

C

Thank you very much for everything that you've done so far. It.

B

Helped me learn more about docker. I didn't really know anything about docker to begin with one great way: trial-by-fire do.

C

A

All right thanks very much anything else that you wanted a report on so so just to be sure Alex. That means that arm 64 image and s and 390x image is now being now being published under the Jenkins for eval docker hub tree with tags there and everything. That's.

B

Correct yeah there's also power. Powerpc image was being published as well. Okay,.

A

So that's a TPC 64 le2 idea. I, remember right! Yeah.

B

A

Great, that's really.

B

Good, thank you and I need to send something out on the mailing list, probably the best mailing list, not actually probably the users mailing list actually about those images being available because I know they're gonna was kind of the driving force for the yesterday. 90 x1, but it'd be good to get other people to use the other images and get some feedback as well.

A

Excellent. Thank you. Okay, yeah, so I'll put that as a put that into an action item for you to report in upcoming sessions. Thanks very much.

A

Anything else on docker, multi, Arch, no, no, okay, next topic does installer status. Alex back to you again, so.

B

Yep you know this: is we actually have the capability now to build this on CI that Jacob at I/o I've brought up some windows agents?

B

Could it allow us to do that, so we can actually build the Installer and then, as I mentioned before the code, signing cert is in process. So once that's done, we should be able to have a fully automated windows in the dollar bill.

A

Okay, so now you say: CI Jenkins are there what about trusted? See I trust.

B

It also has the capability, but it'll, be nice for the editing inside out to have that capability as well.

A

Silent and just for information will continuous delivery foundation, be the issue or the certificate whose name will be on the certificate. I think the old one had kousaka's name on or the current one has coasted days name on it. Will it now be a CDF certificate or that.

B

I believe that the case yes, so that the problem we've had is says that his code signing third only he can really use it right. Mommy.

C

B

That's been difficult to automate anything, so olivier has been really excited about this as well for his work on the automated relief of bingen.

A

Yeah excellent yeah kohsuke correctly, doesn't really want to place his personal code signing certificate on a public server or on an even a trusted public server. It's it's his certificate. That makes sense. Okay, thank you. Anything else on Windows installer status, um no I, don't Biko.

A

So the last topic I had on the agenda was a report on Jenkins world and DevOps world and I think the best answer there is refer to Marquis blog post I thought. That was an excellent summary of so many things that happened at Jenkins world DevOps room. Sorry that Alex, we didn't see you there, but great to have a large community. We had over 2,000 people in San Francisco and at the conference in total, really an amazing amazing effort.

C

It was really awesome: I, don't even think that blog post encompasses all of what took place there and what transpired so yeah, so slides.

A

Slides and video recordings are I think still being processed, but the commitment was that they will be made available.

A

There were some really positive results: great outcomes.

A

Those are all the had. Are there any other topics that we've missed.

A

C

A

To me nothing I can think of great. Then let's call this meeting done. I will save the recording and we will I'll post the recording later today and schedule us a next meeting in two weeks. Thanks everybody awesome have a good day. Everybody.