Jenkins Cloud Native SIG, 22 Jul 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: ☀️ GSoC CloudEvents plugin mentor meeting 2021.6.28

Description

We start by discussing IBM's docs on Configuring Jenkins as an event source: https://www.ibm.com/docs/en/cem?topic=integrations-jenkins

Then Shruti demos her latest work. And we discuss questions on using Jenkins as a sink and the scope of Jenkins actions.

A

um Yes, I think this plug-in, or um this doc is using that plug-in, and it's using, um I mean private cloud event, management, which is something I haven't looked into, but it makes sense that um it will be something which is similar to just receiving and emitting events for ibm cloud and anything that maybe like triggers events in ibm cloud or any event that happens in ibm cloud. uh They want to send the notification over to a sync.

A

Yes, it's I is using the event as a jenkins as an event source going into ibm cloud events.

B

And with the event's sake at the cdf, there are certainly people who are very involved in that who work at ibm.

B

Have you been able to attend any of the events thanks? Not that you have to, but it just it just might become.

A

um And someone at cdcon from fedora uh one of the projects from fedora mentioned that you know they're doing a lot around how to enter. Then I was like oh yeah steven singh and I should attend this. I then asked when it's happening, because I confused the dates um but but said that it happens tuesday and the next might be happening in july.

A

Yes, I am looking forward to attending the future because I think those are important also because they are across projects and how they are using events and cloud events in their projects.

A

um Alright, you are you're on mute.

B

All right there was, there was london noise and then I have too many tabs. I have it in my calendar and I haven't been for a few weeks, but I have it on a monday, so I don't know if you have, if you found the cdf calendar I'll, send you a link to the cdf calendar. We can double check times, for it sorry go on.

B

um No, were you saying something? No, no. I was saying that I just wanted to because I think you said tuesday. I just wanted you to know, and I think it is not not today, but um the following on my calendar anyways next week's monday.

A

All right, thank you for letting me know, carl I will and yeah. So I will also this week. um I wasn't able to do a lot um because, uh like I was kind of you know, got really into watching cdcon, but then I thought maybe the weekend I'd be able to do something.

A

But then I had to get my second dose of vaccine, which was so like the side effects were so worse than the first house, um but but it's fine now and um this week, I'm hoping to accomplish a lot so but I'll still do a little bit of the demo of how the ui has changed and um what's new and how the headers are and the events.

B

That's great and and don't worry about this week because I mean I'm sure your work has actually moved forward. Well, but also cdcon was amazing and I'm really glad that you were able to enjoy it and then I'm also really happy. You got your second vaccine. That's awesome.

C

Thank you. Thank you.

C

I think my internet is pretty slow.

A

So you know the last week we were sort of thinking about just moving to a way, so the users can have the option to select multiple events at a time rather than just you know if they wanted to select multiple events. The the option that was um in the ui earlier was just all events, but that was not maybe the the the case that we wanted and we wanted to give users the ability to select events on here, just clicking on them. Whatever the data.

B

Nice, it looks good.

A

So um just so earlier, there was also the all events option, which is still a part of it is inside the code which I will remove, but uh for the sake of putting it into um the the jenkins contributor summit and the github at that time, I removed the all events option from here and also the config part of it.

A

uh So you know um by default, all of the options will be selected and if, if you know over here, all the events will be sent, so we can also try looking at how this is going to look like uh I'm going to save this and also the default equals true.

A

It wasn't um working on yeah.

A

um Anyway, so um the the default equals should not, it wasn't working inside of uh inside of jelly file. So what I did was just do like a equals. True.

A

Inside, do you guys see my code, uh our vs code on the right.

C

A

So, since all events were selected, the two top events are event um a job created and job updated. So obviously they are not sent because that didn't happen, but I can also show how they're going to look like. So I know the last time we talked we were looking at uh the the you know. The type was just earlier. I just had like the type as jenkins yeah, because this was like emanating jenkins.

A

I was like okay, but then I would but then uh mauricio also suggested changing it, and then I also looked into events from captain and techton uh and on google event are again, the the type was inclusive of the sort of the url of where it's um originating from and the uh object.

A

So here it's like the queue here, it's um job and then obviously the type of events mentored waiting, which you left and they're happening in a sequence or we're going to get job started job completed finalize and if there was a job failed that would be emitted um besides job uh finalized. So if a job had failed, there would be two kinds of revenge off finalized and also job failed, and I can also try a little bit of editing this.

A

Also, on the job updated event and similar, I have uh a computer added and computer, I think failed, um even but it's in inside of a clone copy that I have because it was a bit different and I did not want to change a lot of things over here until I was sure that it is working, but some changes in terms of the jelly you know I had tried a lot of things with jelly when I was trying to do sort of a repeatable with what I have so a repeatable here would have looked.

A

A

So repeatable would just be this, but this part starting here to uh the all the events that would be inside of the repeatable, but that was uh not working and then I also tried doing other things like putting this entry feels inside of a different file in the cloud events, google config, so everything the the everything is inside of the global config right now, like all of the events, the getters and the setters, the the data bound setters and also logic, to make sure that you know, since I'm, using uh sort of like an event list to so all of the events, whichever are true would be put inside of this list of events, and then inside of stage is where we would be getting all of those events and then processing it, as should this, should this event be sent over it.

A

Has this? Has this user selected this particular event? So all of these configurations for the kind of events you know created updated all don't doesn't need to be here right now, but I'm not going to comment it out just yet and uh other other configurations like sync type and sync url are also inside of google.

A

But what I had initially was something like and point, and the end point class was uh was where all of these events were present and events like created, updated, and this basically had endpoint inside of it, which was being configured in the java. But that was also not working.

A

I can go back, is to show how I was looking at.

C

A

So this is the first holder class which I closed, because uh it it the it was really different from the other one, which is in main right now.

A

So I had something like end pointless and endpoint, and this was an entire class which was inside repeatable, which was working.

A

So it was something like we have the endpoint list, and this is going to be coming from the endpoints variable and the endpoints variable was basically just a endpoint uh instance inside of the global config and the endpoint instance was nothing but just it had the list of events and it had the sync qra, but it seemed to not work inside this jelly file. So I had to move all of this in the cloud config or like the global benefit.

A

So if you, if you guys, have any ideas on you know, because I I think this is not really clean and we can make it better and I I really really tried with jelly, but there were, uh it was showing up in the ui, but the only problem was it was not saving across applies or saves in the ui configuration. So I had to configure it this way when I had anything looking like.

A

A

Checkbox exactly but I I looked at other conflict files from different plugins, but.

A

It wasn't working and I'm not exactly sure why, because I did try doing it the way other plugins, no other plugin had this sort of inner class configuration in a check box in her class, as in you know, a cloud event, sober config, holding a reference to an inner class like endpoint and that being configured through jelly, so they didn't have exactly that, but they had a way of accessing um like in our variables and in our just maybe like getters and setters.

A

So I don't really know, but you know if, if you feel like this is fine, then we can go ahead with it. But I honestly don't really I'm not really impressed with how the global config is right. Now, I'm just a lot of just a lot in there, and also uh this.

A

This is sort of the functionality which I've had to keep for making sure that the events as like a person is on the ui and as they uncheck the the the check box want to make sure that it gets deleted from the um the events list. Do you guys maybe have any thoughts on this? Sorry, it's all totally. Okay, if not, we can move ahead with how it's looking right now.

D

I mean if it's, if it's working, I I would just just move on for now, because the important thing is to be able to easily configure it and you know not spend too much time on it. um One thing that might this is totally future, but if you look at like, for instance, the thin backup plug-in it doesn't, it doesn't have like glo global config like this it. It has kind of its own separate app where it manages settings and it's a better user experience.

D

I'm not suggesting you move to that now, but that potentially could be something we look at in the future. If there's time it's just it's just better, because all of its settings are on on one screen all by itself, rather than the. If you have a lot of plug-ins installed, the global config is just it's a it's a pain. um I use the global config for some of the the plug-ins that I um created to it.

D

It just it just like it just adds to the mass, in my opinion, but again I'm not suggesting you change it now, but just something to keep in the back of your mind. If you have time later after after we have all of the like actual cloud event, stuff uh working and ng stock, isn't it.

A

We can, um I think, like I'll, be really interested in looking into it. Can you maybe send a link to that in the track channel.

A

A

A

um And also jeff your idea on interfacing the common methods inside of um like outside of different models. You know the model and job model to sort of get the source and tie for cloud events. I think it worked really beautifully.

A

You know it's a lot more cleaner and it, I think you know this piece of code. It's a lot more also elegant than like using all those elifs. It would have gotten very, very huge because there would have been different event, listeners of course, so I'm thinking.

D

Oh good, I'm glad it was.

C

C

A

um Yeah, so so some of the changes over onto tasks- it's not just the unit testing some changes to does how stage was running, to sort of make it a bit more cleaner.

A

I guess- and I'm still, um as I add, the the fourth event listener, the computer listener, I'm thinking of dividing this a stage between different classes for each listener. Each so like a job listener would have a stage, as we talked about last time, because it's making it's going to just make more sense when it's divided and it's not it's not going to be super confusing. I think um yeah.

A

Those were the changes for this week again, as I said, not not a lot of um work done, but but I'm hoping that starting this week um can get more accomplished and then start doing more work in terms of writing more tests and also just writing the implementation for jenkins. As this thing which I've started looking, um I think it should be good. This.

D

Is a great start.

A

B

Good work, as always, did you have any any additional questions on how to move forward? Are you comfortable with what you need to do next.

A

um I think I'm pretty sure on what I need to do next, um but maybe one question would be when we are implementing uh jenkins as a sink.

A

um I am guessing that, like the project, it just needs to remain inside of this as like a global config. Would I'm just thinking? Would we need to have any ui input when we're talking about jenkins, as a sync like? Would users need to configure anything like okay, here's, what we'll be sending events to you like jenkins, will be receiving events from um so and so like this particular url, or this particular client, or is it just?

A

You know no config in terms of no code or no config in terms of the ui, but jenkins just receives a certain event. It's going to parse for whether it's a structured kind of a cloud event or a binary class, and then, depending on that event metadata. It can extract the type and then uh trigger that particular uh the particular action that it needs to did.

D

We talk about um authentication, whether we want to make sure that we, we trust the source. That's sending us events or is the thought just anybody that that has the url can send them.

A

um I don't think that we talked about it yet, but I think that's a very good idea and also like a very important implementation. um I think like what we initially did was. We said: okay, let's start with jenkins as the source, so we did not go into a lot of conversation with jenkins as a sink, but now, since the time is I'm approaching to implement it, uh I think we are starting to think so.

A

Yes, thinking about authentication or whether or not this particular url or this particular just project can send us events or not. I think that's really important, and I think I should start looking into yeah.

D

I'm not sure what what what that, what the options are for that, that I mean that that's the only thing I can think about the top of my head. That might require some kind of ui. There might be other stuff, but nothing comes to mind. um I I don't. I don't know that we we need. Well, I mean if we have, depending on how, how flexible the authentication is that it might include.

D

um You know permissions about like types of events that can be consumed or something so I don't know if some sort of web hook interface would work here or whether there's better technology. This is a little bit outside of stuff. I've worked on yeah.

A

I've been thinking about just uh uh ui changes too and like what I I was maybe thinking of is that jenkins, yes only receives their certain, because you know the last we were talking and mauricio mentioned that it's the duty of the thing to decide whether or not the sink wants to work with a certain kind of event. So maybe that's um wait. How do you want to say something? Okay,.

B

That I was thinking this my impression is that a sings job is to determine whether or not they want to receive the event essentially ascribe to subscribe to it. But beyond that, I don't know how much I don't know how much um control or or programming that happens.

B

I think it's like you subscribe to the events that you want to be in, and then this goes down the chain that the events themselves are omitted and then there's a question of who subscribes and then each person who subscribes for each service uh or saying that they have their own like service, will decide how to handle that the message from the event the data from the event.

D

Yeah, that's that's probably all that's required for this. I was just thinking about like like in github with their their web hook. Ui you can grant permissions to different types of things, but but just because it's not clear to me that we need that here.

D

um Just just like, like you're allowed to send me an answer or you're not it would make me happy.

A

We can think more about it and start with a basic implementation.

A

Has been forwarded so do we still like think that, when we are saying that um the sync decides what to do with the event, do we? If all of that is it going to be inside the logic or should we move some of that to like the ui code, so ui has a bunch of events, uh for example, uh um also above sent me this the event thick vocabulary, which is going to standardize sort of what each event means and what each event should be doing.

A

uh So, if you're thinking in terms of that, maybe when someone says okay resource has been created, what jenkins wants to do is run a a particular job, so.

A

Of that not maybe not the url, but maybe just the host of thousand or the source, not the second sorry, the source which is emitting the event, and then the the user can also select what events are coming in from that particular source. So our logic will only work on doing that particular or just emitting those particular actions, or just doing those particular jobs that it needs to do when it's receiving those particular events.

B

Yeah, I think that sounds quite good.

D

Are are the? Could you think of actions that jenkins could do other than running running a job.

A

Yes, actually that was um a conversation that I had in the jenkins contributor summit. I was like you know what I think actions it's more just like when I am thinking of it. It's more like you know, irani job or like run a uh start or complete or just end the job or something like that. But then I mentioned to about that. We need to think outside of these actions and maybe think of again going back to the vocabulary.

A

We need to think of running some standardized actions like starting a new node starting or something like that which is just outside of the general scope when the events are just standardized as a the vocabulary has certain events like I don't exactly remember right now, but it had something like resource created and resource updated. So what maybe? What we might want to do is have a job which is going to test the availability or just test the um stability of that particular maybe project or that particular you know something similar to that.

A

So I think that, having part of it moved to the ui and just selecting which event slash, events are emitted from that host or from that source might help. Us reduce some complexity in the logic since we'll not be putting in a lot of okay.

A

If event is this and this or this and then do this, and maybe that's what I'm thinking, but I'm not sure if that's the right way to think- and this may be something that I will need input from the entire like team and hearing your guys's idea on what you think the implementation can look like and maybe what the end product is just going to be a mixture of all of our ideas.

D

Yeah I I I like, I like what I haven't spent much time thinking about this, but I kind of like the the the direction you're going from what you've said. I mean you get a particular event. You might want to run a job, and so there's other things you might actions you might want to take. You got a particular event you might want to create. You might want to start a note or stop the note or something um you could.

D

Maybe there could maybe be an event that like creates a user there, so there are maybe some other actions that you might want to do. So I I the flexible model, makes sense to me. Maybe.

A

I'll also, like start researching different actions, because I'm still not really sure about. I still like noaa factions as a jenkins user. But I need to go and look more into the documentation and just understand the scope of different actions and what um they all tie into.

B

There is also a jenkins pipeline authoring sig, which is different, but they might very well have ideas on all the different things that might be happening that you could be doing within a pipeline. You know this. This type of question, I'm just thinking.

B

Reading the doctor is very good, and but it can be a bit. You know it might be interesting for you to ask a wider range of people as well.

A

um All right sounds really good, and that was the only question. That's in my head right now um and as more pop up, I will put them in the chat.

B

Just a heads up that the first and only evaluation, the midpoint evaluations for this summer's gsuk will be between july 12 and july 16th, and it basically is the mentors and students submit their valuations of one another, so the mentor team will submit one, and then you submit one strategy and what we have always done with the jenkins shoe stock. Is we do student presentations at this stage, and this happens at a jenkins main up, which is especially planned for this?

B

As we are taking part in g-suck this year under the cdf umbrella, we will likely do this under the cdf foundation. So there will be a cdf type of meetup, but it will be the same idea where all the gsoc students do say a 15-minute presentation and then five minutes q a and we have six. So it's going to be about two hours, but so a couple questions we are thinking that the possibility of having them pre-recorded or live is a good one.

B

Usually they were live, but just because I I don't know, I think pre-recorded can be quite good, especially for asking for only 15 minutes. So there's that and then the other thing is so the week of the evaluations themselves are between the 12th and the 16th. But we can do this presentation either before during that week or after, and I just wanted to ask you shitty if you had a preference.

A

um I I can do before uh so like when we say before. Do we just like mean the week before I can maybe like send a recording.

A

um You know like the week before maybe midweek like a wednesday or thursday. Does that sound okay.

B

Yes, so yes, so in which case, if you, if you want to do it, recorded that and that's absolutely fine, um if you send it the prior week so before the 12th, then we will likely have that meetup, of course, after that, so it will be. It'll just be a matter of gathering, and but that sounds good to me. So then we'll either run the meet up itself, either at the end of that week, right before evaluations or during the evaluation week. Does that sound good is there? Is there anything happening that week?

B

That would make it hard for you to attend. I just wanted you to be able to be part of it. You know if you have any family events or anything.

A

um No there's nothing that I know of that's happening and I should be available um and I it also sounds really exciting. So, yes,.

B

Okay, good excellent and we'll be sending out more information about the exact time of it. I just have to discuss with everyone good yeah really looking forward to it should be lots of fun. The presentations are always good and it's amazing the work that's being done so and your work is awesome. So I'm very excited for your presentation.

A

um But I really only have like jenkins and the source um done right now, I'm not really sure. If this is enough or should I maybe like add bits and add, since you know we are talking about starting going into jenkins in the sink, and I can see what gets done by that point and put that into the presentation if it's looking, okay of course, but what we have right now is that, okay, it's not enough.

B

Yeah, it's great you're working so far has been amazing. You you're doing that and I'm sure you know it will progress in the next 10 days too. But what you've done so far is fantastic.

D

Yeah, this is one of one of the the best projects I've I've been on. I mean I've been. I forget, I've been on like just just a few two or three, but just been really easy and doing lots of work and and keeping contact with the mentor. So you know- and I I had somebody that just would sort of disappear and didn't see him for a week and that and but yeah. So it's all good.

A

Thank you, so I'm excited for that um and okay, so the recording you said, 15 minutes and then just it should it be, like demo plus, also like talking about the project in general, like the collaboration of say, jenkins, with cloud events and how that's going to help interoperability in general and also just extend you know to you, know the whole idea of cloud native and standardizing events across different systems.

A

I'm just thinking of thinking of that uh and I think.

B

Both is okay yeah. I think that sounds really interesting and it makes the subject more accessible to people who are maybe not looking in the space and so kind of give some context for them which- and it gives a sense of why this is super interesting, which is always nice, but make sure you have enough time to present the work that you're doing, because this is really for you to share. You know your work as well, but it is good to put contacts in if you have time yeah. That sounds good.

B

Thank you, jeff and thank you. Thank you very much so great. We can wrap up the meeting now and see you all in one week's time, but we'll be in contact on slack. Thank you.