Java automatic code issuing method based on Struts2 frame

Abstract

The invention discloses a Java automatic code issuing method based on a Struts2 frame. The method comprises the following steps: S1) firstly collecting online files and catalogues to be issued; S2) executing the automation incremental backup through host polling; and connecting the host through the iteration, and executing an application engineering backup script on the host to realize the total backup of the engineering application on the remote host; S3) uploading the newly issued online file from the local to an application catalogue of a remote server, and realizing the incremental synchronous production; and S4) while the uploading of all host files is over, restarting a remote application by calling a script file on the remote host. The provided Java automatic code issuing method based on the Struts2 frame is capable of realizing the automation of an issuing link through using a Java program, effectively preventing the mis-uploading and the uploading leakage of an online process,and greatly reducing the working strength.

Description

technical field [0001] The invention relates to an automatic code release method, in particular to a Java automatic code release method based on the Struts2 framework. Background technique [0002] When engaged in operation and maintenance in the mobile communication industry, one of the most important job responsibilities is to be responsible for the production environment code release of mobile-related channels (also known as "online" in the industry). At that time, the code version control tools for various channels were mainly SVN and Telelogic Synergy. SVN was used as a development version management library, while Telelogic Synergy was a production code version management library that was completely independent of SVN. A simple understanding is that the developer's code can be updated to the SVN repository at any time, but only the code that is allowed to be released to the production environment can be updated to TelelogicSynergy before going online. As configuration...

AI Technical Summary

Problems solved by technology

[0008] The following questions are listed based on the actual configuration management work on site. These factors determine that the purely manual configuration management work will cause many problems, mainly because the work pressure on the configuration personnel is high, and the work efficiency is not high. , prone to miscommunication, missed transmission, missed restarts

[0009] 1. There are more daily code releases and batch code releases per week

[0010] 2. There are many channels involved in a single go-live, and each channel requires code collection, incremental (full) backup, incremental upload, and application restart in the production environment

[0011] 3. During a single go-live process, different developers have to constantly modify code bugs, resulting in the need to frequently repeat go-live operations

[0012] 4. For batch code synchronization, complex requirements, and project code online operations, it usually lasts from 22:00 of the previous day to around 5:00 of the next day. Factors such as repetitive online operations and fatigue from staying up late will also cause configuration In the actual operation process, managers are prone to problems of code miscommunication, missing transmission, and process leakage

[0013] 5. Repeatedly logging in and operating the production environment during the online process is very prone to misoperation, which brings certain security risks to the production environment

Images