Continuous delivery for IoT by María Gómez The software industry has spent the last 10 years creating tools and frameworks that reduce the friction in the delivery process, like continuous integration tools, test driven development, automated deployments, etc. There should not any reason why projects that have hardware components cannot use the same tools. However, in practice, this process can be really costly and risky and it requires a mindset that hardware and embedded system developers are not used to. In this talk, I explain how to apply continuous delivery practice in projects that contain hardware and software components and embedded systems and how to solve the most common challenges. Main topics include: -Strategy for creating continuous integration pipelines -Tips on how to reduce the development feedback cycle -How to automated deployments and test on physical boards -What development practices work in this environment

1. CONTINUOUS DELIVERY
FOR IoT
JOnTheBeach 2018

2. ©ThoughtWorks 2017 Commercial in Confidence
Maria Gomez
@mariascandella
Market Tech Principal TW Spain

3. ©ThoughtWorks 2017 Commercial in Confidence
A bit of
history

4. ©ThoughtWorks 2017 Commercial in Confidence
Continuous Delivery is the ability to get
changes of all types—including new features,
configuration changes, bug fixes and
experiments—into production, or into the
hands of users, safely and quickly in a
sustainable way.
continuousdelivery.com

5. ©ThoughtWorks 2017 Commercial in Confidence
Waterfall

6. ©ThoughtWorks 2017 Commercial in Confidence
The last mile

7. ©ThoughtWorks 2017 Commercial in Confidence
Continuous Delivery

8. ©ThoughtWorks 2017 Commercial in Confidence
What about hardware?

9. ©ThoughtWorks 2017 Commercial in Confidence

10. ©ThoughtWorks 2017 Commercial in Confidence
10

11. ©ThoughtWorks 2017 Commercial in Confidence
Continuous Delivery
CD maturity model: https://info.thoughtworks.com/Continuous-Delivery-
Maturity-Model.html

12. ©ThoughtWorks 2017 Commercial in Confidence
Architecture

13. ©ThoughtWorks 2017 Commercial in Confidence
Software architecture is "the important stuff
(whatever that is)”
Ralph Johnson
https://en.wikipedia.org/wiki/Ralph_Johnson_(computer_scientist)

14. ©ThoughtWorks 2017 Commercial in Confidence
Architecture

15. ©ThoughtWorks 2017 Commercial in Confidence
Architecture

16. ©ThoughtWorks 2017 Commercial in Confidence
Architecture
http://evolutionaryarchitecture.com/

17. ©ThoughtWorks 2017 Commercial in Confidence
Architecture
https://en.wikipedia.org/wiki/Raspberry_Pi
https://en.wikipedia.org/wiki/Artificial_intelligence_systems_integration

18. ©ThoughtWorks 2017 Commercial in Confidence
Quality
Assurance

19. ©ThoughtWorks 2017 Commercial in Confidence
Quality Assurance
FUNCTIONAL
INTEGRATION
UNIT
http://blog.asset-intertech.com/test_data_out/2012/03/what-is-board-bring-up.html

20. ©ThoughtWorks 2017 Commercial in Confidence
Continuous
Integration

21. ©ThoughtWorks 2017 Commercial in Confidence
Continuous Integration
Develop &
commit
Test
Deploy
Feedback

22. ©ThoughtWorks 2017 Commercial in Confidence
Continuous Integration

23. ©ThoughtWorks 2017 Commercial in Confidence
Environments &
Deployments

24. ©ThoughtWorks 2017 Commercial in Confidence
Environments & Deployments
Automate:
● Tests
● Infra
● Deployments

25. ©ThoughtWorks 2017 Commercial in Confidence
Deployment pipelines

26. ©ThoughtWorks 2017 Commercial in Confidence
Deployment pipelines
Repo
A
Repo
B
Repo
C

27. ©ThoughtWorks 2017 Commercial in Confidence
Jenkins agent

28. ©ThoughtWorks 2017 Commercial in Confidence
Release
Management

29. ©ThoughtWorks 2017 Commercial in Confidence
Release Management

30. ©ThoughtWorks 2017 Commercial in Confidence
Organizational
Alignment

31. ©ThoughtWorks 2017 Commercial in Confidence
DevOps culture
Ops
Dev
Business
martinfowler.com/bliki/DevOpsCulture.html
QA

32. ¡Gracias!
@mariascandella
mgomez@thoughtworks.com