 Hello, everyone. This is the G-Surf Jenkins docker-based quick start weekly meeting Sorry for missing last week meeting. I think I clicked on the wrong link my bad anyhow Jean-Marc and Ashutosh were there in the meeting. He's got positive on YouTube if I'm not mistaken Jean-Marc will won't be able to join us today though. That's just the free of us last week I gave quite a lot of work to Ashutosh and There was one big part which was about Trying to get the first step for the CI test, you know We chose to start with GitHub actions and we see it was not as simple and easy as I had imagined anyhow We had a few action items still to do We had something to add about the Maven tutorial Because there was a part missing in the documentation explaining what is happening behind the scenes for the second persona We had envisioned but that's not urgent at all. So that is that has been moved to a distant milestone So we're always on week 29 so we'll try to focus on milestone week 29 this week and First thing I'd like to be solved is the reverse proxy issue Because it's not good looking you know when you are starting the tutorial you see there is a reverse proxy issue You're not really confident with the rest of the project I know the project works pretty well, but you know getting the reverse proxy issue is not cool to see We also have something to do about the Python example This week. I hope it's not too complicated and we have the big part about the GitHub actions and experiment now I Gave quite a lot of work. I already said that to Ashdosh last week and He was not able to Go to the end of the tasks and that's perfectly normal. I was maybe too Ambitious about that, you know, I thought it would be kind of easy, but it was not and What worked for me did not work for Ashdosh, you know, I provided an example PR Which kind of worked but I had a very simplified setup and not the four examples the four Quickstart examples, so I didn't think of that and of course it didn't work as expected But I should I will let us know more about that later on So I took all the milestone we had all the issues today and move them translated them to Next week my stone and you know each milestone in now another week I thought I can't remember when you're supposed to get done with G-Sock project. I think it's between the middle middle of August and the end of August Yeah, I don't Know, okay, that's okay. I should I'm the mentor. I'm supposed to know about that, but that's not a problem. We'll do what we can Until you're not available anymore and we'll see you later on what's left to do but Anyhow, we'll have some parts that do work even if we haven't solved all the issues or work items I was in vacation last week they time off So I was not able to work for this project or attend meetings Were you able to go to? Docs office hours previous week all the week before the previous week Yes, I did attend the Previous week before previous week this week it was not held because Mark was on holiday Yeah, okay, cool So I did attend it and we Okay, I don't We talked I don't remember exactly what I talked we talked about because it was two weeks ago Yep, no, that's okay. Thanks for going to this meeting. I know I think that after the meeting I saw a few comments of Mark in your repo Especially for the plugin updates, which we are not focusing on this week So I think you may have talked about plugins or not Anyhow We didn't talk about that Okay, now for the repo A few weeks ago John Mark wanted us to have some kind of can ban Because for the time being we only have milestones which proved quite handy, but you can't reorganize You know the issues or work items they appear the way they appear and some of them may be more Prioritized than others, but we can't see them in them in the milestones view So that's not perfect, but as we already are somehow late Um, I don't think we should focus on creating a can ban, but Whenever you feel like doing so You could create a project on github and create a can ban, but frankly That's not mandatory We could do without until the end of the project just do that if you want to experiment with that But frankly no pressure to have a can ban or something looking like that. Okay Thank you Now for the maven tutorial that you Showed during the demo Um, we still had a question Which was should we get the user to fork in clone all by himself or let's the scripts do it I think even if it hasn't been written yet, we turned down yet I think we agreed that we should have a script that does that kind of thing But that we shouldn't run this script by default, you know People are expected to know how to fork how to clone how to use their local IDE So the script could be helpful maybe later on in the process when we will use um ci on ci jenkins io So there could be some kind of automation in order to get uh the riposte forked in clone locally and some but For time being we should not have it Called directly within the jenkins ini.sh and I think that's okay as you touch it's not being called by default anymore Is it? Yeah, that's cool Okay Now for all the pull requests, I just saw one just before the meeting started. Well done So this one is about github actions and Frankly last week, I wouldn't have been able to review it had you done a draft pull request So that's not a problem, but as I'm back on track. Hopefully Don't hesitate to make all the draft pull requests Even if that's early even if that does not work so if ever I could spot or be gentle or remark something that Does not work for us. Uh, we could let you know Not saying that you're doing some things that don't work, but You know, we are just a little bit more experienced with darker and so on. So maybe you could spot something early on so that you don't go into a dead end Whatever so please yes Commits and push regularly create new branches. Let us know create draft pull requests Even if you don't ping us because you think it's not ready to review and you don't want to Us to spend some time something that is unfinished But that's just so that we can spot if ever there is something we could help with Okay So of course, I haven't been able to review Your pull request, but we'll do so later on. I think you still Experience some issues with the whole process. It doesn't work as expected yet. Am I right? Yes, I Right now it's working fine, but I have a doubt in the Running a building a job from the part on the with the call command I don't understand that part completely from FPR others. I have Right now the GitHub action works for Whenever the changes have been made to the particular directory, for example, if it's Changes are made to the second example. It will only run the second examples And the GitHub actions and not others But the default one will always run the Example on the root directory that will run regardless of Whatever is changed Okay So I will have a look at that Frankly to get it working on my draft PR. I spent a lot of time Because I had trouble Parsing, you know the Jason result, for example, with jq, you know, sometimes I had some trouble with the jobs that had never run I also had no as I think you had Um, no, it's not that easy. It's not Yeah, it's not easy. Definitely. So there are maybe some things to tweak to get it running in each and every case I have a look at that and Let you know on the on the review If ever you need to do some pair programming this week, uh, don't hesitate to ask for Half an hour or an hour We could progress together Just in case so that you don't get stuck Cool There were other pull requests, but they were just proof of concepts for next milestones Uh, or even for this one. So you already had spotted the adding github actions for Jenkins validation For next milestone, there is also the push the images to the hub because Damian DuPoteau and mark weight told us it's nice to build on the spot Um, it could be helpful for the ci once more once we migrate to ci Jenkins IO But for the end user, I think I put a lot of details in this pr But for most of the users, uh, we could face some issues For example, they could try to build that on the platform We haven't tested and that does not work Which is not cool, uh to discover when it's already too late because Imagine it's not a powerful machine. It takes half an hour to build and in the end. Boom. It does not start So yeah, we'd like to avoid that And I tried to build on lots of different architectures in this pr. I tried on s 390x I highly doubt any First time Jenkins user is using such a platform, but anyhow, I think it was working ppc 64 le I got some trouble when building And I think I also had some problem with arm v7. So anyhow, I just chose to add arm 64 and amd 64 which means any pc um, I guess Any recent pc So we'll just focus on these ones, but it's for our next milestone Then we also have the get rid of the mandatory bash file because for the time being we have the Jenkins in it and the Jenkins tear down bash files Which work very well But don't work for people using windows without wsl. Yes So it's it's a draft pr that works for me. It may not work for you. I think there is a lot of work ahead But yes, that's just a proof of concept. Uh, so we get rid of the bash files So that everyone can get it to work Whatever the platform may be as long as they have docker desktop or docker common line Docker client and docker server available for that platform Uh, then we have another tutorial Which is pretty straightforward and we have a python tutorial, which is for this milestone this week. Hopefully Then uh, yes, go ahead Ashutosh No, I I didn't want to say anything particular. I was just agreeing Cool, thank you because I know I talk way too much As for the work items, we still have 17 to this day and I think I will find some other ones this week um But for this milestone so this week I'd like that we focus on the githubot weaver sproxy setup is broken and it's not only github I saw comment from mark or joe mark. Yeah, which who was saying that it's not working with During the previous and of doc's office hours and mark setup. It was not it was also showing this statement Fever sproxy is broken So, um Please while we review your pr from today Have a look at that if you can and try to find why it's not working anymore I think it has worked in the past, right? It used to work No, did I daydream? Whenever the local local server has not used it doesn't work So it only works when local who state it is used and mark was not using that uh-huh That's okay, and the githubot also still the same Got it Hopefully you sorted it out pretty easily. We'll see Then we have build a python app with pie installer um We'll see but I think this one is you could do it by the end of the week Except if there are some things I haven't spotted it yet, but I think it should work pretty easily Okay, and the next one is about the ssh key generation, but I don't remember Were you able to reproduce the issue or not? This one is solved. Uh, I did Post the message to john mark, but I think you didn't sort but there's this one is solved This is not happening anymore That's cool cool Good news Um And then about the plugins. I think we had the discussion through one GitHub issue about that and we agreed That we should keep the plugin updated. Thanks to a script Which would give the whole list of the plugins not only the one we need But the one which are installed by default when you are creating a new genkids instance It could be kind of overwhelming for end users to see these big lists of plugins, but that's the best way to have um Different lists of plugins that work all together, you know Not just a subset that you know work together, but you don't know about the other ones And whenever you start or you restart a genkids and instance and you didn't take care of the embedded plugins then there is some Um Information you don't want the end user to see, you know, he starts his genkins instance and The ui is already complaining about plugins being outdated It's kind of disturbing for the end users. So that's why we showed the solution but once more it's not something we'll address uh during this milestone it would be for next next one or maybe the A few weeks from now, whatever. Oh, 31. So two weeks from now whoo, uh We covered everything I had in mind, but Please, uh, let us know baby into our as you touch what you were thinking about Is it if there anything you would like to talk about are you struggling with something we should know? off In the GitHub action file. I do want to see in the build building the job section I don't understand that part from your PR company. Okay Come on. Um Okay, uh, sorry. I don't master google docs So ouch So with the job creation, that's right Yes Yeah With the judge creation in the github action Okay, um You don't understand the Workflow the way it works or you don't understand why it doesn't work I don't understand the workflow right now Okay, uh If there anything we could yeah, go ahead if you, uh, uh Have any documentation where I can find, uh, how this works That would be helpful So how the job creation works, uh, when using the rest api yes I I didn't search it myself because I just I wasn't just trying that That's what's easy to find Okay, um Okay, uh, of course I had found a few pointers here and there about job creation with Jenkins rest api. So I'll try to give you the links but frankly, uh The documentation Is not really complete and, uh, you know, it's not state of the art documentation. I think I found um A few hints here And a little bit of documentation there and I had to connect dots By myself And I even think that's uh, some of the commands I used Where by experimenting uh failing and trying something else. So some things are not part Of the documentation I found they may exist somewhere I don't know where so yeah I totally get it that you don't really understand how it's working um If I remember what I remember is that you have to authenticate to begin with Sorry So as we have only one user for example, which happens to be admin With a very weak password um, I first Kind of login, you know with just a user password in the url Then it gives me I think a crumb, you know, uh, it's to protect cr sf Then I get with this crumb uh cookie File, so I've got uh user password crumb Cookie file and then with that I managed to get uh an authentication token So all the first steps are just to create an authentication token And once I have this authentication token I have to Make a post HTTP post request to start a job That's what I think I remember and the problem is Your your jobs Which could have been mine Use some spaces in the names Complicated so we have to double escape them In order to get them started I I spent quite some time before understanding that because the jobs could not be found I was wondering why anyhow, so once you start that it then gives you Uh, I think it's a jason answer But the very first time as we have never ever started a job There is lots of values which are no or empty. So we have to make a loop and wait Until we get something that we can use and then gq a jq sorry Tries to grab the number of the build then if it's something it can understand then we say that the job Is doing well and then in the end Um, we are waiting until the job is marked as completed and successful But just out of the top of my mind, I could have said Bullshit, uh, I don't know. Uh, I'll try to find the documentation and give you some links That should be explained way better than what I just did The the point I don't understand is uh, I don't understand which command is Clicking the build now button In the process. Oh Would you like to share your screen and show us your code or Yeah, yes. Yes. Cool. Thank you Beaviento if you know about that, please Help us Okay Any Can see I can see your screen. Yeah You can see vs code or the browser A code code Okay, this I don't understand Where is it launching the job part this part, okay Uh, it's doing nothing because just eco commands. Oh Yes, the job naming code is that's what I told you it's double html escaped Um, I don't understand which command is building the job. Yeah, it's not these ones For the timing it's later on Where is the call command? It's missing a cold. Oh, no, it's there. Okay. If the call minus s minus k admin token This one Yeah Okay, I didn't Okay, I look into it in the documentation and try to understand it I was not getting which way from the Build is taking place That's why I was getting confused Okay, I 92 Okay, I'll remember it Good luck Okay Thank you. You're welcome um Anything else you'd like to talk about before you wrap it up No, I just want to apologize for slow progress and that I'll Work extra hard this week to cover up everything No, that's okay. We knew that you had to travel back to school and that you had to Settle something. I guess you're in a dorm or something. You have your room and have you already started your first How that they went to help me, uh, you know, you're Sitting and listening to the Teacher so your first glasses Oh, this course is whatever. I'm sorry Yes, okay, so You already have Okay, you already had told us that we should not expect As much work from you as the previous weeks because you are back to school So that's okay. And for last week, frankly, I should only have given you small items and not Something as big as github actions. I thought it was easy. I was wrong. So that's my fault So you don't have to apologize for that I was it was way too ambitious and You know in the previous week, we had lots of back and forth. We were changing on the ghoul dogs or element metrics, whatever and last week. I wasn't there to Help So that explains also why you were late. That's okay Uh, it was expected and all is fine I told you in the beginning of the meeting that we shifted everything one week That's fine So please for this week, uh, focus on small items while they're into i and maybe john mark review your Uh, github actions pr so python and About yeah, it was proxy And if we finish that by the end of the week, I'll be happy And maybe we even We will even be able to merge your public rest about github actions. You never know That could happen. That would be cool Yes Bevan too anything to add Cool Um as I said before a stash if ever you want to do some pair programming To have another pair of eyes even if they are old and tired Don't hesitate. We'll see if we can find a time slot together and yes, please commit regularly push regularly and Being us when you think it's almost ready or if you are stuck You never know we could maybe help Okay Cool, uh, best of luck for your new year at school And see you later on this week Thanks a lot for your work Thank you. Bye folks