-
Notifications
You must be signed in to change notification settings - Fork 0
/
params.json
1 lines (1 loc) · 1.4 KB
/
params.json
1
{"name":"Build Canaries","tagline":"Early warning of project danger","body":"> **Noun** \r\n> canary in a coal mine\r\n\r\n> (idiomatic) Something whose sensitivity to adverse conditions makes it a useful early indicator of such conditions; something which warns of the coming of greater danger or trouble by a deterioration in its health or welfare.\r\n\r\n## What?\r\n\r\nThe idea of build monitors is not new, but building your own takes time and focus away from building the actual software you want to build.\r\n\r\n## How?\r\n\r\nPrimarily we have created a build monitor, [Nevergreen](http://nevergreen.io/), that we believe can be used by most projects \"out of the box\". For the times this is not the case, the entire codebase of Nevergreen is open source allowing it to be improved or completely modified by anyone in the community. We have also extracted several libraries out of the Nevergreen source allowing them to be used directly, for completely new and different monitor ideas.\r\n\r\n## Why?\r\n\r\nAs teams and projects get bigger and more complicated, there are more chances for build and integration failures. The earlier and clearer these failures are presented to the teams involved the better. You can read more about continuous delivery here, http://www.thoughtworks.com/continuous-delivery","google":"UA-57813748-1","note":"Don't delete this file! It's used internally to help with page regeneration."}