Shulou(Shulou.com)06/01 Report--

This article mainly explains "how to build a continuous integrated environment with jenkins+Git". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to build a continuous integrated environment with jenkins+Git".

Continuous integration ensures that problems in the development system can be quickly found and repaired through automated construction, automated testing and automated deployment, and reduces the risk of integration failure. make the system always maintain a stable and healthy integration state in the development. Jenkins is a widely used continuous integration tool. This article records the whole process of using jenkins+Git to configure the continuous integration environment and the holes I stepped on (the holes in the jenkins process are often not configured for the first time, but when some configuration items are changed after the configuration is finished).

Tomcat8.0 download address: http://tomcat.apache.org/

Jenkins download address: http://jenkins-ci.org/

When the download is complete, drop the jenkins.war into the tomcat/webapps directory.

By default, jenkins's workspace is placed in the C:\ Users\ Account\ .Jenkins directory

If we want to change the workspace, we need to configure the JENKINS_HOME variable in the system environment variable to point it to the target workspace. It should be noted here that when tomcat starts, jenkins will not read the JENKINS_HOME variable and must restart tomcat. There is also a hole in restarting tomcat. If tomcat is started by executing the tomcat/bin/startup.bat directory from the command line, it is useless to stop tomcat alone. You must shut down the previously mentioned command line. Only then will restart tomcat,jenkins use the directory configured in JENKINS_HOME as the workspace. In addition, once the workspace is changed, all configurations that were previously too jenkins will be invalidated.

1. Add a git plug-in to jenkins

two。 Configure the location of the Git.exe in jenkins.

3. Create and configure job.

Click New Item on the left, select a free-style job, and click OK.

Select Git in the source code management tool (Source Code Management), add the Git repository, add the Git certificate, and select a branch:

With regard to the certificate, we choose the form of SSH:

If the Git warehouse has sub-repositories, we need to configure the sub-repositories. Here, select to update all the sub-repositories:

Click Save, go to the control interface of the job we just created, click Build Now, and we can begin our journey of continuous integration.

Note that the build here does not check for errors and output in build.bat, in other words, if build.bat fails, the build process will not fail. The solution is to use jenkins's Log Parser plug-in, just like using Git Plugin, to find the Log Parser plug-in in plug-in management and add it. After adding, configure Console Output Parsing in jenkins

Thank you for reading, the above is the content of "how to build a continuous integration environment with jenkins+Git". After the study of this article, I believe you have a deeper understanding of how to build a continuous integration environment with jenkins+Git, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.