Jenkins Configuration as Code Project, 25 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: JCasC sub-project Office Hours, Mar 25, 2020

Description

Regular Jenkins Configuration-as-Code project meeting: news, ongoing development and the roadmap discussion. Full agenda and meeting notes: https://docs.google.com/document/d/1Hm07Q1egWL6VVAqNgu27bcMnqNZhYJmXKRvknVw4Y84/edit#heading=h.qxoliak5cp5t

A

Are we recording yeah cult? Welcome everyone to the Jenkins configuration is code office hours for March 25th on the call we have myself Oleg and family John Joseph Slayton Antonio.

A

We've got the agenda which is sitting in getter. If anyone wants to add anything, feel free, you can get to the document from from the bottom here, we'll start off with any news.

A

It's a recently sneaked shaders snake humor was extracted out to an API, a plugin that was done by Emilio, with Antonio's help, so that's merged to master, but not yet released.

A

We have I think we went through this last time- support for additional user attributes. So that's currently with the local security realm. You can you'll be able to add things like email address, display, name, timezone.

A

Ssh all stories keys and a few other things it should be adaptable to other security realms, but I haven't tried yet so other security realms can probably use ours, but it may need. It may need a little bit of work to make it so that other security railbus can adapt.

A

It's probably restricted at the moment, but there's been interest and I think there was someone in Godot who was using the azure ad plugin and they were they wanted to have the authorized keys managed by Jake asked so we probably won't be too hard, but the ground works there for that now, so prop might come back to the milestones one. At the end, we've got time to go through it, so system raid was merged a few weeks ago.

A

So Jake asked as support for its merged, but not released to waiting for the milestones before doing the next release at the moment, but we may need to move on so the bond version bub is still there. It's currently ignoring the failures in cloud-based folder, both just you know, leagues, said that take a look at it, but I haven't heard anything.

A

Be great to get this over the line at some point: I'm, not sure yeah. So basically, I just ignored the test, because I couldn't I couldn't figure out why it was failing, and that was enough to get it to be a green build, but I haven't heard any feedback on their.

A

Ceo Jenkins IO is Jake, asked haven't touched on that recently, but the AWS side of it is starting to work on stage. I can say: oh and there's talk of moving the Jenkins master to AWS, and that would be done with Jake asked and the groundwork is there, for it just need to pick it up again. You.

B

Have regarding coolant master, we have one obstacle, basically, code from infrastructures code for AWS, so right now everything come on in ws is country, good manager, it's not just about Jake caste. It's about the entire infrastructure, yeah.

A

B

I did a fuel meter to the work cooking today at once. If you want to meet master there, yeah.

A

Yeah there's no current rush to move it there and even if it was I, think the current one could be adapted on without moving it as well. I'll try pack this up the next couple of weeks. Hopefully secrets encryption with external secret key oleic, yeah.

B

So I just put it to the agenda first to highlight that it's still in my home of shame, because I got a couple of private Pink's over the past week about this pool request. So I declare my intention to get it over the line and to deport my environment, so I hope to get it done for me right now. The main problem is, of course, encryptions and difficut, because one doesn't easily implement it right in java, but effort to get it over the line.

A

Well, they'll be good. We have a configuration api plugin here.

B

Also by me, so I'm not sure how long you plan to delay the release for the current master branch. I want to try to implement configurator API so that we don't have to bump that core dependency. So Jake asked but yeah I wanted to work on it two weeks ago. I didn't get to that, but if I have any time so.

A

The current plan is to release once we get milestones in yeah.

B

In the worst case, we just reduced the vision of Jake asked, and then we do an extra days where you don't be to the current dependency yeah.

A

B

It's possible, it will work. So it's not a blocker. No.

A

Yeah plugin compatibility highlights so Adrienne merged the mela plugin pull request, but it hasn't been released. I pinged him yesterday he said he'd do it, but then he was having issues with Windows, see I I wasn't passing I think that's most likely because been a lot of instability and the Emperor of it'll. Last week, yeah.

B

It's been sometime yesterday to get it to be triggered, I believe it now. Master branch is to Finnick yeah a bit if it passed once and in the worst case and this plugin, we can say that we go without windows, because there is really no windows dependent functionality in the plugin, so we and leave without that release. So yeah.

A

Yeah time zone, property I think that's sitting waiting for Olynyk as he put on hold it's cleared of few approvals, but.

A

Okay, yeah load on my best attribute to me: okay, it should be straightforward. Hopefully it's a very small change, but it does impact the data.

A

Edmund monitors this ones. Everyone seems to love reviewing this PR.

A

It's getting people from all over the place jumping in on it, but I think it's I think it's really for everyone, so something that's touched so little. Everyone is very interested in the thread safety of it.

A

It's had about ten different review cycles and for like it's 15 line change, but pending a couple of people approving it I think it's really.

A

Log recorders, that one so wait that one's basically Edmund monitors but a lot more complicated as part of the public API.

B

Changing implementation, so basically the situation is similar to plug-in manager, because Jake asked works quite late in the initialization cycle. So we miss a lot countries which were created before. If you can take a look reporters mr. ekeus as we wanted to move plug-in manager, a little startup cycle, this plug-in installation manager, library or other approach for work recorders, meaning you might need to do the same later and maybe, for example, for system properties or whatever.

B

So if you want to have integrated cask experience, when we will likely need a core library for that, another implementation, the J custodian.

A

Possibly certainly gives the full experience, but it depends on what people use log record is for mostly for me: I've, mostly seen it for plugins during runtime.

A

B

It's better than nothing, so this request should be merged, but yeah. That is probability we don't have to typically yeah.

A

Yeah, it's yeah. The complication with this is that it's part of a poor public. It's part of a poorly designed public API and maintaining compatibility is difficult.

B

To change so many peers. Well, we can duplicate a lot of matter today, because I don't dating video uses them no.

A

It's three plugins the touch-ups.

B

Okay, yeah I do my best to reveal the core pull request: they've been so behind Jenkins, core and other stories, but I'll do my best forecast things for the rest. I think I knew be still behind because of ad hoc student application period and then project selection, no.

A

So we've got some roadmap entries for the J casts a project on the agenda yeah. So all this numerators delivered well sister, Marie capabilities, delivered and I guess has it as well yeah.

B

So for me, sister Marie T, you still in progress with a burst roadmap because we have a follow up. A pic is a bunch of changes. So even if you have support me, principal photo of them up, I would rather prefer or to invert.

A

The resist when.

B

We have good end-user experience for that yeah.

A

Absolutely yeah pretty.

B

Much sure the simple plug-in compatibility, though they it's harder to define when it's done, but I think that you should edit the road bump, because it's a pretty important topic for the drink is coming in. You can.

A

Go one cuz: you can't really see anything well, you could have 90% of plugins compatible all all plugins with over 50,000 installations, comparable I.

B

Agree but yeah we can mark it as a progress and then think when we set it to complete it because right now it's we still have no Jenkins code. We have some plugins which are not compatible. Vg cask I mean the popular ones. So I would rather say that right now it's not completed but yeah. You put it in progress and then do something.

A

Yeah, it's not many major ones, so this doesn't change very much anymore.

B

Yeah, because passionates and github, but it's somewhere so I, think that I will so, while working on the roadmap I will like the Edit entry to the G cask sub-project page, just reference github issues, because they have aggregated each other and lira and so be yeah.

A

Yeah then had a help and documentation that sort of thing suggestions welcome.

A

As a configuration sauce, API I've taken a bit of a look at it and made some progress on it, but got distracted.

B

Yeah ugly, it would be a good addition to the roadmap. Well, we can put it as future or maybe should shut down and I'll show. What's your plan above it add.

A

Difficult it's just fiddling with the classism.

B

Well, but it would include some implementations right so, for example, is three implementation. You know discuss is sledding before maybe other in communications, because API is good, but we need again a story which is consumable by end users.

A

Yeah yeah yeah well, sir. Yet this is delivering the API and then there's implementations, so the plugin would come with the simple ones out of the box and then the clouds would be off in their own plugins, yeah, I'm, not sure what else there is.

A

The crink to create the secrets that you're working on.

B

It's a reasonable, but I. Don't think that it's important enough is this, though there is another jab jab 2 to 5 current dependent radio, which would create global.

B

A

B

It not is not merged.

B

Here you can open pull requests so folder business.

A

B

For any credentials, provider and I believe that he, in its motivation of Jake asked, is referenced yeah. So I still need to talk to Chris to understand to what his plans about that, because it's not ready as a drought.

B

Right now, yeah.

A

B

Think that if there is consensus that we want her to proceed to get bad, then I it could be a road map. Entry, yeah.

A

This is also potential for things like yeah, making it easier to define folders making easier to define jobs.

A

Some of the more.

B

Difficult sites of defining the jobs of folders as llamo yeah.

A

Job dsl works for us. It's not very declarative.

A

B

Yeah, so if anybody has ideas like that, just put them in the developer, menu at least or submit against my pull request so that we can integrate them. We'll still have some time to finalize the roadmap before it goes. Public I mean one two months at least so we can discuss it later, but starting these discussions it would definitely help yeah.

A

It's I mean it's a living document anyway, I assume so updated whenever we want.

B

A

So that'll be the main list post. So the other item that I skipped over was the milestones, pull request.

A

So I think we've got three issues with it. At the moment.

A

We've got one that the test fails quite often on Java 11. It fails.

A

It's failed once on Java 8 to that them that Olek had their concern about race conditions between Jes Ruby hooks and the one was that there's been reported issues with job DSL and.

A

Job tears are running before the get here service of loaders.

B

Yes, so job this sale is something complicated, but well, if I don't think it's really related to this change, because if it, if you have rest condition now, you should have had it before.

C

Always been missing something the issue with the key tree. A plug-in is that it has some validation than it does, based on the server when it tries to create the job, and that it should only do that on one time when it like tries to check out stuff uh-huh.

B

So before Jake asked is fully loaded, yes, but again it should have been happening or maybe not no you're, right before it was a race condition. So, depending on your luck, you would have got two different results. Now it would be fine and consistently, which is probably an improvement to do something about. It is.

A

That just a change in the case here, plugin required I, would.

C

Say it would be a change in the key to a plug-in there?

C

Well, it shouldn't do validation on the thing that that job wants to have like I've seen other plugins that did that and those we fixed that assume something when you change the job with validation, yeah.

B

The problem that we still don't really have the communication of how milestones should be used.

B

Maybe we really need to start a jab or whatever for that well jab or not as a full-fledged process and but as a documentation page because, for example, right now we cannot point a dear plug-in maintainer store anything.

C

But it's not viewed a milestone issue, as I would say for kids, a plug-in and plugins like that. They shouldn't apply any assumptions to global configuration when job to yourselves applies to or tries to apply a job they should just apply and then, when usually all their other plugins. When you run it it does it on top or at runtime. When you try to execute the job, it does the logic to that. It needs to check now the server connection works and stuff like that. Yeah.

B

We have a lot of such for validation logic in Jenkins, but we don't invoke formal additionally in Jake asked. So if we assume that we start invoking a common origin for invalidation, we would have had a lot of similar issues.

B

Yeah, if you plug in just, does it another routine.

A

So maybe just came back to the gravy issues.

B

So for groovy sure I believe that we need FEC in magical score, so the one which I asked to remove from the original pull request from Francisca.

B

So we get it. We documented because right now, groovy hooks behavior is just not documented, so we can fix it as we prefer. The commented, the current state and then, if you introduce in milestones for those who want a different behavior new milestones and member rubycles but yeah for me, I'd only feasible way is to actually do it on the course side, because otherwise you cannot really combine. Groovy hooks and Jake. Ask anymore.

A

Right so you say: leave the current one as, as the documentarian add new hooks, so that people can use different ones if they want to.

B

Yes or maybe just introduced a new groovy hook, so for me the main problem is the current state that we have LTS baseline, which doesn't have a fix. So if you just started off stage and say it's a fits for grooving it hooks then lucky it can be a bit closer to the neck, so ts release. But if you introduce new milestones that meant everything key, it will be much harder to Bach posture, it's still doable, but we need to talk about it.

B

So I think that you can just assign the section item to me because it was me who caused it and yeah I think just clean it up. So.

A

Just so add new milestones said no ID masses, add new gravy, Hawks and Jenkins core well.

B

Yeah we need two new hooks on Jenkins core and we need to fix the behavior of the init hook, maybe because so the problem that you need hook is is it makes no sense anyway, so we need to define stricter installation are rules there and I will probably just proceed with what Fran did so we, the routine status quo, like we had before the change, because right now we need who can be triggered in peril. Mr. old loaded can be triggered after everything is initialized, so you cannot really do anything probably visit.

A

Okay, the other issue with this core quest is the so there's a test here that tries to reproduce the race condition.

A

This test, initializer.

A

It's using in it to Emma.

A

So it's using a cloud and it's using a whole bunch of stuff I'm, not sure if it needs all this.

A

Was using cloud and LDAP security realm.

A

And a bit of other configuration and it's trying to.

A

It's trying to get the get tool, configuration and check that the file has been creators.

A

But this is, this has not been very stable.

A

This just try to remember this test when it's doing so once it finds to get tool file, it creates a file to say that it exists I.

A

Was trying to run after Jake asking before job loading.

A

So I'm not sure whether we need to adjust the test or not bring it in or.

B

This test, mostly this the code, is a Rican yeah.

A

B

As long as the code is written correctly, basically, the test just confirms the bed and doing it will be quite hard to be ended. So I, don't have strong opinion and I can live without this. Just being just could be moved to comment it out for now used to recommend it to me ya.

A

Know so yeah I think I'm happy with that as well. I would probably remove the test before merge. If we're happy to do that.

A

It's not reproducible locally from what we can tell franceska around 20 times locally and wasn't able to reproduce it fairly reliably, reproducible once the I, possibly slower and other things going on. Okay. So let's just agree for now, then that will not merge this, but to move this forward, we just need the groovy hooks sorted.

A

Is that fine with you from.

A

All right, no objections, so that's everything that I have. Has anyone added anything else or anything else they want to go through.

B

Yeah, maybe one question about plug-in installation manager, project idea: I wasn't following they get a shot close now, but my understanding right now that we don't have students applying feet right, saying.

A

A single students interested in it, okay,.

B

Oh, it doesn't particular blockers because these two can do come into breach if needed or we can implement whatever we need on our own. So yeah it was just wondering. What's the current state knows.

A

There's been users coming in questions and not with us. We know I'm, no one interested in the project that I'm saying you.

B

Know like a huge search of applications and questions just in several weeks, but yeah I would say that success ratio of these applications isn't a bit high. So.

D

Let's see how it goes, okay sounds good.

E

Yeah actually I was interested in this project idea, but you are allowed to apply for only three it's difficult to make out. So many proposals.

B

Probably you shouldn't.

B

To work on this, every definitely do something parallel or maybe there should be, could be some opportunities so yeah, for example. Definitely if we talk about dr. Pollock and dr. Druker system proposal, there is definitely a lot of opportunities to interact with Jacob, for this cup check sake, Carrie yeah, there might be some errors, I'm, not sure.

A

We know other than just being compatible with her.

D

B

Would say yeah.

E

So I'm gonna die sing. The single pull request to the plug-in installation manager. I guess there needs to be tests added to that PR. So, since the project proposal periods over I guess now, I have some free time. Since results will be announced a bit late a month later, I guess so till I guess something I can I can maybe contribute to some of these areas. Yes, tastes the same yeah, there's a why a mock test here, I, don't know.

A

Probably just infrastructure failing yeah just died.

B

Country is not stable. Engines sometimes wishes regarding crime, okay, even more suspicious to phasers yeah.

A

All right anything else.

B

So I will try to get milestones to request submitted tomorrow, because it's already a bit over dinner and since maybe a subject for the to bed portion they'll try to do as soon as possible. Sure we.

A

Get big great to get a sound.

D