Jenkins Google Summer of Code Office Hours, 26 Jun 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GSoC Office Hours June 26, 2019

Description

Meeting notes: https://docs.google.com/document/d/1H0gJt1zdr37YDpuSLXSeFqYco_a_CIrAuZ1f0Oyl4XE/

A

Okay, we're live welcome everyone. This is the a google Summer of Code office hours for the Jenkins organization on June, 26 2019, and during this meeting we we answer questions from mentors and students with regards to the process and the program.

A

Okay, do we have an agenda for today.

B

We discussed all evaluation plans and expectations that the last meeting.

B

Unless somebody else wants to put anything specific to the agenda, okay,.

C

I was just curious what the feedback was its presentation. Yesterday, I saw justice response about. Even we couldn't join, live all right. The when we did our student presentation yesterday we mentioned that we didn't get any many questions and then I saw Jesse's response, saying you would have been able to make the meetings anyway. So is our expectation for there will be follow-up questions.

B

Well, basically, there is expectation, but again what we did yesterday and today is rather practice session, because yeah we using unity to just try out to the process, and then we will have a real scale Emma during the next evaluation fix. Okay, thank you, yeah. This approach suggest to take you.

B

Obviously, if there are people joining to be here, and if there are questions, it would be nice, the usually there are only few people who ask questions during the DeMars, because the most of SEC whole lives already for the opportunity to ask questions to participate in project discussions. Okay, we still want to use this demo stenotic facilitate the discussions and maybe even most because those projects.

C

B

Of any other questions.

D

I saw have some questions about the alpha release, so I don't know. We had talked about kind of sinking up on this meeting. Trike go ahead with those.

D

Okay: okay, yes,.

A

D

Ahead, okay, so I had notice that, like the first time, I tried the it like released to github, but then it wasn't an artifact turi. So then I redid it, but it I, don't see like a second release and github was I supposed to see one. Let's.

B

Take a look so do see my screen.

D

Let's see yes,.

B

It applies to all projects.

B

Away, you do any kind of releases, so here what we can see, there is one release which is reference tests. Is it a good one alpha one? So there was only one release recorded to github and VA. We can double check what's inside, and so here you can see that there is on the release and after that you can see that yeah. There is preparation to the ladies as one step and another is prepare for next development duration, as a second step, so it looks like I am.

B

D

Ok, so I should just try to release again then yeah.

B

Basically, if you afraid about any issues, so you an alpha freeze, you can basically do whatever you want and yeah we could try to investigate. What's up, we could try it, but yeah best advice is to just burn the release and to have another one on the top of it. So maybe MIT metadata shouldn't be correct. So if you take a look at this project, you can see that now it's here zero that one alpha two snapshot.

B

So theoretically, it should be released correctly now, but yeah you can only try. You see.

D

D

And then, um basically, the next steps after this are once I get that fixed I just need to include like a change log, including like, what's actually in that release. Yeah.

B

It's a common practice regarding change logs. We have multiple standard approaches in Jenkins. One is just putting a change, looks too leaky or to github. So, for example, one of the states a bit okay, for example, we can go to plug-in pump, so here you can see that there is change lock as a markdown file. So this is an old approach which has been heavily used in some components and not even all.

B

The approach is to just put a change Lopes to be here, but they don't really expect new projects to use wiki Havilah we move to github, and recently we had a new flow Portugal, a generation powered by the released router. So if you go here, you can see that there are some releases recorded as it happens. For example, there are a couple of releases with some references to Aquarius, etc, and basically this is the flow which has been just announced a couple of weeks ago.

B

It's a powered by a tool called release drafter, and this release. Rupture is basically just a github vacation which is configured in Europe. Is it correct? Well, configured is probably overstatement because all the information has been retrieved from a global configuration provided by the jinks project, so you're, basically just the right type templates and you can get get regeneration running so, if you're interested in bed. So you can just go to github, and here you can see that there is documentation.

B

How can use it, how to configure it for your repositories and you can start from there in order to just.

B

For the first session.

B

D

Gonna say: I did look a little bit at that yesterday, so I don't have like admin rights for my repository right, because I think there was a note that if you don't have that you have to like submit a ticket, so I just wanted to.

B

Just save it for you.

D

Okay thanks, yes,.

B

Or if you one day it can just publish it yeah. This is published please and it easy it first release for this component and then, when you create new versions. Looking at the real change logs, you can edit this change logs. If needed and the wait. You can also enable the relief structure. So they tell you that automatic change, location.

B

Okay, thanks: okay.

A

Do we have other questions.

A

Abdo d'ye: do you have questions? No, nothing.

D

B

Okay, so there is no questions so yeah in 90 minutes, we'll have a second part of G, so Brahmas just make sure to prepare to them. If you are presenting, if you're not present in your modern, welcome to join in the troop and watch the projects by other students and I guess it will be the last public meeting for the first relation.

B

We also asked all mentors say if you haven't submitted your evaluation late. Yet this lady, please do it as soon as possible. We have shape change logs, sorry, Google Docs for regulation templates and you can use them thanks a lot to all students. All students have already submitted the variation. We are just waiting for few mental teams.

A

Okay, so if that's all I suggest, we adjourn the meeting.

B

Everybody gets more time for podium or.

A

Practicing their presentation.

A

Thank you. Everybody. Okay, I'm gonna, stop the broadcast now. Thank you. Everyone.