bitbucket-pipelines

Best Practices

• Use specific Docker images with pinned versions for reproducibility
• Define caches in definitions section for dependency caching
• Use artifacts to pass build outputs between steps
• Use services for external dependencies (databases, Docker, Redis)
• Use deployment keyword for environment tracking (staging, production)
• Use trigger: manual for production deployment gates
• Use pipes for common integrations (AWS, GCP, Slack, etc.)
• Use branches section for branch-specific pipeline configurations
• Use pull-requests section for PR-specific validation
• Set appropriate step size (1x, 2x, 4x, 8x) based on resource needs
• Use parallel steps for independent test suites
• Use definitions/steps for reusable step definitions with YAML anchors

Documentation Sources