Jenkins installation
To be compatible with the jdk1.7 version of the production environment, from the official website, Jenkins must be a version prior to 1.6, so download jenkins-1.596.3-1.1.noarch.rpm to install locally:
-IVH jenkins-1.596. 3-1.1. noarch.rpm
After installation, modify the Jenkins configuration file:
VI /etc/sysconfig/jenkins
According to the actual situation, modify the following two, usually Tomcat has occupied 8080 and 8009 ports:
Remember to open the corresponding port in the firewall and restart Jenkins:
Service Jenkins Restart
Open the browser and enter Http://IP: port to see that Jenkins has started:
Jenkins Configuration
With regard to the configuration of Jenkins, official website documents and web blog posts have been described in detail, here we only introduce the most basic configuration, can get Jenkins to work as soon as possible.
Click Create a new task, enter the task name, here is the MAVEN project example:
Enter a project name and description:
Source management Using SVN, it is important to note that the SVN address should be given directly to the development branch, not the entire warehouse, otherwise it could not be built:
Build the trigger and use the poll SVN update to trigger the build whenever an update is detected, and the schedule is the polling cycle, which is set to 50 minutes:
Build this column to indicate that Jenkins needs the MAVEN installation path and click the system configuration:
To find the Maven section, click the Maven Install button and enter the name and path in the input box:
After saving, do not worry about starting the build, or you will not be able to create/delete the directory due to insufficient permissions, you need to first add Jenkins to the Sudoer list:
VI /etc/sudoers
, allowing Jenkins users to allow any instruction:
Next, you can click "Build Now" on the left navigation bar, and then follow the build prompts to troubleshoot the problem:
Linux Environment Deployment Record (iii)-Jenkins installation and configuration