This article introduces developers to common continuous integration DevOps interview questions to help you successfully get the offer you want.
Q1: What is continuous integration?
I would suggest that you start with the minimum definition of continuous integration to answer this question. This is a research and
development practice that requires developers to integrate code into a shared code base multiple times a day. Then automatically build to verify each code modification, so that the team can find the problem as soon as possible.
1. The developer clones the code to a private workspace.
2. After coding, they will submit the changes to the shared code base (version control warehouse).
3. The CI server monitors the code warehouse and checks out changes when they occur.
4. Immediately after the CI server extracts these changes to build, run the unit and integrate the test.
5. The CI server will immediately inform the team whether the construction is successful or not.
6. If the build fails, the CI server will send an alert to the team.
7. The R & D team will solve the problem as soon as possible.
8. This process will be repeated continuously.
Q2: Why does the R & D team need continuous integration of development and testing?
For this answer, you should focus on the need for continuous integration. I suggest that you mention the following explanation in your answer:
Continuous integration of
development and testing improves software quality and reduces delivery time by replacing traditional testing practices after all development is completed. It allows the development team to detect and locate problems as early as possible, because developers need to integrate code into the code warehouse multiple times (or more frequently), and then automatically verify each integration.
Q3: What are the success factors of continuous integration?
Here, you must mention the requirements for continuous integration. You can include the following points in your answer:
Maintain code warehouse
Automated construction
Let build self test
Everyone makes sure that the changes have been submitted to the baseline every day
Keep building fast
Test in the clone environment of the production environment
R & D team can easily obtain the latest deliverables
Everyone can see the results of the latest build
Automatic deployment
Q4: How to migrate or copy Jenkins from one server to another server?
I will accomplish this by copying the jobs directory from the old server to the new server. There are many ways to do this:
Simply copy the corresponding job directory to move the job from one Jenkins server to another.
Make a copy of an existing job by cloning the job directory with another name.
Rename the existing job by renaming the directory. Please note that if you change the job name, you need to change all the jobs that try to call the renamed job.
Q5: How to create backup and copy files in Jenkins?
This question can be answered very directly: to create a backup. All you need to do is to regularly back up the JENKINS_HOME directory. This includes all build job configurations, slave node configurations, and build history. To create a backup of Jenkins, just copy this directory, you can also copy the job directory or rename the directory.
Q6: How to configure Jenkins job?
The solution to this answer is to first mention how to create a job: go to the Jenkins homepage, select "New Job", and then select "Build a free-style software project". Then you can set the elements of this freestyle job:
Optional SCM, such as CVS or Subversion where the source code is located.
Triggers used to control when Jenkins executes the build.
Some kind of build script used to perform the actual work of the build (ant, maven, shell script, batch file, etc.)
Optional steps to gather information from the build, such as archiving artifacts, recording javadoc, and test results.
Configure the steps to notify other people / systems of the build result, such as sending emails, instant messages, updating issue trackers, etc.
Q7: List some useful plugins in Jenkins
Below I will mention some important plugins:
Maven 2 project
Amazon EC2
HTML publisher
Copy artifact
Join
Green Balls
I think these are the most useful plugins, you can also add plugins that you think are useful. But make sure to mention the above plugins first, and then add your own plugins.
Q8: How to ensure the safety of Jenkins?
Make sure that the
global security configuration item is turned on.
Make sure that Jenkins is integrated with the corporate employee directory with appropriate plug-ins.
Make sure that the permission access setting for the project matrix is enabled.
Automate the process of setting permissions / privileges in Jenkins through custom version control scripts.
Restrict physical access to Jenkins data / folders.
Conduct regular safety audits.
