Jenkins Google Summer of Code Office Hours, 18 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins GSoC Office Hours, Nov 18, 2020

Description

After a short break, we are restarting the Google Summer of Code office hours in the Jenkins community. At this meeting we have talked about upcoming GSoC 2021 and discussed the current project ideas. We are looking for mentors, org admins and students!

Meeting notes: https://docs.google.com/document/d/1H0gJt1zdr37YDpuSLXSeFqYco_a_CIrAuZ1f0Oyl4XE/edit#heading=h.que9twu9qli8

A

So hello welcome to jsoc office hours. After a long break, uh we will recontinue our regular office hours. So last official office hours was on july 22nd. After that we had a few retrospective meetings, which we didn't put in the this agenda, because uh there were separate meeting loans and now we return back with uh focus on gsop 2021..

A

We have uh several students and past years of participants on the call and yeah before we start, I would like to just quickly summarize uh what is the current state? So we finished the jsoc.

A

There are a few pending education items left like publishing the results, blog posts, etc, but overall gsoc 2020 is over and yeah. Thanks to every participant. Now we focus on gsoc 2021.

A

We intend to participate at the jenkins project. At the same time, we are in early planning stage, so we still need uh to define the orc admin team. We need to define mentors teams, we need to create project ideas. So what we have on our website at the moment is just a few initial project ideas. Basically, what we wrote over from the previous year, the ideas which we still have interest in and which haven't been uh watched on in gsr 2020, and there will be more ideas in the future.

A

So if you are a mentor interested in the project or if you want to submit any new project idea, let us know we can keep extending this list. So it's just a initial ending and uh you know, over the next few months we will have much more details on the website um this year. Gsoc will be slightly different from the previous years. So, if you have seen the timeline, you can see that now there are two coding cycles, um so g-shock is basically shorter than it used to be in previous years.

A

It means that when we define the projects and project ideas, we will have to take it with the account and yeah.

A

Also, there will be some changes in the initial phases, but largely the gsoc format remains the same as before, so they will be still application phase, where every student is welcome to reach out to the projects, discuss, project ideas, application drafts and then once students submit the applications, we will have application review, which will happen internally within the organization and after working with the other mentors and with google, we will announce a final list of projects.

A

It will happen on may 17th, so a bit later than it used to be before, and the community abundance will be over on june 7th. So, basically, there will be still three weeks as of community bonding as before and uh yeah. There will be two coding phrases. Both coding phases is approximately one month. So, instead of three months of coding, basically, you have two months of coding.

A

The rest remains same as previous years.

A

Okay, so that's what I wanted to tell about the plans and changes again right now. We are looking uh for participants, including cork admins, mentors and students, but we can start discussions now and if you have any specific topics to discuss, if you have any questions, let's just discuss them so that we can start addressing these comments and okay before that, do we have any potential mentor uh on the call or just potential students.

B

I will I'll probably be a potential mentor this time so.

A

Okay, so yeah for you, it's a good time to think uh what would be a project you would be interested in in terms of mentorship in terms of project ideas and yeah. We can discuss it in the chat. Also, there are guidelines about opposing project ideas, so you can start exploring this area by the way.

A

What is the project interesting to you or the area.

C

um So actually I just I was looking at the project ideas. um I think remoting monitoring looks somewhat interesting. Maybe uh so I think yeah and let's see maybe I can come up with a few ideas. Also.

A

Yeah so in previous years we had from 20 to 30 project ideas this year. So let's see how many we have in total, but this list is definitely expected to grow.

A

Okay, so and from potential students, are there any questions, any topics you would like to discuss on questions specific to projects.

C

Yeah, hello, hello, everyone yeah. Actually I was I, I went through the project, ideas and uh uh one of the projects caught my attention that uh uh plug-in installation manager uh tool uh like I went through that and for that I saw the requirements like what what skills I need. So I was not that comfortable in java, so I went through the like I'm I'm learning java at the moment, but I'm like now comfortable with it, but there was a mention of java configuration as a code.

C

The gcask yeah like the how the jenkins docker image and configuration has code work in this skills to study and improve section. Fourth, one.

C

The fourth point yeah so uh like uh I wanted like an heads-up like. uh Can you suggest me from where uh I should like learn about these things? uh Actually I saw a talk on this. uh There was a talk by uh nicholas the louvre uh on on uh pragma or something like uh at pragma conference on youtube. I went through that but uh like it is uh something which uh I'm not that comfortable at the moment.

C

But like do you have any suggestion or issues or anything like which will make me familiar with this topic, because I think this is a very good project like package management, uh I like uh understand the importance of it and I also went through the like theory of package management, but not yet that comfortable, but I'm going through it so just wanted in uh like a reference or something to get more on this.

C

I went through this yeah.

A

So you can start from documentation, uh we have some documentation for configurations, code plugin, and we also have a lot of demos specifying particular topics. So here you can find demos and yeah. There is a lot of plugins.

A

uh Usually when you start with this topic, my recommendation would be to just start from creating your jenkins instance, maybe trying to configure it for your project and then to move this configuration to configurations code. So you could follow the guidelines here. For example, there is documentation about features, uh um configuration export which describes how to export configuration from existing instance.

A

So once you create your instance, you can just try to convert it to is called using these guidelines using a docker image uh so that it's also decreased. Here. You can find this information, how the docker images separate and if you need any specific grammars the results. For example yeah. There are multiple repositories which follow of approximately the same pattern. I will just show you my repository damaging configurations code, so this repository basically shows how to configure everything with docker jkusk.

A

So you can just follow the example.

A

Here: okay, thank you yeah, so I will put some links to the meeting.

A

A

And while any other questions.

C

uh Actually, I have one more question uh just.

D

C

Not much of a question but uh like what's your suggestion on that thing, I was like setting up my own jenkins instance, but, uh like uh I didn't want to what I should say, uh install a lot of software and all that, so I what I did was I tried with the jenkins docker image and uh there was like to work with jenkins, plugin installation manager.

C

There was a one like reference guide about how to quit like how to start a quick start section. There were huge, like all the points from mentioned, clone the project run the test. There are several different lists of plugin. All those things were mentioned in the uh projects uh projects website page, so I was like uh I was just wanted to ask like. Should I go with the docker image like?

C

Should I try running tests and uh like uh trying this tool with a docker image or with the jenkins instance like I began with the docker image, but I'm like not that much comfortable with docker. So what would you prefer like? What would you suggest? What should I do in that? Like? Should I go with a local instance or with docker docker.

A

File docker image, so in this case, look at this rather in implementation detail you can use the tool without a docker and you can connect it to a local jenkins instance.

A

So personally, I would recommend to explore docker, because docker is a foundation technology which is good to know and which is widely used at the moment.

C

And docker is also required for this project, also right for plug-in installation manager, tool.

A

So it really depends on what would be your final proposal, because here we offer a project idea. So basically it's.

A

Just our vision of what could be done and what would be the main tasks and priorities, but we do need to define a project. It's a student replicants who define what would they do? They submit a proposal. We make decisions on that. So why dokit was there.

A

So yeah, you can see that turkey is mentioned multiple times, uh because uh yeah, one of the main objectives uh for this project in 2020, was to integrate it into the official docker images.

A

You can see that this project is currently in the drafts, because the description is still needs to be updated. uh Current stated that we already have it inside the docker image. So if you go to jci docker, you can see that the tool is already embedded there. Just second, that is plugin.

A

Management, sorry, it's in the documentation, just don't see the navbar okay, so for pre-installing plugins you can see that plugin installation manager is already in preview here.

A

So the first step is done, but there are still issues we discovered during the evaluation and also there are other use cases where the two could be integrated, so it still remains relevant at the same time yeah. What would be the particular percentage of the work it's yet to be seen and discussed in the proposal.

C

Okay, all right, thank you.

A

Yeah, thank you too. So yeah you can definitely play visit without docker. There is a lot of things which could be done without docker. So if you go to plugin installation manager tool, for example, there is a number of open issues, actually not that many at the moment, but yeah there are some defects which need to be fixed.

A

There are also some enhancements which could be done, so you can play this that without even touching docker, and if you come up with a proposal which doesn't involve docker and just improves the tool or integrates with other technologies tech, I think it would be doable.

C

Okay: okay, I'll, try, okay, okay I'll, like I'll, see, let's see.

A

Yeah, so we had uh joining configurations called uh think meeting today and we discussed this too a bit because yeah there are still defects which impact adoption and also we still have a problem of uh having multiple tools when so. This is a gsoc 2019 project. It was created by natasha stapa, one of our students. Then it was improved over time, but we still have the main issue, because this project was created to replace other plugin management tools. We have replaced uh in the docker image, but the results.

A

There are also many other plugin managers in jenkins and we still need to keep replacing them, and it's also something you could play.

C

C

Okay, uh so like our basic main goal of this project is uh like, as far as I like. If I try to simplify the whole like in crux, our main aim is to create a tool, uh for example, a package man, basically a plugin manager, which will replace all kinds uh every other plugin manager which exists at the moment in jenkins, to install plugins right. That's the.

A

C

If, okay, in theory.

A

Yeah in practice, of course, there are different obstacles which could prevent using this tool everywhere, but at least some usages could be replaced uh even now. For example, I'm a maintainer of jenkins file runner, it's a basically fast mode for jenkins, so you can execute drinks pipeline in the container and then this container shuts down- and here I also have a task for adopting plugin installation manager.

A

There is definitely a good request for that.

A

So this is uh one of examples. It's not finished, but it basically replaces the internal plugin management logic by a plugin installation manager, library and you can see that the logic in the tool is quite short because it just supports a few use cases. But instead of that, the idea that here you would get full featured plugin manager.

A

Same for the use cases, you can find a lot of plugin management code which could be improved.

C

Okay I'll go through them, then thank you.

A

Maybe so you can probably go a bit back, so if you go to 2019, there are also project ideas, and here you can find the original problem statement. uh Well why this tool was created.

A

So it's here yeah at that point we were doing project ideas in google doc, which also worked fine. So here you can find, for example, a list of existing complementations and you can just go through these implementations, but your custom work package is still there. It hasn't been uh switched to the two jenkins evergreen uh yeah.

A

This project is deprecated at the moment, so it's probably not uh the most important thing jenki's filed runner is here also other implementations which is still around, so you can explore the original scope and the original problem, which could be a additional source of information for you well, at least it would help to understand why these tools exist and the way you would like to adopt here.

C

Sure then I'll go through them. Thank you. Thank you.

A

Okay, so any other questions comments.

A

So how we do this meeting? Basically, we hold it uh well, there are questions. If there are no questions, we basically close the medium earlier, so that everybody gets more time.

A

If there is no questions again, we are just starting, and since we don't have other mentors number three, because.

A

But yeah, I guess we will just keep working on that and honestly. So if you haven't yet joined the million, please please do so because we will be doing canals once there and yeah. We will go to the development list soon to facilitate project ids.

A

Also, if you are looking for more project ideas, so this is just the list of what we removed, but you can find more project ideas, for example, for 2020 on four other years. Many ideas haven't been published for 2021, but there is still relevant.

A

So, for example, there are some ideas for jenkins for jenkins sex. Not all these projects have been completed during the previous phases and even if they were completed that might may find some ways to extend that. So, for example, if you interested to work on pluggable storage last year, we finished external fingerprint storage, but there is still a big scope of different stories which we would need to deliver.

A

Just a second plug was published, so, for example, you can just navigate through pages and find these stories and problems. This could be potentially a project idea, even if it's not listed at the moment, and if you have any idea what you would like to work on personally, just link it up in the guitar channel and we can discuss what we could do with it because yeah if.

C

There is an idea if there.

A

Is a student we can could ask around? Maybe we would find mentors for this project idea and yeah and the original project ideas are definitely our preference in the genghis organization.

B

Once again, I'll go again so about the automatic specification generator for jenkins recipe, and so I read about the idea: I've gone through tracker and open a paradox, but the project talks about the automatic automation of the specification generator. So at one place I saw the documentation and there was like a documentation on the swaggerhub, but someone commented over there that it needs to be automated, so um yeah so right now I don't really have any idea about how we can do the automation of that so yeah. Any next pointers will be.

A

Definitely something to explore also just an additional sort of ideas for you. This year we published the public junkies roadmap, so here you can find wider stories and initiatives on which the community is working on. So here you can see that there are some items in preview so which have been delivered at least partially.

A

Also there are items which have been currently worked on and items which we want to handle in east future or at some point. So if you are looking for a project idea, you could definitely take a look at these columns so near to your and future, because there you could make a proposal for your project also some items, including currently they could also be extended.

A

You can find a particular area to work on, so you can just take a look at this page and if you see something interesting to you and something which could fit the gsoc time frame and you solve the basically project type, because jsoc is just about coding, then you can make a proposal for project videos sure that we could find mentors and interested stakeholders.

B

um Yeah thank you for that. I haven't gone through this but yeah. My question was about this uh specifically about the specification generator so.

A

A

So it's uh in 2021 right.

A

Okay, specification generator.

A

Sorry, I was probably answering the question so here again the idea remained the same as in the previous year, so we would like uh to have a generic specification for rest api or for subset of rest api for this project idea. You can find discussions in the mailing list because last year we had students, who've been making proposals.

A

Topic for initial discussion, so you can find some additional sort of inspiration just by going through uh the discussion. So, for example, here we can see check this thread as an example.

A

uh Well, this is probably not the ideal one. There are just a few messages, but there are more threads which could help them here. We can try to find them later so just uh start by investigating rest apis.

A

If you have existing jackets instance, you can play with that or you can just play, for example, with ci gen casio. You cannot because our rest api is restricted.

A

So most likely you won't be able to really call the endpoints or some of the endpoints accessible here.

A

So api is blocked here.

A

Yeah, maybe just one appear, no, it's it doesn't for me, but you can find another jenkins instance, uh which is public and which exposes apa, and you can really start writing simple code, for example, extension etc, which could help this process in common stories.

B

A

So open api basically, would be your good starting point. Also for some code you can see discussion links. You can also see how other things work. For example, there is.

A

It's plugins, I'm not sure what purpose it's here uh but yeah. There are some uh components which already generated some data from jenkins. So, for example, if you go to configuration score plugin, there are two features: one is schema generation, another one is documentation generation and both of these features actually use the same indexing approach. They analyze code and analyze, extensions and generate the documentation.

A

So, for example, here json schema, so you can explore the code inside.

A

D

A

Okay, sorry, if uh advance is too abstract but yeah, it's probably an array to look into and again for example, next week, if you're interested, we can make a deeper dive because everybody, including me, you need to restore.

A

D

A

So is there anything else I could help with yeah.

B

No I'll go.

D

A

Also, have you already checked out swagger hub or whatever it's called these days.

B

Yeah I have explored so I gotta find open api specification practice or uh some kind of thing for dartmouth's.

A

B

So so are we planning to swagger up or like something like swagger up should be generated, and uh every time like a rest, api is something is changed and automatically documentation should be generated. Is that agenda for this people? It can be an agenda.

A

Because, again, it's up to a student to submit the proposal. So, for example, you explore this project, you define what would be interesting to you and what would be important. You discuss it to these mentors and after that you come up with project scope definition and, for example, if you propose integration with swagger hub or if all mentors agree well, why not? It's definitely something which could be useful, but uh while working on that, you still need to uh to keep it in account.

A

uh The project duration, because yeah two months is not that long and not everything can be delivered in two months. In this project there will be like a lot of foundation, work just to get basic functionality running.

A

So, if you're able to also deliver integration with swagger hub, why not.

A

Anything else for today.

A

Looks like not so then, thanks to everyone for your participation in, we will keep working and preparing to the project, most likely we'll do official kickoff in december, but meanwhile you're welcome to start exploring the projects or to propose your own project so that you have more information and we start preparing for the next year.

A

Thanks so I'm not 100 sure whether we will have a meeting next week, uh but if there are any questions, please bring up them in the chat, so we have uh jenkins uh g sub guitar. This chat is open, 24 7., so every if you have any questions just drop in there, and if there is agenda we will definitely host a meeting next week and even if needed, we can have even more meetings. So it's quite unlikely in this early stage of the project.

A

And thanks all and the video will be available by tomorrow, so I will stop the recording and see you next week.