Jenkins Documentation Office Hours, 28 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2020 09 28 GSoD Office Hours

Description

Google Season of Docs office hours for the Jenkins on Kubernetes documentation project with Zainab Abubakar as technical writer. Topics included a diagnosis session for a RunAsUser failure.

A

This is google season of docs office hours, the 28th of september 2020.. Thanks for being here, I'm going to share my screen and we can look at the proposed.

A

Agenda there we go so you should see right now. I think the agenda is empty other than who we've got attending so draft google docs seems like a proper topic. Are there other topics? We should add to the.

A

A

All I could ask about incremental delivery of.

A

Parts into segments, a larger structure.

B

Oh, I do have a topic to add as well right mark, and this is the transfer of.

B

Org admin for google summer of docs. I have an update for that. ah Oh good, okay,.

A

Excellent thanks.

A

I don't hear any other topics so shall we go ahead.

C

um I think we should um add a topic on the issue I raised last um at the last meeting. Mikey was not around so yeah.

A

Oh, oh, the service account issue is that is that this one's you know.

D

A

Okay, good, so I'm sorry, I I mistakenly thought we had that result. My mistake, let's I would propose we put that one top of the list, because that was one we had agreed. We would we would cover today, if it wasn't resolved by today,.

C

A

A

All right so so then, let's take this one as the first topic um xenapp. Could you describe the problem you saw and you may need to share your screen if we get to that point.

C

um Yes, I can share my screen now.

A

Great, let me stop sharing okay.

B

A

Okay, it says that it started screen sharing, not quite visible yet.

B

A

ah There we go now. I see it. Nice ide, a visual studio code, maybe.

C

C

um Hope it's clear, clean enough.

B

I can see it.

C

Okay, um so this is where I'm having issues this part, so the default value. This is um my jenkins value file. Dot yam file got this from um jenkins, helm, charts requisitory on github, so um the default value that is there, is 1 000. But when I um create this using 1000- and I run I'm not able to the port keeps crashing, I'm not able to do anything on jenkins. It's I'm having some permissions issue and I'm not really sure how to resolve that.

C

I can't exact into the pod, because it's it's not starting, so I'm not really sure how to resolve the issue with um the permissions. If I use, if I run as user 1000, but when I run a zero, it works, but using zero means, I'm running jenkins as roots, and I wouldn't want to do that. So I just did this, so I can just um get jenkins or so I can continue with the documentation, and this doesn't block me from documenting other parts, but I would like to have this stage result.

C

So um I'm guessing, like christie mentioned um in the last meeting, I'm guessing. I missed this step in the installation, but I'm not sure what that is. So that's the problem, I'm having.

B

Give me just a second: I am just taking a note.

C

B

And this is the official jenkins helm chart.

B

B

So just so I'm clear you're saying when you run it as user 1000, it does not work.

C

A

Is that I didn't think to ask you on friday know: is the fs group also need to be one thousand? I I'm not sure what yeah.

C

A

Okay, so you make them.

C

A

C

Yes, both came both are one thousand by default, so I change the both of them to zero.

B

Is there do you currently have an example of where the pod is crashing, that you're able to show us that we could maybe debug live.

C

Okay, um I'll do screenshots and and send to you.

B

Yeah, you can send it to me directly.

C

B

The the command that I'm looking for and I'm gonna put it in the chat for zoom here- is.

B

Give me just a moment, while I type it.

B

This is in the jenkins, namespace, correct.

C

B

Okay, that's one! I am gonna need another one. As.

B

B

hmm The sky pod.

B

Can you scroll up on your jenkinsvalues.yaml scroll to line.

B

One can you scroll down a little past, the base64 encode. I want to see the lines right after.

B

B

And scroll down about 10, more lines.

B

Stop right there.

B

And you put the service account in that we discussed last week correct yes,.

C

B

Can you show me that, uh can you show me that yammer.

C

B

I don't see it yet. I still just see your open file window.

C

Okay, this is it.

B

Can you scroll down.

B

Keep going, I just want to see the cluster role.

B

B

Scroll back up to the cluster uh cluster role, I want to just see what verbs are in there. Stateful set pods logs exact okay go down just a little, so I can see the.

B

B

Wow- okay- that's really weird! I'm gonna have to look into that because this should, by just my initial, looks at it. This should actually work.

B

uh So let me let me look into that and I will get you an update.

C

Okay, I'll also do the screenshots and send to you to give more.

B

Content yeah that'll be great. Thank you very much.

C

B

So you can put that as an action item for me mark on the list. If you'd like.

A

Okay, here we go sharing my screen again and.

A

Okay, so so give me it was.

A

Aren't key to attempt to duplicate the.

B

Problem is that mars, marquee uh marquee to it uh debug run as user.

B

B

I'll start, looking into that, once we're done with this.

A

Call excellent thanks: okay,.

A

Anything else on that topic then,.

C

A

Okay, great thank you so then the draft google doc for installing jenkins on kubernetes and just a minute while I grab a copy of that link to that doc there. It is.

A

All right so is he not, I think, you've seen kristen's feedback. Yes, a couple of minor items.

C

B

I'm going to be reviewing that it's on my list of to do this morning. Okay,.

A

And mark yours is a credible review. Mine is the review of an amateur, so much appreciated. I started I started executing the steps bumped into something that I didn't quite understand. What the failure mode was and have to do some more exploring yeah I'll. Take a look.

B

At it, that's it's on my list.

B

A

And did you have any specific topics you wanted to bring to us with regard to it zeno anything in detail where you say I'd like to talk about this or this.

C

A

I didn't get that anything about the installing jenkins on kubernetes document that you would like to review with us specifically, while we're on the call.

C

um Not really um the only discussion that I've also have is um there's some comments. Christine dropped about the structure of um the documentation, and I understood what she was saying, but um I also structured it. This way with um the location is going to be in in jenkins, the iowa since there's already a heading installing um jenkins in jenkins dot io.

C

So this is just going to be like a section of that page.

A

Right, okay, so I think her concern is addressed by exactly what you said. So that's very good, because you're going to integrate it into this page for installing is that correct.

C

Yes, exactly so it's going to be um under the installation, part from kubernetes.

A

Yeah so just like we have a docker section. Today we will have a. We will have a kubernetes section. That is part of this broader document.

C

Yes, so, under the kubernetes session, we're now going to have different options for installing um jenkins on kubernetes.

A

Got it okay, so that makes sense. I'm gonna just embed a copy of that into the link good, very good.

A

Okay- and I had one on this- just capitalization, because linux users, like me, have a case sensitive set of commands.

B

A

Good any other questions or topic.

C

No none for now. Okay,.

A

All right, then, oleg had raised a question about incremental delivery of segments into a larger structure. Does he now? um What are your thoughts on that? Do you see how it could work, etc?.

C

I I don't really understand what this, what this means.

A

I think oleg's intent was that there's a a framework or an outline form of the final document.

C

Okay, like um a skeleton or something.

A

Yes, yes, skeleton, that's a good yeah, that's a very good word for it and and and then pieces are added in faster, smaller steps or more frequent.

A

Smaller steps to the to the to the skeleton yeah.

C

Okay, um so my question here will be that um this skeleton are we going to create it on jenkins, dot, io and push it their posts and start um adding the content later on, or it's just for us to use it as a guideline as the documentation goes forward and then also the skeleton? Is it going to be um in relation to what we have on jenkins.I or just the content we are adding to it.

A

Yeah good question, so my my my thought was add the skeleton to jenkins at io uh if you're uncomfortable with it being visible, make it as conte as comments commented, sections has commented a doc, so the famous four slashes creates a starts. A block comment and four slashes ends. The block comment.

C

A

So you could, you could do it. That way would be one alternative. That would let you have a place to put things without displaying empty headings to readers during the period while it's developing, you could also. We have plenty of places where we have empty headers as well.

C

Okay, um I don't know if it's possible to get like an example, so I can understand.

A

uh Yeah good question: let's see marky, are there any places you can think of where we might already have an example that we could use to highlight this.

A

I don't know of know of any off offhand myself, but we might be able to find some.

B

Yeah, I can't think of any.

A

We certainly got plenty. We've got many places where the the the content says. This is a work in progress, so um maybe that's what we should get as examples and say: look: here's here's! How we've we've got this this section of material that is identified as a work in progress. Here's how it was done.

A

Actually, maybe let's, while we're here, maybe we can avoid that leaving the action open you, okay, if I just look really quickly for for as a sample.

A

So if I recall correctly, system administration was a pretty common place to have yeah so, okay, so here's here's one example: backing up and restoring jenkins says right now that it's a work in progress but and monitoring jenkins, also says it's under development and security yeah good. So these these pages give us some indicator of hey, there's they're part of a bigger section, but they say look. This is under. This is under development.

C

A

Okay, so does that? Does that help you z, yeah, that's sufficient.

C

Yes, it does okay. So um as regards this, I think what I'll do is just um go through all the contents. We've agreed to work on for the documentation and see the sections in jenkins or iowa, where we can add them or open a pull request. So everyone can review.

A

That sounds good to.

A

Let me get this. That sounds very good.

C

Okay, so um for installing jenkins on kubernetes, since I already have some content on that I'll just include that in the pull request. So that section is not empty.

A

Right right, that sounds really.

B

A

So anything else on the the incremental delivery idea that any other clarification you'd like to request. You know.

C

No, it's it's plenty. Okay,.

A

uh Transfer organization admin from oleg tamarki marky.

B

Yes, I talked with oleg uh yesterday or today I can't remember which day it was and he it is on his list to do uh so. Hopefully, he'll be doing that within the next day or so.

A

That's something he has to initiate. Certainly it's nothing that they would accept. You saying I want to be the new org admin. Take him off.

B

He just has to list me as one and then we'll remove him as the third and then there'll just be two. Oh all right.

A

Great all right, any other.

D

A

Okay, so I assume our one of our goals for the next session thursday is we'll see a pull request, ready for, based on the the install material that you've done. That's cool, yeah, excellent thanks, very much xena. Thank you. Marky.

C

B

Thank you all have.