Enterprise Technology Organization Enterprise technology
Bamboo & Bitbucket to GitHub Enterprise & GitHub Actions
Discovery, classification and a reusable workflow architecture for moving a large Bamboo and Bitbucket estate to GitHub Enterprise.
Representative experience of the VBR engineering team. The organization is not named, and internal details are omitted.
- Bamboo plans
- 99
- Deployment projects
- 32
- Environments
- 106
- Environment variables
- 500+
Challenge
- A large Bamboo and Bitbucket estate had grown plan by plan, with heavy duplication.
- Hundreds of environment variables and deployment environments needed a secure new home.
- Release approvals and artifact handling had to carry over without weakening governance.
Business context
Rewriting each plan individually would have reproduced the duplication in a new tool. The engagement started by understanding the whole estate so a small set of shared workflows could replace it.
Architecture
Simplified view. Internal names, addresses and configuration are omitted.
Solution
- Discovered and documented 99 Bamboo plans, 32 deployment projects, 106 environments and more than 500 environment variables.
- Classified plans into patterns served by reusable L1 workflows.
- Designed L2 integration so each application consumes shared workflows with minimal configuration.
- Defined a JFrog Artifactory strategy for artifacts and promotion.
- Modernized security: environment-scoped secrets, OIDC to cloud, and scanning as required checks.
- Recreated release governance with GitHub environment protection rules.
Technology
- Atlassian Bamboo
- Bitbucket
- GitHub Enterprise
- GitHub Actions
- JFrog Artifactory
- OIDC
Engineering approach
- Step 1
Discovery
Extracted the complete inventory of plans, deployments, environments and variables.
- Step 2
L1 classification
Grouped plans by build and deploy pattern.
- Step 3
Reusable workflows
Built shared workflows once, for every matching plan.
- Step 4
L2 integration
Connected applications to shared workflows with thin per-repo configuration.
Security
- Variables and secrets moved to environment-scoped storage
- OIDC federation in place of stored cloud keys
- Security scanning as required checks
- Release approvals as environment protection rules
Outcomes
- A complete, documented inventory of the legacy CI/CD estate
- A reusable workflow architecture in place of per-plan pipelines
- A defined path for artifacts, secrets and release governance on GitHub
More enterprise experience
Azure platform transformation
A tenant-to-tenant Azure migration onto a unified AKS and data platform, delivered through Terraform, Terragrunt and Harness.
- Azure
- AKS
- Terraform
- Terragrunt
- Terraform Enterprise
AWS cloud migration & modernization
Migration from a managed hosting provider to AWS, built on a multi-account landing zone with security, monitoring and disaster recovery designed in.
- AWS Organizations
- EC2
- ECS
- S3
- RDS
Secure file transfer modernization
A Citrix ShareFile replacement built on ECS Fargate, Cognito and DynamoDB, with sign-in through the organization's Salesforce identity provider.
- ECS
- Fargate
- Amazon Cognito
- Salesforce
- AWS Managed AD
Discuss a similar transformation
We'll talk through your environment and how we approached comparable work.

