Refine your ci:cd pipeline with automated test
0 likes373 views
The document discusses CI/CD practices, explaining continuous integration (CI), continuous delivery (CD), and continuous deployment as methods for automating code integration, testing, and deployment. It highlights GitLab as a comprehensive DevOps platform that streamlines software release processes using tools like GitLab Runner and pipelines defined in .gitlab-ci.yml. The focus is on improving efficiency and reducing the time spent on toolchains in software development.
Refine your ci:cd pipeline with automated test
- 1. CI/CD
- 2. Aditya Rahman Universitas Negeri Malang (UM), Komunitas GNU/Linux Malang (KLiM) mail: aditya@klim.or.id telegram: @kudaliar032 gitlab: https://gitlab.com/kudaliar032
- 3. CI Continuous Integration is the practice of integrating code into a shared repository and building/testing each change automatically, as early as possible usually several times a day. CD Continuous Delivery adds that the software can be released to production at any time, often by automatically pushing changes to a staging system. Continuous Deployment goes further and pushes changes to production automatically. CI/CD?
- 6. CI/CD Tools
- 7. GitLab? “GitLab is a complete DevOps platform. Spend less time on your toolchain and more time on what matters: releasing great software.” https://about.gitlab.com
- 8. GitLab Runner is the open source project that is used to run your jobs and send the results back to GitLab. GitLab Runner
- 9. ● Jobs that define what to run. For example, code compilation or test runs. ● Stages that define when and how to run. For example, that tests run only after code compilation. GitLab Pipelines
- 13. Thx...