 Hello everybody, so we are having the weekly open planning meeting for Jenkins Essentials. So today we are not a lot of people, there is Oleg, Mendy should join soon and so there's me. Oleg is kindly setting up the meeting even if he had a lot of important things to do so we are going to try to make it short. So on my side, I have just finished and filed a PR to provide a cloud-friendly installation for Jenkins Essentials for AWS, the PR, I thought I had linked it so yeah, it's here. And I also did a video, oh the link is bad, linking to OPR is not very useful. So I did a video explaining everything, it's a 10 minute video demonstration basically. And so this is going to allow people to using cloud formation, create from the ground up an instance running in the cloud, in the AWS cloud. So I think I already explained a bit last time but basically it's going to be using both EC2 cloud plug-in but also preconfigured instance so that it will be using the artifact manager F3 plug-in which basically is going to let you store things in the cloud in F3 instead of sending binaries back to the master file system as was usually done and most often usually done on Jenkins masters. And along the way I had to file and fix and discover a lot of issues mainly on Configuration Ascodes project, it was interesting to set that up and so I filed a few PRs in there and that's mostly it and I'm going to be switching to some internal task for my company and then get back to this a bit later this week hopefully and that's for me. So I guess if there's nobody else for now I guess we can just wrap it up. So I'm going to summarize what's going on for Mendy. So Mendy is mainly right now working on prototyping the sentry using error logging for sending things to sentry basically offering access to developers to pipeline developers for instance to error logging and she's going to be also tackling SUNISH very important JIRA which will allow to actually wrap up and I'm going to give the mic to Mendy to summarize those and yes that's it for me at least. Mendy are you here? Yes I'm here. Okay you want to summarize what you're on and what you're going to do? So I have been working on the prototype force and the error logs over to sentry. I've been playing around with a couple different options and working on adding some tests for that and I'm almost ready for that one to be ready for review and then I am currently researching adding the flavor in we are evaluating how to get that saved into the database but that hopefully won't take too much longer that's pretty much me. Thank you so yeah that one is going very very cool because this is going to really be a critical part to actually make essentials work because for now we're forcing Docker cloud flavor which doesn't make sense and I actually installed everything for AWS even in the basic foundational plugins so that I could wrap up the AWS flavor for so far now this is a really a critical one that is going to be yeah awesome so thank you Mendy thank you everybody I think we are good Oleg you want to say anything before we go? Yeah actually I had one question so we have Jeff 309 I've taken the link to the chat it's about bill of materials originally it was proposed by Carlos and we were discussing the usage of this Jeff essential survival so I wanted to ask you whether they use it now or if not do you plan to use it? Yes so it's actually used so not everything is wrapped up but per se for instance if I show you the code base on the service side it's there's that file here that is the BOM and right now there's some code that actually resolves that BOM kind of you know like in Maven world computing an effective resulting BOM which is not really a BOM in that case so ingest.json is the computed file from the essentials BOM so yes we are using that so possibly because this is Tyler who worked Tyler who worked on that part so I'm not absolutely sure he made you know double check if everything in the script in the JEP is being respected in the implementation but basically yes we we are using a BOM. Okay cool yeah so the story behind my question is that I plan to spend some time in order to retell this Jeff either over the fence or the first depending on the usages because so far I was aware that we use it only in customer work packages you use it in essentials now yeah we likely need to reconcile the exact format because I think they are slightly disconnected I'm not sure it would be working you know from one to another to the other and so on but yes basically it should be very much the same so that's why I was talking about what Mendy's work will allow me to remove that part is forcing you know EC2 and artifact manager S3 on every single instances even if on Docker flavor for instance which doesn't make sense you know in the long term but yes that's it. Okay so yeah I have a bunch of comments regarding this Jeff on my own but yeah I will probably provide some updates at the next meeting so maybe decide how we proceed then. So let's I think we are done so thank you Mendy thank you Oleg and see you next week. Bye bye. Thanks again.