Jenkins Platform SIG, 4 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Platform SIG 2020 06 04

Description

Jenkins platform special interest group session June 4, 2020 included a report from the Google Summer of Code project 'winsw support YAML configuration', the Windows platform support policy, and the Git plugin performance improvement project. Brief status report was also provided on plans for the Alpine image updates to the latest JDK version

A

I, this is the Jenkins platform special interest group. It's the 4th of June 2020. Welcome everyone.

A

Let's go ahead, I'm going to share my screen and let's look at the agenda to be sure that we've got all the topics we want to cover. So talking about open action, items, ban windows, service wrapper for supporting Windows Windows servers, wrapper support for llamó parsing.

A

Windows support policy. Oleg then I'll give a brief summary of the get plugin performance. Google Summer of Code project that rishabh is working on and if Slayton happens, to join us, we'll do custom Jenkins built service project. I can talk to docker images and alpine. Briefly, as a discussion topic, any other topics you need to add to the agenda.

B

I, don't think so. Okay, so.

A

On the action items the we are using, the CDF zoom account now. So that's in progress but needs a needs. A pull request to show to place the new URL into the calendar.

B

So coriander is not diminished by pull requests, it's managed just by Google Calendar, okay,.

A

So to calendar updated thought: I had the good I will yeah.

B

So maybe you're talking about Jenks event calendar, but the bonus I'm going to just you, create and replaced by embedded calendar I may.

A

B

On managing its website.

A

So, are you okay, if I leave it, as is in the yep.

B

So we'll give you reference, I mean directly from the platform sig page. It makes sense to update that, but not for the recurring events. I, don't just under movies fire rate.

A

A

At forum page, if already there yeah I'm, not sure if it's already there, because I think I had intentionally not included it there so that we didn't have it exposed that publicly I've still got the open action item on a jet for doctor operating system, support that continues a Windows support policy, yeah.

B

So Windows support policy itself is done. You know talk about it later. There are some downstream action items for integrating changes, etc, but they become this. If you claim that this section item is finally done excellent.

A

And and it's merged everything said yes, so thank you. I still have the action item to review the darker build: rework PR, Alex and I were discussing it in addition, in context of docker images in Alpine, and so we'll talk about that later in this meeting as well.

A

Okay, Windows Server rapper support for yeah Mille Boadicea. Would you like to give us a summary? Even just verbal is great a brief summary of where things are and I'll take notes.

C

Okay, sure yeah, actually, what I am doing is so previously Windows surprised about for XML and what I'm doing I'm jisub 2020 is update, Windows stepper for ML support. Actually the configurations will be filled with the ml file and at the moment, what I'm doing this actually I create a PR with prototype with ml support and I am waiting for review Falak and to continue with that and in the project.

C

Also, I am going to do some documentations related to sorry Windows setup and what I'm doing it ml, supporting and I'm sorry but I, don't know talk about core things about I'm still getting used to use into episode.

C

So yeah those are the things I'm good doing, jisub, meeting, Julie and yeah. Let's so I think.

B

Thanks for the update so Kay, my mate, who also was mentioned, that the wrestling for the quest for exist a schema for small configurations, because here right now, jinguk's project uses XML. So, while llamo configuration is in progress, we could already get some babies from this project. Once of the scheme is landed.

A

So Oh, like I'm, not sure I, captured that so the there's a pull request with the XML schema definition as well. Yeah.

B

Excuse me: ah okay, but the exit is just a standard. Somehow.

A

Great okay, thank you.

A

Boadicea thanks very much anything else on Windows service wrapper.

B

You know one thing which we will talk about later: we will be updating windows, service, fiber versions in the Jenkins core. So right now we use version 2.7 or even good five, which is a bit old and there are new versions, and these new versions include a particular useful features. For example, permission my elevation when you install the service, so you want long. We need to run agent, Jerez administrator in order to be able to install those windows service so yeah this changes soon.

B

We were just waiting for Windows support policy because it requests some changes, the rendered. But it's what we will talk about later well,.

A

That's great because I had somebody who was asking me personally, hey: how is the? How is the install as an administrator, so this will improve the experience for users as they as they attempt to install the agent process as a service yeah.

B

Yeah, there are many other changes, but yeah I would say this is the biggest one I wanted to touch low end it last week do today even a hard test which we've had some delay in window support policy discussions. So finally, I didn't.

A

Excellent that that is really encouraging. So is that one, then, that Boudicca would end up creating a blog post on or a Docs page change on it, or is that something that would come from the Jenkins core team when, when it's used not.

B

I guess it would come up from its core team, because it's not really a little Whitaker's project is basically a lot of changes by next term over past few months. Some of these changes have been already integrated. Some are still need to be integrated, but yeah. Once we get innovation, then the next thing is to also include changes by a belief, and so I think that so it's just a foundational work, but it really provides ready-to-drink is usually I.

B

Don't think there will be new documentation but yeah, maybe some updates, because we already have documentation. The documentation is just flawed, so it may not might be cleaned up and simplified.

A

Good okay, that's great.

A

Wonderful, thank you, although you want to take Windows support policy.

B

So quick update, we already had the discussion and there was significant about that. What has changed so the? Firstly, the policy was merged yesterday. So, if you go to the Jenkins a website now you can find it there. It was a result of biggest this governance on meeting where we approved some changes, so the notable change that we moved, Windows 10 support from level 1 to level 2, because right now we don't have means for testing called it.

B

So our observable is looking into test automation, but if, for the time being credited that it would be it'll catch and everybody's okay with it so wooded dreams. Firstly, now we have an explicit list of questions we actually support, so we can now. We know which is important for some of the projects.

B

I would say they include Janie, we included in our in our libraries and we have been already hit by updating and suffering from winning API versions on all the platforms and pretty much the same product net, because right now so whatever was about talking and that we a bundle windows service record for that not framework to and the things cannot do- is basically very old and it became a maintenance burden. No, not all fishes ain't included.

B

So this new policy increases me mod supreme owns a professional to the country at home and at the same time, if you need to use Windows services window service assisted on the component depending on you, don't and you can use not corporations goals and you can any window service record.

B

So, for example, the.

A

Yama library, boutique.

B

Is working on yeah Dean has very limited support for that night too. So.

A

Great, that is, that is wonderful news. Yeah.

B

So Yama library didn't work for it connection window to but bear is about limitations, so dotnet is organized slightly different from Java. So what if you want in Java, you can and get the same, but restrictions work differently.

A

Well, and that is dotnet to even maintained by a Microsoft anymore, I mean that letter certainly is not. Okay,.

B

Not fair is all that metaphor is also obsolete. Oh also,.

A

Okay, so yeah so trace.

B

Of that need for basic accounts from minimal viable option, let's say Windows 7, but we can bump it further later. So it's just temporary state, most likely I, didn't be suggesting to go to a good night product 5 in a few months.

A

Okay, so when previously, when we say we were saying that for that was 4.0.

B

Or something I see, and thank you yes, so it's the dotnet framework to be specific, because dotnet, core and dotnet framework have different fashion. Look.

B

So yeah this is the Minot thing with at least it should improve all options to improve in your service.

B

So Windows service record already provides distributions for modern dotnet versions, but yet not a framework to become say over right. There.

A

Okay, so there so that, for instance, that, therefore, that five already has a will SW package available for it. Yeah.

B

So the latest version right now is 4.6.1. I wish packages are provider. You can provide newer versions, we provided corporations, so basically the packaging just defines the minimum required version of the pack and, for example, in Jenkins. We have a lot of hearts so that dotnet framework to rations from modern versions. There is already a request from next tournament, which basically most of these hugs, so it will become a bit simpler and it's more testable.

B

So here I'll spend some time this month finale. So these changes because they.

A

Anything else on Windows support policy or Boudicca. Any questions from you, aw, like on Windows support policy.

C

A

Great. Thank you thanks very much. Thank.

C

A

So next topic brief summary on get plug-in performance ji-suk project, so the Rishabh has provided a benchmark for request and he's actually revised it several times working through the process of bringing jmh benchmark execution on to see ID engine can style so that we can use the gives us the benefit of having access eventually to s, 390x PowerPC 64 and be 64 Linux and Windows Linux or Windows AMD, 64 and potentially.

B

So the program with exhibit Edgington CEO is still not designed for benchmarking. We had this discussion last year as a part of JSOC, the part of platform Sigma Kings, but the only month, provision and core virtual machines. You know continues it's not exactly how you do performance testing if you want to get metrics so yeah, if you improve performance by ten times, it's one story, but if you with about 5%, then our current infrastructure isn't able to reliably capture that and.

A

And that I think right now, given that this is the initial exercises, are actually comparative checks between CLI get and jagged I think the risk is relatively low there. The agreed wholeheartedly yeah.

B

There was no risk you just shouldn't use. This matrix is absolutely knows for sure.

A

Yeah, so the risk is benchmark. Comparisons between between runs are ultimately unpredictable because we're getting it on demand provisioning. Now, one one of the things I like that we I did see is that the pipeline library seems to use a resource lock, which attempts to prevent more than one more than one performance benchmark from running at a time as though we're locking on to specific class of hardware I haven't investigated. Yet, though, so yes.

B

The library method- and that is a blog post from a be there- was a substituent into some of nineteen know what the homeless photo. Stretcher, plugin, so pipeline library stepped uses, hi ma'am machines, so basically the machines we are using for acceptance, that's harness, and yet these machines, I believe they still provisioned, as virtual machines, most likely still on asia.

B

Still, these machines are not that predictable in terms of performance, in terms of especially it comes to network overheads so but yeah, it's definitely better than running connect. I.

A

Yeah, okay and they understood there, okay, so.

A

Between runs between jobs, yeah.

A

They get a different machine.

A

Mm-Hmm, so one of the one of the techniques we've also been using has been to run the same benchmarks on Mark VI server, which has fixed hardware, but it's ancient fixed but old hardware, so it tells us something different. The other is that he's running his on Rishabh is running on his Mac, so we're seeing interesting samples and doing being able to cross-check between various configurations to say: hey.

A

Is it consistent that on small repositories Jake, it is in fact faster than CLI yet, and is it consistent that on very large repository CLI get is dramatically faster than Jacob, so those kinds of.

B

What's that until you run out of memory, because JD is much more resource consuming.

A

Right well, even even ignoring the the resource consumption we've seen that with large repositories, command line get wins every time, even even if Jake it has lots of memory available. It's still fundamentally slower than command like it is command like it seems to somewhere between the 10 megabyte repository and the 90 megabyte repository Jake. It loses the race.

B

A

B

Some advantages for cases where you cannot use a common line. Indeed, for example, if you want to fetch a particular file using it, then with drink it you have opportunities to shortcut particular needs. Another. For example, query logic is file from repository. Okay, in the most cases, I think you should just use proper provisions like github, wrench stores or whatever. We shall do it without hanging JD's magic right.

A

Where the the benefit there is get, the branch sources can then use the REST API they can. They can make direct requests to a single file yeah, so that continues the we also have two or three pull requests pending. Several pull requests already submitted.

A

One is for the redundant fetch removal.

A

That one is for is to refine and improve the benchmarks.

B

One think I have to drop, adjust good, an emergency meeting request; okay. So yes, sorry for the late notice and next thing we should just have a full meeting with no participants.

B

Thank so like later bye. So.

A

Last topic was docker images in Alpine and there Alex Errol the maintainer of the Alpine images, Alex Earl myself, and how awkward and one other person met. Last oh and Oleg met last week and discussed. How do we approach the dot? The Alpine images right now? We need to update the Java on Alpine, because it's currently JDK 8 update 212.

A

It's there for several several major revisions behind are several revisions. Behind the current. The current Java 8 update 252, that is in progress, alex, has submitted a pull request and the change really we'll have to use adopt out of open JDK instead of using JDK the open, JDK bundled with Alpine, because Alpine no longer provides JDK updates beyond 212 for Alpine 39, so that that part of that transition will be adopting adopt open JDK. It's also expected that we will eventually update our Alpine based operating system version to 3.11 or newer.

A

The items that we had for our meeting today, Boadicea, unless you have others I'm, going to go ahead and stop the recording and close the meeting. Okay.

C

A

Thanks very much thank you for joining. Thank.

B