Configuration as Code in Bamboo
1 like16,551 views
The document discusses the challenges and benefits of using configuration as code (Casc) in Bamboo, highlighting the limitations of UI-driven configuration such as lack of version control, tedious changes, and limited reuse. It emphasizes the advantages of using YAML for creating manageable and reusable configurations, while also acknowledging its limitations. The document outlines approaches to creating and managing Bamboo plans, with a focus on leveraging configuration as code to enhance workflow and flexibility.
Configuration as Code in Bamboo
- 1. Configuration as Code in Bamboo Bamboo Specs PRZEMEK BRUSKI | BAMBOO ARCHITECT | ATLASSIAN
- 2. Agenda Language choice How to start Examples Future What is CasC?
- 3. Clone is (not) your friend Limited sharing of common entities Black box Configuration is hidden, cannot be versioned or peer reviewed No bulk operations Even a simple change can be very tedious if you have to do it across the whole instance UI-driven configuration does not scale
- 4. Clone is (not) your friend Limited sharing of common patterns Black box Configuration is hidden, cannot be versioned or peer reviewed No bulk operations Even a simple change can be very tedious if you have to do it across the whole instance UI-driven configuration does not scale
- 5. Clone is (not) your friend Limited sharing of common patterns Black box Configuration is hidden, cannot be versioned or peer reviewed No bulk operations Even a simple change can be very tedious if you have to do it across the whole instance UI-driven configuration does not scale
- 7. Configuration as Code: representing the configuration of a system through source code. CONFIGURATION AS CODE - THE CONCEPT
- 9. Compact Easy to read, low syntax clutter Flat learning curve Master a few rules = master the language No entry barrier Use your standard tools to edit it YAML is a user friendly format
- 10. Compact Easy to read, low syntax clutter Flat learning curve Master a few rules = master the language No entry barrier Use your standard tools to edit it YAML is a user friendly format
- 11. Compact Easy to read, low syntax clutter Flat learning curve Master a few rules = master the language No entry barrier Use your standard tools to edit it YAML is a user friendly format
- 12. No reuse Reusing your credentials, repositories is problematic Validation No tool supported validation No integration with tools Context sensitive documentation YAML does not solve all problems
- 13. No reuse Reusing your credentials, repositories is problematic Validation No tool supported validation No integration with tools Context sensitive documentation YAML does not solve all problems
- 14. No reuse Reusing your credentials, repositories is problematic Validation No tool supported validation No integration with tools Context sensitive documentation YAML does not solve all problems
- 15. Powerful definition languages are the easiest way to manage a big CI instance. CHOOSING THE LANGUAGE
- 16. Teaser
- 17. Starting with Configuration as Code
- 18. Starting from scratch Documentation Archetype Open Source CasC documentation • Introduction • Tutorial • Reference documentation with samples • Javadocs
- 19. Starting from scratch Documentation Archetype Open Source A single command…
- 20. Starting from scratch Documentation Archetype Open Source Use the source • The plan specs language • Archetype • Examples
- 21. Working on the plan Editing To the server! Workflows Editing the plan • IDE recommended • Not IDE specific • Documentation available for major IDEs
- 22. Working on the plan Editing To the server! Workflows It’s a program. Run it.
- 23. Working on the plan Editing To the server! Workflows Choose you workflow • Run from IDE • Command line supported • Bitbucket Server-stored plans (preview!)
- 24. Your first plan
- 25. THE PAST BAMBOO SPECS
- 26. Beyond creation Removals Updates Reuse Removals for nested entities • Stages • Jobs • Tasks
- 27. Beyond creation Removals Updates Reuse Property updates • Change what you want and rerun the spec • Renames supported through unique identifiers
- 28. Beyond creation Removals Updates Reuse Last but not least… • Extract you jobs and tasks into methods • Put your plan variables into common constants • Parametrise your methods
- 29. Do not just store your configuration as code. Manage it like code. CONFIGURATION IS CODE
- 31. Create multiple plans Product branches Matrix plans JIRA 7.2 Product Branch
- 32. Create multiple plans Product branches Matrix plans JIRA 7.3 Product Branch
- 35. Beyond Hello World Other features Planned Feedback Configurable via code • Shared credentials • Linked repositories • Repository-stored plans (preview)
- 36. Beyond Hello World Other features Planned Feedback Next in line • Full coverage of plans • Support for deployments • Custom plugins • Plan export • Download variables/repositories from your server
- 37. Beyond Hello World Other features Planned Feedback Your priorities matter • Server configuration • Per-branch configuration • Lightweight YAML format • …
- 38. Q&A
- 39. Thank you! PRZEMEK BRUSKI | BAMBOO ARCHITECT | ATLASSIAN