The Holy Grail of continuous delivery in distributed teams environment
0 likes118 views
The document discusses continuous delivery in distributed teams, emphasizing the importance of early and continuous delivery of software. It highlights tools and practices like GitHub flow, code reviews, static code analysis, and effective team communication. The author reflects on their journey towards achieving continuous delivery, noting areas for improvement such as increasing test coverage.
![Before we go further
Yup! It was on the 16th of October 2006!!!
The second meeting topics:
- Dynamic model creation with Ruby and creating “Page scraper” applications
[Szymon Kurcab]
- Calendar and operations on dates with RoR
[Mateusz Jędruch]
- Testing web interfaces in Rails with Selenium on Rails package [Maciek
Ksiązek]
Good to be back here :)
KRUG today: 1361 members in KRUG Meetup group!](https://image.slidesharecdn.com/krug-cont-deployment-190318224226/85/The-Holy-Grail-of-continuous-delivery-in-distributed-teams-environment-5-320.jpg)
The Holy Grail of continuous delivery in distributed teams environment
- 1. The Holy Grail of continuous delivery in distributed teams environment by Szymon Kurcab
- 2. Before we go further Do you recognise this logo?
- 3. Before we go further
- 4. Before we go further Question: When did the first KRUG event take its place (year/month)?
- 5. Before we go further Yup! It was on the 16th of October 2006!!! The second meeting topics: - Dynamic model creation with Ruby and creating “Page scraper” applications [Szymon Kurcab] - Calendar and operations on dates with RoR [Mateusz Jędruch] - Testing web interfaces in Rails with Selenium on Rails package [Maciek Ksiązek] Good to be back here :) KRUG today: 1361 members in KRUG Meetup group!
- 6. A few words about myself CTO @ Paladin Software repertuary.pl aka kina.krakow.pl co-owner Ruby’ist and Hacker
- 7. Why this topic? Stay DRY - Continuous Delivery for Rubyist by Michał Knapik Focus on distributed teams environment and the case study
- 8. Vocabulary • Continuous (automated) deployment/delivery First principle of Agile Manifesto: “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” • Distributed team (in Paladin Software)
- 9. Tools / prerequisites • Github flow • Code reviews (1 or 2 people need to accept) • Codeclimate: • static code analysis (rubocop, overcommit) • code coverage • Specs, specs … and more integration specs! (no flaky specs) • CI (Semaphore 2.0) and Heroku/AWS • Production-like test/staging environments • Smoke tests
- 10. Tools / prerequisites • Other tools: • Honeybadger • New Relic • Intercom • Papertrail • Scout • Hirefire • and more … • Periodic security pentests (focused on new functionality)
- 11. Tools / prerequisites … and more • strong and motivated team (quality hiring procedure) • trust, trust and … even more trust • code ownership aka taking the responsibility • good communication between teams • daily stand-ups • Slack + Google Meet communication • pair programming • as few paperwork as possible :)
- 12. A plan how we’ve reached the CD goal No plan at all :) It just happened when all prerequisites were fulfilled.
- 13. Place for improvement • even more specs and better code coverage • … you tell me :)