 Yeah. Okay. It's been recorded. Okay. Um, so yeah, today is July 31, 2019. And, and this is the jkask meeting. And, and today we're going to go over the reason releases. Yeah. So we had a reason release last week. I can share the screen. I don't know how that's gonna look. Let's see. Where do we go? You are now presenting. How do I, I forgot how to share screen hangouts. It's if you move your mouse to the left, there is a panel and the screen I see. Um, application window. No, it's gonna be weird. Okay. So yeah, I don't know how that's gonna look because wide screen. Um, so yeah, um, we had a bunch of fixes from, um, I don't know how to pronounce his name. I will die. Yeah. So fixing up the configurator data. So it will pass empty collections instead of, yeah, no pointers. And also try to fix up any configurators that are like required. So, or mandatory fields, trying to discern that. And, and then OLA was nice to print out secret variables that wasn't resolved during import. And yeah, and then we added a possibility of converting and exporting sets. Um, so yeah. And the number format exception when logging or exporting Jason was fixed. So, um, yeah. And then some test fixes. Yeah. So basically quality of life release, the number of improvements to data bound configurator. Yeah. So probably it will improve compatibility with a number of other plugins. We still don't yet know about. But yeah, to be seen. Um, next point integrations. Joseph, um, your screen's very hard for me to read. Maybe zoom in a little bit. Yeah, yeah, it's too minute. Yeah. That's about that's better. Yeah, I think that that's fine. I don't see it though. So that's weird. That's fine. Yeah, that's because you have. Yes, I have. Hopefully that's better. Yeah. Okay. Yeah, yeah. That is great. Okay. For all two screens. No, all two wide screens. Anyway, um, yeah, that was that was mostly the release. And then we had some discussions about integrations, I guess, if we can move on to that. Um, we quickly discussed moving the vault secret support to the Haschicope vault plugin to avoid clash loading issues and also just it seems to be better suited to be located in that plugin. Um, so yeah, um, I have gotten maintainer permissions. So I should be able to make a release whenever and I got okay from the maintainer. So yeah. Okay, so if we got everything approved to the school, everything is approved. So should be should be I'll see if I can get something out. Mm hmm. To quote that moves it around. Basically, it would be a breaking change. But I think it will take a while till we are ready to release it. Because yeah, Haschicope vault plugin needs some facelift, maybe some test automation. Well, we have the test automation actually already here from jcasc we can just move over and we can also I will move over the other stuff. But the facelift I pretty much fixed the palm. I already set the pull request for fixing the palm to the plugin. So hopefully it should work. I have had issues running. There was plugin dependency issues basically. But that was just the the palm being misconfigured actually. So yeah, I'm just looking at the code and the code should be mostly similar. Otherwise, there's people who have open pull requests that might have some issues that that fixes it. And probably submit a couple of pull requests. Well, first, the common ones like release drafts dependable. It makes sense to enable it from the beginning. Yep, makes sense. Yeah, this plugin is tested on Java 11. So it might be something to fix as well. Yeah, I think so too. Well, basically it runs on docket machines. So I assume that the tests that they actually deploy docket in order to be complete, which is not surprising, but you might need to adjust some bits in the logic. We should be able to use the recommended Linux agents to use Docker. So well, basically our Linux agents offer docket. So theoretically it's just a matter of the label change. Practically it knows. And then I think that people want actually the updated version of there's a new version of the Waltz driver plugin or Waltz Java driver plugin, which that has a Kubernetes support as well. And then there was a feature request to actually support agent, Walt agent, which is like a proxy client that handles like caching and auto authentication. That seems to move that feature request over to this plugin. Yeah, yeah, yeah, I'll, I'll, if I move it, I'll add it as well, I think. But that should definitely be possible. Yeah, basically the test won't pass on Java 11. Yeah, and also build on Java 11. Yeah, so I will probably submit a pull request for that. Well, basically it's not going to be worse. So yeah, I approved the plugin form thing. But yeah, I think we can just have the creating changes incrementally. And yeah, submit a release drop another things today. Sweet. Oh, you can do that if you do it first. We'll see. So yeah, that's probably probably also ongoing development, I guess. Yeah, you can zoom in this screen too. Let's see. Was there anything else on the other side? Where did you go there? Yeah, this was support Waltz agent. That would be a nice feature. But it moves to Haseko approval. Yeah, yeah, and you, you created a issue about improving the simple conflict. Is that something we can actually solve? Or is it something we have to solve upstream? Well, it will likely require purchasing structs plugin in addition to JCASC. Because structs plugin basically has no API methods which take context and account. So when you look up for symbols and whatever it doesn't take, for example, base class, generics, all the things, we could utilize in order to improve symbol matching. But the improve is a keyword there because it will never be ideal. So again, we would just address some use cases out of the box. For example, I think it's not a secret we had symbol collision between one of open source plug-ins, SSH slaves plugin, and called this NIO SSH slaves. And the reason for that is because, yeah, since the plugins have really similar functionality in some sense. So, yeah, there are functional differences, but you're basically they have common classes like SSH launcher. Though they're different SSH launchers and obviously JCASC wasn't ready to do that. Yeah, and I also think we saw Azure had issues with their credentials. Yeah, exactly the same. Yeah. Yeah, the credentials run as some dodgy looking card, though, I think. Yeah, well, it still can be improved, I think. Yeah, from what I've seen in the credentials plugin, we will actually need somehow to somehow resolve generics to make a guess where the symbol belongs. Yeah, working with generics in Java is probably not the best thing already. Resolving generics in a safe way with class inheritance. Let's see. But it might play out. We also have the issue that we probably haven't solved is inside credential plugin. Actually, the configurator, of course, breaks whenever something is not right. So it just breaks everything instead of the one that is the problem. I think certificate also currently is like the certificate credential is currently broken, which is coming from credential plugin. So those two are like there. Yeah, there is a compatibility issue for certificate credentials. But here, basically, it's not broken. I would say it's just a horrible user experience. Yeah. If you really want to configure certificate credentials with J-Cars, what? Yeah. You can, as we had someone, there's a workaround, but it's not nice. You had to do, you had to encode it in Bay 64, as I recall it. Yeah, I can look up for issue. It's reported in Jenkins, but yeah. So those are the ones that require a file. Exactly. It requires a file and the workaround is to provide it in Bay 64, because then the code knows that it should make it right. Okay. Yeah, I already forgot the Bay issue bit, but I remember that it was a horrible workaround, but there was a workaround. Yeah, we will need to do something. I guess one of the ways is to actually just introduce new credential type, which uses not file, but whatever string, so that you will have another credential, which would be independent. There was a security issue, why they weren't using string. I think that was why it actually broke. Yeah. So security stuff, we will figure it out. Okay. Right. So yeah, I guess we can move on and there's still something else. Well, there is also another issue, which was reported recently. It's just a second. It's a jcask configuration history. Oh, yeah. Yeah. So basically, I want to bring up just to get more feedback, because it looks like a really nice feature. You don't happen to have a screenshot showing what the other one looks like. Or is that probably on that? I think it's on here. This is string. Oh, there was a recent release of pipeline config yesterday. Basically, they reused the engine of job config history and facelifted this engine. And yeah, I see no reason why we couldn't do the same thing for jcask. Maybe an additional plugin. It looks really plausible. I like the facelift. So that's nice. So I just brought up this topic. I do not want to work on it immediately and I'm not sure whether anybody wants to plan on that, but getting some feedback and maybe looking for contributors would be nice. It looks promising. But usually you, usually most people have that. So in version control at least. So I don't know how nice it, of course, if someone is doing manual changes, I'd be more interested in those. Yeah, a lot of manual changes people are making. Yes. We still have CLI support. And I want to better view the configuration without being able to make changes to it. That too. So yeah, something to keep in mind. Maybe we could expose configuration as code in a new permission and not be admin UI or something. Yeah, adding permissions always require additional steps. We can definitely do that. And there are some examples of plugins which already do it. But yeah, for me, we had a larger discussion in Jenkins project about having freed on the administrative UI. Because it's not only about JTask, there is a lot of features in Jenkins. For example, if you want to access system logs, if you want to just see what is the system configuration. Without being able to edit it or what you do. Basically, currently, all the permissions are locked down to Jenkins admin. So if you're admin, you can do anything. But just having a way or person to have freed on the access code in the state of your eyes would be nice. Maybe JTask could be also part of that. Yeah, absolutely. But I think the problem is that everything's just built around checking the administrative permission. Well, once the Jenkins offers another permission, we can be considered it. Yeah, we can introduce new permission inside the JTask specifically. It could be a quick win. Or we can wait till eventually Jenkins code offers redundant permission. Okay. So should we move on to community-match stuff, I guess? Sure. I guess you take it from here. Okay, so just quick updates. We have got some progress on community breach. Basically, I got all preliminary approvals to run this program. There is a pending request to Jenkins governance meeting to approve the final budget. The meeting will happen today. But even if something goes wrong, I believe I can crowdfund the budget from other sources. So I would say that we can proceed with the project. Basically, now you have the current expectation that you're sliding on the code. Now you'll be a student. Joseph will be mentors. At least elite mentors. Other people are also welcome to participate. And we can kick off the project once all of you are ready. So even tomorrow if you want. Sure. So then would you like to say something? Yeah, yeah. I think I had a discussion at all like, yeah, so I think we're done with the preliminary stuff about the way we can proceed with the project. I think something that I wanted to discuss is first of all the guitar chat. Yeah, because we lose a lot of a lot of a lot of important stuff in the channel because there's doubts and stuff. There's issues by raised by people. So we might lose important discussions there. So that's what I proposed. Like we could have a separate guitar channel for the community bridge. It could be named anything. Or it could be named ID integration and stuff. So if you want, if it's created on behalf of Jenkins, that would be amazing. So Jenkins slash community bridge or Jenkins slash ID auto completion. That would help us a great deal. We would be able to discuss anyone could join. What do you guys think? Sounds like a good idea. Yeah, I need something. I can create a chat right away. You just need to be on the name. Yeah. I think you can. What name do you think? Since it, I think the project is like it's three phases. I mean, there's no, there's no collective name for it. I mean, do you want like J, J cash, J cash community bridge or something? But if you keep a community bridge, then it would be difficult for people to find. What if in the future, if anyone wants to come in and contribute to a, but the ID auto completion, it would be difficult to find the channel or maybe you could name it something similar. Maybe ID auto completion or what? I mean, excellent. Well, we could. We could call it Jikas DevTools or something like that. Yeah. Yeah. Yeah. The problem for that. Yeah. This channel will still have a limited lifetime, I guess, because in longer term, there is no sense to have separate channel when we have a main configuration as code one. Yeah, we have to just keep it and shut it down when it makes sense. Okay. So Jikas DevTools project. Yeah. Okay. Yeah, I want to mention community bridge there. Also, if you want taken. I don't think it matters much. Okay. Okay. Okay. No, our configuration is called DevTools. Whichever. It's long, but I mean, I'm not typing it. Okay. Let's keep it as is. Yeah. I'll create the channel now. So while I do that, you can just proceed with the rest. Yeah. So I think the next thing that we will discuss, I think we just skip the phase one initiative for a minute. The Jenkins IO page. I think you were saying that you needed you were going to do that. Right. So I think we can agree that would be done. Do you need any help in setting that up? Well, I didn't plan to do that. It was my understanding. Okay. If you want. So I can do that if needed. But yeah, I think that it would be, but if you just create your own page. So we already have a sub project page for JCASC. Yes. Basically what you could do, you can just create a new page and the link I'll provide right now. Thanks. Thank you. Oh, yeah, it looks brilliant. Sorry. It should be improved this page. Yeah, you can improve this page, or maybe you just want to create a new page. So similar to what we do in JSOC. Basically, you can take the JSOC template with all the metadata because it's a separate layout type. Yeah, not this one, or maybe this one. Yeah, you can, you can inline your Google Doc. Inline everything, your Google Doc file. Yeah. Yeah, yeah. I'll share it with you guys before, before I begin. Okay. You just send a poor request and we can have a lot. Yeah. Yeah, right. So, yeah, I can create a skeleton for you, but yeah, you can do the same on your own. Yeah. It's not a big deal. So, so do you want me to create a poor request or something? Yeah, just create a poor request to genkisayo. And would it, would it be any domain under slash JSOC or do you want me to do the second one? So under slash JSOC, you can just create new page like community breach, Jcast, the DevTools or something like that. And yeah, you can just create a new page and reference it from the existing main page. Yeah. And then you'll help this machinery. Genkinsayo, right? Yeah. Okay. So basically this JSOC shows it's all configuration as code. So you can develop it locally. Yes. And you will need to study it anyway because for blog posts, et cetera, we use the same platform. Okay. Then I think the, yeah, we have the last one that the candidate invitation. Yeah. I think that's the invitation to the organization. Thank you. Mm-hmm. Yeah. I think that you can just start or something. And we get the formula. So what I'm going to do is I'm going to start with the first one. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. Okay. So what I'm going to do for that. You mean, you mean a bit hop organization, right? Yeah. So for get hop organization, I will just create a team like JCAD tools or whatever, add all participants and make the repository and the repository available to all participants. So I will do it right after a meeting and you will be able to request the reviews and whatever. Okay. Yep. I think that's for the normality is part of the I think we left with just one discussion point. I think the initiation. How do you guys want to proceed? I mean, Joseph, any ideas or thoughts? Any discussion points? Since we're dealing. Is this how to get started? Yeah. Yeah. Yeah. Yeah. Since the first one is I think we're trying to fix the Jason schema, right? Yeah. So how familiar you are with Jason schema and the configuration is code schema. Have you been looking at it? Because I looked at the phone. Yeah. Go ahead. Go ahead. Yeah. I mean, so one, I just get a bit familiar with Jason schema and then I'd start with the Jenkins with no plugins and just configuration as code and try and explore it and try and validate the schema against it and explore what the issues are and just and then tweak, try and tweak the schema to work. So something you can validate and then take a look at what changes you need to do to the code and also one big thing we'd quite like to get out of this is testing out of it. So if we can look at ways to improve the testing of the schema so we don't have regressions. We had suggestions to move the generation from jelly into being generated from Java code because then we can test it a lot easier and it's quite likely a good thing to do but so I put it up into discovery analysis and just looking at where easy wins are and where the bigger ones we can be. Okay. So one question about that. Yeah. So you can come here. So if we start creating this tasks, would it make sense to create a project within a configuration as code plugin repository? I mean, we can create a project. Yeah. We can create GitHub issues for stories you want to deliver on then it will be much more visible. Yep. Okay. Yep. I think that would be a good idea. Okay. Get help. Project. We've been. Also another thing I wanted to notice when do you guys are when are you guys available like for floating a noodle or something or maybe a 30 minutes meeting? I mean, what are your general availability times? That's always a difficult answer because time zones. Yeah, of course. Create a doodle. I'll create a doodle. Yeah. So this time works good for me on Wednesdays and Fridays. I do the doodles. Yeah. You can catch one GitHub or get her sometimes. Yeah. Like I'm a lot more available on GitHub and get her than I am for current for calls. Yeah. Yeah. I'll probably just want to get from my life. I guess. Yeah. Get a notifications. The best. Sometimes I don't see. Get a notification for hours. I highly recommend this one. Notifier for GitHub. It's a nice extension. Just keeps you. Yep. Oh no. Oh no. Jordan. I just can't. My emails work pretty good. Yeah. Probably unsubscribe from many repositories to make it efficient. Yeah. Well, I unsubscribe from the ones I don't want. But yeah. Damn it. Subscribed to too much, I guess. Unsubscribing is good. I made. Manipulating some production and I'm watching to them. I still have a lot. Yeah. Sounds good. Okay. So. Yeah. All the machinery for the project. Today. We will still need to turn on the project. And I mean, once we have everything in place, we need to send a kind of welcome message to the developer manatees. So you can reference channels today. You can summarize what you're going to do. I mean, the places you already have in your proposal. And you're probably, it makes sense to do the link there. So if you get active feedback from somebody, it would be nice to take the availability in the account. I think. I think it's either tomorrow or maybe the next week. Yeah. Okay. Yeah. Sorry for distracting you with machinery stuff. No. Yeah. Just to discuss the tasks. I'll shut up. Okay. So yeah. Yeah. Anything else? I think, I think, I think no, no, I don't think anything. I think we would, as soon as I just bought the configuration, I need any help. I'm just stopping you guys on the guitar channel. Sounds good. Yeah. I think that's, that's it. Okay. To, to, to just end the call. Then have we done anything else? Probably waiting for. I guess nothing else. So post updates in the guitar channel. Once everything is created in the least. Sure. Yeah. Sure. Sure. Yeah. Do we have the next meeting in two weeks because it conflicts with Jenkins both then we can probably reschedule or just skip it. Okay. Or some results. Yeah. Are you going? No, no. Nope. Yeah. I'm not going as well. You shouldn't worry much. Okay. But yeah, maybe we didn't, I would like to join, but yeah, she would be able to join at this time frame though. Yeah. It's a bit late, but it's okay for conference. Don't keep it as it's right. Yep. Sure. Yep. So yeah, then I guess that's it. Yes. Joseph for running the meeting. Thanks to everybody for. Thank you so much. Have a nice day.