Jenkins tutorial 2

This article studies the use of the clearcase plug-in jenkins. By default, jenkins does not support the clearcase download tool. You must install the clearcase plug-in. 1. Install the clearcase client on the CI server. 2. Make sure that the account running jenkins has the corresponding permissions of clearcase. 3. Install the plug-in. in plug-in management, select "jenkins clearcase plug-in ". 4. Select "Base Clearcase" in the job settings ". View tag: view name. If there is a duplicate view in the existing clearcase environment, CI will automatically delete the tag of the existing view. View path: view path. Name of the view created on the clearcase view server. Config spec: configure the rule load rules: Download the rule. Confirm which content to download. Use update: If this option is selected, it indicates that the current view is updated every time. This is faster, but the files generated in the previous compilation will be retained. If this option is not selected, a new copy is generated, which is slow, but a new environment. Run the job to download the corresponding clearcase code to the CI server. This article describes how to use the ssh-slave plug-in. In windows, run the java-jar jenkins. war Command to run jenkins. In System Management> Install as windows service, you can set jenkins as a system service. In a distributed ci environment, one of multiple ci servers is the master, and the other is the slave. The master assigns jobs to different slave machines for execution, and uniformly manages and schedules all jobs. If a project needs to be compiled in both linux and windows, it can be completed through distributed compilation. The ci server in windows is the master server, and the linux ci is the slave server. After linux is compiled, the compilation result is shared to windows ci through samba, and the job on windows is triggered to continue the compilation. 1. Add nodes. It has the following parameters: a) Description: Description of the node B) Remote FS root: working directory of the node c) Labels: Label d of the node usage: you can select "only allow running jobs bound to this machine" or "use this node whenever possible" e) Launch method: indicates that the Master node controls the slave node. For linux systems with slave, select "Launch slave agents on Unix machines via SSH ". Click "Advanced" next to it and enter the ssh ip address, user name, and password. F) Availability: "keep this slave on-line as much as possible ". Make sure that the node is available as much as possible. 2. After adding nodes. You can assign jobs to different nodes. Select "Restrict where this project can be run" in the job settings, and enter the label of the node to ensure that the job runs on a node. This article studies the use of the CppCheck plug-in. 1. Cppcheck is a static check tool for C/C ++ code defects. Different from C/C ++ compilers and other analysis tools. CppCheck only checks bugs that cannot be detected by the compiler, and does not check syntax errors. 2. Install the plug-in. In plug-in management, select "Cppcheck plug-in". After installation, the "Publish Cppcheck results" option is added to the job settings. 3. Copy the CppCheck tool to a directory on the CI server. Then configure the check in the job. In "build", select "execute windows batch command ". Enter "c: \ cppcheck.exe -- enable = all -- xml c: \ code 2> result. xml" in the command ". 4. Check "publish cppcheck results" in "Post-build Actions ". In "cppcheck report xmls", enter the result. xml file name generated in step 3. In step 4, result. xml is analyzed and the analysis results are displayed in jenkins in the form of charts or text. 5. Enter the alarm threshold value in "Build status. 1) if the error ratio is lower than this value, the job is normal. 2) if the error ratio exceeds this value, the job is abnormal. 3) when the total number of errors exceeds this value, the job is unstable. 4) when the number of new errors exceeds this value, the job is unstable. 5) if the total number of errors exceeds this value, the job fails. 6) if the number of new errors exceeds this value, the job fails. 6. "Severity evaluation" indicates the levels of errors to be selected to determine the job status. 7. "Graph configuration" is a chart option, including the chart size and metrics. This article describes how to use the Robot Framework plug-in. 1. Robot Framework is a keyword-driven automatic testing Framework. The Robot Framework plug-in can count the total number of automated test cases and the number of successes and failures. 2. Install the plug-in. In plug-in management, select "Robot Framework plugin". After installation, the "Publish Robot Framework test results" option is added to the job settings. 3. Configure the Robot Framework runtime environment on the CI server. Then configure the check procedure in the job. In "build", select "execute windows batch command ". Enter "pybot test.txt" in the command, in which test.txt is the test case. Www.2cto. com4. check "publish Robot Framework test results" in "Post-build Actions ". The default value is used. 5. Run the job to view the trend chart and details. In a multi-node environment, you can set jobs to run dynamically on relatively idle nodes to improve resource utilization and speed up building. The specific settings are as follows: 1. On "Restrict where this project can be run", set the nodes on which the job can run, and separate the nodes with "|. For example, "node1 | node2 ". 2. Set the node to "only allow running jobs bound to this machine ".