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

This article introduces how to use docker to deploy micro-services in jenkins. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

Build an image

The DOckerFile format is as follows

FROM java:8-jre

MAINTAINER 303600370@qq.com

ENV TZ=Asia/Shanghai

RUN ln-sf / usr/share/zoneinfo/$TZ / etc/localtime & & echo $TZ > / etc/timezone

RUN mkdir-p / gateway

WORKDIR / gateway

EXPOSE 9999

Docker build-t upms:1.0. / / Note that DockerFile is in the current directory, otherwise please specify the path

/ / View the image we generated

# docker images

REPOSITORY TAG IMAGE ID CREATED SIZE

Upms 1.0 5a85b918f97b About an hour ago 311MB

Auth 1.0 ebe9c89204a3 2 hours ago 311MB

Gateway 1.0 d569bd2776b5 2 hours ago 311MB

Register 1.0 72b8e3d9053d 6 hours ago 311MB

Jenkinsci/blueocean latest 15c11ce3d610 46 hours ago 567MB

Jenkins/jenkins latest ca03aad4393c 2 days ago 648MB

Gogs/gogs latest a9376695685c 3 days ago 90.6MB

Portainer/portainer latest 2869fc110bf7 4 weeks ago 78.6MB

Java 8-jre e44d62cf8862 3 years ago 311MB

Jenkins installation

Docker run\

-u root\

-rm\-1

-d\-- 2

-p 808014) 8080\-- 3

-p 50000VR 50000\-- 4

-v jenkins-data:/var/jenkins_home\-- 5

-v / var/run/docker.sock:/var/run/docker.sock\-- 6

Jenkinsci/blueocean-- 7

1 automatically delete the Docker container when jenkinsci/blueocean is closed (the following figure is an example). If you need to exit Jenkins, this can be kept tidy.

2 jenkinsci/blueocean runs the container (that is, "detach" mode) in the background and outputs the container ID. If you do not specify this option, the Docker log for this container that is running is output in the terminal window.

3 Mapping (for example "publish") port 8080 of the jenkinsci/blueocean container to port 8080 on the host. The first number represents the port on the host, and the last one represents the port of the container. Therefore, if you specify-p 49000 8080 for this option, you will access the Jenkins on the host through port 49000.

4 Map port 50000 of the jenkinsci/blueocean container to port 50000 on the host. This is required if you set up one or more JNLP-based Jenkins agents on other machines, which in turn interact with the jenkinsci/blueocean container (acting as a "master" Jenkins server, or "Jenkins master" for short). By default, the JNLP-based Jenkins agent communicates with the Jenkins master through TCP port 50000. You can change the port number on the Jenkins master server through the configure Global Security page. If you want to change the TCP port value of the JNLP proxy port of your Jenkins host to 51000 (for example), then you need to rerun Jenkins (through this docker run … Command) and specify this "publish" option-p 52000 Jenkins 51000, where the last value matches the changed value on Jenkins master, the first value is the port number on the host of the Jenkins host, through which the JNLP-based Jenkins agent communicates with the Jenkins host-for example, 52000.

Map the `/ var/jenkins_ home` directory in the container to the volume with the name jenkins-data. If the volume does not exist, then the docker run command will automatically create the volume for you. If you want to restart Jenkins every time (through this docker run... Command), this option is required when maintaining the Jenkins state. If you do not specify this option, Jenkins will effectively reset to the new instance after each restart.

The jenkins-data volume described in 5 can also be created by the docker volume create command: docker volume create jenkins-data instead of the mapping / var/jenkins_home directory is converted to a Docker volume, and this directory can also be mapped to a directory on the computer's local file system. For example, specifying this option-v $HOME/jenkins:/var/jenkins_home maps the container's / var/jenkins_home directory to the jenkins subdirectory in the directory on the local computer, which is usually / Users//jenkins or `/ home// jenkins`.

6 (optional / var/run/docker.sock represents the Unix-based socket that the Docker daemon listens to through it. This mapping allows the jenkinsci/blueocean container to communicate with the Docker daemon, which is required if the jenkinsci/blueocean container needs to instantiate other Docker containers. If you run a declarative pipe, its syntax contains the agent part using docker

For example, agent {docker {...}} this option is required. Read more about this on the Pipeline Syntax page.

The jenkinsci/blueocean Docker image itself. If the image has not been downloaded, this docker run command will automatically download the image for you. In addition, if any updates to this mirror have been released since the last time you ran this command, running this command again will automatically download these published mirror updates for you. Note: this Docker image can also be downloaded (or updated) independently using the following docker pull command: docker pull jenkinsci/blueocean Note: if copying and pasting the above command snippet does not work, try copying and pasting this uncommented version here:

Complete command

Docker run-u root-d-p 8080 jenkins-data:/var/jenkins_home-d-p 50000-v jenkins-data:/var/jenkins_home-v / var/run/docker.sock:/var/run/docker.sock-- restart=always jenkinsci/blueocean

After jenkins uses the default installation, login page

Create a new build task (managed as code)

Select git

Save Task-> build Task

Java service construction

New Task (add shell)

BUILD_ID=donKillMe

Api_pid= `docker ps-a | grep getaway | awk'{print $1}'`

Echo api_pid = $api_pid

If ["$api_pid"! = "]; then

Echo restart getaway

Docker restart $api_pid

Echo sleep 3s

Fi

If ["$api_pid" = = ""]; then

Echo mkdir images

Docker run-- add-host=pigx-mysql:172.17.0.1-d-p 4000 lac 4000-v / getaway:/getaway-- name getaway getaway:1.0 java-jar / getaway/getaway.jar

Echo sleep 3s

Fi

Construction

Appendix

Jenkins data address (possible)

/ / Project root directory

/ var/lib/docker/volumes/jenkins-data/_data/workspace/

/ / jar directory

/ var/jenkins_home/workspace/getaway/target/getaway.jar

/ / Log directory

/ var/lib/docker/volumes/jenkins-data/_data/workspace/getaway/logs/

Initial password directory / var/jenkins_home/secrets/initialAdminPassword

So much for sharing about how to use docker to deploy micro-services in jenkins. I hope the above content can be of some help and learn more knowledge. If you think the article is good, you can share it for more people to see.

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.