Embed Size (px)
Citation preview
Bittium DevOpsPresenter: Veikko Rytivaara
Date: 29.11.2019
Connectivity to be trusted
Bittium 2018 | Public2
Key Figures
About BittiumBittium provides reliable and secure solutions for connectivity, tactical communications and biosignalmeasuring and monitoring.
Listed in Nasdaq Helsinki
BITTI700
employees
Approximately
1985Founded in
R&D investments
29.1%of net sales
R&D investments
15M€in 2017
Headquarters in
Finland
Oulu
Offices in Finland, UK,
Germany, US, Mexico and Singapore
Net sales
in 2017
51.6M€
Experience
• 300+ R&D projects for radio elements in throughout different mobile network generations.
• A world leading service and technology provider for 5G
• Forerunner in industrial IoT and wearable technologies.
• Main development partner for adidas miCoach Smart Run sportswatch
• ISO 13485 Certified R&D services for healthcare & medical sector
• CE and FDA approved Bittium Faros™ innovative ECG monitoring device
• Bittium NeurOne™ - High-Res EEG System with TMS and fMRI compatibility
• Over 25 years of defense technology experience in domestic and international R&D projects
• Bittium Tactical Wireless IP Network™ for Finnish Defence Forces for nationwide Command & Control (C2) usage
• Founding Member of European Military SDR project ESSOR
• Bittium Tough Mobile™ secure LTE smartphone, the only mobile solution in the world certified by NCSC-FI for CONFIDENTIAL security level
• 100+ R&D projects for different handsets, several turnkey mobile phones in 2G, 3G, 4G and satellite
• Satellite-terrestrial phones to Mexican Government
Over 30 years of experience
Bittium 2018 | Public3
Tackle problems at the “value producing source” → time-to-feedback →better ROI
Where CI can “help” [how]:• Traceability: Who made what and when it was made. [YES]
• Design and Implementation of features [Not, SORRY]• Build: compilation and linking [YES]
• Testing of implementation on several “test levels” [RUN, ANALYZE, REPORT]
• Documenting [PRODUCE, ANALYZE, REPORT, not WRITE]
• Test analysis, e.g: are these tests [maybe, mostly YOUR job]
• Test coverage analysis: what is being missed [YES]
• Memory analysis [YES]
• Static analysis [YES]
• Refactoring [SUPPORT]
© Bittium 2018| Public4
Embedded DevOps
DevOps in an embedded development context• TASK: Comparison of DevOps pipelines built with Jenkins and Concourse CI
• including version control, code review, automated building, analysis and testing and deployment
• Built using Docker (can we benefit from BTRFS here ?)
• Evaluate the PROS and CONS and effort spent
• You can switch team members around at some point so also YOU get to evaluate whatworks and what doesn’t. We want to hear real opinions of real developers who triedboth solutions.
• Interface for CI and localhost development should be the same (if possible)
• Meaning that building on a development machine is same how it will work on the CI
• Use of Docker Compose preferred over using raw Docker Engine
• Deploy SW to real target device for system testing (Rasperry PI or similar)
• What we want• PoC evaluation of which CI/CD makes most sense for this specific UC through really implementing the pipelines
• BONUS: Enviroment setup done using SaltStack or via custom scripts
• Why you should join/interest this: DevOps Wow is becoming the de-facto in the industry and so are containers, so people havingexperience in these methods are in high demand. You will gain real work experience on DevOps in an embedded context.
© Bittium 2018| Public5
