 Okay, welcome to the regular Jcast Coffee Sours. Today we have only two people on the call, me and Tim Jakam. So yeah, this will be a really quick session. Yeah, we'll open our regular agenda. So I guess for the next meeting we should add how was the summer to the agenda. Okay. So yeah, we'll fix it later. So regarding our common agenda, did you have any new releases since July 3rd? Yeah, there was one release, 123 on July 3rd. Would you like to summarize it? Yeah, so certain plugins that took, it was mostly scripts. So now support multi-line export. Basically if there's a string that has a backslash n in it, then it will be exported multi-line, which makes it look a lot nicer and it's a lot easier to maintain. I guess that's the message here. So that was a really nice addition. There was a bug with the export viewer where you had to copy the whole content previously. Now you can just select parts of it out. There's just a very minor CSS fix. And the other one is floating point values were being exported and getting weird YAML conversion done to it. Now we properly support floating point numbers. I think it was coming up as like bang, bang, something, something. It wasn't exporting very nicely at all before. Basically it supports both float and double types, right? Yeah. The code is around double here. Yeah, that's cool. And that's it. And I think we have a couple of small changes pending release. Data bound configurator to convert and export sets, number for exception and system log when exporting JSON schema and unit test failure on Windows only. Yeah, maybe we should think about enabling Windows by default. It just takes so long. It makes the build on the PR take up hours to even out. I've came back in the morning after creating a pull request and still had it not run before. Yeah, so basically we have issues with Windows builds when Jenkins core rebuild is running. Because Jenkins core rebuild consumes a lot of Windows execution time. And we hit the limit in our cloud API provisioning. So when Jenkins core rebuilds to the stuff, Windows nodes are even slower than Linux and Linux is very slow. Yeah, yeah, so that's why we don't use Windows because it can take a very long time for a pull request build to go through. So yeah, I guess I'm the only one who uses Windows on the regular basis. Yeah, I think Joseph uses Windows as well. Okay, then it explains why he kicks it. Yeah, basically when I discovered the pull request, I was working on exactly the same piece. Yeah, no. Joseph does the same thing, but I don't think he runs the tests locally except when he's releasing. Yeah, fine. So anyway, we have some bits stitched for this release. And we have one change from a video pending about no point of exception for empty collections. But yeah, at least it's not ready to go so far. Yeah, it's pretty close. It's just a couple of questions. Yeah, right. So basically what it does is if it requires a list and if we see that the field is mandatory, somehow then we should create an empty collection, which could be a good improvement for some import cases. But yeah, we still need to finish it. Yeah. And this is it. So yeah, there is a bunch of stall pull requests. But yeah, this one is just a minor quality of life improvement. Yeah. I think that that's it for now. Yeah. Yeah. So regarding Congolian activities, do you have anything to do with the work scheme? I'm currently looking at the configuration SPI. Configure the API? Yeah, configure the API. Yeah, just looking at the work that was done previously on it and trying to figure out an API. It's not the nicest because it assumes input streams getting passed quite far down to YAML reader. I've got something that kind of works, but I'm not quite happy with it at the moment. But sorry, it's not the API plugin. It's the API for configuration sources. It's to allow plugins to support S3 sources and Azure sources and whatever sources they want. Yeah, have you some cut to your slide in about that? Because I know that he was about to input to his project proposal. And whose project proposal? Yuffie's. Yeah. No, I have his slide in. I don't think he's looking at the configuration API. I think he's just looking at the ID integration and he wanted to take a look at something else beforehand. I think the dry run. Yeah, it's a long way away. Okay, so yeah, basically, my guess is that if he wants to support three IDs, it would be rather quite a project on its own. Yeah, I think. If you have sliding on this call, we could have discussed that. But yeah, I'll just comment here. Yes, you can know that. Yeah. Yeah, there's the question about rich funding to the Jenkins board. A good preliminary approval. So basically, we have everything in place. My plan is to follow up in the community. Sorry, and the developer might at least once I get final information from the board, but yeah, it looks like everything is set for this project. So we can start with something August 1st to start it officially. But yeah, it's basically up to you, Joseph, and sliding. Okay, sounds great. This is what I want to do here. Any other ongoing activities on your side? No, I'm just trying to get the build monitor plugin to not export a lot of extra properties in the view. So three line change, but the build tool, the build tool is quite outdated. So I was trying to fix that up a bit. Yeah, that's cool. Yeah, on my side, I'm working on some changes. But yeah, they're in the prototype state. Okay, I hope that they will be come public in maybe one month or so. Yeah, I can't really tell much about them right now. Cool. But yeah, I'm trying to do something. So yeah, the garden issues, we got quite a few. The plugin compatibility was not much. It just doesn't work. Yeah, and this is the issue we were discussing before the call about the export issues, leading to no point of exception. Yeah, maybe there's something we can do around that because one credential type that doesn't support JKS can stop all of them being exported, I think. Yeah, it looks so. This particular type is the main credentials. Yeah, it's probably the AWS credentials because if you scroll down, it's got all the types that he has configured. Yeah, the way I wanted to improve the export they need to track the pass because it was working on export issues for a while. And now it's really difficult to bring also them sometimes. So regarding AWS credentials, you're basically it's surprising that they don't work because, well, I test this plugin and it works on my machine. There is some edge keys. Yeah, all the rest of them look like very standard plugins. So it uses AWS credentials. Simple. And I'll show you it works for me. Okay, well, we'll see. But yeah, we get to stop that. Maybe it was a new regression. Yeah, he hasn't shown all his plugin versions. Okay. So yeah, maybe it's something to touch in the template because we have plugin version probably they didn't get that it's about JKS plugin. Yeah. Yeah, it's a quick piece. Okay, so it looks like we're getting some progress. Yeah. I guess we key. So when you release, you'll be caught eventually. Okay. You're getting the same issue as I am. It's showing two draft versions. I think it helps kind of bug at the moment. It looks like it's released the draft ratio. So why it shows two versions. So you may see that tags are different. And you're probably it was caused by it because I have changed the pattern. And yeah, so that in a few repositories. Yeah. So basically what I need here is this thing. So five days ago, I changed the name template. And since name template is not ever written, it looks like it led to these reports. And yeah, it's quite hot because so before that we were using minor patch version there. Yeah. So we use two digit version mostly in Jenkins Core. Well, Jenkins Core and plugins basically what you've got here. You get two versions is exactly the same version number. Is it because the configuration has changed and we haven't released? It'll probably be fixed on the next one. It should be. Yeah. Is there a way to discard a draft? I didn't even know you could have multiple drafts. Yeah. Delete my echo. Delete. What do you find now? Yeah. So basically drafts are visible only for repository maintainers. Yeah. I wish they were visible in public because basically there is nothing to hide here. Yeah. I mean, you can see a change lock of pending changes. Yeah. I was exploring it a few days ago because I'm working on a release router for Jenkins Core. But yeah, it looks like there is no way to configure a public release router in GitHub. Yeah. Does GitHub community feedback form? I think you can see in feature requests like that. Yeah. Right. Whatever. We can survive. Yeah. I'm still waiting for my beta access to GitHub actions. But you're doing it your part. Okay. Good. I think you're moving forward. The other thing was a fair few issues on Jira. I just had a look before. Well, not a huge, there's not a huge number. I closed off quite a few of the ones that have been fixed already. Yeah. Basically, it's what I think about in the list because yeah, what I just thought that it really needs to be default assigned. Yeah. Jenkins Jira. And I'm not sure how much time she has for that. Yeah. I think she has time to monitor it. Yeah. So yeah, we have quite a few issues. So basically, I track GPS capability ones. I'll try to keep them up to date. Yeah. I think that's fine. The most of the traffic goes through GitHub anyway. Yeah. Yeah. If you discover something, we can just peak. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. I think we just peak or peak peaks or near contribution. Yeah. My personal preferences towards using Jira, but yeah, basically use a bit happy issues. One person. Yeah. So I'll just fix one because I definitely missed this one. So before, again, okay. But yeah, this is a common case. Well, pretty much the same as GitHub issues that people would create such requests for, yeah, for Gcast plugin. And basically, we don't want to work on any new integrations inside the plugin like this. Yeah. So fixes, yes, for sure, like the recent fix for property for extension resolution, but they are not new integrations. Yeah. Okay. Anything else to discuss today? I don't think so. Okay, so if so, I think we can just close the meeting and get some time to talk and something. Okay. Yeah, thanks a lot for the time. No worries. Okay. Hopefully in September, when vacations and Jenkins Volta over you will have more people on the call. Thanks a lot. See you in two weeks. Bye. See you. Bye.