After upgrading jenkins, I did not choose to restart, and as a result, I manually turned off the service in the system. As a result, when I restarted, it reported that config.xml could not be found. The first line was the following error: org.xmlpull.v1.XmlPullParserException, and the result was an error prompt. config.xml was not found in the path of jenkins.war.bak, then https://updates.jenkins.io/download/war/ to download the previous version of jenkins.war, stop jenkins and restart it, and finally start successfully.
I encountered this problem again when starting the slave through the java web method: hudson/remoting/Launcher : Unsupported major.minor version 52.0, I don't know whether the version of maven or the version of jenkins is inconsistent with the java version of the slave. java is upgraded from 1.7 to 1.8, and after downloading the tar.gz package, add the JAVA_HOME configured with ~/.bashrc:
export PATH="/home/appops/local/conda/bin:$PATH" export JAVA_HOME=/home/appops/software/jdk1.8.0_161 export PATH=$JAVA_HOME/bin:$PATH export CLASSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar
After running source ~/.bashrc, the startup is successful through java -jar agent.jar -jnlpUrl http://XXXX:8080/computer/ssp_run5_hzbdg_201/slave-agent.jnlp -secret c94680180fea2ad8c8d2751679288956242e4f6ebcc35b97391188d3b82cbe9f.
When creating the mvn task, the error that the file cannot be found is as follows: Caused by: java.lang.NoSuchFieldError: DEFAULT_USER_SETTINGS_FILE. Then downgraded maven on master and slave from 3.5.2 to 3.3.9.
Configuration reference: https://segmentfault.com/a/1190000008373293
You can also use the following command to operate mvn test -DsuiteXmlFile=testng.xml