 Here we are. So hello everybody. This is Google Summer of Code office hour for today, August 10th. Welcome everybody. Thank you for joining. And so we have today we have Jakruti and we have Harsh as contributors and we have Chris and Alyssa on deck too for this meeting. Thank you everybody. So Adrian is just joining Ashutosh. Well, okay. I just said the people that were available and here they come, they're joining. Hello Adrian, hello Ashutosh. Just checking sound with Ashutosh, do you hear me? Why are there still no mute or struggling with these cables over the place? We'll check afterwards. So let's do a short roundup with where the project is standing. A double check I want to make. I know it's August here in Europe. Many people are taking holidays. Just want to be sure that holidays are correctly covered for everybody that nobody's alone sitting in the cold. This basically what I want to discuss or share with you. I have no other news or information for you. I will leave time at the end if you have a topic you would like to raise. So short roundup as usual. What happened last week? What is planned for the coming weeks? Maybe just highlight if you feel comfortable if people in your project team are unavailable. And just tell me what's going on. Now first one in a row on the top right on my screen is Jakruti. So Jakruti, tell us. Hello everyone. I just want to say that coming two weeks will be really crucial for me. Because it is not just because I have to complete a book because Adrian has made it clear that he doesn't actually want me to succeed in a number of contributions and number of projects I have completed. But he wants me to be more efficient and autonomous of how I go about things, how I understand things on my own, which are research work items. So I am from now on going to focus on that mostly. And also about my updates, I won't say that, okay, this program is finished or this is pending, but I have to do this. I would actually tell you what I am learning and what mistakes I did and when I'm stuck. So speaking of that, the bug fixes that I'm working on. There were a few things that like, there were a few parameters I could work without, which I had used. So that was what Adrian pointed in the review. So I fixed that one. In the next probe, it was again implementing an abstract class, which was a little different than what I had implemented. So I kind of messed that up. Then I read about it, Adrian explained me. So now I have also completed that part. I have implemented it again and it is under again review. So I hope these things will put in around this week. For next week, I already have like, I have a list of things to like probes lined up to complete. So I will work on the next task. If these two get completed, if these two was that completed this week, that's all from my side. Okay, good. Thank you for the update, Jakruti. So quality instead of quantity, which is, which really makes sense because when you have quality, the quantity comes automatically. Don't hesitate to reinforce some, I won't say the word weaknesses, but in the Java and object-oriented sphere, I think some reading, it's difficult, I know, but I encourage you to read. The book I pointed out in Gitter is a book that helped me personally quite a lot. I would read that. Thank you. Yeah. Okay, worthwhile to put some work there. Great, Jakruti. I know you're putting a lot of effort in it. We're all behind you, all behind, believe that. Thank you. Thank you, Jakruti. If somebody wants to add something just for holidays, I think Adrian is going to leave for a couple of weeks. Everything is organized. Is that correct for you? Yeah, correct. Yeah, yeah. I'll be off starting this Friday, officially for my company this Friday afternoon, my time zone. However, this is completely, to me, that's open source and I'm lucky to have that and all during my workday, but it's also something that I watch outside of that. So I'll be monitoring, maybe not as closely as I'm now, but I'll be monitoring everything that Jakruti is asking any question, any comments on the side. And I know that another mentor, Antoine, is coming back next Wednesday on the 16th. And yeah, I think Keo would be back in two weeks. So yeah, there's plenty of, there's a lot of people that will be here for you, Jakruti, so no worries about that. We are not abandoning you. And we make sure that you'll get all the help that you need. Okay, great. Much appreciated, Adrian. You know what I'm going to tell you is be careful also for your health. Holidays are important. Have a nice cream on me. And we'll check that. But much appreciated that you're involved. I have plenty of drinks for you. Okay, good. Thank you for the updates. Next one in a row is harsh. Tell us what has been happening, what you plan to do in the holiday period. I think, well, Chris is watching you back at two and I don't know when he takes holidays. So I don't know. It's always there. Harsh, go ahead. I'll stop talking. Yeah, so we were in this week, mostly we were testing the milestone two and we found some bugs, like some really deep bugs of auto merging stuff. And we were fixing it like I messed it up because I did a mistake of type. Like I had to use capital B for Boolean and I used small b. And that's why this thing was not working. The way it should be and Mark tested it. So shout out for Mark. Like he tested it really, really well. And the testing is going on other than this, like because the milestone two is the core of the migration, once it gets merged, other full requests are almost very easy to get merged. Like they're not much of a problem. So like, yeah, it's going well. Once the tests are complete, I think we should be good to go. Like I have added the milestone four and milestone five also. So it's just merging that has to be done. So I'm hoping that this week, like our testing for the milestone two will be completed. And then in the next proceeding weeks, we will be able to merge all the full requests. It's still a lot of testing required. So what is the current testing goal and how much has been already tested? Actually, this this plugin, because we need to test it a lot because like I've almost divided a lot of things in it. And the problem is the, like I've created some 10 or 11 pointers for testing and we also need to test the permutations and combinations of those so that we know that things are working as we want it to be. And another thing is, if I make a slight change in the plugins code base, then we have to test everything all over again. Everything. Because of course, yeah, we are going to deploy it in production. And if someone finds out that there's something bloody wrong with it, then they won't listen, right? So yeah, a lot of testing has to be done here. And I know, I know the answer, but it's interesting to explain to everybody. Normally tests should be automated. Is there a reason why you're doing it by hand currently? Yeah, like one of the tests we were having for the plugin are very outdated. So we have to like improve them. I improved a lot of the tests, but I think 30 or 40 were left, like 30 or 40 unit tests were left. Other than that, I think 100 or something were already automated. But we are not really like focusing on that because automated tests only test the part of the unit, like the unit of the plugin. If they're not testing it completely and interactively, and the tests are integration tests and end-to-end tests that are there in the plugin, they're extremely outdated. Like they're thinking that I think they're based on GitLab 8. And to get it working, it's quite difficult. It was a stretch goal. I don't know if I'll be able to achieve it or not, but it was a stretch goal. So we are, like Mark suggested, that we do interactive testing much more. And in the case of proxy settings also, we cannot test it through unit tests, even when I tried using test containers and all. But I think it will be much more of an effort to actually set up automated integration tests for proxies and all. So we are doing all the tests manually. But you're just not lecturing, but here pointing out what it's the case, having automated tests would make the life easier, but it's a big investment. But let us not forget this part. It's like not doing the dishes and letting them in the sink. After a while, it goes over and you have nothing left to eat indecently. So automating tests should be something that keeps nagging you in your mind. It would be a very good addition if you continue contributing, especially as you have now to know. But I guess Chris is also going to do opportunities to work together. But the best tests are automated tests and that are maintained. Okay, very good. Chris, do you want to add something about our project? We may want to add some automated tasks later once we are sure what to ask for. Because right now there are a lot of things that we know we should test for, but they're not testing yet automatically. It made sense. And for me, I don't know with who I discussed that, but the tactical decision that was made made really sense. I just want, especially for the junior that I hear, so skipping tests is a recipe for disaster and the best tests are automated. So this is my, I know I shouldn't do that, but just wanted to point that out. Nothing is like for a test. We normally need to have two servers, so one for Jenkins and one for GitLab. Like if we do a local Atex, it's too slow. So you have to resort to it. It's part of the frustration actually, because we are using the GitLab image and I am using a MacBook and it's very slow. You'll have to wait for 30 minutes for the container to start and it usually gives me 500 and 502s. And it takes a lot of effort to get the tests working. And I think 30 or 40 of them are actually left and those tests that are left, some of the tests belong to milestone two. And I was not, I tried to work on that test that I gave, I think two to three days from a single test actually, because how hard it was, it was to test it because the GitLab for just forced a architecture on the GitLab plugin and now it is very difficult to test it. So yeah, that's one of the reasons like I slagged off the tests and tried to make the code in the production work first because if the code in the production does not work, what are the tests for? But if once the code in production works and we have, I think, one week or two weeks before the GSOC ends, then we can work extensively hard on the test part. Yeah. Okay, but what I like very much is that you know you have a very good understanding and a good teamwork. So there, I like that. The only major bug we have is for Auto Merge, which is the only issue, major issue. The only issue we have is with logging because for some reason we see some logs, but the action has been completed normally, but we get some errors for some reason. Okay, great. Let's move to Hashutosh somehow. He lands every time on the bottom of my list. I don't know how you managed to do that. So go ahead, Hashutosh. What is happening? Yes, so last I had a couple of tasks remaining for the previous week's milestone for which I have opened the PR. So they are working on my end. And other than that, I was working on integrating end-to-end multi-lunch pipeline project through the tutorials. For that is working on mine for which I will be creating a PR soon. So other than that, there are one other task which is mostly documentation. So that shouldn't take too long. And also I think just giving you a hint in case you're going to start now the discussion on how to integrate that now into the global Jenkins documentation ecosystem and what is required. It needs to be industrialized. Yes, I will be attending tomorrow's Docs Office hours Asia for that too. And other than that, I think there was one other task in the milestone of creating variable for using the repository for which we are using my repository right now. Yeah, a lot of people will like to use Jenkins. A lot of things have been set up to just work and are working with your account. And this is part of the industrialization that this is then moved over to the Jenkins ecosystem. Okay. Thank you very much. I think Bruno is on holiday until Wednesday of next week. Yes, but he's checking in. Okay. I don't feel like he's checking in regularly. Right. Okay. Very, very good. I'm still catching up with your project. So I have other things going on too. And but I see I'm not doing the mentoring that's required. I just see that everything's going okay and you're moving it. Great. Okay. So I see everything's going on, seen some messages on Gitter popping up from Vendit. But I think he's in between exams. So let's... I will have a meeting with Vendit tomorrow to discuss like what to do to fix the current and horror docs previous. Okay. So that is to be in a shape that's ready for presentation. Yeah. Good. And you have a discussion with Mark too, because one of the concerns was that it would be a waste that we have a half finished system. I want to have another meeting on Saturday as well to talk with Mark if in case he'll be there. Next week he will be away. Yeah. So anyway, but I see that all the projects have the hands on the steering wheel and know where to go and even if people are away, good. Okay. So I'm good. Good progress, hard work, sometimes bumps in the road. But let's keep trucking, as they say there. Is there somebody who wants to raise a topic, ask a question or has just a comment to do? Like I had a question. Go ahead. When is the end-term presentation? Because I can have my exams flashing. Okay. This is something I'm going to discuss with Alyssa because she's a grandmaster of Java online meetups and knows all the magic required to organize them. Currently it is planned mid-September, somewhere mid-September, which seeing your smile harsh is in the middle of your exams. Yeah. Right. Why do you guys always have exams? Why do teachers always have exams? Take an extra portion of economics and computer science. Okay. No problem. Here we'll come with a couple of dates and see and try to find a compromise. The end-term presentation is decoupled from the evaluation. So it is just wrapping up and finishing. Yeah, so the end-term evaluation is still September 5th, right? I don't have the... The evaluation is due, at least for the mentors, it's due end of August, but I believe that for the GSoc contributors it's due prior to that, at least a week prior. Anticipate probably the second week of this month. Go ahead. Have a look. I had a very tight schedule because I took some courses from my institute for other subjects also. So I have a lot of exams. So in the middle of September also I have exams and I am currently in my second year. So we have to do some summer projects also. So for the summer projects also, I think I'll be busy till September 5th and that thing also. That's why I'm a bit low in the project right now. I'll get in the pace after four to five days. I'll get into the pace till 15th of August. I think I was a bit busy. But yeah, I want you guys to find a place from September 5th to 15th, I guess, because I think 15th will be my exam. So 10th, yeah. Or after September 2. After the 10th, I have examinations. What they did was because of the added subjects, like it's not yet known when we'll choose exams, please. I'm just speculating because they told me it will be between this. Right. Here, Harsh, I'm going to contact you one-on-one by mail so that I'm sure because I have nothing to take notes here. Just to check for the dates and going around with the other mentors. And see what happened. Can you see what I said? Oh, there probably was a wasp. I heard somebody yelling. So, a wasp. Here, I'm going one-on-one and we need Alissa and myself. We need to make work on planning it. And we want everybody to feel comfortable because it will be a nice wrap-up of a long journey because we started that journey together several, several months ago. So remember the picture of the big mountain. It starts. I wanted to do it live because I'm just bored of recording stuff. And I don't want the interim presentation to be a recording. But I have a lot of exams for God's sake. I'm giving quizzes every four to five days. Okay. Good. We'll check that with Alissa. Are there other questions, comments? Yeah, I do have some comments because I got for the booting Jenkins.io project. We may need to extend it because we want more features to be completed. I'm not sure I understood that correctly. Can you rephrase that or say that again? Yeah, because for the booting, Jenkins.io project, more time. So the issue is the presentation for that project might need to be delayed. More time or so. Okay, then what is something for you and I that we dig into the GSOC rules and see how we can make that. So to have extra time. Yeah, but for the presentation, we may have to do it later. Yeah, Chris, you're making my life horrible because I understand your problem. Don't worry. Yeah, there's need more times. It's like I planned that ahead already. So it's expected because we did talk with Mark, we did talk with Wajif and Yiming and they all said it's okay. Yeah. And would doing the online presentation and September something acceptable? I think so. Yeah, it should be completed by the end of September. I think maybe just one month extension at most. I'm thinking or hoping. Yeah, okay. Harsh, will you be in the middle of exams or quizzes or so? Because you're scaring me with all your exam. Yeah, I think it's in the end of September. I should not have examination. I'll recheck, but I don't think so. I should be having an examination. Okay. Sounds sounds good. Ashutosh, how would it look for you on your side in September? Or doing the presentation? I don't have exams in September, so it will be fine for you. Yeah, okay. Nice. Jakruti, is it okay for you in September? In September it's fine. Okay, well, you don't have exams anymore, but who knows might have other obligations. I don't think on September, I will let you know. Okay, good. Perfect. Thank you. Okay, so this is workfully signed me. Yeah. And we'll work on that. Okay, thank you very much. We're not there yet, but the end or one end is approaching. And continue like that. So, well, no, it was not good to say that way because some projects need a little bit more time to complete. But anyway, you got the message. As somebody I know stays, go, go, go. Let's finish this. Bye-bye, everybody. Thank you for joining and thank you for all the good news. And for those that go on holiday, enjoy your holiday and try to hook up. Bye-bye, everybody. Bye. Bye. Have a great day, everyone. Thank you. Bye-bye.