Software development practice based on frequent submission of granular changes
This article includes a list of general references, but it lacks sufficient corresponding inline citations. Please help to improve this article by introducing more precise citations.(July 2016) (Learn how and when to remove this template message)
Part of a series on
Software development
Core activities
Data modeling
Processes
Requirements
Design
Construction
Engineering
Testing
Debugging
Deployment
Maintenance
Paradigms and models
Agile
Cleanroom
Incremental
Prototyping
Spiral
V model
Waterfall
Methodologies and frameworks
ASD
DevOps
DAD
DSDM
FDD
IID
Kanban
Lean SD
LeSS
MDD
MSF
PSP
RAD
RUP
SAFe
Scrum
SEMAT
TDD
TSP
OpenUP
UP
XP
Supporting disciplines
Configuration management
Documentation
Software quality assurance
Project management
User experience
Practices
ATDD
BDD
CCO
CI
CD
DDD
PP
SBE
Stand-up
TDD
Tools
Compiler
Debugger
Profiler
GUI designer
UML Modeling
IDE
Build automation
Release automation
Infrastructure as code
Standards and bodies of knowledge
CMMI
IEEE standards
ISO 9001
ISO/IEC standards
PMBOK
SWEBOK
ITIL
IREB
OMG
Glossaries
Artificial intelligence
Computer science
Electrical and electronics engineering
Outlines
Outline of software development
v
t
e
Sketch of flow diagram for continuous integration
In software engineering, continuous integration (CI) is the practice of merging all developers' working copies to a shared mainline several times a day.[1] Nowadays it is typically implemented in such a way that it triggers an automated build with testing. Grady Booch first proposed the term CI in his 1991 method,[2] although he did not advocate integrating several times a day. Extreme programming (XP) adopted the concept of CI and did advocate integrating more than once per day – perhaps as many as tens of times per day.[3]
^Cite error: The named reference martinfowler was invoked but never defined (see the help page).
^Booch, Grady (1991). Object Oriented Design: With Applications. Benjamin Cummings. p. 209. ISBN 9780805300918. Retrieved 18 August 2014.
^Beck, K. (1999). "Embracing change with extreme programming". Computer. 32 (10): 70–77. doi:10.1109/2.796139. ISSN 0018-9162.
and 25 Related for: Continuous integration information
In software engineering, continuousintegration (CI) is the practice of merging all developers' working copies to a shared mainline several times a day...
The comparison of various continuousintegration tools is done on the basis of platform, license, builders and Integration IDEs. The following table compares...
build-automation utilities on a scheduled or triggered basis; a continuousintegration server is a type of build-automation server. Depending on the level...
pipeline which includes continuous delivery. The types of tools that execute various parts of the process include: continuousintegration, application release...
Integration testing (sometimes called integration and testing, abbreviated I&T) is the phase in software testing in which the whole software module is...
rebuild the software. Good practice today is also to use continuousintegration as part of continuous testing, so that unit tests are re-run for each build...
of either (more often) continuousintegration and continuous delivery, or (less often) continuousintegration and continuous deployment Canary release...
control, bug tracking, software feature requests, task management, continuousintegration, and wikis for every project. Headquartered in California, it has...
method (DSDM) Kanban Scrum Crystal Atern Lean software development Continuousintegration is the practice of merging all developer working copies to a shared...
standard DevOps practices such as automated build and test, continuousintegration, and continuous delivery originated in the Agile world, which dates (informally)...
development lifecycle, source code is continuously being built into binary artifacts using continuousintegration. This may interact with a binary repository...
until after the stand-up. Specific tools and techniques, such as continuousintegration, automated unit testing, pair programming, test-driven development...
Tests are executed during or alongside continuousintegration—at least daily. For teams practicing continuous delivery, tests are commonly executed many...
whether an integration project is worth the effort. Artificial intelligence systems integration Cloud-based integration Configuration design Continuous integration...
SonarQube provides automated analysis and integration with Maven, Ant, Gradle, MSBuild, and continuousintegration tools. SonarQube supports the programming...
significant break presents itself. Continuousintegration will avoid delays later on in the project cycle, caused by integration problems. Because XP doctrine...
Probo is a user automated testing tool that provides continuousintegration, workflow organization and quality assurance using the same tool for project...
how to get home. This process was named path integration to capture the concept of continuousintegration of movement cues over the journey. Manipulation...
122.392019°W / 37.791303; -122.392019 CircleCI is a continuousintegration (CI) and continuous delivery (CD) platform that can be used to implement DevOps...
Automobiles. Palantir Apollo is a platform to facilitate continuousintegration/continuous delivery (CI/CD) across all environments. Palantir's original...
entire lifecycle - from integrating with model generation (software development lifecycle, continuousintegration/continuous delivery), orchestration...
an integral is the continuous analog of a sum, which is used to calculate areas, volumes, and their generalizations. Integration, the process of computing...
October 2012). "Puppet or Chef?". Ramos, Martin (4 November 2015). "ContinuousIntegration: Infrastructure as Code in DevOps". easydynamics.com. Archived from...
invoke behavior on another. Common uses are to trigger builds with continuousintegration systems or to notify bug tracking systems. Because webhooks use...
Global Information
