• Introduction


• 1. Start CI with versioned public CI docker images


• 2. Start a new product in a mono-repo


• 3. Start CI with local GitLab CI YAML files


• 4. Start scripting with raw commands


• 5. Use workflow:rules and rules


• 6. Abstract duplicated code (without YAML anchors)


• 7. Use artifacts and cache as intended


• 8. Split jobs wisely


• 9. Use needs keyword wisely


• 10. Avoid downstream pipelines


• Conclusion


• Further reading

Introduction

GitLab CI is a powerful tool that has gained significant traction …

abstract best practices cicd code devops docker files gitlab images introduction patterns pipeline practices product public raw rules scripting workflow yaml