Continuous Delivery Foundation cdCon 2021, 6 Jul 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Embrace ChatOps by Following the git-flow as Usual - Rick Zhao, Qingcloud

Description

Embrace ChatOps by Following the git-flow as Usual - Rick Zhao, Qingcloud
Speakers: Rick Zhao
Simplicity matters. It’s not desirable for us to invest in more systems or platforms. The best scenario is to keep our daily work unchanged. For example, software engineers usually spend a lot of time writing codes or documents and also have interactions with various pull requests. Lighthouse is similar to Prow, but it supports multiple git providers. We can speed up delivery no matter if you're using GitHub, Gitlab, or Gitea.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/

A

Hello: everyone thanks for joining my session, embrace shadowhopes by following the git flow. As usual before I get started, I'm going to introduce myself a little bit and with linx foundation, apec evangelist jenkins, contributor, cdf ambassador, a devops software engineer in cooperspeed.

A

I did a lot of contributions in open source community such as deacons and a coopersphere coopersville community focus on cloud native area.

A

Please don't hesitate to contact me if you are interested in.

A

I guess some of you might already know a little bit about the chat ops, but in order to make us on the same page, please let me introduce it a little bit chat. Ops is mostly thought of as using chat tools like slack to communicate and execute scripts and commands.

A

It is very easy to understand it.

A

For example, we don't need to open a platform or system just need to type the command on the chat box, so it can execute the scripts or commands.

A

For example, we can deploy a application on an environment just type the deploy command.

A

It is very convenient, isn't it, but today I'm going to introduce another type of chat. Ups.

A

It is sm webhook based users, can get feedback and chat on issues and progress, and I believe this is the right place for developers to to collaborate with each other, because all developers always need to commit their codes and do the reverb work on github provider such as github.

A

So they don't need to open a new tools.

A

So they don't need to open a new platform or system just use the github as usual,.

A

Bros is a very.

A

Pro is a awesome project comes from kubernetes community. It has a lot of.

A

It has a lot of amazing features.

A

A

This job can be please submit or post submit.

A

In my opinion, submitter equals to pull request. Merge, so play submit, can execute before the pull request gets merged.

A

Pluggable commands with slash foster, so if you want to type a command just type, slash foo, for example, slash look good to me or slash hold it. It is very easy. Fourth configure the policies or processes.

A

This is also very important for us.

A

We don't. We don't need to rely on human beings about the.

A

Github merge automation with batch testing logic. It is very convenient. We don't need always wait. The the pro will program merge your proquest automatically once you're pro.

A

Pro will merge the.

A

Program merge your progress once they are.

A

Proven, what's your progress once they match the.

A

Pro were merged your progress once they matched some particular labels. For example, look good are approved, designed for multi-organ skill with dozens of repository for many teams. They have a lot of repositories even across some orcs, so this is very convenient for a big team.

A

Config updater this plugin or feature can help us to update the configuration of pro it is very convenient. I will tell the details later higher abilities as benefits of running on kubernetes pros components runs as a deployment, so it is very easy to have many replicas and it can have the high ability previous metrics.

A

This kind of feature can help us to monitor the pro instance.

A

Today's main character is lethals.

A

I will have a comparison between pro and the lighthouse flow comes from kubernetes and it can only support github, but let's host can support many different git pro weather.

A

Typically, that host can support all kinds of git providers such as github gitlab, kde, bitbucket and cox.

A

So, as you can see, pro is not friendly integration, but letters can integrate with other system easily and pro is part of the kubernetes test. Infra project and the lighthouse is a imp, independent project. So we can, we can do the contribution easily, but that horse still has some drawback.

A

For example, peru has hundreds of contributors, but the lighthouse only has tons of contributors. Peru has plenty of plugins, and the lighthouse has a few of plugins.

A

But unfortunately, let's host and the pros have the same code base, so it is very easy to reuse the plugins from pro okay next step. Let's ask talk about the installation.

A

It is very easy to install it just need to and just need to add the helm, chat, repo and update. It then install it before we get deep into it. You need to know some key configurations.

A

The first thing is git provider tab. You need to choose one of them, it could be github, gitlab or others, and please provide a get user. On the token, I'd suggest that you to choose a boat account instead of your personal account.

A

It's webhook token. This is important if you want to execution some pipeline job, so you need to choose a engine type, it could be gx. Taktong chickens then provides the public engine connection such as ul, username and token.

A

So, if your resource is ready, then please let me introduce the basic usage.

A

These basic usages are common in lighthouse, firstly, command prefix support all commands, have the prefix lh aka that host or not, for example, you can tap the command, slash, hold or slash lh, thus hold.

A

This is very important, for example, gitlab supports some commands, so conflicts might happen between gitlab and the lighthouse, but the prefix supporter can avoid it. Second active or passive mode.

A

Some plugins were triggered by user. Another were triggered under some conditions. For example, if you have a pull request and has wip prefix, then the plugin will add a wip label automatically.

A

Third, remove effects.

A

Let's say if you find a bug and you can type the command slash, kinda dashboard, it will add a label with candybag, but later you'll find it is not a bar. So you can just remove the label by slash. Remove this kind bug.

A

Okay, I will introduce you some important plugins first is welcome.

A

Every single repository can be customized. You can give a customized sentence to welcome your contributors.

A

You can have a notice for the newcomers to let there know some notice about your repository harp plugin.

A

If you want harps from other contributors, you can just tab, slash help and it will mark current issue needs help hold normally. We hope our progress can be merged automatically, but in some conditions we don't want that. For example, I want might need more manual tests, so I just tap the slash hold command.

A

It will block the automatically merge until I believe my manual test was done, so I can just hold it cell plug-in.

A

This plugin will indicate the size of proquest automatically.

A

It is important for the reviewers to reveal the pull request.

A

Overwrite plugin, sometimes the maintainer might want to force the job states be successful, so you can use this command lifecycle, this plugin commanded issues and the progress left circle.

A

For example, you can close reopen your issues, but you don't need to be author or a maintainer. It is impossible without lighthouse owners plugin. Normally only the committers can commit the changes to your git repository.

A

And sometimes it's on convenience, because you are, you always need to grant the full permission to a user instead of some particular directory. But with this plugin you can have a owner fair to record the all owners.

A

The owners can have the permission on some particular directory trigger plugin.

A

This plugin can trigger a problem with name such as it can trigger an e3 or performance test.

A

Normally e3 or performance test will last a long time, so you don't want to run it a lot configure updater.

A

This is awesome plugin.

A

It can update the configuration as a git of 3 and you don't need to have the permission to control your kubernetes cluster job execution.

A

Let's host support two kinds of popular engine. It could be jenkins or katang.

A

The job could be free, submit or post the submit. Please submit the jobs triggered by user's comment, for example, slash test a name post, the submit triggered once a program to get merged.

A

This is suitable for cost aware job such as e2er performance test.

A

Okay, I want to show you how to add a git repository to your lighthouse. First, you need to grant the main permission to your boat account.

A

Second, add a webhook, the payload url likes this. It ends with hook. Content tab is application, slash json the secret is optional butter. I highly recommend you have it.

A

Then please check send me everything, for example on github, so it will send all kinds of events to your lighthouse.

A

Third, let's host config, you need to add the configuration on plugins cover map. The scope could be org, slash repository or just org.

A

Hands-On this is the last part I will demonstrate how to use that horse on issues, pull requests and update config. Okay, let's assume we have a bug. This is a fake box.

A

So I just need to tap current back.

A

With eater for a second, you can see it. This account add a label current slash bar. So let's assume this is not a bug, so you can remove it.

A

Okay, our both accounts will remove this.

A

Label- and we also can add other labels- I will create a new fair under creator. Proquest new field.

A

You can see the bottom counter has a two commands here.

A

This indicates the pull request is very, very small, extremely small, and if I believe my proquest is still working progress, then I can have this proof. Prefix.

A

You see, it will add, a label do not merge work in progress.

A

This episode, plugin, if I done with this request, I can remove this pre.

A

A

Okay, as you can see here, there is a pending state. It indicates not multiple needs. Three labels approve the label, look good to me label on the right label.

A

I can type this label writing.

A

But please don't forget, I can't use this.

A

As you can see, he now, I just need two labels approved and look good to me, but I don't have the permission to let add the labels I can use another account.

A

Okay, I can type look good to me here. It will add the label.

A

And I also can tap approve. Actually, I also can add this label manually.

A

A

So, just let us read it for a second.

A

This p, this pull request can be emerged later.

A

Okay, that horse theramy should not have needs okay to test the label, because we don't test it yet.

A

So if I want to test data, I can tap e to e.

A

A

As you can see, I get a response. It tells me cannot trigger testing until a trusted user reveals the proquest and the name okay to test message.

A

This because I don't have the permission, so I need to use my another account. I will left this comment. Ok to test.

A

So this commander added, ok to test the label under remove needs, okay to test.

A

Now I can test it, so, as you can see, this proquest was merged automatically. I can't delete this branch.

A

The last part, I will show you the updated configure.

A

And you can say, I have three configure file here.

A

This part it can allow us to update the configuration automatically.

A

Because I have a plugin here, this is my ripple current repo this in this repo. I only have a one plugin config updater, so I'm going to try to test it.

A

Let's assume I make this to 10 and create a new branch.

A

A

So this is a excellent response. It tells me my configuration is invalid. Well, the smaller size is bigger than a large one. So I'm going to change it.

A

Because this return on this is zero, so I can type, for example,.

A

80. again, as you can see, the validation is successful, but we have three commits.

A

Here, how should I do if I want to squash on the merge.

A

You can see here.

A

As you can see here, if I have a label test, slash scratch, then that hose will scratch it. So I can tap here: label ready.

A

A

A

A

Because, let's host don't allow the author to have the approved and look good to me, so I will add it manually.

A

The both accounts are merged automatically. So let's check the merge method.

A

As you can see, let's host just merge and scratch. It.

A

A

Thank you all for listening to my session. This is.

A

Thank you all for.

A

Thank you. Thank you.

A

A

All thank you all.

A

Thank you all for watching my session. You can follow my.

A

You can follow me on the link.

A

You can follow me on the linkedin, twitter or github.