Scribd
Upload
82 views

Continuos Integration Q & A

This document discusses concepts related to continuous integration including version control systems, CI practices, benefits of CI, build tools, and metrics. It covers topics such as afferent and efferent coupling, build triggers, private versus public builds, and tools used for version control, builds, testing, and code analysis in CI pipelines.

Uploaded by

Jorge Castro Sanchez
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
82 views

Continuos Integration Q & A

This document discusses concepts related to continuous integration including version control systems, CI practices, benefits of CI, build tools, and metrics. It covers topics such as afferent and efferent coupling, build triggers, private versus public builds, and tools used for version control, builds, testing, and code analysis in CI pipelines.

Uploaded by

Jorge Castro Sanchez
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Work Branch is also known as_.

Codeline

Which is not a CI practice ? deploy to prod

Git is a _ version control system. distributed

Activities that are part of continuous integration. All options(version


control,test,code build,inspection)

Which is NOT a benefit of CI ? bugs & defects no longer occur

Release branches are created for resolving merge conflicts. False

Which is NOT true about continuous integration ? moving code in large


amounts
Rapid feedback is a key factor of CI.

If the build runs for a longer duration, it may delay the reporting and fixing of errors.
So stage the builds (split builds logically).

Complexity determined by Cyclomatic Complexity Number (CCN) .

Afferent Coupling :

 Who depends on you.


 Measure of how many other packages use a specific package.
 Incoming dependencies.

Efferent Coupling :

 Who do you depend on.


 Measure of how many different packages are used by a specific package.
 Outgoing dependencies.

__ is a .Net build tool. NAnt

Capablility of your build system to handle an increase in the amount of


code that it integrates and analyzes is known as .

Pipeline break and build break is one and the same. False

Time taken to fix a broken build is measured using __. Build repair rate

_ is a measure of incoming dependencies. Afferent coupling

Build can be triggered by a version control tool. True


Private builds are executed after moving the changes to version control.
False

Version Control - GitHub, Subversion

Java Build - Ant, Maven

.Net Build - NAnt, MSBuild

Java build scheduler - Jenkins, Cruisecontrol

Static code analysis : SonarQube, Checkstyle, PMD

Code Coverage : Jcov, Clover, Serenity

Unit Testing : NUnit, JUnit

Functional Testing : Cucumber, Selenium

Final assessment:

Trunk is also known as ____. Mainline

is a continuous integration server. Teamcity—not sure

Build can be triggered by a version control tool. True

Git is a _ version control system. Distributed

Select a CI tool based on it's ___.both (extendability & resistability)

Which of these is not a valid build trigger ? manual trigger—not sure

Which is the most important operational parameter in CI ? robustness—not


sure

CCMetrics is used to identify _. Code complexity

Which is NOT a benefit of CI ? Bugs & defects no longer occur

Which is not a CI practice ? deploy to prod

Complexity of a code is determined based on ___. Cyclomatic complexity


number
Private builds are executed after moving the changes to version control.
False

Release branches are created for resolving merge conflicts. False

Commiting a code change, when the inspection fails , is perfectly fine as


the code logic is working fine anyway. False

__ is a .Net build tool. Nant

Practice of developers integrating changes directly in the feature or work


branches and commiting the changes at the end to the mainline is known
as _. Promiscuous integration/continuous integration---not sure

Which of these is not mandated for a CI pipeline ? infrastructure as code-


not sure

Code changes can be hidden,enabled or disabled using ___.

Which is NOT true about continuous integration ? moving code in large


amounts

What are the reasons for a build to fail ? build break

Functional testing can be automated using Jenkins. True

Which of the following is an artifact repository ? nexus—not sure

Git, Mercurial and Subversion are centralized version control tools. False

In a normal scenario, software from is deployed to production. Work branch

Component test is executed as part of _.Integration build

Work Branch is also known as_. Codeline

How are component dependencies injected in a workflow ? run unit test &
build package—not sure

Staged builds include _. Both(commit & secondary builds)

It is a proven fact that reducing the CCN of code is known to reduce the
number of errors or bugs in the code. True

Private builds can be triggered automatically. False

_ is a measure of incoming dependencies. Afferent coupling


Capablility of your build system to handle an increase in the amount of
code that it integrates and analyzes is known as . build performance—not
sure

CI pipeline consists of .stages

Which of the tools is not mandated for integration in a CI pipeline ?

Feature branching is used to _.


Which of the tools is not used for establishing a pipeline workflow ? maven

Teamcity is a . build scheduler

CI servers use the _ expression to poll for changes. Cron

_ is a code coverage tool. Cobertura

Arrange in order- A. Running Unit Test B.Running Static Code Check


C.Check for Code Coverage D. Build Package BACD

Control flow graph is used to calculate _. Cyclo complexity

Which is the first code analysis to be executed ? unit test

You might also like