FutureWorkz DevOps Workshop Day III - Gitlab Runner for CD

Transcript

1. Gitlab Runner for CI/CD DevOps Workshop Day III
2. Continuous Integration / Deployment
3. Warm Up What’s the current development process? What’s the current build process? What’s the current deployment process?
4. FutureWorkz Flow - Problems?
5. - Source code version conflicts between SCM servers. - Developers have direct access to production servers. - Difficult deployment errors debugging. Foreseen problems
6. Continuous Integration
8. FutureWorkz revised workflow
9. 1. Automate deployment process. 2. Centralized source code repository: GitLab. 3. Continuous Deployment Toolchain: GitLab CI and Runner. 4. Coder has no access to production server. 5. Coder writes the deployment script. 6. Sysadmin only monitors the servers. 7. Coder writes documentation. Futureworkz CI/CD Workflow
10. Deployment Automation Build and Release will be now triggered when you push to staging/master branch.
11. Single Repository GitLab is the single repository of every project.
12. Gitlab CI and Runners CI monitors the builds. Runners will be executing the builds.
13. Coder no server access - Easy server access management. - Easy project handovers.
14. Deployment Script Coders write the deployment scripts. SysAdmins write the provision scripts.
15. Sysadmin monitor the server And coders manage the development and deployment. - Debug - Request packages installation. - So on.
16. Documentation Documentation is needed for every project. Documentation includes the following info: - Technologies used in that project (database system, background job, etc.) - Test run instruction. - Production environment description. - Environment Variables.
17. GitLab CI and Runner
18. GitLab CI To build, test and deploy your code. - Integrated in GitLab. - Free and open source. - Scalable.
19. GitLab Runner An application which processes builds. Deployed separately and works with GitLab CI through an API.
21. .gitlab-ci.yml Project configuration. Define the set of jobs to be done. Written in YAML.
22. DIY
23. Try Gitlab CI Executing a simple ruby test on CI and get build passed.
24. questions?