The capability of your build system to handle an increase in the amount of code that it integrates and analyzes is known as ____________.
Answers
Answered by
35
Well, I am not sure since the options also have not been given. So, I am giving an assumed answer.
The correct answer could be - Continuous Integration (CI).
Continuous integration (CI) is a method of merging all the developer working copies to a shared mainline that happens many times a day. The primary aim of CI is to avoid any kind of integration problems which are called as "integration hell".
The correct answer could be - Continuous Integration (CI).
Continuous integration (CI) is a method of merging all the developer working copies to a shared mainline that happens many times a day. The primary aim of CI is to avoid any kind of integration problems which are called as "integration hell".
Redhat:
Capablility of your build system to handle an increase in the amount of code that it integrates and analyzes is known as; A) Build performance, B) Build Integration, C) Build Scalability or NONE of the options given.
Answered by
7
In software engineering:
Continuous Integration (CI) is the ability to combine all developer working copies to a shared mainline.
It prevents developer's local coy from drifting far off and there avoids catastrophic merge conflicts.
Therefore, Continuous Integration is the capability of your build system to handle an increase in the amount of code for integration and analysis.
Continuous Integration (CI) is the ability to combine all developer working copies to a shared mainline.
It prevents developer's local coy from drifting far off and there avoids catastrophic merge conflicts.
Therefore, Continuous Integration is the capability of your build system to handle an increase in the amount of code for integration and analysis.
Similar questions
English,
7 months ago
Business Studies,
7 months ago
Math,
1 year ago
Math,
1 year ago
Math,
1 year ago