 Hello everyone. This is a GSOC Jenkins Docker base quick start weekly meeting We're almost done with GSOC project. It's almost the end of it. And today we have BeaViento, Jean-Marc, Ashutosh, of course and myself So the last two weeks have been pretty calm, I would say But nonetheless the project is progressing We had a few work items that have been done last week and the week before and before going to the Current pull requests and the work items that we should focus on this week I'd like to talk about which we discussed about the presentation That should happen end of August or beginning of September. Maybe Jean-Marc knows better than I do and About a possible extension of the date If ever we would need a few weeks more to finish the project So I'd like to hear you about that. First of all, the presentation Jean-Marc, would you have any dates to communicate? They're Sorry for the noise in the background Come here Dates we initially plan to do the presentation the 21st but The consensus was that we'll do it one week before Which is if my memory is good The 14th so on Thursday 14th If this matters so one week before Okay, I can check exactly the date But I need to juggle here No, that's okay. So it's just before the middle of September Yeah So we still have 14th Okay, 14th 14th for the presentation It's only Ashutosh and us clapping hands or it's something we have to do together Is that question for me or oh, yes, sorry Jean-Marc Because you happen to be an admin also, that's why I'm asking So what do you mean with clapping hands? Just us as mentors being part of the audience and cheering When Ashutosh does the presentation or do we have to do the presentation together the four of us? I prefer Ashutosh does it he did a good job last time Yes, indeed. It's the mentee that will present If necessary if he wishes he can call in the mentor Just be So keep in mind that it will be 15 minutes per presentation So questions with questions. Yes So 10-minute presentation solid if you run into troubles you can grab a couple of minutes But no one will be allowed over 15 minutes, of course Got it Fine Any question about that Ashutosh No, no questions Okay now for the possible extension we got a message on Gitter earlier today by Chris turn asking should we Extend the deadline for this project or are you good with the existing deadline to which I answer I Will ask other people from the project, but I think we're good. We've done what we've done We're happy with what we have and That would be fine But I want to get your feedback Jean-Marie Keshutosh and Viviente. Who's first? You're the first You started yeah here Yeah, so first thing it's a general question to the whole group. It was asked by Chris and I asked him to steer These opportunities because there's some administrative Magic that needs to be done From what I've seen especially if we if the PRs for integrating the work from Ashutosh Into Jenkins IO are created and that we started a discussion there I Don't see a need for extending now The the other part of that question or that answer is now if Ashutosh is going to disappear Somewhere between the moon and Mars and and we we don't see him anymore It would really be a pity to leave the work as it is unfinished, so but here This work I see Ashutosh smiling, but I think he got the message but We can arrange the the finishing of it At a different pace more respect respectful of Ashutosh College time and and so on but it would be a waste To have something half baked and that we need to throw away because nobody's is following it anymore Got got a message so to summarize because I gave too many words There I think it's a very good decision to stop the G-soc type of Interaction, but I would love to have a G-soc like or open source like collaboration continuing on on this project that that would be really a Great thing, so this is my point of view Bruno back. Yeah, thanks a lot John Mark I'm on the same line in fact and I didn't know if we should add as a Final target, you know integrating to jenkin.io. So I asked the question to Damian on the portal this morning And he told me we don't have the bandwidth to integrate the image creation and so on into Jenkins infra for the next two weeks and I can't promise that we will have the bandwidth at the beginning of September so I'm okay with adding as a final target integration into the jenkin.io official documentation, but we won't be able to integrate the whole docker thing into the Jenkins Organization, that's a pity, but that's what it is there. We have a small amount of time And so it wouldn't make sense to extend for me in order to get some more time for the Jenkins Infra team to integrate. I should just work. So no need to extend from my point of view either And also, yes, I would love to continue work on this project with all of you And maybe do something around Aktoberfest We'll see what you can do later on Berbjanto, what's your feedback by that? Yeah, we can hear you Okay, yeah, I think it's okay We don't need to extend because I think most of our work already did it Got it Thank you. I'm reading because because of the noise here. I had a hard time to understand. Yeah Yeah, okay. Oh Yes, I was saying we're mostly happy with what we have now. It's not finished, polished, but it's kind of working and yes, the cherry on the cake would be to have our documentation Integrated into Jenkins.io and that will be it. Unfortunately, no Technical items would be integrated into the Jenkins organization yet because of time constraints. Cool Anything else you would like to say Ashutosh or maybe into our remark before we go to the pull request and work items Yeah, so You mentioned it won't be available like I don't know what what exactly is the problem like will the bandwidth Will be expanded expanded later or something? We can hope so Bruno explain what you meant with yeah, it's it's not the bandwidth of the network if the bandwidth of the team it was a metaphor an image because We have a huge work item in Jenkins. Yeah regarding to network bandwidth funny you know, yeah and people from The infra team are working on reducing the consumption of the bandwidths that we have thanks to J For for example, and that takes a lot of time we also have another work item regarding the latest LTS and Then they have been some bugs lately with the image a Docker image creation and Also, we have to migrate some of the work into arm 64 for Money because of the money it costs less to use arm 64 for example so lots of things that are really Pre-eritory and we can't use that time to integrate your work into the Jenkins in Organization so that the team that does not have enough time in the coming weeks to integrate your work So not really related to network bandwidth. Sorry for that Just a hint for a shoot us There this will be something interesting for you to observe and eventually participate in Infra team is looking for contribution more on the infrastructure part So you could Eventually with their their help Contribute help because you know what you have built and Learn how they work and in in that manner Increase your knowledge In more infrastructure part, which I know is one of your your interest and they're looking for help and they can give you also a tickets or things to solve where You can definitely help the Jenkins community So That's a good idea Yeah, just remember. Just remember. Sorry to cut There's a huge pile of work Prior to work that's that's I will even say life-threatening for the Jenkins project They they absolutely need to to do for in Bruno just mentioned it Jay frog is giving us Important infrastructure to for the continuous integration of Jenkins But we're consuming by the popularity of the product. We're consuming a huge huge network bandwidth And we absolutely need and we've been requested by them. You need to decrease that because this is Rocket high and and we cannot support that anymore. So actions are taken Taken there a good way to enter that and then I conclude on that and Bruno can guide you With that too is they have a regular meetings of the infrastructure work and so that would be a good thing to start attending To do to those meetings. So you hear and so you know what's going on Is something for after bullsummer code back to you Bruno? Thank you, Jean-Marc, and yes, that was a very good idea now that you know darker and Jenkins There are lots of things you could do to help Jenkins and the infra team for example this morning I made a PR for the darker SSH agent that you're using for our GSOC project Because I saw that we needed to upgrade to bookworm, you know gets rid of bullsize and go to bookworm It was just a few lines of code and it already got integrated Merge and released today and frankly you can do that You could do that if you ever feel like you like that, you know, it's pretty rewarding Just to enter a few lines of code and bam your name is part of a Jenkins agents release So yes, maybe after GSOC But the same is also valid for Bevianto. Sorry to cut. Yeah. Yeah. He's also invited in where he is more skills In that domain, so have a look Yes, please do so and if you ever feel intimidated or something please reach out to me I could help be some kind of proxy to introduce you to those repos for example Thanks a lot for this inside your mark. That was a great idea. Anything else I should touch before we go to the work items and PRs Yeah Yeah, I was thinking the same that we won't need extinction if I was thinking if not the Infra team we can at least Get all the PRs to the Jenkins.io for all the tutorials By the end of the project Cool, thank you Perfect and another thing I forgot to forgot like in the last meeting When you said to attend the Docs office hours, but this week's Docs office hours was not supposed to kill life. Oh, yeah Yeah, so I wasn't able to ask Mark about if it will be there. I I tried to attend the EU timing but Mark was not attending that one either He was in yes, I think he was on holiday or something In this Google calendar said that he was attending DevOps days or something. Oh Okay, so maybe this week we'll see yes Thanks a lot Anything else? No, nothing else Cool, let's go to let's go to pull request now. So I've seen I Wrote three, but I think I saw five plug-in update PRs last week So this warms beautifully Congrats on this work. I'm super happy to see that kind of PRs boom boom boom, you know, just review looks Okay approved merge and we're ready to go Then we have variable for doc a hub repository so It was because you were you still using your own repo and maybe one day we will be part of Jenkins repo So never know so in you introduced Just a change of a variable If I'm not mistaken so that yeah Whenever ooh, let's bet that bigger whenever we'll migrate to somewhere else We will be able to use a different Docker hub username fine Then this one is adding an updating a read me What was that about? What to date the title for this one? Okay This one is for separately building the If someone is not trusting the images he can he or she can build the images so oh Yes, I remember now yes Yes, because You know, it's a chicken and egg problem like John Mark always says Because if we make it to the Jenkins IO official documentation we will have to reference your repo or your Docker images and Not that many people know you yet So they can feel some kind of insecurity using your images and that's why we are proposing to rebuild Locally the images just in case people would be afraid to use yours Then you fix something that was Bummer we couldn't use the automatic opening of the browser when using git pod and You change just a little thing that made a huge difference you went from open browser to open preview And this has worked in then for me at least each and every time because it was kind of randomly Working and now it's working each and every time which is fine and then You clear this one the removing reverse proxy warning, but only for git pod I think I remember there's some kind of IQ or JQ in order to change the jcask value when using git pod, am I right? Yes, I added it to the git pod.yms file Like yes, and then with YQ Okay, fine And it has proved to work because locally I have Warning when I'm not using the right URL and in git, but I don't have the warning anymore. So that's cool And Now let's go to the open PRs There's only one if I'm not mistaken. So let's get rid of the S. It's the end-to-end Multi-branch. So this one was the last tutorial we had spotted It used to be with a docker-in-docker and it was pretty obscure and Complicated and you change it. Oh, you change quite a lot of files in order to get this tutorial to work and You don't have to use docker-in-docker anymore I think you told us last week that you started with the same agent as the node Tutorial and that this does work for you. I've reviewed that and it also worked For me, but you asked us for a review So would you have anything to share with us? Would you like to share your screen and tell us more about this PR? Yeah, so for this PR, it's a Extinction of the node tutorial kind of so it uses the same it works on the same agent, but We need to add the blue ocean plugin for this So we need to use different controller and all the other tutorials. We are using the same controller But for this one will use the same agent, but different controllers. So I Have to edit the Docker-compose file itself because in the tutorial we were using the same controller and it was kind of dependent on the controller because That's yeah, so I Have created the updated the docker-compose file for Different controller, but it was giving it giving some errors to me because I am not sure why it was giving but the it was giving errors while updating the plugins not updating the plugins while creating the images the Importing the plug-in dot txt file. It was giving some errors during that time I think because the plugins are not updated in that file Right now, but I'm not sure yet Mm-hmm. Okay, so we should review it, but it's not ready to merge Yes Okay, and another thing for this. I'll have to edit all the GitHub actions too for this to integrate this into them, too. Yes. Yes, that's I've updated I Have only one GitHub action is left that is the testing of the main one the which tested all the containers So I'll have to upgrade that one Yeah, that's tough one But that will work. Okay. I'm sure Okay. Thank you So we still have 10 items to this day I guess you haven't been able to progress because it's none of your fault about Dependable is not configured yet Dependable, but I don't understand why it's not working. I looked into it There are not many tutorials on the YouTube and other places either, but I Checked I checked everything. I think but it's still not working Be avianto, I think I remember I read this week a comment of yours saying that it was not working on your fork either Yeah Sorry, sorry, it's working or not working not working. Oh, okay Mm-hmm, and you don't have any more error message or whatever that could help us knowing why Okay So why does it work on mine? I Don't get it Jean-Marc, have you tried? Dependable on your fork or not? No Okay, honestly, I've I had no consumed my other course No problem about that. It was just in case because I don't know I'm the one who started Dependable on my fork and then made a push request to Pro request to the main repo So I don't know if I did something that blocks other force or even the upstream to work with Dependable Maybe it's my fault and I don't know what I did Maybe not I enable Dependable on another repository And now did I check if it worked or not? I have several repos which on fork and That work with Dependable But and I also have some other repos which are forks of official Jenkins on which Dependable works But I'm not the one who started Dependable on those forks, you know They were already part of the main repo when I cloned them So, I don't know Okay, I Would try this week to find something Bruno, I will have to drop in about two minutes Go Jean-Marc, you're free to go. Thanks for coming. Thank you. Yeah, okay. Yeah, sorry. Okay, and don't get lost between the moon and Mars, right? Yes, yes, I Want to merge my quote to the Jenkins Yeah, okay Thank you later then. Bye. Bye you buddy. Thank you Then the next one was the end to end multi-brand pipeline project creation we already talked about this one. It's a work in progress The next one is use github tools to configure jk I don't think this one is mandatory, but that would be a nice things to have if it's still Didn't you solve that already? Yeah, I don't remember this one Yeah, the thing is we wanted to retrieve The exposed URL things to GH port, but I think we don't need that anymore in fact Because it's already done maybe not with GH port, but I think in jk ask you already changed the Jenkins URL in some way yet. It's already available This one is old one. Yeah, that's right. Yeah, yeah close issue Done Right, that's cool. I don't think I can try that but that's okay Now then Use depend about if ever if wants to work and update CLI to keep the samples up to date. So for depend about you Just say which kind of ecosystem you're using for example, we are using Docker ecosystem because we have Docker files So just say we are using the Docker ecosystem here are the links to our Docker files and it will do its best to Update the versions you're using in the variables Docker files. So this one should work Whenever depend about It's okay with working on your repo Maybe that would be just a little work to do. I don't know if you've done that Because you added some Docker files Lately for the multi-bronze pipeline for example, and I'm not sure it's part yet of the update CLI Depend of a configuration. I think it's not part of that But as it doesn't work yet well You get the idea then I was thinking of update CLI because dependable is somehow Limited update CLI is also limited on some other parts But the combination of the two makes for a very robust update system So if you find the time to experiment with update CLI Please do so. So we have a working sample With continuous update and as dependable doesn't work that well Well, maybe we should Switch to update CLI. I think we'll have another LTS tomorrow for example Jenkins LTS and It would be nice if we could have a bit CLI to update our various Docker images Of the controls thanks to them, you know having the latest Jenkins LTS version for example and It's the same for the Debian version. We are based on And so on and so on and so on there are lots of things to update if you really want to and we could even Go up to the samples, you know, you have several samples for Maven node and so on Various repos you could put update CLI or depend about in these repos also So they also get updated So we don't have to let people experiment with some things which are outdated or vulnerable for example Okay Then we have build and push the Docker image even only if the Docker files have changed I'm almost sure you've already implemented this one, right? Yeah, I think I saw your GitHub action only fired if the Docker file change. So Let's close this one. Oh, that will be a light week and let until you experiment with a video which could take the whole week Close issue That's cool and then open the first PR on Jenkins.io. So I don't know how this one will look like because The format you're using for the documentation which lies within our repo Isn't quite the same as the official documentation of Jenkins so I guess you would have to fork and clone the Jenkins.io repo and then make the Modification directly in another branch and propose them to Jenkins.io not using directly The documentation you wrote, you know, I don't want just to copy your file into the Jenkins.io repo But just make the modification until it looks almost the same than the first Existing documentation on Jenkins.io, but with the latest information you entered into your repo. Okay Yeah I have used the Jenkins.io documentation while writing the blog Yeah, of course. You already know that And you already know how to Build the Jenkins.io website on your local machine also Yes, you're not using Windows, of course So that does work on your machine on Windows. It's a mess even with WSL2 Anyhow The last one is optional. It's a proposal set of other examples to implement We've done, you've done most of the tutorials we were thinking of so Maven, Python node and multi-branch And maybe there would be some other ones to implement. The goal there is not to Solve them, you know to make them but just to create some work items some Issues into the repo so that anybody later on could try to tackle this. Okay But this one is not mandatory just if you have time to and of course you should think of the final Presentation the demo So you should you could take some time Because we still have more than two weeks But yes, you should definitely start to think about that You did a great job for the mid-term presentation And I'm sure if you invest time enough into the next one. It will be great also and of course don't hesitate to share or to do Rehearsal with audience, be it friends, family, mentors, whatever if you feel like it, okay Great Whoa, time is running Anything else you'd like to share Ashutosh? Cool Okay So if you don't have anything to add, let's call it done and See you next week on the same meeting and before that, of course, we have the Gitter element Matrix you name it if you want to discuss emails and That's all the video should be available for everyone 24 to 48 hours from now And if we don't get in touch by next week, have a nice week. Bye. Bye Thank you Welcome