Configure Bitbucket CI/CD Pipelines
Expert agent for Bitbucket Pipelines CI/CD configuration, providing YAML templates for parallel execution, Docker builds, caching strategies
Why it matters
Automate your software delivery with expert Bitbucket Pipelines configuration. This asset helps you build efficient, scalable, and maintainable CI/CD workflows.
Outcomes
What it gets done
Define basic and multi-stage pipeline structures
Implement advanced caching and Docker integration strategies
Configure deployment patterns for AWS and Kubernetes
Optimize pipelines for security, performance, and error handling
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-bitbucket-pipeline-config | bash Overview
Bitbucket Pipeline Configuration Expert Agent
An expert agent that generates and optimizes Bitbucket Pipelines CI/CD configurations. It provides bitbucket-pipelines.yml templates with multi-stage builds, parallel test execution, custom caching for Node.js/Gradle/Maven/Cypress, Docker integration, and deployment workflows for AWS and Kubernetes. Includes security best practices, error handling patterns, and performance optimization techniques. Use this when setting up or optimizing Bitbucket Pipelines for projects requiring parallel execution, advanced caching, Docker builds, or multi-environment deployments to AWS or Kubernetes. Ideal for teams managing complex CI/CD workflows with manual production gates, integration testing with service containers, and artifact management across pipeline stages.
What it does
This skill provides expert guidance for configuring Bitbucket Pipelines CI/CD workflows using bitbucket-pipelines.yml. It delivers YAML templates for multi-stage builds, parallel test execution, caching strategies, Docker integration, and deployment automation to AWS, Kubernetes, and other platforms. The agent specializes in optimization techniques that reduce build times and improve pipeline reliability.
When to use - and when NOT to
Use this skill when you need to set up or optimize Bitbucket Pipelines for Node.js, Docker, or multi-language projects with complex deployment requirements. It handles scenarios with parallel test execution, custom cache definitions, and multi-environment deployments with manual production triggers. Use it when integrating with AWS S3/CloudFront, Kubernetes clusters, or Docker registries.
Do NOT use this skill if you're working with GitHub Actions, GitLab CI, or other CI/CD platforms - it is Bitbucket-specific. Avoid it if you need simple single-step pipelines without caching or deployment complexity, as the templates assume intermediate to advanced CI/CD requirements.
Inputs and outputs
You provide your project requirements: programming language/framework, testing strategy, deployment targets (staging/production), cloud provider (AWS, Kubernetes), caching needs, and whether you need Docker builds or parallel execution. The skill returns bitbucket-pipelines.yml configurations with image selections, cache definitions, script commands, artifact management, and deployment steps.
Integrations
The skill provides configurations for Docker (multi-stage builds, registry push), AWS services (S3, CloudFront, CLI configuration), Kubernetes (kubectl deployment, rollout status), PostgreSQL service containers for integration testing, and Node.js package managers (npm with offline caching). It supports cache definitions for Gradle, Maven, Cypress, and Next.js build caches.
Who it's for
DevOps engineers and platform teams managing Bitbucket-based CI/CD pipelines for production applications. Frontend developers deploying Node.js applications to AWS or containerized environments. Backend teams requiring database integration tests with service containers. Release managers who need manual production deployment gates and multi-environment promotion workflows.
Here's a basic pipeline configuration example:
image: node:18
pipelines:
default:
- step:
name: Build and Test
caches:
- node
script:
- npm ci
- npm run test
- npm run build
artifacts:
- dist/**
branches:
master:
- step:
name: Deploy to Production
deployment: production
script:
- echo "Deploying to production"
develop:
- step:
name: Deploy to Staging
deployment: staging
script:
- echo "Deploying to staging"
The skill emphasizes security best practices including repository variables for secrets, secured variables for production, and validation of environment variables before use. It provides error handling patterns with proper exit codes, debugging information, and cleanup tasks using after-script blocks.
FAQ
Common questions
Discussion
Questions & comments ยท 0
Sign In Sign in to leave a comment.