Server set up - Getting stepped on pit (1)
I aim
Initially, the server set up, configure the environment, remote hot deployment.
It recommended to start
The following do not see, looking directly at jenkins articles. (There are aliyun build links (the god of writing))
And tortuous process
I would like to achieve a start to build server + hot deployment, want to use tomcat + maven plugin to achieve (when coming true, now that companies are using jenkins). That jenkins, began to take jenkins, here it is a simple cloth springboot project.
Connection github, and finally automatic deployment to achieve jenkins deploy war package, to achieve the deployment of a jar. Write a simple shell script. (Simply do not spray).
Unrealized: github uploaded building (trigger remote building), have the opportunity to refill the pit.
The following is purely personal note .. his original left
tomcat installation location
- /usr/local/tomcat
- find .. -name “tomcat”
java installation location
- Find a limited command whereis whereis java path
- Java.conf found under (system configuration files) etc in user / share / java
https://www.cnblogs.com/lossingdawn/p/10856199.html
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64/jre/bin/java
This operation fairy ah, hyperlinks
linux file directory
https://www.runoob.com/linux/linux-system-contents.html
maven installation directory
/root/app/maven/apache-maven-3.6.1
8080 port to display
https://blog.csdn.net/Magic_Ninja/article/details/82975659
Traditional project deployed in three ways (without looking)
The third direct look good, that is the essence of my day to write linux, tomcat context of three ways (like a)
https://cloud.tencent.com/developer/news/255843
Best Deployment? ? ? ? The results can only access the network? ?
https://www.jb51.net/article/115660.htm
https://www.cnblogs.com/ouyxy/p/6663811.html
These are ordinary items
Seek death to the pit, but also to look at from the beginning
Create a maven
https://blog.csdn.net/zz210891470/article/details/53737883
Why is this tomcat-maven remote repository is not ah
To add dependent
<dependency> <groupId>org.apache.tomcat.maven</groupId> <artifactId>tomcat7-maven-plugin</artifactId> <version>2.2</version> <type>maven-plugin</type></dependency>https://www.cnblogs.com/luchangyou/p/7573481.html
Citie end. I do not do.
Asked a friend, do so now out of fashion
Tomcat comparison of the difference jenkins
https://blog.csdn.net/Magic_Ninja/article/details/82975659
tomcat9 stuck solutions
https://blog.csdn.net/queshuihaimian/article/details/78117356
jenkins turn up here