Jenkins Configuration as Code Project, 5 Jun 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins Configuration-as-Code. Project meeting, June 05, 2019

Description

Meeting minutes: https://docs.google.com/document/d/1Hm07Q1egWL6VVAqNgu27bcMnqNZhYJmXKRvknVw4Y84/edit#heading=h.5memo7uf2obx

A

Okay, I, really welcome to the regulatory junk is configuration is called sub project meetings today is June. 2019 we've had several people on that call, so Joseph Patterson, ninja, commander adama know we have several topics and agenda thing, but we all just share my screen.

A

Okay, this screen- yes, I, hope this time, I don't mess it up, because yesterday we had the knowledge transfer and yeah. Finally, the screen share wasn't recorded properly. Okay, so yeah mmm I just followed the agenda template you should've had before so everything I wasn't able to make today, but I believe she will adjourn next weekend. So yeah. Let's talk about news. There are also some of these incompatibility for Jake asked.

A

There are some ongoing discussions about Jake, asked test automation in Jenkins code and also test framework enhancements, and if you have any other topics, you would like to add to the agenda. Let's discuss that. So does anyone want to discuss anything else? Apart from this list.

A

A

Yeah one of the topics we could discuss, we have one open request to the Jenkins core to just one, but one seems to be stalled about default properties, or maybe we could also add them to the agenda.

A

Okay, so yeah last meeting was almost one months ago, since that we had a bunch of junk is configuration is called releases.

A

Actually, we had well quite a number of religious scenes at that time. I believe the last release we were discussing was wonderful 14. So maybe you Joseph would like to summarize what changed since at that time, because you drive into the integrations yes.

B

So we fixed a bunch of the export issues we had, but that also meant, while fixing those we moved all the stuff out to the decided order, the respective plugins. So we no longer have any support plugins inside the latest release. So that's a good achievement. I would say that we that we now have everyone in every plugin has their own configurator that they used to pre hosted inside them. So so people can go ahead and uninstall support plugin, that's a and we yeah we mostly did bug fixes I.

B

Guess we had a a stapler converter issue because of a core update that was lucky caught in time before it became. Why sure I would say so.

B

And other small bug fixes yeah. We made some requests, though, from 1718 they're they're, probably a little bit of going straight to 19.

A

In terms of exports, yes, so yeah thanks a lot for fixing it quickly. One comment about the decoration is called support gates, but yeah. There is a way to achieve the market as duplicated on Jenkins plugin page, because here, for example, here it's not marked as duplicated, and it's also not much less duplicated in update centers. Don't.

B

Think it has a Vicki page, that's issue, I, guess.

A

Yeah, maybe it's also something to consider just to have a kind of Tom stoner there. So yeah basically duplicated a plug-in. So that is a process which we it's pretty straightforward. Actually, so you can use that in order to just bit the notice on a plugin page and in a bit.

B

A

So yeah it's something to keep in mind yeah. Do we have anything else about your new releases, I.

B

Think we code most of it like yeah few bug fixes that's not to look worthy to mention other words. I know, there's actually one important so so there was a bug where, if you were using docker instances or any environment variables to the config file that you could point to was was being or the environment variable. Wasn't the preferred thing. So if it was previously loaded to configuration, then it would always use the one that was configured inside, that it's the source, I guess or the configuration file over really like preferring the environment variable.

B

So that's one I would say.

A

Thank you. So what else do we have so you maintain years yeah now, it's official so in.

A

B

A

Background noise from London, it's totally justified yeah. So there was a discussion yesterday and now we officially joined the maintainer team, so we have missions.

A

So just in case we have summer breaks and other things we have mobile and wife in the plug-in and in terms of maintenance. So.

A

If we take a look at current repository permission on data by the way team, where you have emerged, permissions right, yep, I,.

C

Didn't give out support plugin because because we finished that, so if Joseph needs to do one more release that potentially no.

B

Support floating was the last one, so yeah.

C

Actually, if we need to deprecated it in the update, seems add, I need.

A

C

A

Yes, so this is our current configuration so proud. My is release both used by Evelina and we have joseph for me team and giving us this security contact. So this is the current configuration. The configuration is called plug-in and yeah. Obviously, there is a lot of things happening around in the project, so maybe maintenance will be more and more simple.

A

Okay back to the agenda yeah, we also got a number of integrations, so one of the topics already referenced by Joseph that configuration is called support. Plug-In is deprecated, so all indications have been moved to the respective plugins. That is also an I'm going work or for making other plugins company book. Yeah I think we can just switch to the next topic about cabbies.

A

There were some changes so, firstly, over past few weeks, I spent some time to scrub all existing physical issues. Nanjing is Judah so yeah. Before that we had some issues in github wishes. We had some issues in my Jenkins. Do some issues directly so I just spent some time in order to produce all the reports and put them in JIRA, so we use the dashboard to be educated to almost one ago, and now here you can see all the references and also resolutions so yeah.

A

There are still some gaps which I will clean up but yeah. Basically it can be a good source of information for whomever wants to understand what is not supported. I think this, the report that we have a list of what is supported because we assumed it is, but with our current frameworks, many things actually supported out of the box, though we didn't test everything so, but yet this does put tracks newly discovered species, at least okay.

A

So, regarding this dashboard, maybe it's a question to you team and Joseph what we do duplicate there first, because my understanding that we still have a kind of overlap between this and this plugin reckon.

C

We should add a link to the dashboards in that comment. I think mr. dashboards, there's one that shows all the issues and then there's one that just shows open their shoes. I think the open issues one is in the readme. Now, okay,.

A

B

Dear for the the plug-in tracker and github was more also for pull requests, because it's a lot easier to track. What is ongoing for pull request and github, at least so that was the idea for that. Yeah.

A

Which totally makes sense, because yeah educast plugin maintain ourselves expected to somehow facilitate integration reviews exactly.

B

A

Our joint in the list tab part 4 pull the request, so what I was doing, I actually I'm doing is joseph that it's rather for pool request when I was a scrub into the dashboard. I just went through the list of issues here and I hope I created JIRA issues for opening. So you may see here, yeah I haven't gotten named all the requests, but I believe that I went through this list.

A

Yep, so we can still keep this for tracking pull requests and then somebody takes a look and just creates a jitter, a major issue so that we get this dashboard. Because one of the advantages here that we have released s filled each kind of mm-hmm.

B

But that could probably be a nice integration to JIRA better clicking or pull request oversight. Washington we've.

A

Had such an integration, but at some point we disabled P, because it was our JV instance. Now there is ongoing project for migrating JIRA instance from self hosted. Instance. Sorry, toth'lazhen cloud. What we move to a passing cloud, maybe we will have a less performance issues and we will be able to reconsider that, but yeah right now performance was the main concern and the root cause. Why we disabled individual, is github I. Think.

B

The a blasian cloud list has also has a better integration for github, so so that you know also a fair point. It's.

C

Just need to be on a new version of Europe question. Clouds should be the same.

A

A

So you can also make the meeting notes by the way. Okay. Another thing by Joseph is actually. We now have a new query for Jenkins core issues, because, in addition to plug-in compatibility issues, we also discovered a number of issues related to Jenkins cough. So here we use the same. Jake has come to be disabled as for plugins, but yeah it just filters on all core issues, and here you may see that. Well, actually, it's quite a number of issues.

A

Some issues out of pull requests like I, did only consider configurations which is well, it's probably big, Mary. It's really and I think it's not just a single feature but yeah. There are also some add a little bit small issues. We are trying to fix like listing list view management default properties into them which we'll discuss later, and there are other such things and hopefully we'll be able to ruin some requests so.

A

A

Anything else about this topic.

A

Okay, one issue which still concerns me. A lot is about this one job floor. We didn't and Jake asked a chicken-and-egg so yeah, it's a pretty herbal tea issue. We have in jcastellan Yin that well, basically, a job loading is not really reliable.

A

So maybe it's something we could think about and maybe at the next meeting, because it's a big chunk of work and you're really procrastinate but I.

A

B

I hit it several times with some plugins and at least as well. That's there that expect configuration to be alive before it's there. Yeah.

C

I, don't have it in my setup, mm-hmm.

A

Okay, so yeah, probably at this dish, you'll end up in jab but yeah. This is what we need to discuss, because we have currently installation graph for Jenkins isn't really configuration is called friendly in any needs. So yeah, it's likely a massive purge for gently score. There.

B

Is also the luck in to management tool that we could probably discuss introducing them at the same time, so they probably need one before us. I would say yeah.

A

So basically, this is a project which happens on the umbrella of platform. Special interest group, so just I can tell open this page.

A

C

A

Have this project plug-in installation manager, Eli yeah? So this is a project which is currently in progress by Natasha. Stop where she is one of Jesus students. You can see some familiar names in the mint released and basically this project is going for to have a plug-in manager and chili library all I play, and once it's done, we could consider integrating this library into the core and maybe managing plugins.

A

My configuration is called the biggest problem with this plug-in you, this story I agree with you Joseph it is related, but the problem is that it still goes not in the configuration startup. So we a plug-in management would need to happen here, not here yeah. So it's another chicken and egg problem, because you can't really manage plugins from a plug-in and basically what it means for me that it shouldn't be a plug-in.

A

It should be rather a library which we inject into Jing is what file on startup and which does some management, and there are some ways to do that. One of the ways is to use custom work packages as we discussed before, and we inject this library or maybe we could just make it a part of changes called functionality which is also possible, but it will require discussion and also probably a job, but I think might make sense to make it a part of junk score. Oh.

A

Yes, oh yeah, it's also kind of a bigger story. I.

A

Just don't think that we'll get to it right now, because yeah this project is in progress so likely we will have something by August fingers crossed.

A

A

Yeah so for now yeah, it's safer to say that Jake asked just doesn't manage jenkees, plugins and yeah like we will have Jake ask support in the quorum in this tool we might have. You might have support of it into the same configuration files. If you want but yeah, it's storing it to be decide, cost I would say: okay, anything else about core issues.

A

Yeah, by the way, is probably that plug-in management to this list, because now we don't really have it.

A

A

Okay, so if there is no topics key, we can just move on to testing things. We basically have two stories. One is about automating Jake asked tests in the Jenkins core, so it comes actually from. Are these stories because hey we know about several bugs in Jake this course, and these issues are not the first defects we fixed in Jake the score to support the jenga's configurations hole.

A

So this query now doesn't support historical issues which have been fixed, for example, last summer, by Nicola below and probably will need to add them to the dashboard later, but yeah anyway, at least some whooshes represented here and when we fix something it would be nice to have some test automation so that we can cover that and yeah. We had the discussion about that yesterday address in the pull request and the proposal was touched. You have Jake asked integration test say in the Jenkins core. There are multiple ways to do that.

A

So one of the ways which was pretty straightforward is just taking everything to his course the seed, but it looks like a dis approaches, negative feedback from JC and Alex Harrell, because yeah they're concerned that jake has quality has a lot of.

A

Sorry, this test suite already has a lot of tests for the virgeen's penis. Yes, so basically, this is a test suite and the concern- maybe it's already too heavy. The liquid is all fitted by multiple approaches. So one of the approaches that we would just put another test fit here. So, for example, we already have from test fit for GD k, HS, which includes tests which are not relevant in java level.

A

So we could also put a test Jake ask whatever the suit here as one of solutions to address JC's concerns, but yeah it might be between and actually what a JC proposed is to rather have plug-in compatibility, tester so plug in a compatibility test that hasn't been discussed at this special interest group meetings. Yet right nope.

A

Do you want to have a quick introduction for this tool? I would.

B

A

Ok, so what we have here there is a plug-in compatibility test, our framework. Actually this framework is a kind of cornerstone of all new automation.

A

This framework has been heavily used when I worked in a job 200, then, when we working on Java level support in Jenkins. So this framework has a lot of enhancements lots of tooling the communication. Now what it basically does. It runs tests from a plug-in against a particular layer, gently score or work package. So it means that if you use custom work packages or other tools to package your own Jenkins for file, you still can use with this framework and then well, you can run into docker.

A

You can run it in local I think, but what it takes actually takes. Artifact, tiny and it takes edging- is accordin. If you want so you can, for example, plus custom. Urging is what file you can pass a custom sources from a repository or from a log directory and then plug-in compatibility test which will build combination of Jenga support file and the plug-in you passed.

A

So basically, it's a really complicated version of this command, so yeah. What we do in Jenkins, sometimes pry against the new gene, a spot.

A

Jenkins version equal, let's say what 164 so plug in compatibility. Tester is an advanced national debt and it also produces some fancy test reports and compatibility. Matrixes I'm, not sure I have any on this machine because yeah it's a new one.

A

So, let's oh I got some report.

A

Yeah plug in a PCT report.

A

Ok, it doesn't work so yeah. The demo field.

A

Yeah I'll probably apply some tweaks for that once I'm on a whistle to the zero but yeah for now, yeah I'll, probably just open it in such way out.

A

Pct 84 HTML, so I have no idea what what are the reports today? Oh yeah, so this is a combination matrix for some lost Java xi s, so you may see that actually we launched plug-in compatibility, testify against number of logins and against the multiple Jenkins configurations. So it's it was weekly release. It was LCS, and here you can see some test results. So basically, if you go there just well, you just execute a Jenkins I, give you some updates.

A

So it's not just this.

A

My maybe in verify Jenkins version, because we apply a lot of fixes to plug in form and to poem in order to make compatible this new version we automatically they dissolve in for 30 issues. We resolve issues with the plugins. So when just reading poem doesn't work plug-in come up, our tester can work, and this is a main advantage of that.

A

No it it's a lot of complexities and as misdemeanors we also have a lot of fun, keeping a consensus stable and yes, so what we could do, we could just run plug-in compatibility test against configurations code plug-in as a part of Virginia's Python. So we could run take the latest release of Jake as plug-in or maybe the development version, and we could take the under development version of Jenkins code and compatibility tester in order to a defect in the ability as a part of James pipeline, and we have pretty much the same.

A

We could also use PCT in order to do some integration testing can set a j-class plugin. If you want okay, any questions so far.

A

So yeah, maybe somebody has already tried PCT for Jenkins configurational Scott, yes and yes,.

D

It fails it fails because the first thing P city does is process classes. If fail, not is not funding.

D

One library jam, Jam, melted, J, Jamil library we use. If you do, the saying in the playing compatibility in the configuration, was called planning. If you do the same, it fails as well. So maybe we need to to do a hook in the PCT or adjust the lifecycle of configuration, as called play.

A

Yeah, so it's speaking of advanced weeks, you may see that there is a number of hooks here, because yeah this hooks I actually need it in order to work around some issues. We know about, for example, lotion hook what it does it just it properly retrieves well.

A

How the plug-in is organized? We spawned a two located, and here there is some just some vegetation logic which allows to understand whether the plug-in actually belongs to blows so yeah. There is a lot of such hooks, which you make the repositories working properly and if you want to use PCT it's something we will need to fix so yeah. It would be great if we have a shop for it later, so that we could take a look together. Maybe at the next meeting or.

A

A

A

So yeah the Joseph team. What do you think about using PCT for the repository and maybe forging his core once? It runs proper yeah, so.

C

We would move our integrations to PCT rather than and the actual Reaper is that well.

A

You can keep interpretations so as can be retained as we have, but we can use PCT in order to invoke this test against different agendas. Corporations which are not compatible by default, or maybe we could use PCT in other versions to test against Jake asked, doesn't make sense. Yeah.

C

Difference is worthwhile to be able to taste a lot. Recent call versions, we're already running against roughly the latest, LTS I think hey.

A

A

Current version in the baseline, but if you want to be conveyed more.

C

Well is that the build already takes quite a long time and very easy to have infrastructure issues I think that's! My windows isn't being run there anymore.

B

Windows not so much, but it would be nice to get the the fixed agents running out of disk space. That's that's an issue a lot because we have a lot of people trying to do pull requests.

A

Disk space wishes yeah, we were talking about it with Olivier is the the meeting criteria. So maybe we will need work a bit on improving the situation. Well, we will definitely need to do something, but he is complicated. Now.

A

One of the things which we actually hit a few days ago in that, if you want to import configuration or it should have no spaces in the past, no.

D

No it it was fixed, it was failure in the way in the test, because the path I was setting in the input text in the in the UI was wrong was wrong. In Windows in a little Linux was right, so I fixed that and now it it can have spaces.

A

Okay, so basically it's not relevant.

A

Yeah, but here basically at least some windows test, automation definitely wouldn't hurt.

A

Okay, yeah so probably.

A

Okay, I'll just keep it.

A

Okay, thanks for the fixes, okay, other related stories about Jake asked test framework enhancements, so you it's by Ramon and maybe he could explain our context.

A

D

We would like to to add Jake us support for us several plugins, so to go faster on the integration I added, an abstract class to to make it easier for plugging offers to make a plan test to check the complete round-trip. We with we set about configuring an instance sporting. The configuration important that consolidating that configuration again against the UI importing the configuration so far. The the sporting file cannot be imported.

D

So why did work around in the in the pr2? Just use the specific settings for the plugin each conference team as he wrote, because the goal of the test is not achieved because of the failure in the in the export. I think that maybe what we can do until the the export file can be imported successfully is just to crop the specific part of the plugin under test from the sported file and just import that that part with with these Chang in the PR I think the flagging offer is going to be short.

D

The the configuration is successfully exported and imported.

B

A

So how much is missing to get it working isn't about this request?.

D

Yes is searching in that yeah. Oh also, I was trying to validate the the ported file deported configuration against the schema, but I didn't manage to do that, because I didn't find a right tool to do that. I was trying to do Jake, sir or.

C

The judge, the schemer is very broken. Yeah functionality just doesn't work. Okay,.

A

Do we have justice for that yeah.

C

There's an issue with it with some comments: Allah I spin in an arrow on it, but it's quite it doesn't work. There's lots of issues with it. I fixed a couple of them, but it needs a good amount of work or a rewrite. I.

B

Think the best thing to do for this scheme is to rewrite it use a library instead or something that that it feels wrong that it's not like. It's handwritten the with some some, what it's called. It's sting, climatic or or jelly magic, so Java code, instead of like someone and Gooden so handwritten jitney code.

D

So I have a question for team. Is that is he he would be happy if I do that Chang in the PR instead of exported the file and just ignore it struct from this file, the specific part of the plugging and import import that part to be sure that that the the configure exported as a configuration of the planning is safely imported, yeah.

C

That should be fine. Okay, here are gonna get off now: okay,.

A

So we here, we agreed that.

A

Import configuration files as a workaround right.

A

Yeah one of the stories about this particular request. So, while we around yeah, there is a pull request from the junkies core and I'm kind of body blocking credit. So actually I wanted to understand what we do next Bala, which they approved it but yeah the situation with this pull request a bit actually yeah. We want to get rid of these default properties, but yeah. There are two ways to do that. One way is what is current in payment by Joseph just by restricting committed in Jenkins API.

A

So we need some verification and this method is not used anywhere. We have access code to so which includes open source plugins and, for example, some private source plugins I can access. So this method is not used and we could probably just lend this patch as a workaround. The problem that, if even if you less dispatched, won't be available in the LCS baseline, because we current but part of this change where we duplicate EP act.

A

Well, probably, we could, but it would require serious discussion with Oliver goons, as a LCS officer, and one of the workarounds I was proposing for this particular change is actually having Y twist sorry. Blood leads on the yogic ask side so yeah. There was a kind of discussion here and I basically proposed that, instead of doing this patch or maybe in this patch, we teach Jake asked to somehow ignore arbitrary methods be a bus. For example.

A

You may use this engine in order to just skip this method so that it doesn't get exported into a caste anymore. So my question to everybody on this call is: what do we do about it? Do we want to press? It is caught on the pouch, or do we want to have a perch on the Jake asked side, I.

B

Think a pad fit the Jake asks. I was fine, because I already did one patch actually for blacklisting something in credential plugin.

A

B

Because that was specific for credential plugging it was, it was exporting in a very specific place and it was reporting the wrong category, but it was a period. It was weird I shouldn't, be there it's gone now, but I think we should definitely create an engine for introducing blacklisted in other places.

A

Yeah I think it's something issue would be important for us because yeah. My problem is not with this bullet issue specifically, but with the fact that it's rather it's actually ship because yeah, you likely have a lot of such methods and plugins and by having Kuwait just blacklisted I'm on Jake asked side or maybe like we did for JEP I forgot the job, yeah Jeff 200, so.

C

A

Sorry for Jeb 200 a we actually have black list on the plug-in on our site: Jeb 200! Well, yes! So what we did in this implementation is that we actually support passing every source inside plug in directly which block these particular configurations from expert and I. Think that you can pass this resource without modifying ETS without depending on new versions.

A

So it was pretty straightforward for us to just wipe these particular things by a resource file, and probably we could consider doing a similar approach for Jake asked as well. If we hit this issues a lot for Jenkins quarry, we can just hot ot to have an engine inside the j casting and then we can extend by reusing some of the quote from Jeb 200 if needed.

D

Can this file be set by the plugins itself, yes to be able to the player in sulfur to to write his part yeah.

A

This was a whole idea because something like dozens more than 100 plugins, what you have 200 and we didn't want to bump our dependencies to the recent versions like we would have needed so yeah. Here you basically yeah. There is a remote in cross filter, which you put directly to the repository, for example here and here here, project 200 view, at least to cross civilizations and said, pipeline support, plug-in and then.

D

A

Put the resource file and it starts working yeah.

D

I wish ask him to do the same for Jake as the plugins on that can do that, not only in there Jake as plugging itself, I.

B

Would totally agree that.

D

B

Be the way forward: I, don't wanna yeah, so.

A

A

So yeah, this is what we can do, so we can just create a file called something like. Let's say it uses Hudson remote ink and we call it our configuration as codex, but at least I.

D

Like the name meaningful.

A

Yeah you somehow yeah with these methods we ignore yeah. It might be a bit much tricky to implement it because, let's say we can have inheritance so yeah. We will need to somehow handle that.

B

And question: could it not also be annotations instead, perhaps or both.

A

Sort of annotations that annotations might require corp. um So, for example, if we just delivered on additions as a part of existing and configurations code, clogging, then you'll likely require a new port. What we could have is, for example, having a new model in Jake. Ask like something annotations, which would, for example, will target the Java, 7 or Java 8, essentially to Jenkins most and then plugins can include this annotations library. So pretty much like. We do, for example, for symbol, annotations or findbugs annotations.

A

B

Kind of leads into another thing that me until have been discussing in private is that we should probably consider splitting configurator API and the core plugin again or they to take, has plugin yeah.

A

B

That is, that would be now we get back to where I it's beneficial, to split. It basically need to pump the core, and some plugins aren't ready and yeah.

A

B

We already approached.

A

This topic earlier, I believe yeah for me, I do have strong, yes, oh there is by the way it relieves the job from Nicola about declarative data binding, which also reference with api's. Regarding splitting, so we had an old issue for me. Still court really believe that heaven s Pete is a really important because yeah, it's the magic cascade, Garrigan and G cos kPa.

A

So why it's important, because we have a pull request like target Jenkins 164 that one so once the dis put request is ready, whatever annotations may include applying in using this notation so to have to bump to discussions which is not acceptable for many maintainer and another thing that, for example, if we dissolve chicken and make load issues in Jenkins code again, you will have to bomb Jenkins core and then all the dependencies will have to bunk as well. So that's why I believe it?

A

This ticket is important, and here probably we could device that yeah.

B

The other thing is that we looking at the numbers I think we saw that configuration is cool. Most of them were, 90% was above 250, LCS, so yeah, so so it I think for the future of take has it would make sense, because we need new features.

A

Okay, so yeah I'll, just open for discussion. Yeah I basically told all the discussion is Nicola and he's fine.

A

So yeah I'd, open that and yellow have what we need to investigate it, but I believe that for sustainability of the project, it would be something really important yesterday. My addition, the quest they didn't get enough and I'll just needs to be reward completely, because there is no way we resolve owners conflicts in it. Yes,.

B

I think actually I know Tim already started working on it. He did the most by minimal Viable Product. So he already has a branch and everything working. So okay, it could. He had some working prototype at least.

A

A

Okay yeah, if we could do so, it would be really nice so yeah and if too much it's a pull request.

A

Okay, you know just see a team so yeah, you know what to do. Okay, yeah, because yeah, if you get it landed, it would be really helpful for the project. I. Think.

B

So yeah it would be nice mm-hm.

A

Okay, yeah, that's cool okay, so we have seven minutes left yeah, so this engine is something we'll discuss because, yes, since we depend on this story, some wood, maybe we will be able to deliver it yet to be discussed, and since you guys work on that already, you can take a look on it.

A

B

There is one other thing we probably could talk about is I know that the test framework, the Jenkins test framework, if there's a plan to pump the version. That would also be very nice because that would mean we could introduce Jake has stuff. We have a lot of test method. Can.

A

Show you something because yeah in another google Summer of Code project, we are already working on benchmarks. Yes, for Jenkins test harness and one of the things we need for benchmark anak. So there was a demo last week this democracy, video, but would it have? He is just a second yeah there's a lot of coal, but yeah there is configuration, is coaching mhm benchmark, so what it means it's a framework which allows search.

A

We configure pre-configured benchmark instance using Jake's computation s code and we already use it in at all strategy plug-in so in at all strategy plug-in we configure our benchmarks using Rica's, so what it includes here. It basically includes dependencies on configuration s code, which is optional, but yeah I suspected that something like that. It could be a good foundation for other test framework improvements.

B

We have, we have a few functions inside Jake asked that could be benefit and instead of us distributing it, it would be nice if the test on it distributive mm-hmm.

A

Yes, so I believe it can be discussed in the same thread because, yes, since we get some pushback about the inclusion, Jake asked test and before Jake this test, harness is also on the question. But we can try discussing with.

A

All cases yeah so I'm still using two new keyboard and.

A

Yeah, basically, I think that we should discuss it in the same. I might increase this for Jenny Scott, because yeah I believe the stories are interrelated. Yes,.

B

A

My expectation is that, as long as the defenders user, optional.

A

B

A

So as long as we have a dependency as optional in Jenkins s harness we are fine, but he is something which needs feedback, and now we are also waiting for feedback about this pool request.

A

Okay, what I will.

A

So yeah I think that it's yep jakers plug-in is getting so I'm touched. So if you get included into default test from person, is you know issue with it, but here let's discuss it is why the community.

A

Anything else to discuss today.

B

Discussed a lot yes,.

A

My body is interested. You can just take a look at many meetings. Yeah, you start to see so fast progress and the plug-in and yeah. Now we solve this test, automation, etc. We can work towards even more production-ready and, of course, stories like, but it is but expert and maybe even JSON schema is something which is really important to us.

A

Yeah, so thanks all I hope see you in two weeks will.

B

A

D