 Welcome, everyone. This is the Jenkins infrastructure meeting. It's September 15th, 2020. Let's take a look at the agenda and be sure that we've got the right things and talk about them in the right order. So what I had on the agenda. Incrementals status report Tim from you just briefly kubernetes upgrade mirror status report if anything, docker terms of service not sure if we need that one. JFrog Artifactory that's a heads up one that I wanted to talk briefly about Jira upgrade status Oracle cloud. And then one that I'd like to propose to move earlier in the meeting to be sure we get to it release status reports. Anything else that people are feeling like we need to include on the agenda. Oh, go go. Sorry for the long agenda. Okay. All right then. Tim you want to give us the latest on incrementals on kubernetes. There's been a couple of small features from Jesse and Gavin and all deployed final issues, and there are no, no reports many issues with that. Excellent. So that means we've really switched away from the Azure functions and tiredly to running on on a kubernetes based docker image for this there's still other functions that we have on Azure. Oh, there are. Okay. Yeah. And it does anything. There are things that are being hit. Pretty frequently if I remember. Let me look real quick. There's a function for promoting staging to production automatically but that's been broken for ages. Probably pretty simple to fix. Sorry. You guys can continue I have to enter my code and stuff for my authenticator. Okay. Well, but I think that's a that's an interesting one to have on the agenda, even if we don't get to until next week, great to be sure that if there are other Azure functions we could we could or should migrate away from it's good to know. There's no reason to migrate away. The reason that we did for incrementals was mostly that some of the incrementals runs take to take longer than you're allowed to run on the function we were doing it on. The logs went the easiest and went most accessible. And since incrementals is used so much it was just a no brainer to kind of move it over and onto something that's a little bit more stable and under our control. Great. Okay, so, so this this migration was an intentional because of demands we place on the function, not some general purpose limitation of Azure functions we should move away from thanks for the. There's so the only other one that's getting hit somewhat frequently is comment logger, which I am not sure what it's actually doing. I haven't looked at the code and post some of the Jenkins build result into the github PR at least I think it only runs on the log. Okay, I think Jenkins. It's probably going to genes.io bill failures. Gotcha. It still works. I haven't seen it. Okay. Since the password reset, to be honest, I don't think I've seen that in ages. Yeah, so we have an analytics bouncer we have comment logger we have evergreen upload and evergreen is dead so we can get rid of that one. Then the info auto PR or the for that are on there. Yeah, so I think those two just need fixing probably good to get them back, especially the info order pair. Okay, so, so I'll have to I'll listen to the, to the recording later and put the detailed list and I wasn't nearly fast enough to get the entire list into the notes Alex. I can just say, look at the for remaining functions and see if we actually need them. Cool. Anyway. Yeah, we've been working with Adam for a while. So they're obviously not critical to our infrastructure at this point. Right. Oh, no, I was done. Let me just check the one issue is still access. That came right. So that, yeah, it was. Yeah, that was done. I did it. I was going to do it the day after the meeting then I realized it was LTS release day. So you probably not do that. So the day after that went from 115 to so I had to be a two stage so I did it 115 to 116 and then 116 to 117 was actually a fourth stage because you have to do the masters and then the no polls. And then wait for all the no pause to finish before we did the next one. But yeah, so it was all fine. The only issue I had was Loki was still bound to an exclusive volume and it wouldn't let go. I ended up just leaving it because I figured it would probably come right. And I just checked it now and it has was it was and nothing needed changing I and then I ran the build and it was fine. Excellent. So this is done. Yep. Yeah, I've also found that the Jenkins so the Terraform code was still pointing to 1.14. So, Olivia. We did the last update didn't update Terraform, but I've updated that to the latest version. Excellent. So and and really excellent because I hadn't I did not detect one single thing relative to that. That's great. I assume there was some some brief offline periods for some pieces of this. Yeah, some alerts to trigger. It was about under a minute's downtime, I think. I don't know why it happened. This shouldn't really have happened. But yeah, there was like a minute blip. Excellent. That's great. Anything more that needs to be done there. Anything that you want to flag. No, it was all fine. Excellent. Thank you. Mirror status report. I haven't any time to work on the decommissioning but we just need to decommissioner decommission the old one. When we can. Yeah, the old service. So it's we need a we need to find the latest Windows download link and get the and move the LTS RC process to release.ci. And I know that's right. My Chrome is flagging warnings on the Windows download because it's a mixed content. So it's it's currently pointing at the old one which is on HTTP and by default it won't let me download it. Yeah, and that that makes sense that it would flag it right because you're you're switching from secure to insecure. Okay. It's just a needs fixing there might already be a link. I'm not sure. Well, I'm not sure that the, that those bills are being uploaded. Yeah, I need to figure out that. That's all. Thank you. Thanks very much. Change in Docker terms of service. I have no nothing new to report there compared to last week. Any, any red flags from others. I haven't been following it very much at this point. It was time skip. Okay, great. JFrog Artifactory. So there's been discussion. So JFrog hosts repos. Jenkins.ci.org for us. And they, they have flagged to us. Hey, we're worried that you're using an awful lot of bandwidth and an awful lot of Yeah, bandwidth was the primary concern. They've scheduled a meeting today with me, Daniel Beck, and several of their people to discuss. We'll listen here what their concerns are, try to understand them. Our goal is to continue hosting our artifacts on that repository. So we know you need to reduce in this way or that way we'll look for ways to do those reductions. I'd really rather not have to create a project that moves us off JFrog Artifactory to some other artifact hosting system. I just don't want to spend the time. I'm assuming that the two of you are okay not being included in that meeting. We could certainly include you if you feel to join it will be, it will start in about three or four hours. I'm doing anyway, but no, I'm fine. Okay, all right. Okay, last topic or no next topic really status reports so 2.257 release today and an awkward embarrassing thing it had the same problem is 2.256 no Microsoft, no MSI installer. And the reason it has no MSI installer is Microsoft minor numbers and major numbers cannot exceed 256. So we had the same failure last week and I failed to detect it sorry about that. We won't get a new MSI installer until we find a different way to represent the version number in that installer. 256 dot build number. Yeah, I was thinking it's 2.255 dot build number right so 2.255.257 and then it becomes 2.255.258. What about LTS. LTS fourth, fourth component is allowed. So how many how many bits are available. I had more than like four out for LTS and a single version but as far as I know 16 bits in the third position. So this position is is a 16 bit quantity and the fourth position they described as being ignored and having no limit. So that the problem though is if it's possibly ignored then if you try and update from one LTS release to another it may not work. That's and that's a valid point. So right now I believe that in LTS is where I'm actually using that third component for the LTS portion. Okay, so, and, and I think that's pro Alex what I would lobby is let's take that into this issue that I raised. So we've got an authoritative location to discuss it because it's a valid point. The, the general upgrade process that I see most Jenkins admin users is they install the MSI once and then they use the inside Jenkins upgrade to the newest version so just as a war upgrade. And then running the MSI again and doing an MSI based upgrades. So, so, but it's a valid point. It's how do we handle LTS releases, if we shift right. And I'm open to other suggestions. Certainly, I, I'm hesitant one that I thought it was well we can switch to Jenkins three, but I'm not sure that the project is ready for us to declare Jenkins three. The next day they just said this kernel is now such and such without any major actual changes, but I suspect that will generate more noise in the in the community than we're really ready to do just because of a windows of the windows limitation. 22, just like a tone into the first cat first dessert. Oh, oh, interesting. 22. So your suggestion was do this 22 that to know but that still doesn't help us. Oh, oh, and then we would decrement this to be 57. Is that what you're thinking shift left. There's 22.0. 257. Yeah, okay. Yeah, so, so my proposal is let's have the discussion in this in this in the issue. And yeah, that's an interesting alternative. 255 257. But that then has the LTS problem that you noted Alex, we could go 22 there because there is, there is a concept of a display version mentioned. Yeah, we're using that right now. Oh, we're already using that. Yeah, that's we're using it for the LTS right now. Good, I'm looking at looking at from looking at the, the Wix project file. Wait a sec. Let me look at it and we can discuss the in the bug. Great. All right. Excellent. Okay. As long as we don't don't go above 1000 versions for a for one release line like we don't go up to 2.0, you know, 1000. I think we can make it work. Oh, good. Okay, great. Okay, so Alex, you're okay if we have that discussion in this in that, in that ticket. That's fine. Anything else on release status reports, we did release last week 2.2 49.1 and it's been a little more noisy than a typical LTS but not a lot more noisy part of it was upgrade center changes part of it is windows changes and surprisingly little noise about UI improvements just been very successful. Next topic, Jira upgrade plan. Here, the Linux foundation has connected with me they've sent the poll to schedule our next meeting. I still have not made any progress on the actions. I'll do that this week. It's getting closer and closer to November 30, when the support of Jira seven dot 13 ends. Any questions on Jira upgrade. Okay, Oracle cloud conversation. So I met with Oracle cloud or represented from Oracle cloud two weeks ago, and they share that they're interested in helping the Jenkins project and having a more active. Jenkins solution available on Oracle cloud. They sent me a non disclosure agreement and offered to review our Azure bill looking for cost saving opportunities. I'm going to have to talk to the governance board to see what what I can or cannot do with NDAs as an individual I'm happy to enter into an NDA with them but I can't certainly enter into an NDA with them for as the Jenkins project or anything like that. So any guidance from you on that one in terms of past experience with non disclosure agreements. I haven't had any in terms of as a board member at this point so we definitely need to bring it up with a full board because there are people on the board who have probably had experience with the Tyler and so forth so it'd be good to have a discussion with the board for sure. I'll raise it as a question the mailing list today and hope to get it on the agenda for tomorrow's board meeting. Alright, last topic was we have an Azure customer success manager assigned to us now Kayla Linville. And customer success manager in this case is intending to find ways to help us use Azure well and effectively. She's provided some documentation that I've, I've still got a review and I'll send it out to infrastructure mailing list. As I, as I've reviewed it and get some insights what we might do with the information she's provided. Any other topics we need to go over today. The recording will be available separately it takes about an hour usually to process it. Thanks very much we'll end the meeting here.