Jenkins Infrastructure Project, 14 Apr 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: INFRA Weekly Meeting 2020 04 14

Description

Jenkins Infrastructure Project Meeting - 2020-04-14

Notes - http://bit.ly/2T0oZ9v

A

Yep, so how everybody? Let's start for this new in from eating? We don't have specific topics that we have to discuss today, so just I would just start a quick overview. So the first thing is so as last last week, I mentioned that we had some issues with the fastly accounts, so I created an fast account, so I was supposed to be granted with a specific open source.

A

I was supposed to join the open source program and we had some issues and should be solved now so either today or tomorrow should start configuring fastly to use to users in for changes at I/o. So it is something that should be coming in the coming days. Otherwise the main topic has been to work on that check-ins release automation projects, so we did a lot of testing around the packages that you are generating, we spotted a few bugs and- and we fix those bugs- and now we are mainly working on the documentation.

A

So I sent an email on the mailing list when a worker asking for feedback if people are interested I mean just asking for more form for more feedbacks, and otherwise we should try to plan release probably next week, depending on how the Queen this is happening. um So yeah question now: do you want to bring any specific topic?

A

The thing is there yeah.

B

I, like I, like the like suggestion, should we already consider we were delayed this week on doing the weekly I assume or like that. The weekly has not yet happened even now, and thus is this as an excuse to say: let's test drive the this with the current weekly, oh yeah,.

C

We cannot do that so basically, somebody just needs to paint Kiki and say that whatever you were doing is done, I haven't sent a message yet, but if you have an opportunity, why not? There is nothing really critical in this release? Well,.

B

Over mission, yeah I like I like that approach, because it lets us do it during a weekday without feeling obligated to Sunday night to match with something that had been done previously. So it's a great age to try. It actually.

D

We do it on Monday, even if we weren't to do it this week, we'd do it on the Monday. Wouldn't we just so that it's not no weekend.

B

Agreed agreed in the future, but yeah that's valid point.

A

So yeah, my my only concern to do it right now is that there is one last bugs that I would like to solve. So basically, right now we are generating index that estimator, so basically many cover by Carol Jenkins that I own. So when we generate the artifact, we publish it are those artifacts, and then we generate the websites with information like how to install Debian, how to install reddit and so on, and there is still a last last bite that I would like to fix on that part.

A

So it does not really invite the release process or the packages that we are generating, but more like. When we generate a new release, we also publish, we also have data per to potential websites, so.

E

B

Less worried about that than I am about the things that I.

E

B

Don't yet know about, but we will learn about by the virtue of running through the process. The package page I suspect there are many many more things that we haven't yet discovered that are that are that need need further attention. Okay,.

A

So the rise yeah we can, we can start so what like, what would be your? When? Would you like to start this tomorrow? Well,.

C

For me, I would prefer to do it tomorrow on Thursday, so that we have some time to react. Okay,.

A

C

I can just dedicate almost all the time I can send head. Stop the KK, but the team is here. Alex is here, mark is here, so basically, all commenting or surround accept whatever, but Oliver. It's less of concern at the moment until the airship of tears, so I would give it a try. In the worst case, we watch the weekly release. We sent a message to Kiki I asked him to shipping. You reduce on the top of it: okay, not something unknown.

A

It sounds like you plan and for me, for the figure I want to push only one when only only one or two a work to implement that so and should be ready for for.

E

Thursday, well so, could we I have an integrated um KK.

B

Release fifteen minutes: okay, oh okay, done even better. This is an excuse. We could release a new, weekly and and just admit it to discard. Couldn't we.

D

C

You have a lot of things on the backlog and in the poor request queue. So creating Chi, safe release for tomorrow or Thursday is to label sure.

A

C

Even the mock release without changes, but we definitely can integrate something it.

D

Was one maturity with the truline documentation, change and.

C

Commenting on guys, oh.

B

And the maintainer guide: yes, there you go get.

C

That, when merged yes, oh well, uh these changes haven't user facing I would prefer to lend something small but use the facing to be honest. Okay, I'm sure.

D

F

Meant something.

C

Yeah, that's what's wrong and I still have a plan to propose one line fix forging its father on our, so I can just submit it.

D

Just a great going to configuration. If, then, you would reply well, even Felix's timestamp for the thing will keep going. Oh.

C

Yeah so yeah we can take it offline, but so Oliver sort of Olivia. What's your preference about the time when you would.

A

Like this ship it so for me we can, we can plan. Thursday seems to be a good time. Let's, let's say Bellini be I mean, let's say the time where we have people on the US and people on the europe like 3 or 4 p.m. UTC, maybe 3 p.m. UTC. Let's, let's see the best time, but I can send them invites for our Thursday to all the people. Yeah.

C

A

C

Also need to send head up to the developer man degrees, just in case, so if you could do that, it would be great and on our side we will prepare some changes in the master branch tomorrow.

A

I, just a quick reminder on the time here on the timing here triggering a release: the release, job tick around 1 over 30 and the packaging job takes around 30 minutes in the 30 minutes have 15 minutes reader to generate the packages. You have 15 minutes to generate the packages and you have 15 minutes used to synchronize. The different doors should.

D

We trigger the release earlier is that through there, the release doesn't really matter so much. It's just release is just what we're building, if you just trigger at around lunchtime as long as we merge before then, and then the CHEO station packaging and deploying the artifacts that matters well.

B

And and don't don't be hesitant to do it earlier in your day only VA, because Alex and I are both, though we're in the u.s. time zone. We are certainly early risers and on Thursday morning, we'll be up very. At least I will be up very early, Marquis I, don't know for you, but but I think you should feel free to do it anytime on Thursday. Don't delay till your afternoon agreed.

A

A just quick check before I go to the credentials. I just want to be sure, so a leg has the permission to to push to Jake in CI, slash, Jenkins and the master branch. If I'm right never requested these definitions so because, basically I will have some in the current process. I will have opened the variables the me the right, K teaching, Institute Inc ins repository.

G

Arrives yes, yep, so I need I need. I need to be able to write Alex.

A

G

Is access to do that? Yes,.

F

I have access on that work.

A

So I also need write permission on the Marvin repository I. Don't.

F

Have access to do our artifactory stuff.

A

F

That might be Daniel.

D

Danielle and.

C

D

Unitary that I know.

C

So jaesik dick well technically, we could grant access to someone, but only yeah I think it would be better that, since you have watts to the process that you could just orchestrate it and if you need admissions to pusher to the court, I think you can run them by Thursday. So.

A

So drink into a search, engines, artifactory and I- think that's it yep. That's it so yeah right, okay, yeah that sound. That sounds like a great plan, I'm very happy to test this. There is also another topic where marki was helping his auditing the communities cluster and see how we can improve the security process. I, don't know if you have any update that you want to do here. Marki I ran yeah.

H

I ran the initial scan and it didn't break anything because nobody said anything. So that's a positive I ran that I need to configure the scan again to run what I want to do on. The second I want to see if it gave me the same results back that way. I know it's actually running correctly and then I will run. Finally, before next informating I'll run a third scan and then I'll publish the results when I publish the results. I won't make those files public, I'll, publish them in a spreadsheet.

H

That I will I'll share with everybody on this call. Okay,.

A

In which two are you using for this Ken, so nerd boy, so.

H

Now buddy yeah, thank you. So it was. It was a tool designed by heck, do and now they're under vmware, but that's pretty III looked at Spotify x' QQ bought it, and I they did. The reason that I did not like that tool is. It required many permissions and and instead of adding the permissions separately, it altered existing permissions and I did not like that, because I did not want have to go back in and change those cluster admin permissions in the RDoc.

H

A

A

There is there any other questions or topic and automated release.

A

So I don't know if you already started thinking about how we plan to release as well. This table our release, or is it still too early to discuss about that? So, let's just focus on the weekly.

B

Focus on weekly for me, yeah I,.

D

B

I expect several surprises on this one and several more surprises next week and we're going to proudly by the end of April, say we got it all right, I, just.

A

Want to be sure that it's still in our head, so if we have to implement a fix, it does not invite so the way we would release the stable releases. So what does there anything.

A

C

Issues I just wanted to ask whether we want to establish some communication channels for Jenkins core for Thursday. It looks like it would be a good thing to have them when we do all these three days and yeah. That is ongoing. Hollow word about slack versus get urban versus matrix versus whatever, but maybe we could make an intermediate decision how we communicate during this release.

D

Chicken I was just ranting.

A

Mica mica medium, the most important one is the Jenkins mailing list changes the mailing list right.

B

Well but I thought.

A

B

I thought you were I thought Oleg was targeting high interaction, communications back and forth, not not not informational. No, no.

C

B

Like a hundred.

C

And you yeah that stood in the right. For example, we had the same kiss with Alex, oh and with regards to docket agent Renee, mink dr. leekie Turk, so it was also quite a long time communication and if we end up obvious meaning something like that project is Cora, I would rather prefer to have a channel for that. It's.

B

Another question is my assumption: was we would use IRC because that's what we've done before with Jenkins infra.

A

But that's my that's my assumption as well, and that's my assumption as well, and all the people involved in this can use ours anyway. So.

B

Well so, oh like, were you, were you considering hey? Should we try something you try and knit another channel for me, I like IRC right now, because it's familiar and while we're doing something that will be new and somewhat unfamiliar, using a familiar channel, felt like a healthy thing to do.

A

So the question is which what new tool do you want to bring in the loop and.

B

I, in this case, I, don't I want to stay with the old tool personally, just just so that I don't have to worry about tool, changes and build changes. We can change tools later a week or two from now. I, always like that sentiment.

H

I agree with Marc sentiment: I definitely think there should be a discussion about the tool change, but I, don't think it should happen in conjunction with the release.

A

Okay, so let's stick to our se for now,.

A

Yeah, otherwise, if we don't have any other copy that we want to discuss, I think we didn't stop the meeting here. I just.

D

Had one thing that would be good to get fixed um incrementals has been broken for a few weeks, but the I think the passwords expired well I'm, assuming that you don't have access currently to fix that Olivia. What.

B

Are you saying.

D

B

When you say incrementals broken ink levels for jenkins core incrementals for.

G

Finding incrementals publisher.

A

Created the credentials for artifactory right yeah.

D

Yeah, it's the artifactory credentials looks it looks like a satifactory credential.

A

G

F

When I transpose, it gets a 403 I believe.

A

Then then I can contact them here to see. If you can sure has been information. That would be useful.

G

A

At least 10 tickets I'm trying to find it so.

B

That would be a help for me as well. I actually have a pull request to a certain plugin I maintained. It needs an incremental from another plugin, so I didn't realize it was broken and I offered Lee suggested that the students suggesting it should use incrementals and so now I've lied to the student. Sorry about that yeah.

D

It's getting a green tick, but it's because it's just.

B

We found a bill and it's ignoring errors just like it should accept that we're ignoring the air like we should have yeah.

D

Here it is Jessi raised this one. It's an IRC.

A

Ensure the ticket either an RAC or in the document, it's a nice thing. Okay,.

A

Maybe I'm just disconnected from our.

A

So another thing is that yeah.

D

So I can see, I can see the function, but I can't see the logs to the function. You know it's just sort. There.

A

Okay, so just one last question: before we wind up this call, is there a person interested to participate in the FASTA configuration luge I mean? Is there someone who want to have access to the accounts, because right now it's it's only because it gave me I'd be interested in helping out okay, so I can send you an invite I.

F

Had one quick item: if there's nothing else yep, so we're gonna have s 390x and RPC and armed agents coming up our labeling right now for like docker jobs is just the docker and label.

F

So we need to come up with some labeling mechanism, whether we want to change things that currently just require docker to require docker and something else or mark doesn't like that idea. But we need some way of labeling things so that we don't put the wrong jobs on the wrong or at the jaw, the right job on the wrong agent within.

A

The infrastructure.

F

So, just something to think about.

A

I, don't know if you had the time to because I did not follow anything regarding the water, but regarding the IP infrastructure, adding those as agent and Sierra Jenkins at iron and Sun. What's the current status there, because you as far as I know we still have to within, we still have some scripts to configure those those infrastructure, and then we still have to add those machines to Seattle Jenkins that I you're right yeah.

F

That's correct: currently we do have arm you, you added the Packer imaging for arm on AWS at least we have that and that is docker capable. So we can't label it as just docker. So do we do we want to start doing arm docker, you know, s/390 docker has one label that just then we can talk about an IRC I just wanted to get people thinking about it. There.

D

Isn't there is their platform label a plug-in that does this? For you, there.

B

Is but I'm not sure that yeah there is, and we could consider that I'll bring it to IRC and we can have a conversation. There's also an implied labels. There's an implied labels plug-in that will use apply rules to existing labels to generate new labels for us. So we could. We could talk about both those I.

F

Just know that there are a ton of things in like the pipeline library that look for just docker as a label. Right and again so that's.

B

Why I think not docker really implies amd64 and cetera exactly, and we should just admit that. That's the reality we're never going to be able to change that, whether we like it or not, yeah.

D

So for these special ones they just need some other label or some suffix or something right, even the best way to do that, because.

B

We'll need it for dot. We've got something like that with wind dock right now, right, right, Alex, oh, so we just need to choose a scheme that will work for us dealing with multiple platforms and not breaking the compatibility. We have the existing labels yeah.

A

Park it so let continue this description on our team thanks for your time and see you later bye, bye, thanks, yeah cheers everybody Thanks.