Jenkins Google Summer of Code Office Hours, 13 Apr 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GSoC 2021 - Jenkins Plugin Installation Manager project discussion

Description

At this meeting we had a Q&A about the Jenkins Plugin Installation Manager project idea. There was also a brief Q&A about mentoring in GSoX and the semantic versioning plugin. Project page: https://www.jenkins.io/projects/gsoc/2021/project-ideas/plugin-installation-manager-tool/ . Meeting notes: https://docs.google.com/document/d/1H0gJt1zdr37YDpuSLXSeFqYco_a_CIrAuZ1f0Oyl4XE/edit#heading=h.81zjhmhxdlwv

A

Okay, hi everyone uh welcome to the gsoc meeting. Today we have a special uh session about the plugin installation manager project idea. I'm going to share my screen this year.

A

Okay, yeah just a really quick introduction. So we have a project idea for this here, which is related to improving plugin installation manager. This is the continuation of the previous work.

A

We've been working in the jinx community, including soft 2019, when natasha stoppard actually created this plugin and there were a lot of performance and now we have basically a wide open project id which suggests doing some improvements in the tool and if you go to the tool, you can also find that there is quite a number of open issues there, including various feature, requests reports etc.

A

So in our proposal we basically offer experience to take a look at the backlog to find the areas which are interesting for them, including ux background whatever, and to come up with a proposal so yeah. This is the context and we have several students reaching out um any kind of questions and topics related to this proposal and yeah. I think we can start.

B

um So like I, I would like to go first, if no one has issues so yeah like, like you, mentioned one thing about the bomb like bill of material and the infrastructure about that, like what do you think about that, like you also mentioned that we'll have to, I think, make some changes in the jenkins infrastructure to expose that or host that, like the metadata of that. But uh like can we discuss it over here like what are your views.

A

So just clarify: what's why it's so important.

B

A

Of the tickets in this program so currently there are multiple ways to provide versions, but generally you end up with such a definition where you specify what plugin to install and what version to install and the problem that, if you define version you would have to maintain it somehow. So there are tools which automatically update questions. For example, we widely use independent board in the jenkins project. We also use update cli created by olivier and yeah.

A

There are other projects like that, and but at the moment there is no project which would support this channel format. There is a project uh which would which supports plugins.txt, it's a text format, but not this one, and the idea was that okay, why do users have to manage these plugins at all, because we have another component we created, which is called um jenkins bomb. So basically, it's the deal of materials for plugins, which includes a set of plugins for different jenkins lcs baselines.

A

So we don't provide it for weeklies only for lcs and therefore, basically, we have regular releases which provide a set of plugins which has been cross tested using standard jenkins tools, including plug-in compatibility tests, etc, and how it looks for users. Basically, they get a list of versions of something like 100 plugins. By now and these versions at least they get give some confidence so that they're compatible with each other.

A

So it's not like it's fully granted compatibility because we don't use, for example, acceptances harness wherever it has another bits, but it still provides some level of confidence and the idea. What is what, if users use these versions so that, for example, if you don't specify a version here and if you add traditional setting like version source jenkins bone version, whatever just another definition- that plugin installation manager would go check versions of this deal of materials and use these versions as default ones. If nothing is specified.

A

So that's the idea what I mentioned in the ticket. While we had a discussion, I mean your proposal that if you want to read these versions, you will need to read them from somewhere, because currently yeah.

B

Exactly targets.

A

So it means that if you go to project and sayo, it's basically a jinx artifactory instance uh provided by jfrock and which is used by the entire jenkins project at the moment. So here you can find this bomb and basically it will be from xml if you're familiar to this medium, which you can read from there as a developer and when we refer to these builds of materials. Now, maybe in definitions we actually read from there.

A

Okay, it was a bad idea, but well you can find it there, but basically it's just home xml file with the resolved versions and this unwrapped dependency list, because there is some inheritance there. So you get a plain form xml, something like let's say that, but yes, all the versions attached. So this is what uh jenkins build flow uses.

A

If you want to use it in a plugin installation manager, you would need to somehow retrieve this file or maybe read it from a different uh source, and hence I mentioned that it might require some changes in the engineer's infrastructure, because it's really a question of how we want to serve this file.

B

So like how you mentioned from uh whatever the I think you mentioned, jf um a website where you went and bombed up like you searched it. No, no uh like there was one website which you went uh jane fry. I think uh some website which you visited and, like directly you could see the bom xml of bomb over there.

A

Yes, you can see.

B

Yeah yeah: what's the name of this uh report.

A

Or jenkins, okay, yeah.

B

So, like I'll find.

A

An exact link if you want, but it's about just a second, let's take a look, so it's so leo jenkins tools, boom.

B

Okay, so I mean uh like: don't they provide any kind of api or something like uh how update uh dot like updates dot jenkins, provides a json metadata kind of thing. So, like don't.

A

C

B

Anything like that artifact.

C

A

Not in the format you would use for this tool because you can just download the file from there okay, but it has all these limitations so yeah. If you just want to download it.

A

But yeah, so what you can get right now? Well, unless you find something I'm not aware of you, so that are your jenkins.

A

Your junkies tools bomb and there is no tools because yeah I'm looking in the wrong repository. I guess okay yeah. It should be not in public. It should be in.

A

A

For example, this is the last lcs and here, for example, version 27 discussion. So you'll get a detail. I will just put it to meeting the document we use for office.

A

B

Like if I hard code, the urls, then it will be like very hard like every time a new bomb release comes out, we'll have to update it, so kind of we'll have to think something like what what uh what is the like? uh What changes in the infrastructure like uh what you're suggesting I mean creating something like.

A

Yeah yeah, if you're fine with this file, you can theoretically just download it from that url so yeah, because someone issues which needs to be discussed. For example, factory.

A

Okay, it means that we don't provide the same level of availability as for other services. Well, we don't currently have everything thanks to jifrop. It works perfectly but and yeah, so you would also have to parse this format, etc. So there are some my hidden obstacles. If you go to updates uh jenkins scion.

A

Screen sharing so here you can find basically the site, so let's yeah at least join the sales search download. So this is basically our download site where you can find uh plugins where you can find uh war files. This is the mirror, and this is highly available infrastructure. So if you just post bombs today in some format, then you would be able to retrieve this metadata and serve it quite reliably and also the other. Is there update centers so, for example, yeah?

A

Let's just go through this drinking style again and here, for example, the reconfiguration files being shipped so just now, we have a bit different front end there. So sorry, so there is example of one of metadata files we are serving and actually there are a lot more different items. So here you can see that the list. For example, we have information about updates, also information about recent releases, plugin versions etc, which can be retrieved, and then there is information I have need for jenkins plugin site, including documentation, etc.

A

So it's also referenced somewhere from this list. So yeah. This is the metadata. We include and actually reserve more metadata uh but yeah. This is a part of our infrastructure. It's what jenkins uses, so it would be funny for a plug-in installation manager who uses it as well, but in such case you would need to do updates if you feel it's important.

B

So, like just adding um look, I mean communicating with other members like who are involved and on the community and like taking their feedback, what they think on it. I mean just adding one more thing: one more option of bomb will not affect or like harm or break anything, but uh well like it is the part of uh further discussions.

B

You know like if, uh like what you suggested to include bom uh as an option over there that will be like, then we can directly use the environment variable, which is which we have set for the tool and from there on like we can access uh the versions of the plugins right like I think that will be uh so yeah. There are multiple ways how you could do that so, for example,.

A

One of yeah and just provide an example. It's not something I advertise for and that's up to you, but, for example,.

A

A

We can just take something like uh professional.

A

A

I'll just provide an example, so it's not something like you would like to follow. Baseline 2.27.

A

A

You could do something like that and then you could say that, for example, git plugin is listed in bom, so here you can just.

A

Keep get here, for example, for buildbridge branch source, the same for docker same for script, security. You could just keep it like that and for pipeline steps api. So unless you override it, you could keep the format. Something like that. You have to keep jumping on board plugin because it's not included in the bomb.

A

So again, it's just an example of how it would look like.

B

Yeah, like how the user can input the like uh get the plugin.camel, but the processing part okay, yeah.

A

So it's up to you to design how to look right. If you do the before the final proposal, it's great, if you don't okay, it can be discussed later.

B

Okay, okay, I'll try like I, I don't like. Okay I'll I'll, see I'll see money. You are you're active today, right, like you, don't have any as like. You will be uh like if I post my link again, you will be you provide the feedback as soon as possible, because today is the deadline, and I didn't want to like extend this thing to the last day, but I don't know why it happened.

A

Yeah, so my recommendation would be to, of course submit the uh uh my recommendation is to submit your proposal as soon as possible yeah. I cannot guarantee that I will be able to review anything today because I have meetings starting in uh one hour and a half after that they will be more respectful back once, but yeah it's up to you.

A

I just put some.

B

uh Thanks for that uh yeah one more thing uh I have discussed this before as well, but I just want to make this thing clear, uh like uh there was one time I mentioned about the jenkins folder. uh I didn't remember that uh issue where we like. We provide a feature to the user.

B

Yeah add support for generating a new plug-in file based on the current jenkins folder, so like this is the issue and I have very vaguely like discussed or mentioned whatever I want to do in the proposal yeah this and not this one.

A

Yeah, it's actually the previous issue and just I think the sample here.

B

A

Yeah so, and that's something I recommend to everyone: if you see any discussions coming from public, you can just discuss that because.

B

Everyone will be updated with what.

A

Happened: okay, so something like that: um okay, so you're, asking about the generating list of plugins from the folders list right.

B

Yeah, so that folder is uh basically some directory that, where we downloaded our plugins or like, I think you did mention this in one gsoc office or but I tried to find it uh but couldn't find it on youtube. Something happened. I don't know some office hours missing, yeah yeah uh regarding this one, only so what what is the jenkins folder over here like the plugins directory, or I I you did mention this, but I forgot it somehow.

A

Let's take a look.

A

I'm not sure whether I have something, but what most likely I.

A

C

A

So, let's see what is that, so it's basically it's a packaging definition. I believe so. There is no jenkins workspace. Well, let's see what we have in camp or no, it's not something. We need. I'm just trying to find the jenkins, which I would be able to use to discuss, because I already deployed jenkins.

B

So, like are you looking for a jenkins instance where you can find jenkins, folder, okay, yeah well,.

A

You found it so, just whatever I think, from uh development it's two years ago, not that doesn't matter so yeah, here's a jenkins home. So it's a basically a root directory of what jenkins exposes, and today we have multiple folders, including one called plugins, so yeah here you can see this is empty.

B

A

So we will need to find something else again: let's just uh go with our development folders.

B

What will be there in the plugins.hko.jpi files, like those files, will be there.

A

uh Actually, it depends because jenkins support uh supports the possible ones. Okay, so usually they will be gpa files, but in some conditions, so there might be ones as well.

B

So, like just those things will be there now, like other than that, nothing is like.

B

I mean uh just those uh plugins will be there now in that in the plugins folder, like uh other than that. That would be not something which I have I might be there.

A

Just looking for an example, okay.

B

A

Do a clear demo.

A

What I'm going to do, then.

A

A

My auto completion works differently.

A

B

A

Let's create a work directory.

B

A

Okay, so something like that, so I'm just gonna to start.

A

So yeah I'm starting a new version of jenkins. Again, I don't have any other reasonable terminal on this laptop, so yeah I'll, just open another.

A

Console we call it plugins.

A

Okay, so you can see the jenkins instance is starting, so we will install in a few plugins.

A

So while we wait other new questions specifically about this project idea, so I know that london and idita have different questions but yeah just in case I'm missing something.

D

I'm just trying to understand like what exactly is the purpose like what what things we are trying to add into this project like in terms of plugins, like you were explaining something about bomb which is an existing dependency. I guess uh because there's a bomb.xml already existing, so we need to like uh what is the like. In short, if you can give a one-liner like what exactly is the use of this project, it's like doing an installation or something like what it does.

A

So this plugin, uh so it's not a plugin, it's a cli tool which allows managing plugins for jenkins, but without starting jenkins. So basically you can do it in cli mode without starting jenkins, with your configurations and then you just get the plugins unit.

A

Is it clear or not.

D

Yeah, somewhat I'll just go through the documentation. I think you have shared links there. uh So I'll just go through that again and I think there's already an existing code in which, on top of which you are trying to add more enhancements or to this project right.

A

Yeah, that's correct: okay,.

D

And like I just want to clarify for that participant thing like you're saying for participating, we have to submit a new project or we can be part of an existing project which are there posted on the home page of jenkins.

A

Okay, we can discuss it because it's a wider topic, okay, still started anyway, so we have a number of project ideas again. These are project ideas, so we encourage students to export them and to come up with their own project proposals, and this project proposal uh might be based on one of this idea or might not. It depends on you, so you can come up with a completely original proposal um and yeah.

A

Then we will basically review that decide whether it's feasible for the company, where it's visible, technically etc and yeah then decide which projects we accept.

A

So it's a long explanation, it's a short explanation of one process but yeah you can submit any application related to jenkins.

D

Okay, so, basically to participate, uh it's like necessary to submit a new project. uh Oh that's! What you're trying to say right.

A

uh Yeah so the replication guidelines uh so just talk here, if you guys go to the documentation, information application guidelines for students. This is the same moles of the same grade as you would get on the gsoft website. But there is some additional information.

D

A

D

I'm a working professional, not a student, okay,.

A

Then you can be a student, you can be only a mentor and be as a mentor. You can join any project.

A

Okay. So if you.

D

A

D

Or something like to join as a mentor like you have to submit or like you have to raise a pull request or something.

A

For mentors there is no strict deadline, so mentors can join the project at any face. Okay,.

B

A

You're interested my recommendation would be to reach out to the company as soon as possible, because today is a deadline for student applications and yeah. After this we will start some proposals and permanently mentor things.

D

Okay, so uh when uh just two more questions, so how do like suppose I go to the projects? How do I like uh contact this relevant people which are part of that project like there is any slack channel for each project which is ongoing or like? How is there any other communication channel.

A

So yeah for that, uh you can see that uh on many pages of jenkins, you have a connect button on the right and sometimes in the description. So here, for example, if you go to project ideas, you can just then click installation manager we discussed. So here you can see that the description and also contact things. For example, we use platformc as a umbrella special interest tool for this project. So here you can see the main keys. The github chart also regular meetings we organized and yeah.

A

So you can use these links in order to establish a contract with the coming in here.

D

Okay got it so.

A

D

We will be able to raise full requests like we will be able to like uh contribute as well right, apart from guiding the students.

A

Yeah, that's perfectly fine and well, you can contribute. Jenkins is an open source project. There is no restrictions from contributing. So if you go to plugin installation manager tool, there should be contributing guidance on this episode. Okay, I believe you'll be created with the kit once maybe not uh maybe not but yeah. So basically, you can just send me full requests.

D

Okay sure got it thanks.

A

So much when the visitor in jenkins, you can just create your uh submissions. Okay, you can see that there is ongoing installation. So, let's see what we currently have in the direction, sorry that everything is so slow. That's why we use another computer for development, okay, and you can see the layout of this directory, so you can see that installation is still going, but here you can see that there is a number of gpi files.

A

These gpi files are basically represent the plugin packages and then there are also folders, so these folders basically provide unpacked plugins. It's needed for better performance on startup and also class loading happens from basically these folders. So here you can see that there is basically an exposed plugin, including some manifest metadata and jar files, if needed. Just files is basically well it's just the java binaries themselves. The rest of it is metadata.

A

For example, this is a plug-in manifest where from which we extract information, about versions, dependencies, etc.

B

I see so and so like what uh tim has in that issue, what tim erased he like uh he wanted the tool to like go through this folder and generate uh some like generate whatever is in that folder and print it out like in the three formats which I have mentioned so.

A

That was the so basically uh take these folders comment and generate a apply again. Installation manager configuration file representing the state of this folder, so just read the um all, which are bundled extract, the versions um and the information and provide this metadata. So it's not something impossible because again you go to any plugin. There is meta information. There is manifest, and from this manifest you can discover group id which is needed for some configurations.

A

You can just cover artifact id. Well, it's just folder name but you'll, say here, and here you get the plugin id or short name is always a plugin id plus there are other things you could use, but basically you just process, archives and extract this manifest file of parts of it and then generate the resulting file.

B

And the main purpose of this, like is to pass it uh as a configuration or like uh support like uh for the task purpose.

A

Right, yeah yeah. So basically it's a feature for configuration expert. So you use this.

B

A

In order to extract the actual list of plugins on your instance and then yeah, then once it's converted, you can start using project configurations code or basically the same plugin installation manager, but in the installation mode.

B

uh One more question like uh where, like this is this folder uh I mean uh what I should say: constant, actually not constant, I mean uh specified, like its location, is specified for every like uh uh installation like every instance at every computer like wherever it is uh installed jenkins. So it's it's. uh uh The plugin folder is its location, I mean constant, or it varies depending upon where the user has installed his instance.

A

Okay, so it depends on how you use jenkins, because if you use classic jenkins, it's more or less fixed, it's a jenkins home and there is a plugin directory.

A

But if you use jenkins in other flavors, for example, jenkinsfile runner, it's a fast capability for jenkins, then this directory may be located somewhere else. So yeah. My recommendation would be to write it.

B

So like uh for the starting purpose like for the for the initial state, I should like ask the user to provide me the location of this folder that will be a good way or not. Okay, okay.

A

Cool, so basically it's also a question of parameters. You would need to pass.

B

B

A

B

Okay, sorry go ahead right side.

A

So my recommendation again, it's probably a bit too late in the current stage, but here you can just play for these existing jenkins instances and explore how plugin directories are generated because yeah. This is a most common example, but for example, as we discussed instead of gpi files, there might be hpi files here.

B

A

Pieces then, in some cases these files actually represent directories. So font awesome api will be gpi, but it would be directory instead of the archive, because at some point somebody decided that it could be a better option for performance because you don't need to process these files. So there are many such cases that we can discuss later sure but yeah. So this is the basic format.

A

Yeah, please also there, uh but there is an opportunity to disable plugins, so you can add additional metadata file like, for example, jdk tool, dot, gpi, disabled and then this plugin will be disabled and not really installed. So these cases is something you will need to process.

B

Okay, I was like I was saying that I was also looking at the demos of gcask like how I can use or how this tool, like the output from this tools, uh ml file, can be used for so I was also exploring about jks and I'm like currently doing that uh in this time. So yeah definitely uh looking forward to this, and uh uh I also came across the uh this one.

B

Open pull request uh still like the pull request, is still open for the locking part, like uh it's titled as ad logic, and I I'm also targeting that like what uh I don't think like this much progress. In that uh I mean it has been dormant for some time.

B

A

Okay, we can just go to the code again so plugin installation manager tool.

A

So if you look under the code, so we have two components: one is library all interesting code is in the library at the moment and there, for example, we have implementation and there is plugin manager java, it's main class, it's quite big, but here you can so there is a lot of opportunities for refactoring actually, but here, for example, if you talk about login, you can see that the.

A

Main so loading happens through system out, so basically you print directly to std out and it's not a good practice for system login, because there are existing frameworks and apis for that and in jenkins. Historically, we use java ut logging.

A

So it's a part of a standard java, so it's available basically with any distribution, and you can use that so, for example,.

B

Natasha has had opened a pull request on that, like log like she created something, but uh uh in pull requests and the plugin installation manager only there's a pull request like open yeah. So I mean now what happened like why it was not completed. I mean what were the issues if you can tell me like, I can avoid those in future.

A

Yeah, it's a good question. So what happened? uh What I could say that just wasn't finished so some.

B

A

Are quite straightforward, so they can be converted some.

A

Discussion because, for example, there is option.

A

A single entry uh to log it it's quite possible, though it's probably not the best practice, but it's possible.

A

Why didn't we nurture that? uh That's a good question most likely because of the timing. It was quite late in the jigsaw freeze and now it was actually quite early, but it has never been finished and we haven't meshed it during json, then uh we had merged conflicts.

A

And finally now we finished that, so it would be nice to get it over the line. It's a relatively straightforward. So this doesn't care about uh very big chunk of code.

A

But if you want you can do you can actually take this full request and you can analyze that, so you can take a look uh that yeah. So there are some differences, so resolving the match. Conflict uh might not be a bit trivial, but it's possible.

B

So like yeah, I can. I can definitely look into that. I do and like she also mentioned something in her comment like something about levels like level.fine, and all I mean she was. uh She said that uh some some messages were out. Election messages were printed somewhere, not because of the levels and some issues in that.

A

B

A

Features of system modem because you can define which logic level you use for 54 levels depending on how logging receivers or listeners are implemented. This message will be either printed or not.

C

A

Login receivers might be completely different, but maybe console output file, output writing to whatever external login storage and you can set up what login levels they process, what login classes they process and basically, here in this interface, you will see, for example, this message is a warning or this message is a severe error, or this message is information, so just for user information or you can, uh at the other, fine grain levels like debug, etc and then, based on this level, this message will be either printed or not.

A

So, basically, when you work on this change, you would need to determine what is the kind of this message and to set appropriate level.

B

Okay, I was like uh going to yeah. I was like going to do that like undis, uh evaluate what are the levels of the messages but yeah for sure. Okay,.

A

Okay, so usually it's quite straightforward. There are some disagreements, even in the jenkins code. So sometimes we change logan level for particular messages.

A

It's just a question of setting something initial and the default behavior will remain relatively the same while we use levels up to info, because because these levels are printed by, the whole user doesn't configure the system.

B

Yeah like exactly like one, one must like one has to decide initially and then, depending upon the behavior or the receivable of the like, depending on the feedback it can be modified later on, but yeah for sure. First, we'll have to select one level.

B

Okay and uh yeah like I had these questions for now, and uh I think uh some of the issues that I have selected are pretty straightforward. For example, this logging one and these are like, but some are uh some- are a little bit complex. In my opinion, uh I don't know how like pico cli, I I have got the reference of your jenkins file.

B

Runner, like you have implemented that you have migrated that to pcr life remarks 4j, so I've got that reference I'll I'll like definitely make a poc of uh like I'll, definitely create a workflow of how I'll what option should I start with for the pr?

B

So I'm working on that for the migration and the logging. One is a little bit simple. I mean: do you have any suggestions for me to like for the proposal anything like that which you would like to say yeah and any advice like that's it. I don't have any questions. You know.

A

Yeah, so your proposal is quite reasonable in terms of the scope I mean yeah. There are multiple tasks but yeah all the tasks have value for users, so this tool. So I think it's okay and it's uh reviewed later by the mentors. So again, you have a lot of opportunities to improve that, for example, to think how you configure that what would be the formats, for example, et cetera, the scope of issues is generally defined.

B

Okay. Okay, thank thank you. So that's all that's what I had for that's what the reason I ask for this building my names.

A

Are clear, that's, okay, and if we can continue so if there are other questions we can discuss them. I have maybe another 15 minutes, maybe more if needed,.

A

So, just to finish, questions about mentoring, other any other topics you would like to discuss or clarify.

D

So most of these projects are like java specific projects or it's like a mix of all text tag. It can be a nodejs or anything.

A

uh It depends on the project, so this here would say that the majority of projects are about java, so you can see that there are skills to study and improve and you can find the skills just here.

D

A

You technology, but here jenkins, okay system is around gvm, so basically you can pick whatever gvm language. You would like to use and yeah some projects. They are not studied in java at all, for example, governance is written in golang and there are many other components in different languages.

D

C

C

Yeah is it okay? If I discuss about semantic furthering plug-in for jenkins now yeah, let's discuss that? Okay, so um actually it's more about the proposal on the project, so um first thing that it's still in the draft phase, so that won't be a problem right. I'm asking this again, I know, but that is there and uh I've pasted the link to my proposal in the chat. So if you could please, I have a few questions and they are really you did review it once and I think I've.

C

Updated my document, based on all the reviews from uh you, gareth and sliding um there are some uh comments that uh now that I have to submit this proposal on the gsoft page. What is better that, shall I keep the comments as it is or like remove them or how how it should be.

A

They do not provide strong advice on that, because actually the proposals themselves are still reviewed by the organization, so it will be the same list of mentors.

C

Okay, so I think it's better to keep it that way.

C

Then everyone's aware of the previous funnels.

A

Yeah, so basically what I would recommend there are two approaches. So, firstly summarize uh the discussion in the proposal. So, for example, if you came to an agreement with the mentor or if you process the feedback uh process that edit, for example, some bits in your proposal or maybe if you decided not to follow the suggestion or whatever just documenting, let's say considered options in the bottom and whatever putting it there.

A

Then you can resolve this command because um yeah, basically the discussion was closed and it's addressed in the project proposal. After that there is no need to keep this command, but if you leave it as a kind of open discussion, then yeah. This is a separate topic.

C

Got it so? I agreed with garrett on the comment below and I.

A

C

Needful so, uh like I come in there that I have included over there in the sixth point, and then I can close the discussion is that what you use.

C

C

And um with respect to the deployment part of the plugin, where.

C

um Yeah, so down below there is this stage where I've written sleep. This is page one. So if you go to stage three I've written about deployment parts- and I had a word with sladen- also with respect to deployment- he also says that it is too early to think about it. But what do I write here in the proposal.

A

Okay, so yeah, let's define uh the deployment of what, because we might be talking about jenkins release process, or we might be talking about how you would deploy it in pipeline, because here you say that it's semantic version plugin for jenkins, so my understanding that will always run from within jenkins right all right.

A

Okay, so here you can take a look, write, a junkies file and make the plugin ready to use jenkins.

A

I understand what is this uh path, which is basically a jinx pipeline compatibility, but I'm not sure what is this part.

C

Right, okay, so um I might have heard that wrong what I meant there was like a somehow. I would make the plugin compatible with the pipeline so uh suppose some other project which is using this pipeline and uh this project is more like an add-on thing right. So if you have a project- and you want uh an automated semantic versioning, then you install this plugin. So it should be, uh like you know, fitting inside the pipe a gentleman's pipeline like a job in the jinping's.

A

So basically, it's just junk's pipeline compatibility in the plugin, okay um yeah, so yeah. Maybe I misunderstood but yeah. For me, this part just doesn't provide uh enough context: okay, integrate the plugin in two to nine. If it's used and using this is used there, that's for sure write a github actions workflow to trigger a pipeline to calculate the next release version without explicitly installing uh jenkins plugin or using the cd tool.

A

uh This part is quite interesting because, basically here you say that you would do the same, but without jenkins, do you interpret character.

C

No, but or without jenkins, is uh again a question here but like this is something myself and gareth will discuss that. Okay, if someone or say the conventional comments plug in github, if I commit there or my pr is merged, then a github action workflow would be triggered. Where this will, uh this plugin will run and it can automatically detect the next amount.

A

There are plugins which already provide support for hispanic version and github actions, so my uh interest was to understand what exactly you want to do so because, if it ever loves you is existing plugin for github actions, then probably there is no sense in that. um If it's just whatever integration between github actions and jenkins, then we need to understand what would be this integration because, right now, it's not clear.

C

A

A

So anything else, you would like to ask.

B

Do you still have time yeah yeah so like? Can you just a little bit like tell me about the maven repository like what what are we expecting like whatever I I have? The idea is, I know, like the main initial idea or the inspiration was from the customer package like it. Does that and some of the features we want.

A

So you mean for the installation, manager.

A

What exactly am I so.

A

A

This one should no longer.

A

Line this one is anyone else online.

D

I think he lost connection yeah.

A

Okay, let's uh wait a bit because I'm not sure what exactly we should be discussing right.

A

A

Okay, well, we wait. Are there any other questions.

D

So most of these projects are like uh basically improving the jenkins model or something because what I see is like the architecture which uh jenkins follows say like uh like in my job profile, we use jenkins food to do deployment of various applications, so whatever project says propose here, it's just like something: improving the jenkins model or something.

A

It depends so there are multiple proposals. Some proposals are related integrations with external tools, so, for example, integration with cloud events, um integration with stephon pipe clients with well improvements to linkedin separator parameters monitoring. So these are about integration with external tools.

A

Then uh there are some projects which are related to again new features for jenkins plugins, for example, git credentials, just improving how binding works or working on a custom drinking distribution service, which is a separate project but yeah. It's also a lot to be done there and yeah. That's it. We do not exactly improve jenkins model right now proposals, so we do it. We had some proposals a little bit fast here, uh but yeah right now. It's rather practical changes which would provide some features expect by users or some applications.

A

A

Okay, so yeah in such cases, I think we can slowly close down the meeting and if no one should have any questions, we can follow up or offline in a chat.

A

Okay, so thanks all and I'll stop the recording. So we think that uh please ask any questions in the g subject. Thank you. So.

C