The reason for explaining the global tool configuration in advance here is that when configuring tasks later, the premise is that the global tools need to be configured, laying a good foundation first, and there will be fewer problems when configuring later
Plug-in installation: there should be gradle and nodejs that need to be searched and installed
1. Major premise description: The global tool configuration here is all for the jenkins server, that is to say, all configurations are on the jenkins server. So if there is no environment, you need to install it on the jenkins server
2. The configuration of jdk, jar project and war project all need to be used
2. Git configuration, which must be configured, as long as you want to link the code warehouse
3. Gradle configuration, automatic installation is used here, and gradle can also package java projects, which will be explained later in the series
4. Maven configuration, a tool for packaging java projects, can be installed through yum
5. Nodejs configuration, used for packaging front-end packages. The automatic installation is used here. I learned from the blog of the predecessors that this latest version seems to have problems, so I chose a previous historical version.
At present, I only configure these global configurations here. If you have other configurations, you can do them as needed.