Kyma Prow Migration Work Group, 11 Jan 2019

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Kyma Prow Migration WG meeting 20190111

Description

Meeting notes: https://docs.google.com/document/d/1ljEAoCBJXlxx_ATPyvKZ1KoyFOSIBzEAOkN-2H-HhUY/edit

A

B

Hello: everyone, it's some our last right last meeting of working group, prowl Sleeman can I ask you two to share screen or yeah. Maybe.

A

I would be sharing screen later. Okay,.

B

Okay, so we have only one poll point in our agenda for today and it will be update status from atom. Album stage is yours: okay,.

A

So let me know if you can see screen: yes, okay, so let's have a look on the status of the test, infrared repository. What was changing the previous week and so, as you can see, we are working on the netic cluster so on that cluster, that kasturi's provision once a day and kimye's in start and also stability checker. So stability checker, is a tool from the key map and the purpose of that tool is to execute test in a loop and then send some notifications that contain statistics from the result of that.

A

So we are working on that future. Currently, next we are probably, as you know, we are going to release Kim on Monday, so we are working on the release process and recently we noticed that we need to update names of the jobs because they need to be unique. So we created quite huge and poor request that we updated more than 150 files, and now all our jobs have prefixes.

A

So, for example, if you have job that is running as a present mature for master branch, they predict this prayer, a master and so on and so on- and this was this problem was a detecting when we was doing the release candidate of kima and.

A

Maybe I will give you some update about the the release process, so we released RIS candidate one and currently we are in the process of releasing RIS candidates. Also, and let's go to the Kim, a project Kim MA and on the releases tab, you can see first version that was released by proud. So here you can download, for example, assets in my config glass terrarium from a complete cluster local. As you can see, this is the pre priorities.

A

Also here you have the installation, the in the condition about the installation- and here you have the change lab, which was a generated by prowl jobs.

A

Now, let's have a look on the product West to the camera, because we have this boutique West that is going to create risk candidates, candidates to and and the whole execution of the release was quite smooth, so running jobs for every component for every for every component and then running integration test took in when you sum up, it took only two or three hours right now, we are just waiting for some fixes that needs to be included to the risk can be dated to so I hope that so they will be able to finally release candidate so and let's go back to the prowl, proud bored, as you can see, we have only one epic that is in progress is about I plans for raising kima.

A

As you can see, we have nothing to do here. We keep this epic until we finally release version 2.6 point zero, and then we can close that epic end also close. The whole working group, maybe also on an addition to the released process. So our proud master works already. Really good jobs are really stable, so, for example, in the risk and the data to all jobs passed at the first time, and also this class, the pro cluster scales up quite good, so two to nine nodes, so it was able to handle it without any problems.

A

Okay, so that's basically all from my heart. If you have any questions, I.

B

Think question that change lock release body in a part of it was updated right. Just do we have issue on test infra to somehow generate it or use template to to generate it, or do we plan to even do that.

B

A

Be honest I'm not aware of that issue. Also, as you remember, the purpose of all or group was to migrate by.

C

A

Migrate here- and this is some kind of you know, improvement, but you can also write that ticket so I think it's valid, but it idea to do that. Okay,.

B

Okay, yeah, that would be all from my side.

A

Maybe one more thing: I will show you one requests just to increment that I'm working on providing some a checklist which describe how the release process should look like. So this is in in progress so out there I would say even at the beginning, but I would like to describe step by step. Watch the door. I also create some diagram. That explains which jobs are executed and when so, I hope that quite soon we will have checklist. So the next people responsible for the risk have clear instructions. What to do and one yep.

C

A

Okay, so that's all for my set so.

C

I'm not only doing from you um there's a little updates from my sites and Abdullah is working on this, creating a custom image for our human secretion tests, and hopefully it will be marched today and then I already prepare. The change sets for using that's nearly created, customary custom in which, instead of using the appium and also I edits to the new scripts, I added this watch pot. It was not used before and now it will be a part of human decoration tests as well and after that, it's everything should be.

C

B

Okay, any other comments. I would take that as a no. So thank you very much and that's it.

C