CN107015842B - Server-side program compiling and publishing management method and system - Google Patents
Server-side program compiling and publishing management method and system Download PDFInfo
- Publication number
- CN107015842B CN107015842B CN201710209399.8A CN201710209399A CN107015842B CN 107015842 B CN107015842 B CN 107015842B CN 201710209399 A CN201710209399 A CN 201710209399A CN 107015842 B CN107015842 B CN 107015842B
- Authority
- CN
- China
- Prior art keywords
- server
- version
- program
- tested
- compiling
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a management method for compiling and releasing a server-side program, which comprises the following steps: presetting a version sending time table of a version information database of a query server side; inquiring a server-side version information database according to the time table to obtain a to-be-tested version list and a tested version list in the time period; according to the version list to be tested, compiling the programs one by one and issuing the programs to a test environment; according to the tested version list, compiling the programs one by one and releasing the programs to a production environment; and acquiring and storing state information, wherein the state information comprises a release result. The method realizes automatic compiling and releasing of the version according to the version definition information, records the state information of compiling and releasing, and improves the efficiency of upgrading the version at the server side.
Description
Technical Field
The invention relates to the technical field of server-side version upgrading, in particular to a management method and a management system for compiling and releasing a server-side program.
Background
In the actual development project, how to develop, compile and distribute services efficiently becomes an urgent problem. In the process of developing software by many software companies, compiling and releasing are completed by manpower, which is time-consuming, labor-consuming and easy to make mistakes.
Disclosure of Invention
The invention provides a management method and a management system for compiling and releasing a server-side program, which realize automatic compiling and releasing of version information, record the state information of compiling and releasing and improve the efficiency of upgrading the server-side version.
The technical scheme for solving the technical problems is as follows: a management method for compiling and publishing a server-side program comprises the following steps:
step 1, presetting a time schedule for inquiring a server-side version information database;
step 2, inquiring the server-side version information database according to the time table to obtain a to-be-tested version list and a tested version list;
step 3, according to the version list to be tested, compiling the program of the version to be tested one by one and issuing the compiled program to a test environment;
step 4, according to the tested version list, compiling the tested versions one by one and releasing the compiled versions to a production environment;
and 5, acquiring and storing state information, wherein the state information comprises preset schedule state information, acquired version list state information and compiled and published program file state information.
The invention has the beneficial effects that: by presetting the query schedule, the server-side version information database can be automatically queried to obtain the version list after the time is reached, so that automatic obtaining is realized, time and labor are saved, the version list is automatically obtained, the problem of omission of version information needing program compiling is avoided, and the version upgrading efficiency is guaranteed. Meanwhile, in the processes of presetting a schedule, acquiring a version list and compiling and publishing a program, the state information is monitored and recorded in real time, the visualization of the state information is realized, an administrator can acquire the states of the compiling and publishing processes of the version program by checking the state information, the problem can be positioned, and the efficiency of upgrading the version at the server end is improved.
Further, the method further comprises:
and 5: and sending the state information to an administrator terminal, wherein the state information further comprises a fault reason.
The invention has the further beneficial effects that: the method has the advantages that the state information is recorded in real time in the process of releasing the server-side new version and upgrading the server-side version, and is sent to the administrator terminal, so that a system administrator can know the problems occurring in the process of upgrading the server-side version conveniently in time, the problem of releasing the version is solved at the first time, the passive mode is changed into the active mode, and the version upgrading efficiency is improved.
Further, the step 1 further comprises:
the method comprises the steps of obtaining server side version information and first xml configuration information corresponding to the server side version information, and storing the server side version information and the first xml configuration information to a server side version information database so as to compile and release a program.
The invention has the further beneficial effects that: the version list can be automatically obtained according to the preset time schedule, and the version upgrading efficiency is improved.
Further, the step 3 specifically includes:
step 3.1, acquiring version information corresponding to the version to be tested according to the version list to be tested;
step 3.2, acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list;
step 3.3, closing the running program of the server in the application program server and backing up the original program file corresponding to the server;
step 3.4, after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, storing the program file and the second xml configuration information to the application program server;
step 3.5, checking whether the program file in the application program server is correct according to the file release list, if so, restarting the server terminal in the application program server, if the restart is successful, finishing the tasks of program compiling and test environment releasing, if the restart is unsuccessful, restoring and starting the server terminal according to the original program file, and finishing the tasks of test environment releasing; otherwise, restoring and starting the server side according to the original program file, and ending the task issued by the test environment.
Further, the step 4 specifically includes:
step 4.1, acquiring version information corresponding to the tested version according to the tested version list;
step 4.2, acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list;
step 4.3, closing the running program of the server in the application program server and backing up the original program file corresponding to the server;
step 4.4, after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, storing the program file and the second xml configuration information to the application program server;
step 4.5, checking whether the program file in the application program server is correct or not according to the file release list, if so, restarting the server side in the application program server, if so, detecting whether communication between the server sides is successful or not, if so, finishing a task of compiling a program and generating environment release, if not, restoring and starting the server side according to the original program file, and finishing the task of producing the environment release; otherwise, restoring and starting the server end according to the original program file, and ending the task issued by the production environment.
The invention has the further beneficial effects that: the version information to be tested is firstly tested in a program compiling environment, whether a corresponding program file of the version information runs normally after the version information is compiled in a program is tested, if the version information runs normally, after the test is finished, the version state becomes tested, the program compiling production test is directly carried out on the version information, the version information needs to be compiled again in the program compiling production test, the program file is stored in an application program server, after the test server end can run normally, communication check needs to be carried out on the server end, whether communication between two or more server ends is normal is checked, if the communication is normal, the version information successfully generates version release information, and the version information does not need to be modified. If the program file is not normally operated during the program compiling environment test, the version information needs to be modified, and after the test is finished and the version state becomes tested, the program compiling production test is carried out on the version information when the server-side version information database is inquired next time. The xml configuration information corresponding to the version information comprises a file release list, the file release list is a list of version release information obtained by compiling the version information, whether the compiled program files are complete and accurate is checked according to the file release list, and the version release accuracy of the server side is improved.
A management system for server-side program compilation and release, comprising:
the schedule presetting module is used for presetting a schedule for inquiring the server-side version information database;
the version list acquisition module is used for inquiring the server-side version information database according to the schedule preset by the schedule presetting module to acquire a to-be-tested version list and a tested version list;
the program compiling and releasing module is used for compiling the to-be-tested versions one by one and releasing the to-be-tested versions to a testing environment according to the to-be-tested version list acquired by the version list acquiring module; according to the tested version list obtained by the version list obtaining module, compiling programs of the tested versions one by one and releasing the compiled programs to a production environment;
and the state information storage module is used for acquiring and storing state information, wherein the state information comprises the state information of the schedule preset module preset schedule, the state information of the version list acquired by the version list acquisition module, and the state information of the program file compiled and issued by the program compiling and issuing module.
The invention has the beneficial effects that: the query timetable is preset by the timetable presetting module, the version list acquiring module queries the server-side version information database to acquire the version list after the time is reached, so that automatic acquisition is realized, time and labor are saved, the version list is automatically acquired, the problem of omission of version information needing program compiling is avoided, and the efficiency of version upgrading is ensured. Meanwhile, in the process of presetting a schedule, acquiring a version list, compiling and releasing a program, the state information storage module monitors and records state information in real time, visualization of the state information is achieved, an administrator can check the state information to acquire the states of the process of compiling the version program and releasing the version, the problem can be positioned, and the efficiency of upgrading the version at the server side is improved.
Further, the state information storage module is further configured to send the state information to an administrator terminal, where the state information further includes a fault cause.
Further, the schedule presetting module is further configured to obtain server-side version information and first xml configuration information corresponding to the server-side version information, and store the server-side version information and the first xml configuration information in a server-side version information database, so as to compile and release a program.
Further, the compiling and issuing the program by the program compiling and issuing module and issuing the program to the test environment specifically includes:
acquiring version information corresponding to the version to be tested according to the version list to be tested; acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list; closing the running program of the server side in the application program server and backing up the original program file corresponding to the server side; after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, the program file and the second xml configuration information are stored in the application program server; checking whether the program file in the application program server is correct or not according to the file release list, if so, restarting the server terminal in the application program server, if so, finishing program compiling and testing environment release version list, if not, restoring and starting the server terminal according to the original program file, and finishing testing environment release tasks; otherwise, restoring and starting the server side according to the original program file, and ending the task issued by the test environment.
Further, the compiling and publishing the program by the program compiling and publishing module to the production environment specifically comprises:
acquiring version information corresponding to the tested version according to the tested version list; acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list; closing the running program of the server side in the application program server and backing up the original program file corresponding to the server side; after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, the program file and the second xml configuration information are stored in the application program server; checking whether the program file in the application program server is correct or not according to the file release list, if so, restarting the server terminal in the application program server, if successfully restarting, detecting whether communication between the server terminals is successful or not, if so, finishing tasks of program compiling and generating environment release, if not, restoring and starting the server terminal according to the original program file, and finishing tasks of the production environment release; otherwise, restoring and starting the server end according to the original program file, and ending the task issued by the production environment.
Drawings
Fig. 1 is a schematic flowchart of a management method for compiling and publishing a server-side program according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a management method for compiling and publishing a server-side program according to a second embodiment of the present invention;
FIG. 3 is a schematic flow chart of step 130 of FIG. 2;
FIG. 4 is a schematic flow chart of step 140 in FIG. 2;
fig. 5 is a schematic structural diagram of a management system for compiling and publishing a server-side program according to a third embodiment of the present invention.
Detailed Description
The principles and features of this invention are described below in conjunction with the following drawings, which are set forth by way of illustration only and are not intended to limit the scope of the invention.
Example one
A management method 100 for server-side program compilation and publishing, as shown in fig. 1, includes:
step 110, presetting a time schedule for inquiring a server-side version information database;
step 120, inquiring a server-side version information database according to the time schedule to obtain a to-be-tested version list and a tested version list;
step 130, according to the version list to be tested, compiling the program of the version to be tested one by one and issuing the compiled program to a test environment;
step 140, according to the tested version list, compiling the tested versions one by one and releasing the compiled versions to a production environment;
and 150, acquiring and storing state information, wherein the state information comprises preset schedule state information, acquired version list state information and compiled and published program file state information.
It should be noted that, step 130 and step 140 may be performed simultaneously, or may be performed sequentially.
Example two:
alternatively, as an embodiment of the present invention, as shown in fig. 2, the method 100 includes:
step 110, presetting a time schedule for inquiring a server-side version information database;
step 120, inquiring a server-side version information database according to the time schedule to obtain a to-be-tested version list and a tested version list;
step 130, according to the version list to be tested, compiling the program of the version to be tested one by one and issuing the compiled program to a test environment;
step 140, according to the tested version list, compiling the tested versions one by one and releasing the compiled versions to a production environment;
step 150, obtaining and storing state information, wherein the state information comprises preset schedule state information, version list state information and program file compiling and publishing state information;
and step 160, sending the state information to the administrator terminal, wherein the state information further comprises a fault reason.
Specifically, step 110 further includes: and acquiring the server-side version information and the corresponding first xml configuration information, and storing the server-side version information and the first xml configuration information into a server-side version information database so as to compile and release the program. And the version information of the server is inquired when the time set in the schedule is reached, and the subsequent operation execution of the release version is carried out. The schedule is a schedule for querying the server-side version information database, namely a release schedule (release version schedule).
The server-side version information comprises version states which are divided into development, to-be-tested, tested and released. The version state of the initial version is in development, the release version list of the version state to be tested is the single server side running test for the version information of the server side and the compiled program file, and the release version list of the tested version state is the single server side running test for the version information of the server side and the compiled program file and detects whether the communication between a plurality of server sides is normal.
For example, the schedule is set to 8-point 30-point query and 10-point query. Then, inquiring the server-side version information database at 8 points and 30 points in time, finding out a to-be-tested version list with the version state to be tested according to the version information in the database, finding out a tested version list with the version state to be tested, respectively compiling and releasing the versions in the two lists by the version information program, and if the tested version and the to-be-tested version do not exist in the database, inquiring the server-side version information database again at 10 points. And the automation of program compiling and releasing of the version information is realized, and the version releasing efficiency is improved.
Specifically, as shown in fig. 3, step 130 in the second embodiment includes:
step 131, acquiring version information corresponding to the version to be tested according to the version list to be tested;
step 132, acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list;
step 133, closing the running program of the server side in the application server and backing up the original program file corresponding to the server side;
step 134, after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, storing the program file and the second xml configuration information to an application program server;
step 135, checking whether the program file in the application program server is correct according to the file release list, if so, restarting the server end in the application program server, if the restart is successful, completing the tasks of program compiling and testing environment release, if the restart is unsuccessful, restoring and starting the server end according to the original program file, and ending the tasks of testing environment release; otherwise, restoring and starting the server side according to the original program file, and ending the task issued by the test environment.
Specifically, as shown in fig. 4, step 140 in the second embodiment includes:
step 141, obtaining version information corresponding to the tested version according to the tested version list;
step 142, acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list;
step 143, closing the running program of the server end in the application program server and backing up the original program file corresponding to the server end;
step 144, after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, storing the program file and the second xml configuration information to an application program server;
step 145, checking whether the program file in the application program server is correct according to the file release list, if so, restarting the server side in the application program server, if successfully restarting, detecting whether the communication between the server sides is successful, if so, finishing the tasks of compiling the program and generating the environment release, if not, restoring and starting the server side according to the original program file, and finishing the tasks of producing the environment release; otherwise, restoring and starting the server side according to the original program file, and ending the task issued by the production environment.
The method comprises the steps that version information to be tested is tested in a program compiling environment, whether a program file runs normally after the version information is compiled by a program is tested, if the program file runs normally, after the test is finished, the version state becomes tested, the program compiling production test is directly carried out on the version information, the program compiling is required to be carried out on the version information again in the program compiling production test, the program file is stored in an application program server, after the test server can run normally, communication check needs to be carried out on the server, whether communication between two or more server ends is normal is checked, if the communication is normal, the version information successfully generates version release information, and the version information does not need to be modified.
If the program file is not normally operated during the program compiling environment test, the version information needs to be modified, and after the test is finished and the version state becomes tested, the program compiling production test is carried out on the version information when the server-side version information database is inquired next time. Therefore, one server-side version information needs to be compiled and published twice.
The first xml configuration information corresponding to the version information comprises a file release list, the file release list is a list of version release information obtained by compiling the version information, whether compiled program files are complete or not is checked according to the file release list, and accuracy of compiling and releasing of the server-side program is improved.
For example, if the version status of the version information of the server a is to be tested, then a program compiling environment test version list is issued, after the version information is compiled, the program file and the configuration information are respectively saved to an application program server (i.e., a target server), the environment test is completed, and the version status is changed to be tested. When the program file compiled by the version information runs normally according to the release state information and the database is queried next time, the version state of the version information of the server A is the tested state, then a program compiling production test version list is released next time, the version information is compiled again, and the program file and the configuration information are saved to the target server again to complete production test. When the version information of the server A is the tested state, the program compiling production test version list can be released next time. Therefore, one server-side version information needs to be compiled and published twice.
It should be noted that, when performing a program compiling environment test and a program compiling production test, the program compiling and the environment test are performed one by one on the version information in the to-be-tested version list, and the program compiling and the generation test are performed one by one on the version information in the tested version list, for example, if the to-be-tested version list has the version information of the server side a and the version information of the server side B, the program compiling and the environment test of the version information of the server side a may be performed first, and then the program compiling and the environment test of the version information of the server side B may be performed according to the obtained sequence. In addition, the program compiling environment test and the program compiling production test can be carried out synchronously.
In addition, it should be noted that, in the server-side version upgrading process, the state information is recorded in real time, and each time the environmental test and the generation test of one version information are completed, the state information is sent to the administrator terminal, so that a system administrator can conveniently know the problems occurring in the server-side version upgrading process in time, and the problems are solved in the first time, and are changed from passive to active, so that the version upgrading efficiency is improved.
Example three:
a server-side program compilation and distribution management system 200, as shown in fig. 5, comprising:
the schedule presetting module is used for presetting a schedule for inquiring the server-side version information database;
the version list acquisition module is used for inquiring the server-side version information database according to the schedule preset by the schedule presetting module to acquire a to-be-tested version list and a tested version list;
the program compiling and releasing module is used for compiling the program of the version to be tested one by one according to the version list to be tested acquired by the version list acquiring module and releasing the compiled program to the testing environment; according to the tested version list obtained by the version list obtaining module, compiling the programs of the tested versions one by one and releasing the compiled programs to a generating environment;
and the state information storage module is used for acquiring and storing state information, wherein the state information comprises the state information of a schedule preset by the schedule preset module, the state information of a version list acquired by the version list acquisition module and the state information of a compiling and publishing program file.
The state information storage module is further used for sending the state information to the administrator terminal, wherein the state information further comprises a fault reason.
The schedule presetting module is also used for acquiring the server-side version information and the corresponding first xml configuration information, and storing the server-side version information and the first xml configuration information to a server-side version information database so as to compile and release the program.
The compiling and issuing module for the program compiling and issuing module and issuing the program compiling and issuing module to the test environment specifically comprises:
acquiring version information corresponding to the version to be tested according to the version list to be tested; acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list; closing an operating program of a server side in an application program server and backing up an original program file corresponding to the server side; after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, the program file and the second xml configuration information are stored in an application program server; checking whether the program file in the application program server is correct or not according to the file release list, if so, restarting the server end in the application program server, if so, finishing the tasks of program compiling and testing environment release, if not, restoring and starting the server end according to the original program file, and finishing the tasks of testing environment release; otherwise, restoring and starting the server side according to the original program file, and ending the task issued by the test environment.
The compiling and publishing module for compiling and publishing the program to the production environment specifically comprises:
acquiring version information corresponding to the tested version according to the tested version list; acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list; closing an operating program of a server side in an application program server and backing up an original program file corresponding to the server side; after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, the program file and the second xml configuration information are stored in an application program server; checking whether a program file in an application program server is correct or not according to a file release list, if so, restarting a server end in the application program server, if successfully restarting, detecting whether communication between the server ends is successful or not, if so, finishing a task of compiling the program and generating environment release, if not, restoring and starting the server end according to an original program file, and finishing a task of producing the environment release; otherwise, restoring and starting the server side according to the original program file, and ending the task issued by the production environment.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (8)
1. A management method for compiling and releasing a server-side program is characterized by comprising the following steps:
step 1, presetting a time schedule for inquiring a server-side version information database;
step 2, inquiring the server-side version information database according to the time table to obtain a to-be-tested version list and a tested version list;
step 3, according to the version list to be tested, compiling the program of the version to be tested one by one and issuing the compiled program to a test environment;
step 4, according to the tested version list, compiling the tested versions one by one and releasing the compiled versions to a production environment;
step 5, acquiring and storing state information, wherein the state information comprises preset schedule state information, version list state information and program file compiling and publishing state information;
the step 1 further comprises:
the method comprises the steps of obtaining server side version information and first xml configuration information corresponding to the server side version information, and storing the server side version information and the first xml configuration information to a server side version information database so as to compile and release a program.
2. The method for managing the compilation and release of a server-side program according to claim 1, further comprising:
and 6, sending the state information to an administrator terminal, wherein the state information further comprises a fault reason.
3. The method for managing the compilation and release of a server-side program according to any one of claims 1 to 2, wherein the step 3 specifically includes:
step 3.1, acquiring version information corresponding to the version to be tested according to the version list to be tested;
step 3.2, acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list;
step 3.3, closing the running program of the server in the application program server and backing up the original program file corresponding to the server;
step 3.4, after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, storing the program file and the second xml configuration information to the application program server;
step 3.5, checking whether the program file in the application program server is correct according to the file release list, if so, restarting the server terminal in the application program server, if the restart is successful, finishing the tasks of program compiling and test environment releasing, if the restart is unsuccessful, restoring and starting the server terminal according to the original program file, and finishing the tasks of test environment releasing; otherwise, restoring and starting the server side according to the original program file, and ending the task issued by the test environment.
4. The method for managing the compilation and release of a server-side program according to any one of claims 1 to 2, wherein the step 4 specifically includes:
step 4.1, acquiring version information corresponding to the tested version according to the tested version list;
step 4.2, acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list;
step 4.3, closing the running program of the server in the application program server and backing up the original program file corresponding to the server;
step 4.4, after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, storing the program file and the second xml configuration information to the application program server;
step 4.5, checking whether the program file in the application program server is correct or not according to the file release list, if so, restarting the server side in the application program server, if so, detecting whether communication between the server sides is successful or not, if so, finishing a task of compiling a program and generating environment release, if not, restoring and starting the server side according to the original program file, and finishing the task of producing the environment release; otherwise, restoring and starting the server end according to the original program file, and ending the task issued by the production environment.
5. A management system for server-side program compilation and release, comprising:
the schedule presetting module is used for presetting a schedule for inquiring the server-side version information database;
the version list acquisition module is used for inquiring the server-side version information database according to the schedule preset by the schedule presetting module to acquire a to-be-tested version list and a tested version list;
the program compiling and releasing module is used for compiling the to-be-tested versions one by one and releasing the to-be-tested versions to a testing environment according to the to-be-tested version list acquired by the version list acquiring module; according to the tested version list obtained by the version list obtaining module, compiling programs of the tested versions one by one and releasing the compiled programs to a production environment;
the state information storage module is used for acquiring and storing state information, wherein the state information comprises the state information of a schedule preset by the schedule presetting module, the state information of a version list acquired by the version list acquiring module and the state information of a program compiling and publishing module compiling and publishing program files;
the schedule presetting module is further used for acquiring server side version information and first xml configuration information corresponding to the server side version information, and storing the server side version information and the first xml configuration information to a server side version information database so as to compile and release a program.
6. The system according to claim 5, wherein the status information saving module is further configured to send the status information to an administrator terminal, and wherein the status information further includes a fault cause.
7. The system for managing the compilation and release of a server-side program according to any one of claims 5 to 6, wherein the compiling and releasing module for compiling and releasing the program to the test environment specifically comprises:
acquiring version information corresponding to the version to be tested according to the version list to be tested; acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list; closing the running program of the server side in the application program server and backing up the original program file corresponding to the server side; after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, the program file and the second xml configuration information are stored in the application program server; checking whether the program file in the application program server is correct or not according to the file release list, if so, restarting the server terminal in the application program server, if so, finishing tasks of program compiling and test environment releasing, if not, restoring and starting the server terminal according to the original program file, and finishing the tasks of test environment releasing; otherwise, restoring and starting the server side according to the original program file, and ending the task issued by the test environment.
8. The system for managing the compiling and distributing of the server-side program according to any one of claims 5 to 6, wherein the compiling and distributing module for the compiling and distributing to the production environment specifically comprises:
acquiring version information corresponding to the tested version according to the tested version list; acquiring first xml configuration information according to the version information, wherein the first xml configuration information comprises an application program server and a file release list; closing the running program of the server side in the application program server and backing up the original program file corresponding to the server side; after the first xml configuration information is compiled and a program file and second xml configuration information corresponding to the program file are generated, the program file and the second xml configuration information are stored in the application program server; checking whether the program file in the application program server is correct or not according to the file release list, if so, restarting the server side in the application program server, if successfully restarting, detecting whether communication between the server sides is successful or not, if so, finishing tasks of program compiling and generating environment release, if not, restoring and starting the server side according to the original program file, and finishing tasks of the production environment release; otherwise, restoring and starting the server end according to the original program file, and ending the task issued by the production environment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710209399.8A CN107015842B (en) | 2017-03-31 | 2017-03-31 | Server-side program compiling and publishing management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710209399.8A CN107015842B (en) | 2017-03-31 | 2017-03-31 | Server-side program compiling and publishing management method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107015842A CN107015842A (en) | 2017-08-04 |
| CN107015842B true CN107015842B (en) | 2019-12-31 |
Family
ID=59445837
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710209399.8A Expired - Fee Related CN107015842B (en) | 2017-03-31 | 2017-03-31 | Server-side program compiling and publishing management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107015842B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908415A (en) * | 2017-11-30 | 2018-04-13 | 北京小米移动软件有限公司 | Processing method, device, equipment and storage medium |
| CN108255493B (en) * | 2018-01-09 | 2021-04-23 | 武汉斗鱼网络科技有限公司 | Component publishing and compiling method, storage medium, electronic device and system |
| CN109189371B (en) * | 2018-08-06 | 2022-03-01 | 广东小天才科技有限公司 | Software package issuing method and device based on configuration separation |
| CN111104125B (en) * | 2019-11-19 | 2023-09-08 | 泰康保险集团股份有限公司 | Intelligent integrated version management method, device, medium and electronic equipment |
| CN112035161B (en) * | 2020-08-31 | 2023-05-12 | 上海识装信息科技有限公司 | Applet release verification method and parallel release method |
| CN112035365B (en) * | 2020-09-01 | 2023-08-18 | 中国银行股份有限公司 | Version deployment method and device supporting multiple test environments |
| CN112256309A (en) * | 2020-11-12 | 2021-01-22 | 上海达梦数据库有限公司 | Program upgrading method, device, equipment and storage medium |
| CN112596778A (en) * | 2020-12-16 | 2021-04-02 | 福州智永信息科技有限公司 | Application version management method and terminal |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102035892A (en) * | 2010-12-23 | 2011-04-27 | 中科方德软件有限公司 | System and method for automatically releasing operating system version and automatically updating software package |
| CN106502642A (en) * | 2016-09-21 | 2017-03-15 | 北京深维科技有限公司 | A kind of evaluation method of eda tool and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110088011A1 (en) * | 2009-10-14 | 2011-04-14 | Vermeg Sarl | Automated Enterprise Software Development |
-
2017
- 2017-03-31 CN CN201710209399.8A patent/CN107015842B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102035892A (en) * | 2010-12-23 | 2011-04-27 | 中科方德软件有限公司 | System and method for automatically releasing operating system version and automatically updating software package |
| CN106502642A (en) * | 2016-09-21 | 2017-03-15 | 北京深维科技有限公司 | A kind of evaluation method of eda tool and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107015842A (en) | 2017-08-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107015842B (en) | Server-side program compiling and publishing management method and system | |
| CN110287052B (en) | Root cause task determination method and device for abnormal task | |
| CN110321254B (en) | Software version rollback method, device, server and storage medium | |
| CN107665171B (en) | Automatic regression testing method and device | |
| CN109634843B (en) | Distributed automatic software testing method and platform for AI chip platform | |
| CN106708740B (en) | Script testing method and device | |
| CN106970880B (en) | Distributed automatic software testing method and system | |
| US9658846B2 (en) | Software configuration control wherein containers are associated with physical storage of software application versions in a software production landscape | |
| CN105302554A (en) | Android system automatic program construction method and system | |
| CN103699693A (en) | Metadata-based data quality management method and system | |
| CN101408852B (en) | Method, apparatus and system for scheduling task | |
| CN112286806A (en) | Automatic testing method and device, storage medium and electronic equipment | |
| CN111651471A (en) | Target data query method and device, electronic equipment and storage medium | |
| CN111767227A (en) | Recording playback test method and device | |
| WO2019062132A1 (en) | Service rule management method and apparatus, storage medium, and computer device | |
| CN108255735B (en) | Associated environment testing method, electronic device and computer readable storage medium | |
| EP2196901A1 (en) | Systems and methods for tracking software stands in a software production landscape | |
| CN111669428A (en) | Vehicle remote upgrading method and system and cloud server | |
| CN109726104B (en) | Test packet generation method of mobile terminal, test terminal and storage medium | |
| CN107992420B (en) | Management method and system for test item | |
| CN115185825A (en) | Interface test scheduling method and device | |
| CN110674024A (en) | Electronic equipment integration test system and method thereof | |
| CN105320512B (en) | Distribute the method and device of trunk permission | |
| CN109508204B (en) | Front-end code quality detection method and device | |
| CN115372803B (en) | Motherboard test system, method, device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20191231 Termination date: 20210331 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |