cicd-tooling-skills

Plugin cicd-tooling-skills from marketplace ops-engineering-skills in selvarajmurugesan90/ops-engineering-skills. Commands read from the repo's manifest — 1 month ago.

Skills (13)

• aws-codepipeline-and-codedeploy

  Designs AWS CodePipeline stage/action structure and integrates it with CodeDeploy deployment groups and appspec.yml for EC2/on-prem, ECS, or Lambda deploys. Use when the user asks to "set up CodePipeline," "add a CodeDeploy deployment group," "write an appspec.yml," "wire CodePipeline to CodeDeploy,

• azure-pipelines-yaml-and-multi-stage

  Designs Azure Pipelines YAML (azure-pipelines.yml), multi-stage pipelines with environments/approvals, templates for reuse across repos, and self-hosted vs. Microsoft-hosted agent pools. Use when the user asks to "set up Azure Pipelines," "write an azure-pipelines.yml," "add a multi-stage pipeline w

• bamboo-pipeline-yaml-and-java-specs

  Authors Atlassian Bamboo pipeline definitions using either Bamboo Specs (Java DSL, compiled and run to create/update a plan) or Bamboo's YAML specs format, covering plan/job/stage structure and how a Specs definition links to and updates a live Bamboo plan. Use when the user asks to "write a Bamboo

• complete-cicd-pipeline-deployment-for-kubernetes-from-scratch

  Builds a complete CI/CD pipeline for a Kubernetes-targeted service from an empty repo — source checkout, container image build, SCA/SAST security gates, registry push, and a deploy step that ends at a GitOps handoff (committing a new image tag to a manifests repo) rather than a direct kubectl apply

• complete-cicd-pipeline-deployment-for-serverless-from-scratch

  Builds a complete CI/CD pipeline for a serverless (AWS Lambda-style) function from an empty repo — source checkout, zip/layer packaging (not a container image), SCA/SAST security gates, package upload, and a SAM/Serverless-Framework/CDK-style deploy step with alias-based canary traffic shifting, dis

• complete-cicd-pipeline-for-vm-based-workloads-from-scratch

  Builds a complete CI/CD pipeline for a VM-based workload from an empty repo — source checkout, build, immutable machine-image baking (Packer-style AMI, not a container image or a zip), SCA/SAST security gates, and a deploy step that's either a blue-green instance-group swap or a config-management pu

• gitea-actions-and-ci

  Configures Gitea Actions — Gitea's GitHub Actions-compatible CI/CD runner — including self-hosted act_runner setup/registration and the specific differences from GitHub Actions (supported contexts, missing features, runner labels). Use when the user asks to "set up CI on Gitea," "configure Gitea Act

• github-actions-centralized-reusable-workflows

  Designs organization-level reusable GitHub Actions workflows (workflow_call) and shared composite actions hosted in a dedicated repo, so many repos call one standardized pipeline definition instead of duplicating workflow YAML. Use when the user asks to "centralize our GitHub Actions workflows," "cr

• github-actions-single-repo-workflows

  Authors and troubleshoots GitHub Actions workflow YAML that lives in and serves a single repository — triggers, jobs/steps, matrix builds, caching with actions/cache, and composite actions defined within the same repo under .github/actions/. Use when the user asks to "write a GitHub Actions workflow

• gitlab-cicd-pipeline-design

  Authors and troubleshoots .gitlab-ci.yml pipelines — stages, the modern rules: syntax (and legacy only/except), includes for shared templates, and GitLab-specific runner/executor configuration. Use when the user asks to "write a .gitlab-ci.yml," "fix a GitLab pipeline rule that isn't triggering," "a

• jenkins-centralized-shared-library

  Designs and maintains an organization-wide Jenkins Shared Library (vars/ and src/ layout) so many repos consume a thin Jenkinsfile that calls one shared pipeline function, instead of duplicating pipeline logic per repo. Use when the user asks to "set up a Jenkins shared library," "centralize our Jen

• jenkins-declarative-pipeline-per-repo

  Authors and troubleshoots a per-repo Jenkinsfile using Jenkins Declarative Pipeline syntax — agent, stages, steps, post, environment, and when blocks — for a single repository's own build/test/deploy flow. Use when the user asks to "write a Jenkinsfile," "add a declarative pipeline to this repo," "f

• jenkins-groovy-scripting-best-practices

  Covers writing safe, testable Groovy inside Jenkins pipelines and shared libraries — the script security sandbox and approval workflow, unit testing with JenkinsPipelineUnit, CPS (Continuation-Passing Style) quirks, and common Groovy pitfalls specific to the pipeline execution context. Use when the

Similar plugins