Search the World's Largest Database of Information Science & Technology Terms & Definitions
InfInfoScipedia LogoScipedia
A Free Service of IGI Global Publishing House
Below please find a list of definitions for the term that
you selected from multiple scholarly research resources.

What is Continuous Integration

Chapter 12
Emerging Automation Techniques for the Future Internet
In software engineering, continuous integration (CI) is the practice of merging all developer code contributions to a shared mainline several times a day. The term was introduced in 1991 by Grady Booch, known for his work on oriented object programming concepts.
Published in Chapter:
The Open Source Community Choice: Automate or Die!
Morgan Richomme (Orange Labs, France)
Copyright: © 2019 |Pages: 23
DOI: 10.4018/978-1-5225-7146-9.ch012
Abstract
Open source communities have had and continue to have a major influence on the evolution of the Internet. By their nature, such communities involve people with diverse coding cultures and skills. Automation has consequently been of major interest to open source software developers for a long time, and many open source tools have been developed to address code variability and sustainability challenges. This chapter discusses why open source communities must automate and the challenges they will face. Solutions and current examples of automation in open source projects are provided as a guide to what is achievable. OpenShift, OpenStack, and OPNFV communities are used to illustrate different approaches and best practices. Two recently initiated automation initiatives are detailed: “Cross Community Continuous Integration” (XCI) and “Cross Testing” (Xtesting). Finally, some recommendations are provided for new projects as a guide to ease adoption of appropriate tools and methods.
Full Text Chapter Download: US $37.50 Add to Cart
More Results
Chapter 11
Agile Development of Rule Systems
Agility proposes short development cycles concluded by the integration of the new feature in an always running system. Since the integration is frequently performed at the end of every development cycle we call it continuous integration. With continuous integration we have a running system after every cycle, thus enabling early feedback by end-users and a timely detection of possible implementation errors.
Published in Chapter: Agile Development of Rule Systems; From: Handbook of Research on Emerging Rule-Based Languages and Technologies: Open Solutions and Approaches
Full Text Chapter Download: US $37.50 Add to Cart
Chapter 653
Research and Development on Software Testing Techniques and Tools
Full Text Chapter Download: US $37.50 Add to Cart
eContent Pro Discount Banner
InfoSci OnDemandECP Editorial ServicesAGOSR