The costs of continuous integration
The costs of continuous integration
Posted Mar 6, 2020 16:23 UTC (Fri) by marcH (subscriber, #57642)In reply to: The costs of continuous integration by JohnVonNeumann
Parent article: The costs of continuous integration
> I have been banging on about this for a bit now, using simple stuff like githooks and docker to have all of your non-functional CI tasks run client side (linting, testing to some degree, formatting), anything that isn't "deploy this to x" but I don't seem to have much luck convincing people ...
How "simple" is that stuff really? The typical vicious circle is:
- test dependencies and setups are complex, so few developers run them locally
- because it affects only a few developers, the validation/devops team keeps increasing the complexity, asking these few developers to "upgrade" to new test frameworks etc.
- fewer and fewer developers run tests locally
- repeat and the gap widens each time
Ideally, anyone can copy/paste the command straight from the CI log[*] and at worst get a "program not found" fixable with a simple apt/dnf install. A test setup should not be less automated than a build setup - ideally they should be treated as one.
[*] and githooks just a couple lines long, personal preference.