 Okay, hello everyone. No one except me joined the office hours today, so for now I'm only talking to myself, but there is a small amount of very important announcements, so I've decided to share the short video with you anyway. Can you share the screen? And I really hope you can see my Chrome browser now. So the most important announcement is that we have removed plugin management management from Jenkins configuration as code plugin, which means you can't use a root element called plugins to configure your proxy or update site and install plugins anymore. The reason for that is that it never worked well, and we experienced some very serious issues with infinite restart loops that Jenkins ended up in after some of the plugins were updated. So yeah, I think the recommended version of installing plugins for those of you who are using Docker is to rely on plugins installed as a script. And I know it requires you to restart Jenkins, which is not always required if you, for example, want to install a new plugin, but that's the best we can we can provide right now without breaking your Jenkins. So you can't use Jenkins configuration as code plugin to install plugins anymore, but proxy and update site configuration are still available. They were just moved since, as I mentioned, the plugin root element is gone. So to configure proxy, and this is available under a demo folder, you can see that the proxy attribute was moved under Jenkins root element. And then the configuration is the way it was. And then to configure update center sites, you also put it under Jenkins root element using update center keyword. Unfortunately, for now, this is not a part of the demo folder. What I'm showing you here is just the YAML used for our tests. But obviously, it should become a part of demo folder. So it will be moved. I'm sorry, not moved, but the configuration YAML will be available somewhere under demo folder, not only in tests. And another relatively big change that is not there yet, but is coming thanks to Joseph is adding release drafter. There's a pull request that is still open. But it's basically ready to be merged, except there is one thing that Joseph is not entirely happy with, if I understand it correctly. So what it is, instead of maybe let's go back to the history for a second. We were using plugins Viki page to handle a change lock, and it was not always updated together with the plugin new version of the plugin released. And then we've decided to move the change lock to the GitHub repository. And for now, we are using markdown file to provide a change lock. And this change lock is being updated automatically, which means every time after we release a new version, we have to go in and just write the change lock. And it can be automated. And Joseph found a nice way. So he wants to use release drafter. And it will just take the PRs that became a part of given release. And that's how it would look. I was actually worrying that it will mess up the old releases. And the way it looked now, I'm quite happy with it. Joseph introduced a couple of categories. And I really like the way it's being displayed. We just have to make sure that the messages we're putting in our pull requests make sense. So I think we're going to go for it. I mentioned Joseph had a question. And there was a comment, yeah, because together with this release drafter, in this pull request, we have, if I understand it correctly, a couple of different issue templates depending on the type of the issue that is created. It's a bug or feature request or plugin compatibility. And Joseph has asked about suggestion regarding the shape of the feature request plugin. And I promised to have a look at it. I didn't have time for that yet. I'm going to keep this PR unmerged for a day or two. So if anyone is interested in sharing any opinions, just jump in and comment. But very soon it will be merged. I really like the way it looks. And yeah, there's a couple of other PR pull requests that I actually wanted to have a conversation about. So I'm not going to comment much on those. But I think it's worth pointing out that we have a PR in which we were planning to target Jenkins 2.164.1. Since it's pretty stable. So that may happen soon. There's a lot of changes. And yeah, I don't want to merge it without having a conversation about it first. But yeah, there are some other things. But it would be nice to have someone to discuss. So I'm not going to cover those now. That's it. That's all I had to say. I'm going to stop sharing my screen. And I can see no one else joined. So I will just stop broadcasting. Well, thank you for listening. Bye.