domains / families / devops / gitlab-ci-patterns

gitlab-ci-patterns

combined

Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment. Comprehensive GitLab CI/CD pipeline patterns for automated testing, building, and deployment.

When to use

• Create efficient GitLab CI pipelines with proper stage organization, caching, and deployment strategies.
• Automate GitLab-based CI/CD
• Implement multi-stage pipelines
• Configure GitLab Runners
• Deploy to Kubernetes from GitLab
• Implement GitOps workflows

When not to use

• The task is unrelated to gitlab ci patterns
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies are nearly identical, but they disagree on security-critical parameters and one copy adds a 'Template scope' section with constraints the other lacks. Crowning one would hide a real alternative: the rmyndharis copy uses insecure kubectl TLS skipping and password-on-CLI docker login, while the sickn33 copy uses CA-file verification and password-stdin, and sets trivy allow_failure to false instead of true. The sickn33 copy also includes explicit guidance to use verified digests, protected kubeconfig, and to avoid deploying from untrusted merge requests, which the rmyndharis copy does not contain.