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

Jenkins continuous Integration to see how I deploy from 1 to Code Automation

Recently, I need to learn jenkins continuous integration due to work reasons. For a studious and handsome me. It's not easy to learn from him. The company is a small and medium-sized start-up company, in the deployment code, rarely use gitlab, jenkins, etc., and there is no clear production environment-test environment-online environment. The only thing you have is to write the code-log in to turn off the service, upload the code-and turn on the service. This will often lead to a lot of problems, but also bring a lot of tedious work to programmers. This is not, the company's internal consolidation, need a clear process, and in order to reduce the burden on programmers, so they want to use gitlab+jenkins to deploy the code.

Demand

Programmers submit code to gitlab, trigger jenkins automatic deployment trigger, deploy to test server and, if normal, submit to formal online environment

Environment introduction

Ubuntu18.04:

Network: intranet environment service: gitlab environment

Ubuntu16.04:

Network: intranet environment service: jenkins

Centos 7:

Network: public network environment service: php+nginx+mysql

The public network environment is a test environment, and there is no online environment. It is OK to introduce an environment. It is the same reason that the test is successfully launched.

Deployment process

Why go from 1 to automated deployment? Because I don't really want to write about the process of installation and deployment. The process is very simple, without pitfalls and difficulties. There are a lot of Baidu a little bit.

Prerequisites:

1. You need to have your own gitlab account and your own project. Of course, you can use someone else's project, but it may be troublesome to set up some permission information later. So your own is the most convenient.

2. Your public network server must be able to access private network gitlab projects, because in order to reduce errors, the public network server pull gitlab code is used. We'll talk about the details later.

3. Have a heart that is not afraid of difficulties and a handsome face.

First, install the relevant plug-ins

Click system Management-plug-in Management, and you can download the plug-in you want through the search box. When you first initialize jenkins, there is also a step to install the plug-in. Install it as hard as you can. According to your own needs!

Create a job on jenkins

1. Create a new task

2. Enter the task name-Select-Select pipeline-OK

Briefly introduce the advantages and disadvantages of these projects.

Freestyle Job

You need to add module configuration items and parameters to the page to complete the configuration

Each Job can only implement one function.

Unable to code, which is not conducive to migration and version control

Pipeline project

All parameters can be reflected as a pipeline script

You can define multiple stage to build a pipe workset

Configuration coding to facilitate Job configuration migration and version control

The script is written in the Jenkins project

Multi-branch pipeline

The advantages are the same as the pipeline

The script is written in the GitLab project (Jenkinsfile)

For multi-branch assembly lines, blog https://blog.51cto.com/12639039/2352222 is recommended.

3. Go to the configuration interface of job and click the build trigger.

General does not require configuration

Because the requirement is that the programmer submits the new code to gitlab, the jenkins triggers. So select the following option when building triggers

Please don't ignore Gitlab webhook URL: here. This webhook is used to trigger the automatic build of jenkins.

Click Advanced to create a Secret token

4. Add the webhook of step 3 to the gitlab

Fill in the randomly generated string in step 3 at url at webhook;Secret Token. Once finished, just click add.

Connectivity can be tested here.

When you notice here, you may encounter a problem: some users will report such an error when they add.

It says local network requests are not allowed. This is due to the security problems of the new version, which is very easy to solve!

Solution: log in using the gitlab administrator account.

Check both of them. Then go back and add it again.

5. Write pipeline script

There are two options, the first is to write the script directly here (warm tip, the script is written and pasted here on the editor on your computer, because the editor here is as difficult to use as eating Xiang! It's too hard. The second is to use the jenkinsfile file. I used the first one (because the demonstration is simple and easy to understand! Hey, hey, hey.

Click Save when you are finished. You can complete the creation of a job

You think it's over. The most important thing is just beginning!

III. Pipeline script compilation

Let's review the requirements again:

Programmers submit code to gitlab; automatically deploy triggers in jenkins; deploy to a test server and, if normal, submit to an official online environment. But I don't think it's any challenge. I want to add some difficulty to myself. No matter whether the deployment process is successful or not, there must be a nail message sent to the programmer's little brother's group to give them a warning!

Don't say much, explain a little bit on the code:

Warm Tip: this is the code I wrote to meet my needs, please don't copy it, of course I have the same needs at will. At the same time, the middle explanation is also explained according to my code, not deliberately to explain the grammar, please understand!

Pipeline {agent any stages {stage ("pull Code") {steps {echo "STEP 1: clone code"} stage ("Packaging Code") {steps {echo "step 2: code package" sh label:'' Script:'/ usr/bin/ssh-p 62322 root@*.* "cd / var/www/html/pipeline/mytest & & git pull & & chmod-R 777 / var/www/html/pipeline/mytest/storage & & composer install"'} stage {steps {echo "step 3: deploy package"} }} post {success {token' of dingTalk accessToken:' nailing robot The url', jenkinsUrl:' http://192.168.5.194:8080/', message:'pipeline-test code for the imageUrl:' picture was successfully deployed.' , notifyPeople:''} failure {url', jenkinsUrl:' http://192.168.5.194:8080/', message:'pipeline-test code deployment failed for token', imageUrl:' image of dingTalk accessToken:' nailing robot'. , notifyPeople:''}

Detailed explanation:

Agent

Instructs Jenkins to assign an actuator (on any available agent / node in the Jenkins environment) and workspace to the entire pipeline.

Echo

Write a simple string to the console output. Note that this is not the echo or php syntax of the shell command line. It works the same way as they do.

Stage

Defines a conceptually different subset of tasks executed throughout the pipeline (such as "Build", "Test" and "Deploy" phases), which is used by many plug-ins to visualize or Jenkins pipelined current status / progress.

Maybe this sentence is not very vivid (I was also deceived by the official text for the first time). Let's take a picture.

The last of these is the state of post processing.

In the stage block of the packaged code

Sh label:', script:'/ usr/bin/ssh root@*.* "cd / var/www/html/pipeline/mytest & & git pull & & chmod-R 777 / var/www/html/pipeline/mytest/storage & & composer install"'

This is a syntactic command generated through jenkins's fragment generator that can be executed in shell.

So, how do you use the jenkins fragment generator?

(1) Click pipeline syntax

(2) Select sh:shell script from the example step. Enter the shell command to be generated in the text box

(3) Click the generate pipeline script button to form the corresponding pipeline syntax

Post

Similar to the try statement in python. How to perform specific processing according to the results of stage execution is a problem often encountered in the actual use of Pipeline. So here post is to do the function of exception handling. At the same time, you can also understand the post-build steps in the free style (you can download the plug-in for dingding in the free style). And this post block, that is, I want to meet my own need for nail feedback. Speaking of which, in order to give you a better understanding of how to use post, I would like to explain a little more:

Usage restrictions:

Need to be written in pipeline or stage block

Note: the location of the post block must follow this principle, otherwise it will not be executed.

Supported condition presets:

Always: the preset operations in this block are performed regardless of the execution result of pipeline or stage.

Changed: the preset operation in this block will be performed only if the current state has changed after the execution of pipeline or stage.

Fixed: the preset operation in this block will be performed only when the previous run is unstable or failed, and this run ends successfully, and these two conditions are met at the same time.

Regression: the preset operation in this block will only be performed when the running state is unstable, failed or aborted, and the previous run ends successfully, and these two conditions are met at the same time.

Aborted: the preset operation in this block will only be performed when the current status of pipeline or stage is aborted. This state is usually caused by manual pipelining, and when it is generated, it is usually grayed out in the UI interface of Jenkins.

Failure: the preset operation in this block will only be performed when the current status of pipeline or stage is failed. After this state is generated, it is usually displayed in red in the UI interface of Jenkins.

Success: the preset operation in this block will only be performed when the current status of pipeline or stage is success. After this state is generated, it is usually displayed in green in the UI interface of Jenkins.

Unstable: the preset operation in this block will only be performed when the current status of pipeline or stage is unstable. Usually, a test failure or a violation of the code specification will result in this state, which is usually displayed in yellow in the UI interface of Jenkins.

Unsuccessful: the preset operation in this block is performed only when the current state of pipeline or stage is not success.

Cleanup: regardless of the state of pipeline or stage, after other conditional preset operations in post are executed, preset operations in this block are performed.

I used two, success and failure, what to do in case of success and what to do in case of failure.

If the token', of dingTalkaccessToken:' nailing robot doesn't know how to add nailing robot, just go to Baidu next door.

ImageUrl:' will append this picture to the message.

JenkinsUrl:' 's own jenkins access address'. The message sent is this link, which can be directly redirected to our jenkins.

Text messages and prompt messages sent by message:''

The person notifyPeople:' needs to notify'

At this point, the outline of my script is over. If you want to know more about the jenkins syntax, you are recommended to learn the address.

Https://jenkins.io/zh/doc/book/pipeline/ is in Chinese and very detailed. The script I write here is only to meet my personal needs, partners with similar needs can refer to!

Another warm reminder: beginners must pay attention to the writing of code blocks and try to be standardized, because only in this way can they easily make mistakes. Most code blocks of Groovy syntax can be found for half a day because of a curly brace. So try to be standard. It would be better to have an editor with Groovy syntax highlighted.

4. Test the operation of job

Click to build now

After the execution, you can see the whole process through the output of the console.

Nail message

At this point, we are done. Let your little brother programmer try to push the code.

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.