Jenkins details, jenkins details

Jenkins details, jenkins details

Chapter 1 What is Jenkins?

Jenkins is a scalable continuous integration engine.

Mainly used:

1. continuously and automatically build/test software projects.

2. Monitor scheduled tasks.

Jenkins has the following features:

1. Easy to install-you only need to deploy jenkins. war to the servlet container without database support.

2. Easy to configure-All configurations are implemented through the web interface provided by OSS.

3. integrate RSS/E-mail to publish the build result through RSS or send an e-mail Notification when the build is complete.

4. Generate the JUnit/TestNG test report.

5. Distributed build supports Jenkins to allow multiple computers to build/test together.

6. File identification: Jenkins can track which build generates the jar and which build uses the jar.

7. Plug-in support: Extension plug-ins are supported. You can develop tools suitable for your team.

The origin of Jenkins

CI has become a common practice for many software development teams to ensure code quality within the entire software development lifecycle. It is a practice designed to ease and stabilize the building process of software. It helps your development team cope with the following challenges:

1. Software build automation: After the configuration is complete, the CI system will build the target software based on the preset schedule or for a specific event.

2. Build a sustainable automated check: The CI system can continuously obtain the newly added or modified checked-in source code. That is, when the software development team needs to periodically check the newly added or modified code, the CI system constantly checks whether the new Code destroys the successful building of the original software. This reduces the time and effort that developers need to spend in checking the changes in mutually dependent code (it is money to say that it is just a little bit ).

3. Build a sustainable automated test: Build the Extended Part of the check, execute a set of pre-defined test rules after the build, and trigger notifications (Email, RSS, etc.) to relevant parties after the completion.

4. Automation of subsequent processes after generation: When automated checks and tests are successfully completed, additional tasks may be required during the software build cycle, such as generating documents, packaging software, and deploying components to a runtime environment or software warehouse. In this way, the component can be provided to users more quickly.

The minimum requirement for deploying a CI system is a warehouse that can obtain source code and a project that contains the build script.

The components of the system work in the following order:

Check the code to the source code repository. The CI system creates a separate workspace for each project. When a new build is preset or requested, the source code of the source code repository is stored in the corresponding workspace. The CI system performs the Build Process in the corresponding workspace. (If the configuration exists) after the build is complete, the CI system executes a defined set of tests in a new component. After completion, a notification (Email, RSS, etc.) is triggered to the relevant parties. (If the configuration exists) if the build is successful, the component will be packaged and transferred to a deployment target (such as an application server) or stored as a new version in the software repository. A software repository can be a part of a CI system or an external repository, such as a file server or a website such as Java.net or SourceForge. The CI system usually initiates operations based on requests, such as instant build, report generation, or retrieval of some built components.

Jenkins is such a CI system. Previously called Hudson.

The following are some reasons for using Jenkins:

1. It is the easiest to install and configure all CI products.

2. Based on Web access, the user interface is very friendly, intuitive, and flexible. In many cases, real-time AJAX feedback is also provided.

3. Jenkins is developed based on Java (if you are a Java developer, this is very useful), but it is not limited to building Java-based software.

4. Jenkins has a large number of plug-ins. These plug-ins greatly extend Jenkins functions. They are all open-source and can be directly installed and managed on the web interface.

Jenkins goals

The main goal of Jenkins is to monitor the software development process and quickly display problems. Therefore, developers and related personnel can save time and effort to improve development efficiency.

The main function of the CI system in the entire development process is to control: when the system detects modifications in the code repository, it delegates the build task to the build process itself. If the build fails, the CI system notifies the relevant personnel and continues to monitor the repository. Its role seems passive, but it can quickly reflect the problem.

In particular, it has the following advantages:

1. All Jenkins configurations can be completed on the web interface. Some configurations such as MAVEN_HOME and Email only need to be configured once, and all projects can be used. Of course, you can also modify XML for configuration.

2. Support for Maven modules. Jenkins has optimized Maven, so it can automatically identify modules. Each Module can be configured as a job. Flexible.

3. Test Report aggregation: The test reports of all modules are aggregated, and the results are clear at a glance. Other CI is used, which is almost impossible to complete.

4. The component fingerprint (artifact fingerprint) is automatically managed for each build result component. You can conveniently browse and download the component without any configuration.

Poor memory!