3 ms·

Well written. The line between CI and CD has been blurred esp when they’re commonly mentioned together. Many cant tell the difference

• hinkley 7y ago
  Few things are as aggravating to me as people who say they understand CD but then manage avoid practicing any of the tenets of CI. Automated builds are the smallest part of CI. Necessary, but drastically insufficient. If that's all you're doing you've missed the forest for the trees.
  • tomxor 7y ago
    > Few things are as aggravating to me as people who say they understand CD but then manage avoid practicing any of the tenets of CI. It is completely reasonable to utilise one without the other, not all projects are giant multi author efforts trying to wrangle commits. For instance if you have lots of small projects being worked on independently in parallel with no more than one or two authors on a repo at a time, CI is not going to be worth the investment... but CD still has it's uses.
    • greglindahl 7y ago
      It took me a few minutes to set up CI for each of my smallish open source modules - and it caught problems with older Python versions quickly. How am I doing it wrong?
    • jdlshore 7y ago
      Small-scale CI is trivial to set up. A build script and integration VM is all you need. If it's difficult, there's most likely hygiene factors in your codebase that are worth resolving. https://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html https://www.jamesshore.com/Blog/Continuous-Integration-on-a-...