Jenkins Documentation Office Hours, 1 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2020 10 01 GSoD Office Hours

Description

Jenkins Google Season of Docs office hours Oct 1, 2020

A

All right welcome everyone. This is october, the first it's google season of doc's office hours. Let's take a look at our our notes.

A

Excuse that kristen today she's out of the office on vacation, so we've got a topic for the the draft. Google doc pull request, ready for review, incremental delivery of segments into a larger structure and transfer of org admin. Should all those remain on the agenda. Anything we need to add.

B

uh For org admin remain, it's uh still an open item. I know it is on oleg's to-do list.

A

All right, then, let's go ahead and start from the top xenon. How about on installing jenkins? You want to tell us how it's going and let's, let's discuss that.

C

Okay, so um for installing jenkins, I worked on two different options: that's using helm, um the first part just actually explains gives a brief introduction of kubernetes. After that, I gave two options: that's using him and just using um some yaml files that deployment file and the service file for those that might not want to use helm. So those are the two options I currently have right now on installing jenkins on kubernetes and then marcus suggested, adding um a bit of explanation about on clusterrule, binding and clustering.

C

I did that so I'm not sure if anyone has had the chance to review yet.

B

I did look that over and I think that is perfect. We can mark that as completed.

A

So that's this one right here: okay, great.

A

Excellent well done anything else. You know.

C

um No for now I'm working on the jenkins operator.

A

So the helm section is complete, and now is that included in the pull request.

C

A

And you're working on kubernetes operator, yes, marquee, helped me with that. What's the official is it jenkins operator for kubernetes jenkins kubernetes operator thanks.

C

And also I wanted to ask for the jenkins kubernetes operator. Would it be better to have it under the managing jenkins session or under a new jenkins on kubernetes section.

B

Can you remind me how you're doing the helm section is that a separate section or is that under manage.

C

The helm section is under installing jenkins.

A

B

Kubernetes operator also an installation option or have I misunderstood, because that's why I was asking now. The reason is, is I think, if you, if, if I recall correctly from the code, it is installing jenkins, and if that is the case, then it should go under installing jenkins. That's just my opinion.

A

Okay, which even even puts even more emphasis then on your your concern. Z knob about g is the is the installing jenkins page going to be just too huge and yes, we'll have to. It seems like we'll, have to re rework it so that it presents subsections, but I'm still of the opinion. We don't want you to do that, because there are lots of us who could do that and let you keep working on specifics.

C

A

Now are there are there in your experience with jenkins kubernetes operator? Are there things that are done with it during run time, where it's it's also an administrative tool, or is it mostly an installation tool?

A

Was that question for me uh either of you? I guess.

B

I don't want to interrupt xenops so gina. Do you want to answer it? If not, I can.

C

No, I think, maki. I would like you to help in answering that.

B

Yeah, so the jenkins operator does two things number one is it it will? Do your installation number two, it will do administration of various things.

A

ah Okay, and now is that different than helm can I use helm to administer as well or.

B

No you helm is a different way of doing things. uh uh The jenkins operator is another way of doing things it just has more to it. Okay got it all right. Thank you.

A

Hang on just a minute, I need to go close, my door. I fear the sound is going to bother.

A

Okay, thanks thanks for the clarity, excuse my getting a kubernetes education while, while we're doing this, no that's, okay, totally. Okay, all right.

C

So we'll both the installing um installation of jenkins and an administration part, thus on jenkins humanities operator, will both of them be on the same page, just installing jenkins page.

B

That's a good question, I think, for clarity in the use of the operator. They should just remain on the same page or, if there's a possibility to break out that page into uh you know. Maybe you know installing jenkins, and then you have the the the operator is a you know, that's an entry, but maybe we break it off or becomes now another sub entry about the administrative administration part.

B

But I think that's you know it's just an it's an option or if you put it somewhere else, you could, you know, have have some type of uh in an ascii doc linking to the other area where it talks about operator administration. That's another option as well.

C

A

Yeah, my yeah, my preference would be limit the administration, so I think of install as in as the first administrative operation, but then future administrative operations- they go elsewhere to answer them, but would that work? If you said hey, I'm going to do the install portion of jenkins kubernetes operator in installing and all the admin functions I'll put elsewhere, or is that going to make your writing very difficult? You know.

C

No, it's not going to make it difficult, so I think um after the installation section I could just do probably like a brief introduction and put a link to where the administration is properly explained.

C

Okay, so all the information is not on the installing jenkins page.

A

And I think that's a good idea. Yes, that was one from our landmark great.

A

I I like that very much that way. We know that the installing page is going to be huge and we'll split it the or it will be split, not not by you, but it will be split, the still the admin material there. I assume that the jenkins kubernetes operator has lots of admin, things that are unrelated to installation and more about configuration or modifying setup. That is.

A

Correct all right see now back to you.

C

C

I think also for me, or did you ask a question.

A

No, no just are there more things you wanted to discuss with us on installing jenkins on kubernetes, for the install version.

C

A

So the next topic was pull request ready for review. Congratulations! So the pr is there.

A

And uh I'll do my best to review it, it may be a day or more before I get all the way to it, but I will do my best to have it done before before sure. Before our monday meeting.

B

A

B

Reviewed by my review will be in by today great.

C

C

So I've I've basically moved um all the content from the google doc to the pull request. So you don't have to review both the google doc and the pull request. You can just review everything in pin request.

A

Thanks very much.

A

Anything else on the pull request.

A

No okay, we add another topic: incremental delivery of segments into a larger structure.

C

Yes, so about the structure, um you know, I suggested a pull request where we add sections and puts work in progress, but I didn't want to merge everything in a single pull request.

C

That was why I didn't add that to this pull request, so I'll do a diff different um pull request just for the structure alone, so this is not too clumsy or confusing.

A

Great okay and that that sounds good to me uh that separate pull request because we can get different conversations going already get the benefit of the install material, merging and being the users while you're still working through hey here are the other things to do on this. On this structural core request, I like that marquee is that okay, for you perfectly fine.

A

All right so then the goal is, I assume as soon as you get that submitted, we want to get a review of that and then discuss discuss at the next meeting.

C

A

Good, okay, anything else on the structure, full request.

C

A

Marky you want to take that last topic.

B

Transfer of org admin yeah, we are still uh waiting uh not only for the transfer of the org admin, but also to be added on as a mentor and that's not by any fault. I know that uh oleg is: it's got a lot going on, so I will ping him ping him about it before the week is out great yeah.

A

And, and that is a mentor and as an org admin, correct, excellent.

A

Anything else that we need to any other topics that have come to mind or that we need to discuss.

B

uh There is no topic, but I would like to say: uh cnop you're doing an amazing job.

C

Thank you so much.

A

And- and I I echo that zenov I'm delighted, thank you for your contribution. Thank you very much. uh If you haven't registered for hacktoberfest by all means you should, this is certainly a contribution to open source. So congratulations. That's wonderful!.

C

Thank you so much, and thank you for being amazing mentors. Also thank you mikey. Thank you mark for the help.

A

Thank you easy.

A

It is. It's delightful thanks, a bunch. I think that covered all of our topics for today is there anything else we need to discuss before we close our session.

C

Nothing from anything else from me.

A

All right, thank you. So good luck, reviewing pull requests! We'll talk to you. Talk to you in the next meeting. Awesome have a good day.