 Welcome to another Jenkins evergreen open planning meeting. This I think should be fairly quick Let me get the Giriboard moved over to the right spot This I'm guessing Guessing you had a productive day with none of the Americans around yesterday You would hope so Yes, well, I'm still Starting I would say but yeah, I've been playing and I've been somehow Reading and playing with some wrappers around nodes git And in the end right now when I'm playing at we're playing with is mostly and using the row I mean not row but lower level API a child Not child process. I think it's called to basically call git like like it is there for instance. There is that node git very very Attractive or interesting API which seems to wrap in a high-level Git, you know git dot clone and so on but for some reason when I install it on my machine It doesn't work and I as I commented if you scroll down you see that basically everything Crashes and seems to just be separated on Windows, which is not really useful for our purpose So yeah, so Hopefully anyway our usage because I've also reread the spec back at some crazy guy wrote some some time ago Yeah, exactly so Yeah, hopefully anyway, we're not going to have to do some kind of you know Crazy rebays or or re re re or whatever subcommand so Hopefully and normally I expect that calling the subcommand is not going to be the most Complicated part of this is mostly as I have started to dig into the update process and so it's going to be Probably maybe I mean some updates on the 307 which is about the updates lifecycle Something are by by well definition So if people are joining or watching after that afterwards we are discussing the fact Okay, how we are going to handle the fact that if there's something wrong going on after an update then how do we go back? given we know that the file system is likely to have changed or and Jenkins doesn't support if you read the jf 302 basically going back so we use we want to use git to Have a way to go back. So yeah, and So yeah, I expect that the most complicated part is going to be able to call with the right thing at the right places and Change or other adjust the Update lifecycle as it's written right now. By the way, we have another issue about that, but it's unrelated I think we'll discuss that a bit afterwards Yeah, I was going to It's to step back from this task in particular One of the things that we were tackling last week were a lot of the early alpha feedback that we were getting I think we made some really good progress on that What we're sort of the two milestones that we should look at to To Move forward right now There's one which is a blog post on Jenkins IO, which I'd like to get out in the next week or two Talking about Jenkins evergreen start soliciting some feedback explain sort of where we are in the project that sort of thing and then the other Milestone that we have coming up is Jenkins or DevOps world Jenkins world which for my understanding Kuske is going to be referring to Jenkins evergreen in the keynote and Jenkins evergreen is also going to be featured in some marketing materials around DevOps world Jenkins world And so we can expect An influx of interest That week of September 16th to the 19th around DevOps world Jenkins world So this this task in particular That you started talking about this is a pretty integral part of The evergreen promise and the evergreen distribution So I'm glad that you had started on this patiss because I was gonna ask about this because this is one of those really important Important items I try to chose to select I mean to choose things at the right order I think you reordered again. The thing is recently. So that's why I chose that one. Yeah yeah, and I Last week I went ahead and I related all of the tasks that I know are blocking my comfort level for writing a Jenkins IO blog post Which some of the stuff I think the thesis already is already tackled And then Mandy we've got the the deletes on the back end Yeah, by the way, I guess the first about that we I saw on a pull request somewhere I Was going to talk about the very first one there Which I think I are again so this morning when I thought it would be now not present anymore since we are supposed to have a great The background but I I still have But my own Good instance that that's now broken for the same reason that originally so it seems to be during an upgrade So something is wrong here. I mean, yeah We need some tests or some more tests as I think Mandy was working on to understand what's going on because yeah This is problematic and this is going to be a not wow effect. If some people try it after After or during gen 12 Yeah, I've been working on updating the update versions test To see if I can reproduce this I haven't been able to yet I'm not sure if it's that we need multiple updates in there or what we're missing seems like or something like this And I I've not been able to understand every Really how it's it's been going on. I mean I've positioned something and then I reverted I think that the worked around Thing on the essential dotiamo so that you know I would force Docker Commons to 1.9 everywhere and when I reverted that then my instance got broken again when I thought It was something fixed Somewhere if you look at the at the chat, you will see that there is a commit from Tyler like two weeks ago or something That I thought would be fixing exactly that and I thought okay That's that's the reason the back end is actually crashing my instance And so there's two ways either it's the bug is he present for or another form of that bug or the The back end deployment failed and we don't see it but only Tyler or Olivier can check that part. I guess The back end deployment. I'll take a look at There's another issue that you and I had discussed briefly the teeth. I think yesterday about the The containers not being built properly in trusted CI So I think we have a backlog of undeployed back end changes that need to go live anyways Exactly. I by the way, I guess you received too many emails to to understand or I'll let that but yes I filed an infra issue this morning about that to five days old Build forever green on the entrusted CI issue Did you assign it to me? Yeah, I think so but I can double check. I'm pretty sure I did So my The the way that I'm expecting to be operating personally this week is basically Smashing bugs and deploying code. There's no There's no new feature that I'm going to prioritize for myself The only potential candidate after some of these bugs are fix Would be returning to a couple of these tasks down here below some of these other bugs that I have What I also am missing And I think Mandy it sounds like this is this is behind some other bugs on your plate I don't have Much idea of how we move forward with updating the support distribution For the clients and all the configuration. I'm wondering if you had given that more thought towards the end of the week last week I Mean I have some ideas on it. They're not fully flushed out yet, but I completely switch focus over to this other stuff That came up Okay. Yeah, that seems reasonable to me. I think the the Evergreen client and configuration update we should look at as not required maybe for a Jenkins IO blog post but definitely required for Jenkins world Which is a matter of like five days of difference Maxim and that's those are those are long five days Yeah, right. Okay. My bad plenty of time Besides aren't you flying from from France to San Francisco for DevOps road Jenkins road? There's like a whole pen ride that you can Yeah, I need to see because I have a some now issues with my Battery, so I need to see with my manager if I could approve some external Charger or something or hopefully because it's not the case all the time the plane would have a plug But you know, sometimes those plugs that don't accept more than some some amount of of watts Which last time it was you switch off each time I would plug it in so And I know that James And James actually has the pretty same the pretty same laptop as I am I have and Had a look at some different charger that would have a lower Lower watt per hour or so on that would probably be accepted by planes and so on so anyway I'm digressing I Given given how much Jenkins ever dream downloads when it starts. I'm not sure how how effective you'll be from the sky Yeah, or I mean, I've had as you know, I've had it that that Esquid cash sometimes ago But if it's to write or to test things in the real world and so on From the actual back end. Yeah, I'm stuck So the other thing that I wanted to highlight as a What I think we should really Drive to get before DevOps world Jenkins world is the cloud formation launch stack button Even if that's not on Jenkins IO having that in our README. I think would be Pretty good, but that's something I don't know if one of these tickets batiste captures that I'm guessing not No, that's not a case. I was thinking about that some like two days ago or something But yes for now I would hope and I'm yeah I'm very optimistic, but even implementing the chip 302 for the kids were would be already great So I'm well I too often commit to things that I cannot finish in time I would say or it can happen so Depends which answer you want to hear The optimistic one or the well realistic one Yes, I mean I have no idea to be honest, and I need to I think I I tweeted about that or but never heard anything about that But yeah, if someone who watches this which maybe is unlikely And knows how to do that when we will come some help I'll I'll ask a colleague of mine The office here in Santa Rosa if he's done that before he's pretty AWS savvy Yeah So I think what I'm going to do after this meeting is I'll create a ticket for my Jenkins world preparedness for evergreen and yes links some of these tickets that I think are required so we have a pretty good set of Tasks that we should focus on Mandy with the um with the work that you were doing the Really to me the two big things are the support distribution and then the back-end deletes And it sounds like but he's needs the back-end deletes first if I'm not mistaken Okay, I'll prioritize that Um, but just you had made a comment somewhere and I can't remember where at this point that you think that the Back-end deletes part is going to be required for that. I think simply I think it's in that The ticket we're talking about the back-end should delete. I think it's it's in comments on in that ticket. I think But I think I saw I saw two instances of Yeah, you know, there's two actually here So I'm not sure which one okay the one is for client and one is for sending from the server the different things Yes Yeah, yeah, exactly. Okay Because you need if there's something new that created the issue then we need to when we're wearing back To that that that thing has to be removed or we're stuck right I think um The way that I mean Mandy this order actually looks Reasonable to me And The things are in progress should be put back in open or something I guess the documentation is not the most urgent thing or and ready don't come includes. What was that? Yeah, I'll let Mandy organize that And is that thing in review really in review, I don't think Requests got closed. Okay By the way, the thick you're out of the box thing is in review and I think did I did I merge it? Oh, maybe I didn't I think I merged myself. I think I merged myself like yesterday and There's I think I commented saying okay I would still welcome welcome some review some highs on this because well That's not a great thing to merge things without anyone looking at it But it was pretty small so and I don't anticipate any, you know critical thing It was not like like a thousand lines exchanges change. I think it's Yeah, that's one. Yeah I'll take a look at it after the meeting. Yeah, that's great. I'm glad you were able to tackle that That was also one of those important ones So just thinking of the calendar here, we've got two weeks basically if I'm not mistaken Between now and DevOps world Jenkins world, so Yeah, this will definitely be a little bit of a sprint wanted Agile there the bad the ugly Well, are there any things that are blocking y'all or things that I can help move out of the way I Guess you we already discussed that if you can tackle the back-end issue and make sure the thing That is deployed. I mean it's not really blocking me because you know It's not something that it's more something that is you know running in my mind that I know that my instance my public instance Got you know broken many many times and I thought we deployed something that should fix it So I'm still concerned about it So if you can just assess if it if it was indeed deployed the right version And so there's actually something that you need to be filed or considered I mean the thing that is the version blah blah blah did that that issue I thought we would close at already fixed and so if the back-end is already deployed I'm wrong and if the back-end is as already known been deployed at the right way and The fix you did some weeks ago are actually was never deployed to production Then maybe we could just you know after the fact close this one. That's what I mean Yeah, all um I've got some some updates that make this page a lot more useful to That need to be deployed I'll make that the first thing today is getting getting the back-end properly deployed Yeah, by the way, I I remember I find something and I actually was duplicate But basically yeah and embedding somewhere in that page of the version that is deployed But I don't I don't see how hard it's going to be for you So the small matter of programming with that to the top Okay, Mandy. Is there anything that I can do for you? Would unblock Um, I mean I guess like getting that update would help me know because right now with the testing I'm not seeing the same version problems that we're running into with the production deploy And being able to pull that off my list and focus on the delete stuff would help Okay Yeah, sounds like I've got a pretty straightforward path that I need to travel today Um What I think I'll be I'll be looking at Outside of the context of this is I'll be trying to see what sort of Meetings and other things that I can cancel And that I can delete for the three of us Since we are sort of coming down to the wire with with devouts world Jenkins world I understanding Go on. I mean I was going to say for the demo effect of the needs worry some people are trying it The second one on your list. I don't know if it's intended that it's the second one right now. He's really No, that's that's supposed to be in the way. Yeah, I hit that a few times too. It's really annoying Yeah, and for the first time it surprised me because It's on my blog basically so it was really lucky to my blog and I was like Anyway, okay, great, so let's tackle those things. Oh And I'm assuming you all saw the The awesome image that Cassania created Yeah, that's why I provisioned many times a public instance I was not, you know, not satisfied enough to have seen that on me a few seconds. So And by the way, you know, I realized that issue about the redirection But when I was about to tweet some quick video about that provisioning and the nice thing and you know the And I I just was blocked to publish that tweet because it would look, you know They were awkward to have the end idea and something like there's any more I'm realizing that all of this code is sort of in a Weird spot like weird and that I don't anticipate it because I was expecting Why is that voting I was expecting this to have been merged I'm gonna I'm gonna fix this up and get this ready to merge today because there's some code Some changes in the tree that I think you're gonna cause conflicts if we let this stay work in progress for too long Cassania did a really great job Looking the morning while you're trying to you know concentrate or focus you Focus focus You're getting All right Are there any any other things we need to discuss or can we call it a day and get back to work? No, that's okay Nothing else for me. All right sounds good. Thanks. I'll see y'all on get it then All right