Welcome
β Problem #1
Bamboo Server license expired in February
- β Β It still works
- π΄Β No updates anymore
- π΄ No support available
- We need to take action on that
Bitbucket cloud
- Rente migrated in November - 4 months ago
- BU migrated in January - 2 months ago
β¬
impact on code review process (daily doing) β Problem #2
Our experience with Bitbucket Cloud so far:
- β Β It works!
- π΄ important needed features missing
- π΄ significant UX degradation
- π΄ obvious bugs not getting fixed
Β
Jenkins Pros
β Open source
β Highly configurable
β Huge community
β Experience in the company, also in Vorsorge
- (although the tech stack different)
Stay on BB Cloud: Pros
β No need to change anything
Stay on BB Cloud: Cons
π΄ Missing features; bugs and poor UX
π΄ Daily doing is affected (code review)
π΄ Obvious bugs and feature requests are not tackled for years
Solution A
- Stay on Bitbucket Cloud
- Use Jenkins
(we talked to 3 teams, got demos from them)
Jenkins Cons
π΄ High effort of configuration of pipelines
π΄ Controller maintenance costs
π΄ Plugins maintenance costs (upgrades, security issues, abandoned plugins, compatibility issues)
π΄ Jenkinsfile's are sophisticated:
- maintaining them requires knowing the plugins, understanding groovy syntax
Cons
π΄ Configure Jira integration
Β
π΄ More problematic to share code with other teams
Β
π΄ Price of $29/user/month
(but the price for Bitbucket subscription is removed)
Pros
β No maintenance costs at all
Β
β One platform for git hosting and ci/cd
Β
β Code review page - much better UX
- divided into "Overview", "Commits", "Pipelines", "Changes"
- code coverage out of the box
Β
β CI/CD - no need for plugins
- our case is just supported
Β
β Pipelines yaml files less sophisticated, easier to learn, read and maintain
Β
β Customer support
Β
β Experience in the company, also in Vorsorge
Solution B
Code and CI/CD in Gitlab on premise
(talked to 2 teams, saw a demo)
deck
By Pavel L
deck
- 111