 Yeah, I want to make a point about the use the try to to avoid the the security script line to in the Jenkins shadow library. And we have a really big shadow library, and we don't need to to approve any, any script or or use that line for anything we can, we will manage to do everything that we want without have to work around the script security with scripts with binaries with other things. So, I think that this is not required to to use the play, you can always find some way to do the same thing in in the best way that is keeping the security plugin in there. So, there are some plugins like my pipeline utility steps, like note API iterator. For me, for example, it was always a case when I needed to do custom schedule link. I was using note iterator API, which would allow me to query notes and schedule my pipeline. Subtasks for parallel pipelines using them. But you're still there are many cases when direct access to binary API would be beneficial. And for you, honest, what are the common use cases. But as long as he's doing it in a global shared library, I don't think you hit script security. If you're trying to use it in a in your own pipeline or a folder one you will but not in global. Yeah, it's exactly this way we are loading our library in the runtime. So, I think it has restrictions as the library, which is connected to a folder. There's too much code already to rewrite, rewrite, right. So that's why we keep using permissive script security plugins too hard for us to rewrite our old code in order to not to interfere with script security. Is there a reason you're not using a global one and just a folder one, you should just be, if you moved it to global, then I think it would just work. Yeah, but but we can't. We use a library step to load our library dynamically. We need this for versioning. In our case, a lot of the scripts are part of the parameters in the UI. We're using the active choices. Plugging that creates sort of interactive cascading parameters and also creates for us these HTML and JavaScript elements that were interested for more interaction and introducing graphics libraries, scientific libraries and imaging and so on. And yeah, all of those for us, we need to go and approve those scripts. For versioning, we use tasks in the repository, and we have a current task that is used in all the pipelines, and we have some regression or wherever we move that task that is the current to the previous one. And we fixed the issue in the time we released the library 10 times fact between five and 10 times a week. And we managed to have the the library in version it without any issues in the three years that we are using the library more or less. I should say that I don't think I have deactivated the security plugging or use the the other plug into the permissions, whatever it's called. Um, but we have tinker around with a woman's call a wasp renderer or something like that in the, in the startup of Jenkins, so that it will allow it's TML things like that to be rendered. Sorry, I don't know if I'll be using the right moment later for that one. So this one of the topics like you were saying about the stability. So I want to be the voice as well from some of the users that we have at the last thing, like some of them find really hard when you run so many things in parallel on a pipeline to the bag was going on. Right, so that's one of the issues we heard about quite often how to make this easier to the back from the console out and so on. Because sometimes he doesn't even reload correctly the logs in the UI. So that's probably one of the issues from from the point of view of the usability I would like to highlight. And also about the usability I think that's also a good point. The one regarding to make the life easier from the end user how to restart a particular stage when the bill with a particular pipeline fail, not working in all the cases and that's probably one of the key areas as well how we can make people working with the Jenkins pipelines easier that they don't really need to wait for us already here, like some bills take hours, so on, so how you can only run a particular stage of a pipeline easily without going through the entire pipeline as well. That's something that's what I haven't here. I haven't found an easy way to do that and that's why listen from our users quite often as well. There's probably a couple of points now way to point this in case we don't have time to work. The presentation of what we do and how we do things in elastic.