Jenkins Documentation Office Hours, 5 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2020 10 05 GSoD Office Hours

Description

Google Season of Docs office hours for Oct 5, 2020 in the Jenkins on Kubernetes project

A

And share my screen thanks. Everyone welcome to uh google season of docs mentoring. It's the office hours thanks very much. Here's what we've got for an agenda today. Can everybody see my screen already.

A

B

A

All right so um see, I assume we want to add pull request review as a topic. I apologize enough. I have not made any progress on it. The weekend was spent testing, jenkins, 2.249.2 and other topics.

A

Do you want to talk about incremental delivery of segments further.

C

A

Okay and transfer of organizing, I think, continues as a topic all right. Any other topics you should put on the agenda.

B

Also I'd like to ask maki, if there's any updates on the issue, I was having with user group.

A

Okay, oh okay, so I have another one. I guess. um Should we have a helm chart session with porcelain walter now that he's back.

A

Let's just think of an open question for the agenda: okay and uh any other topics to put on the agenda.

A

All right, then, let's work through the agenda, pull requests ready for review so again xena my apologies. I have not reviewed it. I hope to review it today or tomorrow. So sorry that I didn't get to it yet uh marky did you have anything you'd like to report there.

D

I know that there's there's two pr's in am I correct xenobl.

B

D

Yeah I reviewed one of them. I have not reviewed the second one. I will have that done today.

B

Okay, um I also like to ask some- I forgot to add that to the agenda I'd like to ask some questions regarding the structure of documentation. That's.

B

E

That, when I was wondering if it was supposed to be like delivered first, because it was talking about like being a framework versus the second or the first pr that was submitted, which was the installation guide um right.

A

Okay, so would you like me to open up the pr? Is that that this one, the skeleton.

D

B

I have a google doc here. I think it would be easier to be easier to use um the google doc for instructor to explain.

A

Would you like to take a comment? Yeah I've just stopped sharing. If you go ahead and share your screen, we can take a look at the google doc.

B

Okay, um can you see my screen? Yes, okay, so um I don't know if you remember this, google doc, um when I started working on installing jenkins on kubernetes. I created this to show the section where I'll be adding it on jenkins.iwo.

B

So I added additional content to this doc. That's what is in that cool request I opened so um for administering. These are the um initial topics we talked about, so what I did basically was to pick out um sections from this um proposed content and fix them into jenkins, dot io.

B

So um for administering jenkins on kubernetes- I I don't know if this is okay, I put it on the system administration. um Let me open jenkins.I.

B

B

A

ah There we go okay, now, I'm seeing it so the idea was to put it here at immediately below system. Administration is administering jenkins on.

A

A

See now, I'm afraid we're I'm not hearing your your comments or maybe others are hearing it and I'm not.

A

Marky christian, are you hearing.

D

No, I'm not hearing anything okay.

A

All right so so we may have just lost her audio, so, while she's getting back to audio any of oh okay, I assume she's reconnecting any objections from the two of you on on that approach, putting system administration for kubernetes inside the system, admin section, I don't see a problem with that.

E

I mean right otherwise you're more consistent, because if that's where you're going for assistant administration to answer those particular questions, maybe it'd make more sense to put it there anyway,.

A

So the the other alternative that was on my mind that I don't have a strong opinion one way or the other is, should that that hello, oh hello, xena, you're, back great.

B

E

B

B

um As I was saying, I don't know if it would be okay here.

B

E

Well, no, I think she disappeared.

A

I think we may have lost her again: yeah yep she's she's dropped out of the participant list completely.

A

So the the other thought was just like: we have a using a managing jenkins chapter and a system administration chapter and a scaling jenkins chapter conceptually. We could have a jenkins on kubernetes chapter, but for me my personal, I think somewhat preference was put the content inside system admin and inside installing for kubernetes, rather than having a separate top level thing for kubernetes.

D

I'm in favor of that, okay, all right.

E

I guess for me whatever would just be consistent with how we have it for other groups. That's what.

A

I think right and and others others, for instance, the docker install directions, are inside the install the instructions on how to manage uh pieces in docker are inside the system. Administration get chapter. If I remember correctly, see now you're back.

B

Yes, my network is kind of bad this evening. Sorry.

A

So we were just described discussing, I think your question was: should we use put put the system administration, related content in the system, administration chapter or somehow put it at a top level entry? Is that your question.

C

A

And- and I think the the consensus was that putting it inside the system, administration chapter sounds really good to us. What does that feel? Does that seem sensible to you and does that fit with how you'd like it to evolve?.

B

Yes, actually that's um what I did currently the pull request. I opened that's where I actually put it, but I just wanted to confirm.

A

Excellent, very good, so so we can review that pull request, as is, and it's using that structure already.

B

A

Yes, very good, okay, so that makes me even more guilty for not having reviewed it. Excellent good.

B

Okay, no, so um that's the second pull request. The one you've not reviewed the first one, the first one just has content of this quality. I've opened another request, as I mentioned in the last minute,.

D

B

Okay, also for cloud providers um in the content on jenkinson. I didn't really see um something relating to cloud. I don't know so.

B

I just created a different section for jenkins on kubernetes and put it on that. But I don't I'm not adding that to the pull request. I don't know if that's okay or if they don't become information from cloud providers.

A

So I'm not sure I'm understanding the question: is it that okay.

B

um Let me share my screen again.

B

um Can you see my screen? Yes, okay, so for this information here um cloud providers that are setting up cicd pipeline and all that sweet aka. So I was saying on jenkins.io um I didn't see any existing section where um this cloud provider information will fit in. I don't accept if I missed it, so I'm proposing creating a jenkins on kubernetes session, I'm putting cloud providers on diets except if there's a better auction, but I'm not sure.

A

Okay, so so, then the for me cloud providers would be a system administration attribute, um so I would have expected to be under system administration, but I'm okay with it top level as well. The is yours, I'm I'm impressed that we've got anything to say right now about the cloud providers.

A

I thought that the things that you had later in the document were just links to the documents that are provided by the cloud providers themselves on how to use jenkins in their cloud.

B

um Yes, so I've not um written on the cloud providers yet, but since um we spoke about the skeleton of the whole documentation, so I just told you guys to just um take the whole the content as a whole. Then subsequently we build um the content under each section.

A

That makes sense. Okay, thank you. So this is. This is.

D

As far as the placement of cloud providers, I I mean, I think it can either go top level or in the system administration. I don't have a hard.

A

Preference yeah so that that's that's that's where you've placed it is fine, so it's and and the that is a skeleton. That's a placeholder and you'll populate it as we as we get more information or we might offer the cloud providers. Hey. Google, if you would like this, is the place where you put your material, and this is good. I, like that. Okay.

B

Okay, so um I think that's all the question I have on the skeleton I'll just updates the pull requests.

A

Discussions great all right.

A

Okay, so then the I think that answers the topic we had on incremental delivery into larger structure. You've proposed a pull request representing the larger structure. Yes topic, then, was the user group issue and more conversation and.

A

Discussion marky. I think that one was where you had done. Some user group investigation.

D

I'm sorry I was multitasking. Can you repeat that.

A

Yeah so so there was a a question that I think you and cenap were investigating last week relative to something.

D

Yeah, so this is the this is the run as uh and when zenob runs it as zero. Everything works because that's considered root when she runs it as 1000. It is running into a permissions error. I tried this locally and when I switched the port numbers, I think it was between.

D

I can't remember it was like 10 24 and 10 20. Maybe uh I got it to work now when you switch the port, z knob, you still have the same problem.

B

D

Okay, keep that on my app keep that on the list of my action items, I'm going to do some more looking into it.

A

Okay now see now is this: is this blocking your progress or you're able to work around it and continue? Yes,.

B

I've I've found a workaround for it. It's not. I just um wanted to see. If there's um something probably a step, I missed or something so I can update documentation.

B

In case that someone else that faces the kind of issue, but I think.

D

D

I think for now just operate uh on using xero.

B

Yes, I've gone past that I'm good for now: okay, yeah.

A

All right, excellent, thank you. Next topic was that a possible helm chart session with torsten walter. Now that he's back back from vacation, I guess the question is: is to using up. Are you interested in a session with torsten, or was the helm chart session that that marquee provided already sufficient and an additional session with torsten won't help? You.

B

Much well, um the special marquee was really helpful, but I don't think it's hard to have another session with.

A

Justin great, so um how about? Let's see, though the last time we we attempted that I tried to schedule a time that worked for my schedule and completely failed. Do you want to reach out to torsten and ask him because you- and he are both in relatively nearby time zones he's in germany you're in in nigeria, and so you may more easily be able to find a time that works for the two of you.

B

Okay, I'll do that.

A

And if, if you need access to the uh the zoom account or if you need me or someone else to host it during during an odd time, just let us know.

D

Yeah you can, you can either bring myself or or mark. I think both of us have access.

B

A

You all right next topic was transfer of org admin mark anything you want to report there.

D

This is still, this is still open. I know oleg said he will take care of it this week.

A

Great okay- and I have one more item that I forgot to put on the agenda: I'm going to be out of the office uh thursday and next monday, I'm going to go play with my grandchildren.

A

Nice, it is nice. Grandchildren are the best. They are absolutely the best.

E

I'll have fun.

A

There's nothing better than playing with grandchildren, nothing, but that means marky. Will you be available to run this session marky through the the cdf zoom account yep, okay, great and likewise for next monday? Yes, I can excellent. Thank you very much, sorry for my being out, but I'm actually not that sorry.

D

Because I get to play.

A

With my grandchildren.

D

Yeah, don't apologize at all all right.

A

Any other topics we should.

B

B

That's all for me.

F

All right, thanks, recording, will be, will be posted about an hour from now thanks everybody.

E

F

Have a good evening, good day, all.