Jenkins
Interview Questions
Continuous
Integration (CI)
Continuous
Integration (CI) is a cornerstone of modern software development. When CI is
introduced into an organization, it radically alerts the way teams think about
the whole development process.
A
good CI infrastructure can streamline the development process right through to
deployment. Help detect and fix bugs faster, provide a useful dashboard for
both developers and non-developers.
Ultimately,
help teams deliver more real business value to the end user.
Features
of Continuous Integration
- Monitors source version control system for changes. Whenever a change is detected, CI tool automatically compiles and test your applications.
- Automatically monitoring code quality and code coverage metrics.
- Combinate with automated end-to-end acceptance test.
- Accelerated delivery by helping you automate the deployment process.
- CI has help identify and fix integration and regression issue faster.
- CI can open and facilitate communication channels between team members and encourage collaborative problem solving and process improvement.
Why
we need to implement a robust and comprehensive CI for DevOps?
CI
is a mindset as much as a tool set. To get the most out of CI, a team needs to
adopt a CI mentality.
Project
must have a reliable, repeatable and automated build process, involving no
human intervention.
Fixing
broken builds should take an absolute priority, and not be left to stagnate.
The
deployment process should be automated, with no manual steps involved.
CI
server depends to a great extent on the quality of your test, the team needs to
place a very strong emphasis on high quality test and testing practice.
No comments:
Post a Comment