Csc/ece 517 fall 2007/wiki3 p1: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
<u>'''Definition 3'''</u>[http://en.wikipedia.org/wiki/Continuous_integration] | <u>'''Definition 3'''</u>[http://en.wikipedia.org/wiki/Continuous_integration] | ||
<pre> | <pre> | ||
Continuous integration is the name that emerged in the extreme programming community for the software engineering practice of immediately committing every change, no matter how small, to a revision control system. Other developers should always work with the latest version of the codebase. | Continuous integration is the name that emerged in the extreme programming community for the software engineering | ||
practice of immediately committing every change, no matter how small, to a revision control system. Other developers should always work with the latest version of the codebase. | |||
</pre> | </pre> | ||
Revision as of 23:17, 18 November 2007
Two of the important Agile methodologies that we have not said much about in this course are collective ownership and continuous integration. What are the best definitions or examples you can find? Are these widely practiced? Are they controversial? Are there adherents of other design methodologies who consider them harmful? Investigate, through the Web and through the ACM DL.
Continuous Integration
What Is Continuous Integration?
Definition 1
Continuous Integration refers to the practice of committing every smallest change no matter how small to a revision control system.
Definition2[1]
Continuous integration is a software engineering term describing a process that completely rebuilds and tests an application frequently.Continuous integration is accomplished via a serialized build process. At the completion of a task, the developer (or development pair) takes a build token and runs the build process, including tests. If the tests pass, the task can be committed to the source code repository and release the token.
Definition 3[2]
Continuous integration is the name that emerged in the extreme programming community for the software engineering practice of immediately committing every change, no matter how small, to a revision control system. Other developers should always work with the latest version of the codebase.