Automating Java Project Build, Packaging, and Deployment with Jenkins

Jenkins can automate the update, build, and deployment processes for Java projects, which typically use Maven for compilation and packaging, so Maven must be installed in the Jenkins environment.

Jenkins deployment of a Java project includes:

Pulling Git code;

Compiling and packaging the project with Maven;

Copying the packaged artifact to a designated test server via SCP;

Restarting Tomcat on the test server.

Step 1 – Retrieve Git code: Install the Git Parameter plugin in Jenkins (System → Manage Plugins → search and install). In a new job, configure the Source Code Management section with the Git repository URL and credentials. Set the Branch Specifier to $Branch to fetch all branches.

Step 2 – Automatic build: Use a shell build step to run Maven commands. First, change to the cloned directory, then execute: mvn -s /path/to/settings.xml clean install If only one Maven installation exists on the server, the -s option can be omitted; otherwise, specify the absolute path to the desired settings.xml. Ensure all dependent packages are available before building.

Step 3 – Upload packaged file to the test server: Configure password‑less SSH between the Jenkins server and the Java project server, then use scp to copy the Maven‑generated artifact to the test server. It is recommended to back up the existing package before overwriting.

Step 4 – Delete old PID and restart Tomcat: Use a shell command on the test server to stop Tomcat, remove the old PID, and start Tomcat again (e.g., run the provided restart script).

After completing these configurations, the Jenkins job will display all Git branches in the "Build with Parameters" screen; select the desired branch, start the build, and monitor the console output for progress and results.