Using Docker+jenkins+python3 environment to build a super detailed tutorial

Preface:

After the automation is written, it needs to be run on the server every day. I encountered such a problem. The Jenkins container was installed in docker, and then the code was pulled from git and found that the code was in the directory of the jenkins container. When running, it prompted that the python environment and third-party libraries were not installed.

There are three solutions:

The first method: When starting the Jenkins container, mount the container directory to the host directory for execution (this method cannot be implemented) Pass

The second method: Create a local node on Jenkins, pull the code to the local and run the local project (it is more convenient to use on the local machine, but the limitations are relatively small)

The third method: Repackage the jenkins image, install the python3 environment in the jenkins image and execute the project in the container (the steps are cumbersome, but it will be used permanently in the future)

The first and second methods require that Docker and Jenkins images be installed on the server.

1. Install Docker

Install Docker https://www.runoob.com/docker/docker-tutorial.html

2. Install jenkisn image

1. Find the image on docker docker search jenkins
  
2. Download the image you need docker pull jenkinsci/blueocean
  
3. Check whether the docker images are downloaded successfully
  
4. Start the downloaded image docker run -d -p 10240:8080 -p 10241:50000 -v /jenkins_autotest/jenkins_home:/var/jenkins_home -v /etc/localtime:/etc/localtime -e JAVA_OPTS=-Duser.timezone=Asia/Shanghai --name jenkint_test jenkinsci/blueocean
 
#Description: docker run -d: run the container in the background -p: specify the port mapping of the container -p 10240:8080 means mapping the 8080 port of the container to the 10240 port of the host. To map multiple ports, use -p 8082:8080 -p 8083:8081
   -v: mount the host directory and the directory in the docker container /Users/songpeilun/jenkins_home local host absolute directory; /var/jenkins_home container directory (mount the container directory locally)
   -v:/etc/localtime:/etc/localtime Synchronize local time and container time -e JAVA_OPTS=-Duser.timezone=Asia/Shanghai Set container time to Shanghai time (otherwise the container time and local time will differ by 8 hours)
   --name jenkint_test Set the name of the container to jenkinsci/blueocean Select the image name to start the container (latest will be added to the default image. If you pull the image you created, add your own version number jenkinsci/blueocean: version number TAG)

   ⚠️ When mounting a local directory in the container directory, be sure to grant permissions to the local folder: chmod 777 jenkins_home

Enter docker images to check whether the jenkins image is installed successfully

docker images 

Check if the container is running

docker ps

It can be seen that there is already a running container jenkins in docker

This means that Jenkins has been installed and you can now start Jenkins.

3. Start Jenkins

Enter the server IP + port number in the browser http://47.99.98.250:10240/ If you cannot access it, please turn off the system firewall

There are two ways to view the password. The first is to view it in the server's container, and the second is to view it in the mapped local (provided that you have mapped the local directory)

Okay, Jenkins has been installed here.

View the password in the container: cat /var/jenkins_home/secrets/initialAdminPassword
Map local directory: cat /Users/songpeilun/jenkins_home/secrets/initialAdminPassword
#/Users/songpeilun/jenkins_home local mapping directory address

3. Method 2: Create a new local node

Let's talk about the specific logic of method 2. It mainly creates a new local node of Jenkins and uses the new node to pull the code on git to the local (host) to execute the code.

This method is mainly suitable for a local environment that already has a python3 environment. You can directly run automation and use local continuous integration to achieve daily automation reports (disadvantages: because the local node uses the host machine address as the IP, you need to open the computer and jenkins address every time and the external network cannot access it. The limitation is small)

Step 1: Install the SSH Agent plugin in Jenkins

Install the ssh agent plug-in system settings - plug-in management - optional plug-ins and enter ssh agent search

Step 2: Add new nodes

System Settings - Node Management - New Node (Node names cannot be repeated)

illustrate:

Node name: Use English characters instead of Chinese characters (there will be a warning when selecting a node when creating a project!)

Node description: optional

Number of executors: The number of nodes running simultaneously

Remote working directory: The local working directory (/Users/songpeilun/jenkins) requires a user with root privileges to have full permissions on this file

Tags: optional

Usage: Use this node whenever possible

Startup method: Launch agents via SSH

Host: The network IP address of this machine (Network-Network Settings-IP)

Credentials: Select the local account and password that have been added

Host Key Verification Strategy: Non verifying Verification Strategy

Availability: Try to keep the agent online

Node properties --git: git installation path

Then start the node and it will indicate successful startup. Then check whether there is a node file in the local host directory folder.

3. Method 3: Install Python 3 environment in the container

Let's talk about the specific logic of method 3. It mainly runs the code in the container. Git pulls the code into the container by default without mapping and directly executes the code in the container (advantages: does not occupy the server's resource size and can be started at any time; does not require local startup services and can directly use the server address. Disadvantages: installation is a bit troublesome 😈)

Step 1: You need to enter the Jenkins container　　

docker exec -itu root container id /bin/sh

There are 2 ways to install python3

1. Weget installation (not recommended, basically the same as the current installation method, you need to install some dependent packages first, such as gcc, etc.)

2.apk add installation (this version is alpine: apk add, which can be installed quickly)

Finally, pay attention to the system version issue:

If it is centos, it is yum; if it is ubuntu, it is apt-get; if it is alpine, it is apk

Step 2: Install python3 using apk

cd /etc/apk/
echo "https://mirrors.ustc.edu.cn/alpine/v3.6/main/" > repositories
echo "https://mirrors.ustc.edu.cn/alpine/v3.6/community/" >> repositories

Update the apk source so that the download is faster

apk update

Step 3: Use apk add to install the python3 environment

apk add python3

Step 4: Update pip3

pip3 install --upgrade pip

Verify the Python environment python -V
Pip3 -V

After the above installation is successful, you can install the plug-in of the third-party library, which is halfway done.

Install the plugin according to your project needs. Here is my project as an example.

Step 5: Install Python third-party libraries

First create the requirements.txt file

pip freeze > requirements.txt

pip install -r requirements.txt

Then use vi requirements.txt to open the file for editing

base64-test0926==1.0.0
        PyMySQL==1.0.2
        pytest==6.2.3
        python-jenkins==1.7.0
        PyYAML==5.4.1
        redis==3.5.3
        requests==2.25.1
        SQLAlchemy==1.4.10
        urllib3==1.26.4
        wheel==0.36.2
        allure-pytest==2.8.40
        allure-python-commons==2.8.40

The last two require Allure report configuration before installation, otherwise an error will be reported.

⚠️ If the installation goes wrong, don't worry and slowly find out the reason. I spent a long time looking for the reason after the error before. It was because of the lack of greenlet plug-in (I will provide you with a method later)

If there are no problems, the installation has been successful. You can cp your own code into the container to test it. If there is no problem, you can package the image

Copy local files to the container xx directory

docker cp /Users/songpeilun/python_data/allure-2.13.0.zip jenkint_test:/xx directory

I use the Allure report here so I need to install it

Step 6: Install the allure report

Allure is a decompressed package. Here is one for you. After downloading, copy it to the container and decompress it.

Link: https://pan.baidu.com/s/1JbBXOfA0j6saZh7H8RMipw Password: qfnv

#Unzip the file in the container unzip allure-2.13.0.zip

#Configure environment variables vi /etc/profile
Add after PATH: $PATH:/allure-2.13.0/bin (the full path of allure)
source /etc/profile Save and take effect

Step 7: Verify allure

allure --version

4. Packaging/Uploading Images

Stay tuned for continued updates...

5. Configure the Jenkins environment

This is the end of this article about the super detailed tutorial on building an environment using Docker+jenkins+python3. For more relevant content about the Docker+jenkins+python3 environment, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope you will support 123WORDPRESS.COM in the future!