Is integrating code checking it into a software configuration management repository? (This link seems to say so: Continuous Integration vs. Continuous Delivery vs. Continuous Deployment)
Martin Fowler referred to integrating code against a "controlled source code repository." (Taken from this page: http://www.martinfowler.com/articles/continuousIntegration.html)
Therefore a manual integration of code would be checking code into Subversion or Git. I hear about continuous integration. But I never hear about manual integration.
It is well known that Jenkins is described as a CI tool. But can Jenkins check code into a repository? I know it can copy code from such a repository. Checking code into a repository is always integration, right? I don't think checking code out is necessarily integration. Can someone explain how Jenkins is an integration tool based on the apparent definition of integration as checking code into a code repository?