Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
2K views1 page

Continuous Integration

CI practices include deploying to production, using branches, and enabling automated builds and tests. Version control systems can be centralized or distributed. Continuous integration aims to provide rapid feedback through practices like automated testing and building on every code change to catch errors early.

Uploaded by

saranaji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
2K views1 page

Continuous Integration

CI practices include deploying to production, using branches, and enabling automated builds and tests. Version control systems can be centralized or distributed. Continuous integration aims to provide rapid feedback through practices like automated testing and building on every code change to catch errors early.

Uploaded by

saranaji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Which is not a CI practice?

: Deploy to production
Branch is also known as a : Codeline
Git is a ___________________________ version control system. : Distributed
Which is not a benefit of CI ? : Bugs & Defects no longer occur
________ is an independent line of work. : Branch
are created for solving bugs detected after the application is released to the
user. : True
Feature branching is used to work on _____________. : User Stories
Select the activity/activities that are part of continuous integration. : All
Release branches are created for solving bugs detected after the application is
released to the user.: True
____________ branches are created for logical changes. : Functional
IBM Clearcase is a ________ version control system. : Streambased
The minimum number of test inputs required to verify the execution of a program is
determined by ______________. : CCN
Complexity of code is determined based on : Cyclomatic Complexity Number (CCN)
_______________ is a measure of incoming dependencies. : Afferent Coupling
CCMetrics is a measure of non-linearly independent paths. : False
A build can be triggered by a version control tool. : True
The developer runs the private builds before moving the changes to the local
version control. : True
Release build will be triggered by code changes done on ___________. : Both
Mainline and Release Branch
Efferent Coupling is a measure of ____________________. : Outgoing dependencies.
Private builds can be triggered automatically. : False
It is perfectly fine to commit a code change, though the code inspection has
failed. : False
Which of the following is an artifact repository? : Nexus
________ plays a crucial role in helping to reduce the build duration. : Build
metrics
Faster feedback can be received by ___________. : Enabling CI
Which is the most important operational parameter in CI ? : Quality
Time taken to fix a broken build is measured using ________________. : Build Repair
Rate
______________ is a .Net build tool. : NAnt
Which of the tools is not a CI tool? : Travis CI
Git, Mercurial, and Subversion are centralized version control tools. : False
A component test is executed to verify how changes interact with the rest of the
system. : True
In the distributed version control system, developers can clone the central code
base to their local system. : True

You might also like