Chen @ Cloud Edge Sumit 2020 From DevOps to GitOps with GitLab Cheng Wei Chen 陳 正瑋 DevOps Engineer @ 得寬科技
 《Effective DevOps 中⽂版》譯者、GitLab Hero http://chengweichen.com https://devopstw.club Agenda Automation Ops / Infra 團隊 Provision 圖片來源 https://youtu.be/Usb9iUphT6Y GitOps = IaC + MRs + CI/CD GitLab 說的~ GitOps = IaC + MRs + CI/CD Infrastructure as Code Infrastructure System Configuration Application Commit 檢查 .gitlab-ci.yml GitLab Server 產⽣ CI/CD Pipeline GitLab Runner 執⾏ Job CI Job 回傳 Logs 顯⽰於 Pipeline Terraform Ansible Cloud Vault Repository Cloud Cloud App Infra GitLab Runner

#基于原有的old-tag创建新tag（可用于重命名，生 成新tag后，再删除旧的tag） ★git远程协作开发 远程协作的基本流程： ① 管理员在创建一个空的远程仓库（比如在gitlab上创建一个空的项目） ② 管理员创建一个待推送的本地仓库 ③ 管理员关联本地仓库与远程仓库 ④ 管理员在本地仓库中编辑代码，提交代码 ⑤ 管理员推送本地仓库代码到远程仓库 ⑥ 管理员邀请协作成员 h�ps://gitlab.cof- lee.com/username/RemoteRepoName.git #将本地代码库的当前分支与远程的 代码库相关联，远程库在本地的别名设置为rmtRepo（当前本地分支与远程仓 库的分支名称要保持一致）git用户名及仓库名称要根据实际情况修改，比如： # git remote add rmtRepo h�ps://gitlab.cof-lee rm rmtRepo #删除远程仓库 ★协作成员操作⑦到⑨，详见下一小节：克隆远程仓库 ★克隆远程仓库 # git clone h�ps://gitlab.cof-lee.com/cof/pro-1.git #克隆远程仓库到本地，默认 克隆的是远程的默认分支，本例中远程仓库默认分支为main（克隆后会自动在 当前目录下生成项目目录） # cd

interface. You can do this in the Add host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre later to use VCS to store the translations, itʼs already within Weblate and you can base on that. GitLab New in version 3.9. This just adds a thin layer on top of Git to allow pushing translation changes directly to the repository, while GitLab creates merge request. Pushing changes to GitLab as merge request If you are translating a project that is hosted on GitLab and donʼt want to push translations

key, from the same section of the admin interface. Enter the hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the to store the translations, you already have a repo within Weblate can base your integration on. GitLab New in version 3.9. This just adds a thin layer atop Git using the lab [https://github.com/zaquestion/lab] pushed directly to the repository, while GitLab creates merge request. Pushing changes to GitLab as merge requests If not wanting to push translations to a GitLab repository, they can be sent as either

key, from the same section of the admin interface. Enter the hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the to store the translations, you already have a repo within Weblate can base your integration on. GitLab New in version 3.9. This just adds a thin layer atop Git using the lab [https://github.com/zaquestion/lab] pushed directly to the repository, while GitLab creates merge request. Pushing changes to GitLab as merge requests If not wanting to push translations to a GitLab repository, they can be sent as either

interface. You can do this in the Add host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre later to use VCS to store the translations, itʼs already within Weblate and you can base on that. GitLab New in version 3.9. This just adds a thin layer on top of Git to allow pushing translation changes directly to the repository, while GitLab creates merge request. Pushing changes to GitLab as merge request If you are translating a project that is hosted on GitLab and donʼt want to push translations

key, from the same section of the admin interface. Enter the hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the to store the translations, you already have a repo within Weblate can base your integration on. GitLab New in version 3.9. This just adds a thin layer atop Git using the lab [https://github.com/zaquestion/lab] pushed directly to the repository, while GitLab creates merge request. Pushing changes to GitLab as merge requests If not wanting to push translations to a GitLab repository, they can be sent as either

interface. You can do this in the Add host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre later to use VCS to store the translations, itʼs already within Weblate and you can base on that. GitLab New in version 3.9. This just adds a thin layer on top of Git to allow pushing translation changes directly to the repository, while GitLab creates merge request. Pushing changes to GitLab as merge request If you are translating a project that is hosted on GitLab and donʼt want to push translations

key, from the same section of the admin interface. Enter the hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the to store the translations, you already have a repo within Weblate can base your integration on. GitLab New in version 3.9. This just adds a thin layer atop Git using the lab [https://github.com/zaquestion/lab] pushed directly to the repository, while GitLab creates merge request. Pushing changes to GitLab as merge requests If not wanting to push translations to a GitLab repository, they can be sent as either

interface. You can do this in the Add host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre later to use VCS to store the translations, itʼs already within Weblate and you can base on that. GitLab New in version 3.9. This just adds a thin layer on top of Git to allow pushing translation changes directly to the repository, while GitLab creates merge request. Pushing changes to GitLab as merge request If you are translating a project that is hosted on GitLab and donʼt want to push translations