Jenkins Platform SIG, 7 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Platform SIG 2020 05 07

Description

Jenkins Platform SIG met 7 May 2020 to discuss Google Summer of Code projects, Roadmap topics related to platform, Core release automation, agents for s390x, PowerPC, and ARM 42, Docker image renaming, and Google Season of Docs

A

Welcome everyone: this is the platform special interest group meeting. It's the 7th of May thanks for joining us. Let's look at our agenda and then we'll work through it.

A

So an action items. Google Summer of Code, wanted to do a core release: project topic platform roadmap, quick review as 390 infrastructure, progress, dr.p our status windows installer, possibly if Alex joins us, not sure he'll be available there.

A

Likewise for plug-in, install manager and then Oleg did you want to wanted to hear from you a brief status on the in agent image, renaming Google season of Docs and Google Summer of Code projects added yeah.

B

Edit it because you're really touching the only plug-in, but we have two or three depending on who you ask projects which, also, in this platform, seek great.

A

Let's, let's cover that, actually, why don't we put all of them? Let's move that one right up into the early early spot there and, let's put the whole put all of them and we'll just make that one, a sub bullet.

A

Anything else we need to add the agenda.

A

Okay, then, let's, let's go ahead so open action items I have a new item that we added today. We want to switch so that our meetings in general are using the continuous delivery foundation. Zoom account rather than personal zoom accounts. I'll make that switch using the invite that I received from Oleg I still have the docker operating system support action item open my apologies: still there Oleg the open the windows, support policy, I, think that will go ahead. Yeah.

B

So you had a discussion in the developer manually stable. If you have enough it worth to proceed. So my action item is get it done. I wanted to finish the image rename first, but then I will definitely take a look at this story. Maybe after spending some time, this other I'm going to request like images for caches, because so they also need some time to be spent.

B

But the after that I believe that they are not blocked window support and it's a good time to actually get it done because, for example, one of our what project would depend on this story in terms of framework waste lines, we need to support.

A

Thank you all right, then. We've still got the docker build: rework PR, my apologies. I have done no reviews on that. In the intervening two weeks.

A

We do have the infrastructure ready to support it, or at least we've got the infrastructure ready on Sierra Jenkins that I own to support it. But we don't yet have the the reviews necessary to get it done.

A

Next topic: google Summer of Code projects.

A

So, oh like how about if we just open those- and let's take a look here quickly at let you review the ones that we would, we think, would fit well to put them under the umbrella of the platform. Sig.

B

So I will summarize the current state, so my.

B

Project we have seven projects accepted and total in our organization, six projects, Talbot Jenkins, and there are projects which I directly related to the platform special and festive so, for example, first project in the newest custom, Jenkins distribution, build service by Slaton.

B

So last time we see- and it's also headed to the fat16 roadmap- is in the current state.

B

There are other projects we have it's giving in performance improvement, which is somewhat related platform cheek because think it is just a common tool, so my empirical, and to have it under there all this seek or maybe ages other platformer. So with something to be discussed. Then a third project we had this Jenkins winter services, so windows support is definitely within their basic scope and we will be doing regular updates at the seek meetings about how to Lisa this project or one.

B

We already have some prototypes and hopefully we'll be able to iterate quickly with that. So this is one of the projects you, where you like, a start coding period early and by the way. If someone is interested, there will be a project meeting today to paint mean which I will share. The link and the first project, which is probably related to bathroom seek is external, fingerprint storage.

B

So, historically a pluggable storage stories are handled, thunder and roll off are called native, especially interested, but the HST. This special interest group is still government. Secondly, valuable storage, etcetera. You don't have to be in the code to get benefits from the stories. For me, it's rather part of the platform, so I would be hesitant about putting PDA in the base code, because the scope for the seek is already bloated. So we had some discussion with mark a week ago so about potentially speaking basic into well.

B

We should be focusing on distributions and packaging and another one which would be focusing on our platform, teachers, foundation, features or whatever you call it for the project, but we haven't discussion official here. So if anyone is interested to contribute, I think we all started and they Sigma increased once very then.

A

Actually, that's a good one. I should have put that on the agenda. We should be sure we, so that's splitting the cig into two interest groups and I liked your description of them. It was one was packaging and the other phrasing in the.

B

Application and distributions.

B

The second one is foundation, features core features, so core features can be a bit confusing because corphish's, it's not vouching. It's called so.

A

B

Get plugin for me is a core feature by applying the plug-in cipher fiction, but yeah foundation features might be.

A

Yeah I see what you're saying yeah very good. This is.

B

B

Doctor packaging, I guess Java support would stay skinny as well. Oh yes, absolutely well!

B

Arguably it could be a foundation or it could be something else, but it really depends on the number of contributors and reckon of the number contributors is not high. So basically I wouldn't touch it good. Okay,.

A

Excellent. Thank you anything else on google Summer of Code I.

B

Think specific Ann, so we have just started coming into bonding, so all project teams will be meeting organizing channels and once it's done probably or the next week, you'll have a blog post with the summary with links to project and after that I think we will be encouraging called students to join sig meetings so that they can present other projects. They can I meet wider community ñ yeah we target next week, or maybe even I in two weeks. What's a.

A

Great excellent, thank you all right, I think we've already covered the splitting the cig into two interest groups topic need some further discussion on the mailing list. That discussion will happen. Yeah.

B

It's not my immediate priority, because, but the in principle splitting seeks in such way you would be reasonable. Just not making other agendas focused, because you can take a look at this list. We have 12 topics or so so, yeah.

A

Right and and and as we add students to it as soon as we get to six or eight people in a meeting, we run the risk of just over running the ability to be effective. So I like that I'm good next topic, brief status on core release project, so we've released to 233 234 and to 235 as Jenkins release is delivered by core release. Automation and to 235 has been selected as the next LPS baseline.

A

That that means.

A

That means test heavily asked a lot right. We've got about six weeks before the LPS is released and we need to check all sorts of things had an interesting when yesterday the Daniel Beck submitted a fix for on Internet Explorer 11 support for it. So it's there's plenty to be learned and plenty to be tested.

A

The next thing coming for the core release project is security, release and LTS release and that's support for those.

A

This is not an announcement of a security release. This is rather support to do security releases when needed.

B

So you need to use the previous automation infrastructure so right, basically, we depend on key key to cut, reduces.

A

Yep: okay, a platform roadmap I just captured this picture of the current state, although I guess one way of reminding where we are right now anything you wanted to talk to on platform roadmap as it's evolved in the last.

B

Mmm-Hmm we have some other stories which are not listed on this road map. For example, agent renaming is tracked in advocacy and outreach Sigma. But let's talk only about the me she gives on the screenshot, so docket images for Windows there, basically ready to be released. We've had a discussion about what should be the baseline for the release last time, but we in principle we have tested them. We use the common flow for shipping, so we are ready to go and basically Alexa just make announcements and that we can consider this is computer.

B

And actually the same for new windows installer so for new windows, installer vo ship really clear to leaders with been doing Scudder, but there is a tricky thing that new windows installer actually requires new build scripts. So that's why this project has been delayed for almost one year, because we do leaders with new installer on the owner, Newark resubmission environment and a as things stay right now for security and OTS readiness. We won't be able to ship the new Windows Explorer.

B

So, although the story is formally completed at the same time, it's not completed so I'm, not exactly sure. What should we do here? I would.

A

B

Yeah I would personally prefer to wait until it's an old Sears but yeah. Hopefully there is no work to be done there, except getting cover this automation over the line, and we had taken these two stories completed. We have dr. families for IBM now and we have our EC and open j9, so I think we should privatize this Taurus and try to get them over the line so that we can be already delayed for months.

B

So if you could spend some time on finish and then it would be great- and there are also other stories which we like, we need to move between progress. Cousin Jake is distribution service, just because sled in May will go working on that in JSOC. So it's a done deal and another story which we probably need to move is immigration to adopt open. She became distributions, but as one present each other a with open packages, because that was no longer official, openjdk images, Oh Alpine I.

A

Thought that Jim had told us that there was it that they had just, although maybe it isn't fish official. Yet.

B

Maybe for high versions, not for GDP, only I'm talking about opportunity right. If you talk about adopt open, G Dickey, there are distributions for that. Oh, oh.

A

Oh I see wait a sec, so maybe I misunderstood. So you were talking to migration to adopt OpenJDK, but you're saying that Alpine does not have an open JDK image is that right did I understand.

B

Well opens the key which doesn't have a plan. We are all right, the inverse! Thank you, but yeah anyway, Alec sort of has already submitted the political post for master images. We don't need to do the same for agents, but I think that at least for pine we should switch as soon as possible because we all would be behind bug fixes and for other images.

B

We issue those I think about this story, but for me just prior to the trial, pine and follow pine, and we have less risk of breaking things because all pine gives already stripped. So there should be no significant difference between open, open JDK and the Alpine adopt open a sneaky right.

A

Right good point: yes, I! Think more.

C

I think the open JDK version with Alpine was Java 16 early access. So it's not even usable right now.

A

Okay, so which really means it's got to be adopt for because there we're running something right now on Alpine, but it's some something not from not from the open JDK project and not from adopt OpenJDK. Okay,.

B

No, our official open images are based on a 3d key right now they are but adopt open, sorry, open, GD, key images are not supplied by oracle or by open JDK team. They supplied actually by docker somebody for currently maintains them so yeah. This images have always been a bit behind and less maintained that open JDK, but you know they just stop, should be increased and it's understandable, but we still support Java 8.

B

We are still interested in providing Kalpana images, at least for agents, so I would suggest that we agree to adopt open GDP, they're, shorter, okay,.

A

Any other that you wanted to add to the list relative to platform to roadmap colleague, I.

B

Think it's quite parked over again. Okay. For me, it would be finishing pending stories, I opened a gym and other contributors to get Python packages over the line, and after that we can clean up the rest and a minion list.

A

Great all right speaking of platform packages, s/390 and PowerPC infrastructure, so agents are connected to CI a-- jenkins at I/o and they are actively used.

C

A

Yeah, well, that's that and so the the let's see we've got agent. Provisioning automation is still needed.

A

That's a I think Olivier told me: it is puppet based automation,.

A

But it's it's functional as it sits today, so it's usable already and I know I'm using it, and there are other other others that are using it as well.

A

Then, on the darker PR status, that's a needs, review and test.

A

Well, it will excuse me, will need an upgrade guide or will is the sense that will need an upgrade guide, because there will likely be changes as part of that.

C

For the experimental images, yeah I guess all this is just the experimental, so it does not affect normal docker packaging. So yeah there will be a little updates. I guess to how you guys are handling your publishing of experimental, oh gee. No, the experimental should actually a couple there's a couple additional tags, but all the tags should exist. All the same kind of should exist or just a couple different ones. Yet.

A

So maybe maybe what it is, is a blog post to announce it and encourage and invite people to to to test and experiment. Yeah.

C

And it's really cool to see like Alex, that the you know the Amazon arms before working. Oh, that's, nice! Now we have access to all the architectures that you guys are supporting so.

A

A

Okay, sudden next up- and there really is more reviews and merge to urge to experimental and then eventually merge to release yeah test, which will merge to release great all right. Alex, isn't here so I'm gonna take the windows installer just so that those who are here are aware of what what's happening there. Core release. Automation is not delivering a zip file that it used to deliver, and so Alex and I had an exchange in IRC, as he was looking hey.

A

What's the download location, so we've got some work still to do on core release: automation with regard to Windows installing it.

B

Was based a couple of weeks ago, unbelieva the residue a ticket for that originally it was done as an enhancement, because there is no practical need to compress a massage.

B

Firstly, our download site wasn't ready to date right now.

B

Basically, management otherwise is broken, and they believe that we haven't updated it for the worst weekly release, and this is just a minor fix, but we need to apply this fix.

A

That's that's really and I think you're right there. Really there isn't. The msi is already well compressed, zip, zip being that thing doesn't buy us a whole lot compared to just leaving the msi. Well.

B

It's fun to ship both.

B

Also, when you download a massage that gives opportunities for tools like antivirus car, knives, etcetera to check images, msi signed correctly so or not, yeah they assigned correctly. So it would be better to provide a massage on our download site, which.

A

Which is the default and when I click through the download link, when I click the download link from the jenkins download page for weeklies for windows, it does in fact download the MSI to my machine. So yeah.

B

Right because we have to call in to them into a Maasai raw update site is still broken, so it doesn't supply proper, gig and I had to just apply a pull request or inject a direct download link.

B

Ok, so we basically need to update packaging SEO and mirrors changes I out or properly chef for Emma, sighs.

B

You said package and what was the other than mirrors, but yeah, basically, eight. So the same now.

B

So since we see synchronization to package, we just have to fix it in one place.

A

Excellent okay, I'm gonna drop the plugin installation manager topic. It was when we had listed for a head for Alex two weeks ago. We'll have him discussed later Oh, like I, had put agent image renaming on just wanted to give you a chance to share with us the current state there and the progress. Okay.

B

Want me to share the screen Lord! Oh.

A

That would be great, oh.

B

A

Yeah I could certainly open the blog post as well. Let me just do that. What save time then? Okay.

B

So yeah it's a fresh foot post, but actually the changes took place in mid-april and why we didn't post announcements say immediately is because we had ongoing discussion on how to properly my agents voices age but yeah. What changed we renamed. Official images should be used by Jenkins users, so it's very similar to Jenkins agent, it's an inbound agent which is used basically for connection origin or before by TCP or a WebSocket, and there is also a stationary agent image. So all these three images got new names.

B

Also as a part of this change, we streamlined deployment of Windows images so now Windows images, I deployed on the same location and that's why I said that we are ready to the least use Windows support, but a student announced that but yep the main thing that this image is a finally updated, and it was one of the most problematic areas of agent slave to agent renaming we had in Jenkins Iran was just four years ago, but unfortunately, the images which too old.

B

Getting some criticism because other offensive things so finally, then renamed we still have a lot of slave mentions across the organization. So if you want to github query that or something like this I don't mention of slave, some of them are fixable some of the very fixable. But we need to keep working on that, but two main areas have been addressed so obese training and several months ago, name of a city built ancients, bring him so we're working on the stories and in this blog post, I also used portunity to hint the incoming stories.

B

So if you scroll down the resource, what's next section, basically is the very pattern, six initiatives, but if we think I saw some contributors, it would be. Nice would see ya I'm, just using opportunity of having cloud map and recent stories from there.

A

Excellent now you mentioned that the windows images are now coming through are now available through this through docker hub through the usual.

B

With available, we just aligned, because before that we were shipping X images to one location and windows, images to another location.

B

Historically, it was done because of docker hub, audible communications, but now we just deployed to the same location, UNIX images I still built by dr. Hart Oh to build windows images by trusted si. So it's the Jenkins instance for shipping releases.

B

Right now, under the same roof, so it doesn't matter wish to reuse to ship the releases and I believe it at some point. You do switch UNIX built for our CI instance as well. Now, actually see me instance, because we need to replace packages, but whatever.

A

Thank you thanks very much yeah.

B

So I hope we will have enhancement for Windows images, maybe in one or two weeks grated.

A

I had put google season of darks application submitted. If anything you want to describe their oleg before we conclude yeah.

B

So yeah it submitted it's something which is being produced so next week. Actually on Monday we'll have response from Google with our application is accept it or not. If we accept it, we will have one project where technical right that would be working on a particular area for the communication and what we discussed last time. If, if the platform, she has any ideas, what could be improved to there just go to our whole season of dogs website and suggest the project ban.

B

Yeah and if you talk about facilitating documentation, there is another income and project ego I. You expect one. We plan to host it in the late me and one of the stories today is user, documentation and user. Documentation surprisingly includes installation guidelines, for example, in studying click on windows and siding with a in docker, etcetera, etcetera. And so, if somebody is interested, we could try these stories as a partial, this hot, just official announcements for that I plan to ship message on Monday as well.

A

Great well and weekly trains transformation, so the wiki to Jenkins that IO transformation will be part of that. Yes,.

B

It will I'm not sure how much is related to platform sick. Oh there.

A

A

Yeah and for in my case, there are a number of platform, specific things that are still still need to be transferred there. Things like the reverse proxy setup and.

A

Some API things are all sorts of interesting platform, specific topics that are not yet migrated, yeah.

B

So anyway, it's a gradual process so again for wider scale initiatives. We could try a google seasonal dogs, though it's one project, it might be a competitive program, so it really depends from applications on the interest of technical writers and for you, a year excited on it's totally doable but yeah. The time training mode will be quite tight. So if you want to look at something which happening next week,.

A

Any other topics we need to cover in the platform sig today.

A

Jim anything from you.

C

A

C

Think I'm good all.

A

Right thanks, everybody will end. This recording will be archived later today, thanks very, very much bye.