 Okay. Cool. All right. Welcome to the JCASC office hours, January 29. On the call, we have myself, Tim, and John. This hasn't been a lot going on the last two weeks. Directly related to the JCASC project itself, there's been a couple of changes related to going on and core and in the bomb, but no direct news and no new releases. I think there's a few minor pending changes to be released. Just, okay, the only change is fixing a typo in the POM file, basically. So no rush to release that. So yeah, not too much. In regards to related development, we have some system read related work, which is to help give a, it's got two main purposes. One to give a read-only view of Jenkins. If you're going full configuration as code, no one changes anything through the UI. This allows users to see the configuration and export it, but not to modify it. And the other side of it is to empower users to basically be able to see how the instances are set up and allow them to contribute easier. If you take CO.genius.io, it's very hard to contribute to. People don't know what plugins are installed. Updating a plugin is very difficult. People don't know how it's configured. And I think a lot of it is done quite manually. So that's a very good example of where it will be useful. There's been a JEP. That's not actually the right one, so that's limited admin. There's a separate JEP for system read. It's JEP 224. If anyone wants to take a look at that and send any feedback to the mailing list. So there's a proof of concept implementation of it on Jenkins.com. There's a pull request on configuration as code showing how the UI would look to someone's system read. It changes it a bit to hide some content in fields that aren't relevant because they can't change them. But it's pretty much the same. We've had some work recently done on initialization milestones, which is to help fix issues with configuration as code modifying the Jenkins configuration while jobs are loading concurrently. Francisco has seen the pull request. There's been a fair bit of comments and feedback going on there. I think it's mostly waiting for a downstream pull request in JCAST and possibly and I think he's going to send an email to the mailing list just to get some wider feedback on it. But that should mean that we can remove the hack that we have for Jenkins 2.204 plus where you may have to add a delay so that Jenkins doesn't fail to start up. This should remove basically the sleep and allow us to use a direct milestone. So that's all on that. The previous release of JCAST introduced the JCAST test harness which introduced a bit of fallout and updating it in the bomb as everyone using the bomb had to be updated because the previous test harness no longer existed and how the bomb works is it runs all the tests with all the compatible versions of plugins together and when you pull the new JCAST version the other plugins were trying to get the new JCAST version with the new test harness. Sorry not with the old test harness and that didn't work. So basically we had to go through every plugin and update them and release them. We've completed that side of it. Now there's just one plugin outstanding that has test failures due to the credentials plugin had to be I think yeah the SSH credentials plugin needed to be bumped as part of this and it's part of bumping that that caused a conflict in the CloudBees folder plugin. So we just have one outstanding request to merge and hopefully Francisco will be able to take care of this and then once that's released hopefully we can finally update it in the bomb version. It's been a two and a bit weak effort slowly poking away at plugins and nudging maintainers and getting them released but that's almost complete now. Snake YAML API plugin I haven't had a chance to look at. We're focusing on the bomber shoes. JCAST Dev Project we're still waiting for the blog post to be delivered. I think that's sitting with Oleg wants to take another look as far as I know and it needs the file to and it needs the blog post to be updated to the release date when it's released. So it needs a copy editor or coordination between Slater and a copy editor to do it. I've approved it three weeks ago so let me assign this to Oleg. Possibly it'd be good to have the new release out anyway. So there's a few failed releases because they're releasing from CI and the CI wasn't quite set up right but that should have been fixed now and Slater didn't have said that he'll get it released out today which would be good. Plug and compatibility highlights. I'm not aware of any. Just leave that empty. If there's anyone that anyone wants to highlight they can add them in later and I think we've been through all the hot topics. There's one new issue that's been getting a little bit of attention in regards to current Jenkins users with more information. I don't think it'll be too hard if anyone wants to contribute to it. Is there a good first issue? Yeah a good first issue. I think it should be straightforward. I've just been trying to guide. I don't think it would I could do it quite easily but I think someone else should be able to contribute it easily enough and there was also someone in Gita asking about being able to generate or set the API tokens through this. Not really that they need to set them through it. It's more that they want stable API tokens when they rebuild. So that's another potentially another issue to create and we've got the FOSDEM conference coming up this weekend if anyone is going to be there. Friday is a Thursday there is some training on Jenkins run by Cloudbees. I think it's 25 euros for this one on Jenkins pipeline and one on Jenkins X. Friday is Jenkins contributor day and then there'll be a Jenkins stand at the conference Saturday and Sunday and there's this TI CD dev room on Sunday run by Olivia the infrastructure project lead. So if anyone is going to be in Brussels it's a free conference. Feel free to come along. Anything from you John? Cool. I guess we'll end it there. I'll upload the I'll send the recording to Oleg to upload to the YouTube channel. Yeah, cool. Thanks.