5 ms·
He's arguing that you only need CI after a lot of other things already went wrong. If your code is portable, clean, readable, easily maintainable and contains
by fxtentacle 6y ago
He's arguing that you only need CI after a lot of other things already went wrong.
If your code is portable, clean, readable, easily maintainable and contains tests, the benefits from CI over running the build locally are negligible. So CI distracts from fixing the issues that people face when building locally.
- dgrin91 6y agoHow do you enforce test being run without CI? I forget to run tests locally all the time.
- pan69 6y agoSet up a pre-commit or pre-push hook that will run your tests. https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks
- slooonz 6y agoAnd how do you test that your tests pass in other environments ?
- pan69 6y agoDepends on what you're building, you might not have other environments as such, but I get the point (I'm pro CI for the record). My comment was aimed at: > I forget to run tests locally all the time.
- dgrin91 6y agoThis doesn't solve the problem. New person joins the team, doesn't do this. Now what?
- pan69 6y agoIn JavaScript projects we're using Husky [1]. I'm sure other environments have their own equivalents of it. [1] https://github.com/typicode/husky https://github.com/typicode/husky
- jhanschoo 6y ago> If your code is portable Yet how do you know for certain if your code is portable if you only build locally?