company. ▪ CI = Wercker ▪ CD: also Wercker but also manually using Capistrano ▪ Various flavours depending on the project and developer. 18/12/2019 … in the beginning
+ CD: enter Jenkins. ▪ Organic adoption of multibranch pipelines. ▪ Building a stockpile of technology 18/12/2019 … after some beginning The small Rombit DevOps history
backend switched to JVM-based tech (mostly Spring Boot) ▪ Move to Kubernetes ▪ New infra made CI/CD more complex, e.g.: ◦ Various testing strategies ◦ Ansible ◦ Bash scripts … ▪ Jenkins updates & plugin management (being outdated as a daily routine) 18/12/2019 … and also The small Rombit DevOps history
Credstash) ▪ No oversight ▪ Limited user management ▪ Ansible Scripts: all logic possible ▪ Jenkins files: Groovy, logic mingled with scripts ▪ Release and pray strategy ▪ Split the CI from the CD (build & deploy) 18/12/2019 Difficult
Access control ◦ Pipeline trigger management, also for non tech people ⚡ ◦ Proper governance and overview ✈ ◦ Easy versioned plugin management 18/12/2019 Target #3
with a proper UI, drag and drop ▪ Password management ability via secrets & keys ▪ Task groups for repeating tasks ▪ Governance ▪ Working now well for: ◦ FE apps (React) ◦ BE apps (Spring Boot/Node JS) ◦ It has a MacOS agent! Yay! 18/12/2019 Lessons learned so far
for mobile apps with Azure DevOps and Fastlane ◦ Notification strategy via Slack ▪ Getting planned: ◦ Automated UI/integration test runs in CI ▪ To be validated: ◦ .yaml configuration via Code 18/12/2019 Not doing… yet.