# Building Better Firmware with Continuous Integration | Interrupt

**URL:** <https://community.memfault.com/t/building-better-firmware-with-continuous-integration-interrupt/77>\
**Category:** Blog\
**Created:** [September 18, 2019, 4:15am UTC](https://community.memfault.com/t/building-better-firmware-with-continuous-integration-interrupt/77 "2019-09-18T04:15:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![discobot](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.memfault.com/discobot/32/1_2.png) [@discobot](https://community.memfault.com/u/discobot)\
**Post date:** [September 18, 2019, 4:15am UTC](https://community.memfault.com/t/building-better-firmware-with-continuous-integration-interrupt/77/1 "2019-09-18T04:15:31Z")

</div>

Larger firmware projects sometimes have tens, even hundreds of engineers working in a single codebase. This introduces new challenges: builds break, lesser used features get forgotten about, new features miss support for older hardware platforms. Without solid tooling and processes, this can slow development to a grind.

* * *
This is a companion discussion topic for the original entry at [https://interrupt.memfault.com/blog/continuous-integration-for-firmware](https://interrupt.memfault.com/blog/continuous-integration-for-firmware)
