3 ms·
> As with all ideas, everybody does their own version of it in practice. Yes. > Continuous integration (CI) is confusing. At core, no. Not really. See the 1s
by SideburnsOfDoom 10y ago
> As with all ideas, everybody does their own version of it in practice.
Yes.
> Continuous integration (CI) is confusing.
At core, no. Not really. See the 1st paragraph of https://en.wikipedia.org/wiki/Continuous_integration https://en.wikipedia.org/wiki/Continuous_integration :
> In software engineering, continuous integration (CI) is the practice of merging all developer working copies to a shared mainline several times a day.
So the 2 words are defined as follows:
Continuous: at least several times a day.
Integration: merge changes to master.
It's not a tool: it's a practice, a workflow that builds, tests and tools can help you do safely.
Some of these "CI Server" tools also support "build and test the branches" which is useful but is not CI. This is a common mistake.
See also: https://trunkbaseddevelopment.com/ https://trunkbaseddevelopment.com/
- leblancfg 10y agoReally does sound like "Let me shame your practices by redefining what this means in order to sell this service."
- UK-AL 10y agoAs long as those branches are merged in daily, it's still CI. Your working copy is just an informal branch. Sticking it in a feature branch while your working on it is just convince.
- SideburnsOfDoom 10y agoYes. I meant that "build and test the branches" is not itself CI. But it can be a useful practice before merging in a CI workflow. Or it can be a painful set of long-lived branches. But some people have the idea that the build and test of any branch, i.e the automated production of a binary that passes checks, is the "integration" itself. Look out for statements like "We do CI of branches on our CI server".