Overview
“Deployment automation leads to an increased release cadence and less mistakes“
Setting up infrastructure-as-code requires a significant upfront investment but with a positive ROI. Once the learning curve is tackled, teams will experience faster development cycles and fewer (human) errors. Using pipelines targeted at separated development-, test-, acceptance- and production environments enables a hands-off approach for production environments.?
The CCoE assists in:?
- Creating a deployment architecture for solutions, shared services and infrastructure?
- Selecting a secured repository and tools for the application and service deployment code?
- Creating the deployment infrastructure, such as the pipelines, workflows and tool-authorisations?
- Facilitating the use of secret-stores to prevent the use of secrets in code?
- Code sharing between DevOps teams ?
- Consolidation of scripting tools
Activities checklist
Initial:
- Creating a deployment architecture for solutions, shared services and shared infrastructure?
- Selection of repos and tools?
- Pipeline creation, authorisations and workflows?
- Ensuring that secrets are not used in code
Recurring:
- Supporting pipelines for DevOps teams ?
- Supporting teams in using tools and methods
RASCI
| cloud consultant | transformation consultant | ||
| cloud architect | responsible | cloud partners | |
| cloud security specialist | supporting | DevOps team | informed |
| cloud developer | consulting | business stakeholder | |
| cloud engineer | architecture | accountable | |
| cloud analyst | security | informed | |
| product owner CCoE | informed | finance | |
| management | procurement |