CN112165512A

CN112165512A - File publishing method and device, terminal equipment and storage medium

Info

Publication number: CN112165512A
Application number: CN202010936109.1A
Authority: CN
Inventors: 袁烨; 曾水泉; 曲宝全
Original assignee: Shenzhen Erlu Technology Co ltd
Current assignee: Boya Network Games Development Shenzhen Co ltd
Priority date: 2020-09-08
Filing date: 2020-09-08
Publication date: 2021-01-01
Anticipated expiration: 2040-09-08
Also published as: CN112165512B

Abstract

The application is applicable to the technical field of file publishing and provides a file publishing method, a file publishing device, terminal equipment and a storage medium. The method includes the steps that a first trigger instruction is obtained, and issuing configuration information of a current latest file is determined from a preset issuing project template according to the first trigger instruction; acquiring a second trigger instruction, determining a file to be issued from the latest file according to the second trigger instruction, and generating an issuing work order according to issuing configuration information of the file to be issued; and acquiring a confirmation issuing instruction, and asynchronously executing the issuing task of each file to be issued in the issuing work order according to the confirmation issuing instruction, thereby improving the efficiency and the safety when a large number of files are updated.

Description

File publishing method and device, terminal equipment and storage medium

Technical Field

The present application belongs to the technical field of file publishing, and in particular, to a file publishing method, apparatus, terminal device, and storage medium.

Background

In the prior art, code updating using a test environment or an online environment can only be operated in a fully manual manner, for example, an update file is manually acquired from a code hosting platform, a file is manually selected and uploaded to a designated environment server through a file transfer tool, an original file is manually backed up, and the like. The whole file updating process is manually operated, so that the operation is complicated, time and labor are wasted, misoperation can be caused when files are manually updated under the requirement of updating a large number of tasks, and the efficiency and the safety are lower when a large number of files are updated.

Disclosure of Invention

The embodiment of the application provides a file publishing method, a file publishing device, terminal equipment and a storage medium, and can solve the problems of low efficiency and safety when a large number of files are updated.

In a first aspect, an embodiment of the present application provides a file publishing method, including:

acquiring a first trigger instruction, and determining the issuing configuration information of the current latest file from a preset issuing project template according to the first trigger instruction;

acquiring a second trigger instruction, determining a file to be issued from the latest file according to the second trigger instruction, and generating an issuing work order according to issuing configuration information of the file to be issued;

and acquiring a confirmation issuing instruction, and asynchronously executing the issuing task of each file to be issued in the issuing work order according to the confirmation issuing instruction.

Optionally, after generating the publishing work order from the publishing configuration information of the file to be published, the method includes:

and when the release configuration information comprises the audit authority information, notifying an auditor in the audit authority information by using a preset communication mode, and displaying the release configuration information of the file to be released in the release work order.

Optionally, before asynchronously executing the issue task of each file to be issued in the issue work order according to the confirmation issue instruction, the method includes:

determining a first release identification of the file to be released according to a Hash algorithm;

determining the file publishing position of the file to be published according to the publishing configuration information;

when a first homonymous file with the same name as the file to be issued exists in the file issuing position, determining a second issuing identification of the homonymous file according to the Hash algorithm;

and when the first publishing identification is not equal to the second publishing identification, moving the first homonymous file to a preset storage path.

Optionally, after asynchronously executing the issue task of each to-be-issued file in the issue work order according to the confirmed issue instruction, the method includes:

and acquiring a rollback instruction, determining the issue work order needing to be rolled back from the issue record according to the rollback instruction, and asynchronously executing the rollback tasks of all issued files in the issue work order needing to be rolled back.

Optionally, the asynchronously executing the rollback task of each published file in the release work order that needs to be rolled back includes:

when a second file with the same name corresponding to the published file needing to be rolled back exists in the storage path, moving the second file with the same name to the file publishing position of the published file needing to be rolled back, and deleting the published file needing to be rolled back from the file publishing position.

Optionally, after asynchronously executing the issue task of each to-be-issued file in the issue work order according to the confirmation issue instruction, the method further includes:

when the issuing task of the file to be issued fails, acquiring a reissuing instruction, and determining an issuing work order needing to be reissued from an issuing record according to the reissuing instruction;

and when the current user information is detected to be consistent with the publishing authority information in the publishing configuration information, asynchronously executing the re-publishing task of each published file in the publishing work order needing to be re-published.

Optionally, the asynchronously executing the issue task of each to-be-issued file in the issue work order according to the confirmation issue instruction includes:

when the release configuration information comprises release process information, acquiring process parameters, and determining a server corresponding to the file to be released according to the release configuration information;

and sending the process parameters and the release process information to a preset operation system so that the operation system executes corresponding operation on the server according to the process parameters and the release process information.

In a second aspect, an embodiment of the present application provides a file publishing device, including:

the determining module is used for acquiring a first trigger instruction and determining the issuing configuration information of the current latest file from a preset issuing project template according to the first trigger instruction;

the generating module is used for acquiring a second trigger instruction, determining a file to be issued from the latest file according to the second trigger instruction, and generating an issuing work order according to issuing configuration information of the file to be issued;

and the execution module is used for acquiring the confirmation issue instruction and asynchronously executing the issue task of each file to be issued in the issue work order according to the confirmation issue instruction.

In a third aspect, an embodiment of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of any one of the file publishing methods when executing the computer program.

In a fourth aspect, the present application provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps of any one of the file publishing methods described above.

In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a terminal device, causes the terminal device to execute any one of the file publishing methods in the first aspect.

The method includes the steps that a first trigger instruction is obtained, and issuing configuration information of a current latest file is determined from a preset issuing project template according to the first trigger instruction; acquiring a second trigger instruction, determining a file to be issued from the latest file according to the second trigger instruction, and generating an issuing work order according to issuing configuration information of the file to be issued; the method comprises the steps of obtaining a confirmation issue instruction, asynchronously executing an issue task of each to-be-issued file in an issue work order according to the confirmation issue instruction, determining issue configuration information of a current non-issued latest file through a preset issue project template in the embodiment of the application, determining the to-be-issued file from the latest file so as to reduce repeated issue configuration operations of the to-be-issued file, generating the issue configuration information of the issued file into the issue work order, and asynchronously executing the issue task of each to-be-issued file in the issue work order so as to reduce misoperation possibly caused by manual file update of a user, thereby improving efficiency and safety when a large number of files are updated.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1 is a first flowchart schematic diagram of a file publishing method provided in an embodiment of the present application;

fig. 2 is a second flowchart of a file publishing method provided in an embodiment of the present application;

fig. 3 is a third flowchart illustrating a file publishing method according to an embodiment of the present application;

fig. 4 is a fourth flowchart illustrating a file publishing method according to an embodiment of the present application;

fig. 5 is a fifth flowchart illustrating a file publishing method according to an embodiment of the present application.

Fig. 6 is a schematic structural diagram of a document issuing apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.

Fig. 1 is a schematic flow chart of a file publishing method in an embodiment of the present application, and as shown in fig. 1, the file publishing method may include the following steps:

step S101, a first trigger instruction is obtained, and the issuing configuration information of the current latest file is determined from a preset issuing project template according to the first trigger instruction.

In this embodiment, because a user may need to update files of multiple servers in batch at the same time, if the user updates only one file in a fully manual manner, a misoperation is likely to occur, and even the influence caused by the misoperation is ignored, on the premise that a large number of file updating operation methods are the same, the labor and time costs required by the same operation method are also very high, so that the files are smaller and the efficiency is lower, so that a publishing project template meeting the file updating requirements of most files can be preset, and the user can further limit the publishing project template according to the relevant requirements required by the files to be published in the current latest file, thereby reducing the labor cost, saving the time of technicians, and improving the efficiency of updating the whole file. Therefore, the terminal device can determine the distribution configuration information of the current latest file from the pre-created distribution project template according to the first triggering instruction issued by the user on the corresponding operation interface. The publishing configuration information includes, but is not limited to, publishing name information, publishing label information, publishing file source address information, publishing file address information, user right information, publishing flow information, and the like; the user authority information includes but is not limited to audit authority information, issuing authority information and the like; the release flow information comprises prepositive operation information, postpositive operation information, rollback operation information and the like; the latest file is a file which is changed latest and is not sent to a server needing the file for updating the file; the first trigger instruction is information limitation performed by a user based on a release project template according to the requirement of updating the current file.

By way of specific example and not limitation, the terminal device may obtain a first trigger instruction issued by the user system operation interface, and determine, according to the first trigger instruction, a publishing title of the current latest file from a preset publishing project template, where the publishing title may be obtained by a user inputting title information in a corresponding window or selecting in a selection list. And after the terminal equipment determines the title, selecting a preset publishing item template, and further determining publishing configuration information which accords with the current file publishing from the selected publishing item template. Wherein, the title names the whole process of the file updating operation; the source address information of the issued file can be a corresponding version control system, a server or a local part and the like; the release process information can be selected or not selected, and if the release process information is selected, parameters corresponding to the relevant release process information input by a user need to be acquired, so that a subsequent operation script can run according to the parameters. And displaying various states brought by the current operation release configuration information in real time on a corresponding interface of the terminal equipment in the configuration process, binding corresponding variables to the release configuration information determined by various operations by the terminal equipment, and providing support for the change of the subsequent release configuration information by the binding variables.

Optionally, the terminal device may obtain operation information of the user on the corresponding display interface, and configure basic information of each corresponding operation information in the terminal device according to the operation information. The basic information includes, but is not limited to, basic information such as an item name in the publishing name information, a publishing tag in the publishing tag information, and a file source address in the publishing file source address information. And after the terminal equipment configures the basic information, acquiring a user operation instruction, and combining the basic information according to a preset rule to generate different release project templates.

By way of specific example and not limitation, the terminal device may obtain an interface for adding a project name by a user, input the project name to be added, and after the input is completed, the terminal device may determine whether the current project name meets a preset rule, where the preset rule includes a character requirement, a name length, whether the name already exists, and the like.

By way of specific example and not limitation, the terminal device may obtain a tag adding interface issued by a user, and input or select tag information to be added, where the tag information includes, but is not limited to, a tag name, tag description information, a file source to which the tag may correspond, a project name to which the tag may correspond, and the like, and different tag information corresponds to different environments, and the corresponding environments include, but is not limited to, a formal environment, a test environment, and the like; the file source corresponding to the label can be built by self, and a structured query language can be selected. And after the label information is input, the terminal equipment judges whether the current label information accords with the rule or not, and stores the label information into a corresponding database by using a frame method and displays a label adding success interface after the label information accords with the rule.

By way of specific example and not limitation, the terminal device may obtain an interface for adding the source address issued by the user, input or select a name of the source address of the file to be added and a corresponding source address of the file, and generally may select from an open-source version control system.

Specifically, for example and without limitation, after the basic information is added, the terminal device creates an issuing project template according to an operation instruction of a user, associates a project name with a file source address, in the process, the user can input different module names according to different service types and associate the module names with the project, in order to prevent problems of issuing configuration information in the issuing project template, the terminal device judges in advance for a currently set basic configuration, judges whether the current basic configuration meets the above rules, and stores the basic configuration information in real time after the basic configuration meets the above rules, so that when errors occur in subsequent configuration information, the determination of each issuing configuration information in the issuing project template needs to be performed again. And then, the user carries out the next design according to the successful interface of the basic configuration fed back by the terminal equipment, namely, the issuing label is added to the current basic configuration, the terminal equipment receives the operation instruction of the user about the issuing label, and the corresponding issuing label is associated to the basic configuration. And then acquiring address information of a published file when a user adds a file to a corresponding interface for publishing, wherein the address information of the published file comprises a server address of file publishing, a target directory of the server address, related description information and the like, when the terminal equipment completes corresponding operation according to an operation instruction of the user to generate a published item template, the terminal equipment can judge whether the configuration of the current published item template accords with the rule again, and when the configuration of the published item template accords with the rule, the terminal equipment stores the configured published item template into a corresponding database by using a frame method and displays an effective interface of the published item template.

Optionally, after the configuration of the published item template is completed, if the security of the item is further ensured, corresponding publisher information and auditor information may be configured for the item, that is, the user permission information is added on the basis of the creation of the published item template. The terminal equipment can acquire the information of the publishers and the information of the auditors which are required to be added and input or selected by the users in the user permission adding interface, can simultaneously determine a plurality of permission users, can judge whether the current user permission information accords with the rules after the input is completed, and can match the user permission information to the corresponding publishing project template and store the user permission information in the corresponding database by using a frame method after the user permission information accords with the rules to display the effective interface of the user permission configuration.

Optionally, after the configuration of the published project template is completed, if an operation flow required for updating the file is further added, corresponding published flow information may be configured for the project, that is, the published flow information is added on the basis of the configuration of the currently published project template to add some custom operations when the file is published, for example, a restart process operation is added to the post-operation information. The terminal equipment can acquire a flow adding interface of a user, inputs issuing flow information to be added, and comprises prepositive operation information, postpositive operation information and/or rollback operation information, each operation information has a corresponding self-defined operation script, the script can be set in advance, after the input is finished, the terminal equipment can judge whether the current issuing flow information accords with the rule, after the issuing flow information accords with the rule, the terminal equipment matches the issuing flow information to a corresponding issuing project template, stores the issuing flow information into a corresponding database by using a frame method, and displays an effective issuing flow configuration interface. For example, if it is desired to perform an operation of restarting a process after a file is updated, a restart process script is configured in post-operation information in the release flow information.

Step S102, a second trigger instruction is obtained, the file to be issued is determined from the latest file according to the second trigger instruction, and an issuing work order is generated according to issuing configuration information of the file to be issued.

In this embodiment, because all the current latest files are not required to be published, some latest files may not be required to be published to the server because the files are not tested, and the like, so the terminal device may provide a way for a user to select.

Optionally, since some related description information may be required for publishing a part of files, the publishing description information input by the user in the corresponding file description interface may be obtained, and the terminal device fills the publishing description information in the corresponding position of the publishing work order, and may also bind the publishing description information to a variable, so as to facilitate changing of subsequent information.

Optionally, the latest file may be searched for and obtained from a publishing source address preset in the terminal device, and when the searched latest file does not meet the user requirement, the terminal device may obtain file information input by the user on a corresponding interface of the system, and determine the file information as a file to be published.

Optionally, after the configuration of the release configuration information of the release work order is completed, the terminal device may determine whether the release configuration information of the release work order meets the rule, and when the release configuration information of the release work order meets the rule, the terminal device may obtain the configuration information of each release item of the release work order according to the variables bound during the configuration of each piece of information, and further display the configuration information for the user to perform corresponding operations, or further define based on a release item configuration template. For example, the configuration information of each release item of the release item template is acquired through the item number in the release item template variable; obtain a target tag list by publishing tag variables, and so on.

Step S103, obtaining a confirmation issue instruction, and asynchronously executing the issue task of each file to be issued in the issue work order according to the confirmation issue instruction.

In this embodiment, the terminal device obtains a confirmation issue instruction issued by a user on a file issue interface, determines an issue work order to be issued according to the confirmation issue instruction, modifies the state of the issue work order into an issue state by using a frame method, and executes an issue task of each file to be issued in the issue work order in an asynchronous manner, that is, executes the issue task by using a celery frame in an asynchronous manner, and invokes a corresponding task function by using the celery frame to execute the issue task on each file to be issued in the issue work order.

Optionally, the terminal device may generate the release configuration information of each task to be released in the release work order into a detection identifier corresponding to each task to be released, and set the detection identifier to prevent multiple repeated releases of tasks within a preset time. The preset time can be set according to user requirements, and when at least two task issuing requests of the same detection identifier are detected within the preset time of the terminal device, the issuing task of the task to be issued corresponding to the detection identifier is not performed.

Optionally, when the terminal device obtains an instruction to cancel issuance issued by the user on the file issuance interface, the terminal device determines, according to the instruction to cancel issuance, the issuance work order to be canceled, and deletes the issuance work order from the issuance list.

Optionally, after the release is completed, the terminal device obtains the release result, checks the task release result in an asynchronous manner, and stores the result in the corresponding database, so that the user can check the release result, the detailed release information, and the release process log on the corresponding visual interface of the terminal device.

Optionally, as shown in fig. 2, after step S102, the method includes:

step S201, when the release configuration information includes the audit authority information, notifying an auditor in the audit authority information by using a preset communication mode, and displaying the release configuration information of the file to be released in the release work order.

In this embodiment, to ensure the security of file update and improve the public facing the information configuration in the present solution, the auditing permission may be added during configuration, so that personnel without technical background, such as operators, may also issue related codes. The method includes the steps that auditing permission information in user permission information can be configured in a corresponding project when a published project template is configured, after a published work order is generated by terminal equipment, the terminal equipment detects that published configuration information in the published project template used by the published work order includes the auditing permission information, and then the terminal equipment indicates that corresponding auditors of the work order need to audit, the current state of the published work order can be set to be an auditing state, corresponding auditors in the auditing permission information are notified by means of a communication mode preset in the terminal equipment, and various pieces of published configuration information of files to be published in the published work order are displayed so that the auditors can conveniently consult.

Optionally, the various pieces of publishing configuration information of the files to be published in the display publishing work order may be displayed in real time after the auditor is notified; the method also can display according to the operation instruction of the auditor, issue the work order to obtain the operation instruction of the auditor, judge whether the current auditor accords with the internal preset audit authority information, judge whether the state of the current issue work order is the audit state, and display the corresponding issue configuration information of the issue work order according to the instruction of the auditor when the auditor accords with the internal preset audit authority information and the state of the current issue work order is the audit state. When the auditor inputs the approved instruction on the interface of the terminal equipment for displaying the various issuing configuration information of the issuing work order, the terminal equipment acquires the approved instruction, changes the issuing state of the issuing work order into the approved state according to the approved instruction, stores the approved instruction and waits for the document issuing operation.

Optionally, the terminal device may perform identity recognition on the auditor according to the account password information input by the auditor, and determine whether the auditor conforms to the audit authority information in the currently issued work order.

Optionally, as shown in fig. 3, before asynchronously executing the issue task of each file to be issued in the issue work order according to the confirmation issue instruction, the method includes:

step S301, determining a first release identifier of the file to be released according to a Hash algorithm.

Step S302, determining the file publishing position of the file to be published according to the publishing configuration information.

Step S303, when the file release position has a first file with the same name as the file to be released, determining a second release identifier of the file with the same name according to the hash algorithm.

Step S304, when the first publishing identity is not equal to the second publishing identity, moving the first named file to a preset storage path.

In this embodiment, because a problem may occur to the file to be published during the process of publishing the file, or the effect of the file to be published after publishing is not as good as expected, the file that can be overwritten in the same directory can be backed up before the file to be published is published, and the file that can be overwritten is the file with the same name. The unique MD5 value of the file to be published, i.e. the first publication identifier, can be calculated using a hashing algorithm. Determining a file publishing position where a file to be published is to be published according to publishing configuration information in the publishing work order, judging whether the file publishing position has a first homonymous file with the same name as the file to be published, if so, calculating a unique MD5 value of the file by using a hash algorithm, namely a second publishing identifier, comparing the two calculated publishing identifiers, and if the first publishing identifier is equal to the second publishing identifier, determining that the file to be published corresponding to the first publishing identifier and the first homonymous file corresponding to the second publishing identifier are the same file, and not publishing the file; if the first publishing identification is not equal to the second publishing identification, the file to be published corresponding to the first publishing identification and the first homonymous file corresponding to the second publishing identification are not considered to be the same file, but because the file names are the same, in order to avoid the original file being covered, namely the first homonymous file being covered, the first homonymous file needs to be backed up, namely a storage path is preset in advance, the first homonymous file is moved to the lower part of the preset storage path, and then a file publishing task of the file to be published is carried out.

It can be understood that if the first file with the same name does not exist in the file publishing position, the file publishing task of the file to be published is directly performed without performing backup operation. The newly added files or the updated file information after the original files are deleted can be recorded in the corresponding database according to the actual situation and stored.

Optionally, when the first file with the same name is moved to a preset storage path, the file name of the first file with the same name may be modified, so as to search for the backup file during the rollback operation. For example, a time stamp and a second release identifier are added on the basis of the original file name.

Optionally, as shown in fig. 4, after step S103, the method includes:

step S401, obtaining a rollback instruction, determining an issuing work order needing to be rolled back from an issuing record according to the rollback instruction, and asynchronously executing the rollback tasks of all issued files in the issuing work order needing to be rolled back.

In this embodiment, when a release failure occurs in the process of releasing the file, or the effect of the file to be released after being released is not good as expected, the file to be released can be rolled back, so that the file information of the corresponding position of the server is restored to the state before the file is released. The terminal device obtains a rollback instruction issued by a user on a corresponding rollback interface, determines an issuing work order needing to be rolled back from an issuing record according to the rollback instruction, and can obtain issuing project configuration information of the issuing work order and a current issuing state of the issuing work order, such as an issuing success state or an issuing failure state. After the terminal equipment performs the rollback operation, the current state of the release work order can be modified into the rollback state, so that the user can conveniently check the work order. Executing a rollback task by using a celery frame in an asynchronous mode, calling a corresponding task function through the celery frame, and executing the rollback task on each published file in the release work order; after the rollback is completed, the terminal device acquires the rollback result, the terminal device checks the task rollback result in an asynchronous mode, and stores the result in a corresponding database, so that a user can check the rollback result, detailed rollback information and a rollback process log on a corresponding visual interface of the terminal device.

In this embodiment, when each published file in the release work order that needs to be rolled back performs a roll-back task, it is determined whether a second file with the same name, which corresponds to the name of the published file that needs to be rolled back, exists in the storage path corresponding to the published file that needs to be rolled back, for example, the second file with the same name may be the published file name plus a time stamp at the time of one-time publication and a calculated release identifier, how the specific name corresponds may be set according to a user requirement, which is not limited herein. If the second file with the same name exists, the second file with the same name is moved to the file publishing position of the published file needing to be rolled back, and the newly published file, namely the published file needing to be rolled back, is deleted; and if the second file with the same name does not exist, the published file needing to be rolled back is directly deleted from the file publishing position.

Optionally, when executing the rollback task, the terminal device may determine whether there is release flow information in release item configuration information in the release work order that needs to be rolled back, and whether the release flow information includes rollback operation information, if the release flow information includes the rollback operation information, the file terminal device needs to obtain configuration information required by the rollback operation and a script parameter preset by a user from the corresponding release item configuration information, and call an execution script interface of a third-party operating system, and send the configuration information and the script parameter preset by the user to the third-party operating system, and the operating system calls a client of a corresponding target server according to the obtained information to execute a script, where the corresponding target server is a location where the file is released. For example, the process of the server that published the file is restarted.

Optionally, as shown in fig. 5, after step S103, the method further includes:

step S501, when the issue task of the file to be issued fails, a reissue instruction is obtained, and the issue work order needing to be reissued is determined from the issue record according to the reissue instruction.

Step S502, when the current user information is detected to be consistent with the publishing authority information in the publishing configuration information, asynchronously executing the re-publishing task of each published file in the publishing work order needing to be re-published.

In this embodiment, after the release task of the file to be released fails, the user may perform an operation of reissuing the release work order on the premise of determining that the release work order does not fail due to the release of the project configuration information. The terminal equipment acquires a reissue instruction issued by a user on the reissue operation interface, determines the reissued work order, the detailed information of the work order and the state of the work order according to the reissue instruction, when the issuing state of the issuing work order is judged to be a failure state and the user information of the currently issued reissuing instruction is consistent with the user information in the issuing authority information in the issuing configuration information, the terminal equipment enters the flow of reissuing the work order and modifies the state of the work order into the release state, so that the user can know the current state of the issued work order in real time when looking up the current state of the issued work order, the terminal equipment uses the battery frame to execute the re-issuing task in an asynchronous mode, and calling a corresponding task function through the celery frame, and executing a reissuing task on each published task needing to be reissued in the release work order. After the reissue is completed, the terminal equipment acquires the reissue result, the terminal equipment checks the task reissue result in an asynchronous mode, the result is stored in a corresponding database, and a user can check the reissue result, detailed reissue information and a reissue process log on a corresponding visual interface of the terminal equipment.

Optionally, step S103 includes:

and when the release configuration information comprises release process information, acquiring process parameters, and determining a server corresponding to the file to be released according to the release configuration information.

In this embodiment, because a user sometimes needs to perform some operations on a server to which a file is published after the file is published, so that the server can normally use an updated file, for example, a process of the server is restarted after the file is published, if each file is published, a related operation needs to be manually performed to restart the process, the overall operation is time-consuming and labor-consuming, and an incorrect operation may be generated when a repetitive operation is manually performed, so that a related flow operation may be set in the publishing configuration in advance, so that the file can be directly performed without a user operation after the file is published. Therefore, when the terminal device executes the distribution task, the terminal device can judge whether distribution flow information, such as post operation information, exists in the distribution item configuration information in the distribution work order. If the file terminal equipment contains the publishing process information, the file terminal equipment needs to acquire configuration information required by the process from corresponding publishing project configuration information, namely the publishing process information and the process parameters preset by the user, and calls an execution script interface of a third-party operating system to send the publishing process information and the process parameters preset by the user to the third-party operating system, so that the third-party operating system calls a client of a corresponding server to execute a corresponding script according to the acquired information, and the corresponding server is the position for publishing the file of the file to be published. For example, the process of the server that published the file is restarted.

Optionally, when the terminal device issues a task of a file to be issued, information included in the issued project configuration information is detected, a corresponding task operation is performed according to the issued project configuration information, specifically, through a special field in the issued project configuration information, that is, an action field, if the action field identifies that the current task to be performed is a transmission file, a transmission file interface of a third-party operating system is called, the issued project configuration information is transmitted to the operating system, and the operating system calls a client monitor port corresponding to the server to execute the file transmission task. When the task to be performed at present is judged to be a process execution operation, an execution script interface of a third-party operating system is called, then a process parameter is obtained, the process parameter is sent to the third-party operating system, the third-party operating system is prompted to call a client of a corresponding server to execute a corresponding script according to the obtained information, no matter whether the file transmission or the process execution task is completed, the terminal device receives an operation result, the terminal device can check the operation result of the task in an asynchronous mode, and the operation result is updated and stored in a corresponding database in the terminal device.

Optionally, the terminal device capable of publishing the file includes a file publishing interface and a rollback interface. The working personnel for issuing the files can send HTTP requests about the file issuing to the issuing interface of terminal equipment similar to an issuing system and used for implementing issuing general control according to user ends of mobile phones, computers and the like held by the working personnel, wherein the file issuing requests comprise various request information of files to be issued, the terminal equipment acquires and responds to the file issuing requests and judges whether the files to be issued carried in the request information are to be audited or not, and if the files are judged to be audited, the terminal equipment issues the files when receiving instructions passing the audits; and if the terminal equipment judges that the verification is not needed, immediately issuing the file when the terminal equipment responds to the file issuing request. The request information includes, but is not limited to, an item number in the release name information, release tag information, a current operation domain account, a key of the terminal device, user account information of the current operation, a number and release tag information of each file to be released, user authority information of the file, file list information, release parameters corresponding to the process, and the like; it can be understood that, the corresponding issued item template can be obtained according to the item number, and whether the file requested to be issued needs to be checked or not is judged according to the user permission information.

Optionally, if the current user sends an HTTP request related to a rollback operation of the published file to a rollback interface of a terminal device that implements the publishing master control, and the rollback request of the published file includes various pieces of request information of the published file, the terminal device obtains and responds to the rollback request of the published file, and immediately performs the rollback operation of the published file. The request information includes, but is not limited to, a release work order number of a released file, a current operation domain account number, a key of the terminal device, and the like.

Optionally, the terminal device may feed back each result in the current file publishing or rollback process to the user side in real time, where the fed-back file publishing or rollback result includes a request success result after the terminal device responds, or a request failure result without responding, a publishing or rollback success result after the publishing or rollback success, a current publishing work order number, or a publishing or rollback failure result after the publishing or rollback failure, and related log information of the publishing or rollback failure; the log information related to the issue or rollback failure includes a failure reason, a failure prompt, and the like.

Optionally, each to-be-issued file in the issue work order may be distinguished by a different separator, so as to facilitate user operation.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Corresponding to the above-mentioned document issuing method, fig. 6 is a schematic structural diagram of a document issuing apparatus 6 in an embodiment of the present application, and as shown in fig. 6, the document issuing apparatus 6 may include:

the determining module 601 is configured to obtain a first trigger instruction, and determine, according to the first trigger instruction, publishing configuration information of a current latest file from a preset publishing project template.

A generating module 602, configured to obtain a second trigger instruction, determine a file to be issued from the latest file according to the second trigger instruction, and generate an issuing work order according to issuing configuration information of the file to be issued.

The executing module 603 is configured to obtain a confirmation issue instruction, and asynchronously execute an issue task of each to-be-issued file in the issue work order according to the confirmation issue instruction.

Optionally, the file publishing device 6 may further include:

and the display module is used for notifying the auditors in the audit authority information in a preset communication mode when the release configuration information comprises the audit authority information, and displaying the release configuration information of the file to be released in the release work order.

Optionally, the file publishing device 6 may further include:

and the first identification determining module is used for determining a first release identification of the file to be released according to a Hash algorithm.

And the position determining module is used for determining the file publishing position of the file to be published according to the publishing configuration information.

And the second identification determining module is used for determining a second release identification of the file with the same name according to the hash algorithm when the file release position has a first file with the same name as the file to be released.

And the moving module is used for moving the first homonymous file to a preset storage path when the first publishing identification is not equal to the second publishing identification.

Optionally, the file publishing device 6 may further include:

and the rollback module is used for acquiring a rollback instruction, determining the issuing work order needing to be rolled back from the issuing records according to the rollback instruction, and asynchronously executing the rollback tasks of all issued files in the issuing work order needing to be rolled back.

Optionally, the rollback module may include:

and the deleting unit is used for moving the second file with the same name to the file publishing position of the published file to be rolled back and deleting the published file to be rolled back from the file publishing position when the second file with the same name corresponding to the published file to be rolled back exists in the storage path.

Optionally, the file publishing device 6 may further include:

and the obtaining module is used for obtaining a reissue instruction when the issue task of the file to be issued fails, and determining an issue work order needing to be reissued from an issue record according to the reissue instruction.

And the reissuing module is used for asynchronously executing the reissuing task of each published file in the publishing work order needing to be reissued when the current user information is detected to be consistent with the publishing authority information in the publishing configuration information.

Optionally, the executing module 603 may include:

and the determining unit is used for acquiring the process parameters when the release configuration information comprises release process information, and determining the server corresponding to the file to be released according to the release configuration information.

And the sending unit is used for sending the process parameters and the release process information to a preset operation system so that the operation system executes corresponding operation on the server according to the process parameters and the release process information.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the apparatus and the module described above may refer to corresponding processes in the foregoing system embodiments and method embodiments, and are not described herein again.

Fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present application. For convenience of explanation, only portions related to the embodiments of the present application are shown.

As shown in fig. 7, the terminal device 7 of this embodiment includes: at least one processor 700 (only one shown in fig. 7), a memory 701 connected to the processor 700, and a computer program 702, such as a file distribution program, stored in the memory 701 and executable on the at least one processor 700. The processor 700 implements the steps in the above-described respective embodiments of the file distribution method, such as the steps S101 to S103 shown in fig. 1, when executing the computer program 702. Alternatively, the processor 700, when executing the computer program 702, implements the functions of the modules in the above-described device embodiments, for example, the functions of the modules 601 to 603 shown in fig. 6.

Illustratively, the computer program 702 may be partitioned into one or more modules that are stored in the memory 701 and executed by the processor 700 to accomplish the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 702 in the terminal device 7. For example, the computer program 702 may be divided into a determining module 601, a generating module 602, and an executing module 603, and the specific functions of each module are as follows:

a determining module 601, configured to obtain a first trigger instruction, and determine, according to the first trigger instruction, publishing configuration information of a current latest file from a preset publishing project template;

a generating module 602, configured to obtain a second trigger instruction, determine a file to be issued from the latest file according to the second trigger instruction, and generate an issuing work order according to issuing configuration information of the file to be issued;

The terminal device 7 may include, but is not limited to, a processor 700 and a memory 701. It will be understood by those skilled in the art that fig. 7 is only an example of the terminal device 7, and does not constitute a limitation to the terminal device 7, and may include more or less components than those shown, or combine some components, or different components, such as an input-output device, a network access device, a bus, etc.

The Processor 700 may be a Central Processing Unit (CPU), and the Processor 700 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 701 may be an internal storage unit of the terminal device 7 in some embodiments, for example, a hard disk or a memory of the terminal device 7. In other embodiments, the memory 701 may also be an external storage device of the terminal device 7, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are equipped on the terminal device 7. Further, the memory 701 may include both an internal storage unit and an external storage device of the terminal device 7. The memory 701 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 701 may also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. A method for publishing a file, comprising:

2. The file publishing method according to claim 1, wherein after generating the publishing configuration information of the file to be published into a publishing work order, the method comprises:

3. The file issuing method according to claim 2, before asynchronously executing the issuing task of each file to be issued in the issuing work order according to the confirmation issuing instruction, comprising:

4. The file issuing method according to claim 3, wherein after asynchronously executing the issuing task of each file to be issued in the issuing work order according to the confirmation issuing instruction, the method includes:

5. The file publication method of claim 4 wherein the asynchronously performing a rollback task for each published file in the publication work order that requires rollback comprises:

6. The file issuing method according to claim 1, wherein after asynchronously executing the issuing task of each file to be issued in the issuing work order according to the confirmation issuing instruction, further comprising:

7. The file issuing method according to any one of claims 1 to 6, wherein the asynchronously executing the issuing task of each file to be issued in the issuing work order according to the confirmation issuing instruction includes:

8. A document issuing apparatus, characterized by comprising:

9. A terminal device comprising a memory, a processor and a computer program stored in said memory and executable on said processor, characterized in that said processor implements the steps of a method of distributing files according to any one of claims 1 to 7 when executing said computer program.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of a method for document distribution according to any one of claims 1 to 7.