4 ms·

Anyone else find it strange how the author uses CI as a noun? I've never heard anyone refer to a CI platform/system this way before and it sort of strikes me a

Anyone else find it strange how the author uses CI as a noun? I've never heard anyone refer to a CI platform/system this way before and it sort of strikes me as a red flag. Also the idea of running CI on your laptop seems questionable at best, downright irresponsible and insecure at worst. Sure faster builds are nice, but by the time you're running your code through CI/CD its not usually after adding a few lines of for a feature, it's when the completed feature ready to merge or some sort of integration test is needed.

xwowsersx 3y ago
> Anyone else find it strange how the author uses CI as a noun? Do you mean using the term "CI" with no other modifiers/qualifiers? > Also the idea of running CI on your laptop seems questionable at best, downright irresponsible and insecure at worst. Didn't you also use CI as a noun here? And isn't it a noun? > Sure faster builds are nice, but by the time you're running your code through CI/CD its not usually after adding a few lines of for a feature, it's when the completed feature ready to merge or some sort of integration test is needed. I hear you, but not necessarily. You might have a test suite that runs in CI and after you open your PR, you continuing pushing to it and it's nice to have a fast pipeline.
aftbit 3y ago
I think the idea is to run the CI on your laptop for debugging and building the CI process itself. This dramatically shortens the build-test cycle (for the CI, not your product). Instead of "edit, git push, wait for runners, download logs, stare confusedly, repeat", you have "edit, run locally, watch logs, stare confusedly, repeat". Plus you can get real access to the actual runners, so maybe you can do things like strace, gdb, etc to see what is going wrong.
ahtihn 3y ago
I'm confused why you think fast CI/CD doesn't matter. In an ideal world, every commit you make goes through the full pipeline and ideally it's so fast that you get immediate feedback. The only reason that you're delaying code going through the pipeline is that it's slow.

xwowsersx 3y ago

> Anyone else find it strange how the author uses CI as a noun? Do you mean using the term "CI" with no other modifiers/qualifiers? > Also the idea of running CI on your laptop seems questionable at best, downright irresponsible and insecure at worst. Didn't you also use CI as a noun here? And isn't it a noun? > Sure faster builds are nice, but by the time you're running your code through CI/CD its not usually after adding a few lines of for a feature, it's when the completed feature ready to merge or some sort of integration test is needed. I hear you, but not necessarily. You might have a test suite that runs in CI and after you open your PR, you continuing pushing to it and it's nice to have a fast pipeline.

aftbit 3y ago

I think the idea is to run the CI on your laptop for debugging and building the CI process itself. This dramatically shortens the build-test cycle (for the CI, not your product). Instead of "edit, git push, wait for runners, download logs, stare confusedly, repeat", you have "edit, run locally, watch logs, stare confusedly, repeat". Plus you can get real access to the actual runners, so maybe you can do things like strace, gdb, etc to see what is going wrong.

ahtihn 3y ago

I'm confused why you think fast CI/CD doesn't matter. In an ideal world, every commit you make goes through the full pipeline and ideally it's so fast that you get immediate feedback. The only reason that you're delaying code going through the pipeline is that it's slow.