CN112165512B

CN112165512B - File release method and device, terminal equipment and storage medium

Info

Publication number: CN112165512B
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: 2023-09-26
Anticipated expiration: 2040-09-08
Also published as: CN112165512A

Abstract

The application is suitable for the technical field of file release and provides a file release method, a device, terminal equipment and a storage medium. In the embodiment of the application, a first trigger instruction is acquired, and the release configuration information of the current latest file is determined from a preset release 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 issue work order from issue configuration information of the file to be issued; and acquiring a confirmation issuing instruction, and asynchronously executing issuing tasks of each file to be issued in the issuing work order according to the confirmation issuing instruction, so that efficiency and safety in updating a large number of files are improved.

Description

File release method and device, terminal equipment and storage medium

Technical Field

The application belongs to the technical field of file release, and particularly relates to a file release method, a device, terminal equipment and a 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 mode, for example, manually acquiring an updated file from a code hosting platform, manually selecting the file to upload to a designated environment server through a file transfer tool, manually backing up an original file, and the like. The whole file updating process is manually operated, so that the operation is complex, time and labor are wasted, and under the requirement of updating a large number of tasks, misoperation can be generated when the file is manually updated, so that the efficiency and the safety are lower when the large number of files are updated.

Disclosure of Invention

The embodiment of the application provides a file publishing method, a device, terminal equipment and a storage medium, which can solve the problem 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 method for publishing a file, including:

acquiring a first trigger instruction, and determining release configuration information of a current latest file from a preset release item 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 issue work order from issue configuration information of the file to be issued;

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

Optionally, after generating the release configuration information of the file to be released to a release work order, the method includes:

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

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

Determining a first distribution identification of the file to be distributed according to a hash algorithm;

determining a file release position of the file to be released according to the release configuration information;

when the file release position has a first same-name file with the same name as the file to be released, determining a second release identification of the same-name file according to the hash algorithm;

and when the first distribution identifier is not equal to the second distribution identifier, the first same-name file is moved to a preset storage path.

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

and acquiring a rollback instruction, determining an issued work order to be rolled back from the issued record according to the rollback instruction, and asynchronously executing the rollback task of each issued file in the issued work order to be rolled back.

Optionally, the asynchronously executing the rollback task of each published file in the published work order needing rollback includes:

and when a second same-name file corresponding to the released file to be rolled back exists in the storage path, moving the second same-name file to a file release position of the released file to be rolled back, and deleting the released file to be rolled back from the file release position.

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

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

when the fact that the current user information is consistent with the release authority information in the release configuration information is detected, the re-release task of each released file in the release work order needing re-release is executed asynchronously.

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

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

and sending the flow parameters and the release flow information to a preset operation system so that the operation system executes corresponding operation on the server according to the flow parameters and the release flow 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 release configuration information of a current latest file from a preset release project template according to the first trigger instruction;

the generation 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 from issuing configuration information of the file to be issued;

and the execution module is used for acquiring the confirmation and release instruction, and asynchronously executing the release tasks of each file to be released in the release work order according to the confirmation and release instruction.

In a third aspect, an embodiment of the present application provides a terminal device, including 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 described above when executing the computer program.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program, which when executed by a processor, implements the steps of any one of the file distribution methods described above.

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

In the embodiment of the application, a first trigger instruction is acquired, and the release configuration information of the current latest file is determined from a preset release 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 issue work order from issue configuration information of the file to be issued; acquiring a confirmation issuing instruction, asynchronously executing issuing tasks of all files to be issued in an issuing work order according to the confirmation issuing instruction, determining issuing configuration information of the current unpublished latest file through a preset issuing item template in the embodiment of the application, determining the files to be issued from the latest file to reduce repeated issuing configuration operation of the files to be issued, generating the issuing work order from the issuing configuration information of the issuing files, asynchronously executing the issuing tasks of all the files to be issued in the issuing work order, and reducing possible misoperation caused by manual file updating 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 of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a first flowchart of a method for publishing a file according to an embodiment of the present application;

FIG. 2 is a second flowchart of a method for publishing a file according to an embodiment of the present application;

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

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

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

FIG. 6 is a schematic diagram of a file publishing device 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 the particular system architecture, 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 should 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 the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in the present description and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

Furthermore, the terms "first," "second," "third," and the like in the description of the present specification and in the appended claims, are used for distinguishing between descriptions and not necessarily for indicating or implying a 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 release configuration information of a current latest file is determined from a preset release item template according to the first trigger instruction.

In this embodiment, since the user may need to update files of multiple servers in batches at the same time, if the files are updated one by one only by means of full manual operation, misoperation is very likely to occur, and even if the influence caused by misoperation is not considered, 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 very high, so that the files are smaller and have lower efficiency, the release project template meeting the file updating requirements of most files can be preset, and the user can further limit the release project template according to the related requirements required for the files to be released in the current latest file, thereby reducing the labor cost, saving the time of technicians, and improving the efficiency of updating the whole file. The terminal equipment can determine the release configuration information of the current latest file from the pre-established release project templates according to the first trigger instruction issued by the user on the corresponding operation interface. The release configuration information includes, but is not limited to, release name information, release tag information, release file source address information, release file address information, user authority information, release flow information, and the like; the user authority information includes but is not limited to audit authority information, release authority information and the like; the release flow information comprises front operation information, rear operation information, rollback operation information and the like; the latest file is a file which has latest variation and is not transmitted to a server needing the file for updating the file; the first trigger instruction is defined by information based on the published item template according to the current file updating requirement of the user.

The terminal device may acquire a first trigger instruction issued by the user system operation interface, and determine, according to the first trigger instruction, a release title of the current latest file from a preset release item template, where the release title may be obtained by a user inputting title information in a corresponding window or selecting from a selection list. After the terminal equipment determines the title, selecting a preset release item template, and further determining release configuration information conforming to the release of the current file from the selected release item template. The title is named for the whole process of the file updating operation; the source address information of the release file can be a corresponding version control system, a server or a local part and the like; the release flow information can be selected or not, and if the release flow information is selected, parameters corresponding to the related release flow information input by a user are required to be acquired, so that a subsequent operation script can be operated according to the parameters. In the configuration process, the corresponding interface of the terminal equipment displays various states brought by the release configuration information of the current operation in real time, the terminal equipment binds the release configuration information determined by various operations with corresponding variables, and support is provided for the subsequent release configuration information when the change occurs through 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, the names of the items in the release name information, the release tags in the release tag information, the file source address in the release file source address information, and the like. After the terminal equipment is configured with the basic information, acquiring a user operation instruction to combine the basic information according to a preset rule so as to generate different release item templates.

The terminal device may acquire the user in the project name adding interface, 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 a name already exists, and the like, and after the project name meets the rule, the terminal device stores the project name and a project number generated by the project name in a corresponding database by using a frame method, and displays a project adding success interface.

Specific examples but not limited thereto, the terminal device may obtain the label adding interface of the user, and input or select label information to be added, where the label information includes, but is not limited to, a label name, label description information, a file source to which the label may correspond, a project name to which the label may correspond, and the like, and different label information corresponds to different environments, and the corresponding environments include, but are not limited to, a formal environment, a test environment, and the like; the file source corresponding to the tag can be built by itself, and a structured query language can also be selected. After the label information is input, the terminal equipment judges whether the current label information accords with the rule, and after the label information accords with the rule, the terminal equipment stores the label information into a corresponding database by utilizing a frame method and displays a label adding success interface.

The terminal device may obtain the user's name of the source address of the file to be added and the source address of the file corresponding to the name of the source address of the file to be added in the published source address adding interface, and generally may select from the open source version control system.

The method includes the steps that after basic information is added, a terminal device creates a release project template according to an operation instruction of a user, the project name and a file source address are associated, in the process, the user can input different module names according to different service types to be associated to the project, in order to prevent problems of release configuration information in the release project template, the terminal device judges whether the current basic configuration meets the rule according to the preset basic configuration, after the basic configuration meets the rule, the terminal device stores the basic configuration information in real time to prevent errors of follow-up configuration information, and the determination of release configuration information in the release project template is needed again. And then the user performs the next design according to the basic configuration success interface fed back by the terminal equipment, namely adds the release tag to the current basic configuration, and the terminal equipment receives the operation instruction of the user about the release tag and associates the corresponding release tag to the basic configuration. And acquiring release file address information when a user adds file release on a corresponding interface, wherein the release file address information comprises a server address of file release, 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 release project template, the terminal equipment can judge whether the configuration of the current release project template accords with the rule or not again, and when the configuration of the release project template accords with the rule, the terminal equipment stores the configured release project template into a corresponding database by utilizing a frame method and displays an effective interface of the release project template.

Optionally, after the configuration of the published item template is completed, if the security of the item is further ensured, the corresponding publisher information and auditor information can be configured for the item, that is, the user authority information is added on the basis of creating the published item template. The terminal equipment can acquire the information of the publishers and the auditors which are required to be added and input or selected by the user at the user authority adding interface, can simultaneously determine a plurality of authority users, and can judge whether the current user authority information accords with the rule after the input is completed.

Optionally, after the configuration of the release project template is completed, if the operation flow required for updating the file is to be further increased, release flow information corresponding to the project configuration may be added, that is, release flow information is added on the basis of the current release project template configuration, so as to add some custom operations during file release, for example, adding a restart process operation into post operation information, etc. The terminal equipment can acquire the release flow information to be added from the flow adding interface, input the release flow information to be added, wherein the release flow information comprises pre-operation information, post-operation information and/or rollback operation information, each operation information comprises a corresponding self-defined operation script, the script can be preset, after the input is completed, the terminal equipment can judge whether the current release flow information accords with the rule, and after the release flow information accords with the rule, the terminal equipment matches the release flow information into a corresponding release item template, and stores the release flow information into a corresponding database by utilizing a framework method, and the effective interface of release flow configuration is displayed. For example, if an operation of restarting the process is to be performed after the file is updated, a restart process script is configured in the post-operation information in the release flow information.

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

In this embodiment, since the current latest file is not all required to be issued, some of the latest files may not be required to be issued to the server due to factors such as that the files are not tested, so that the terminal device may provide a path selected by the user, when the terminal device displays the current latest file, the to-be-issued file is determined from the latest files according to the second trigger instruction sent by the user, and the to-be-issued file is a file to be issued to the relevant object of the server, and generates an issue work order according to the issue configuration information of the selected to-be-issued file, so that the user can perform subsequent operations.

Optionally, because some related description information may be needed for the release of a part of the file, the release description information input by the user on the corresponding file description interface may be obtained, and the terminal device may fill the release description information into the corresponding position of the release work order, or bind the release description information with a variable, so as to facilitate the modification of subsequent information.

Optionally, the latest file may search for the latest change file through a preset release source address in the terminal device, and acquire the latest change file, and when the searched latest change file does not meet the user requirement, the terminal device may acquire file information input by the user at the corresponding interface of the system, and determine the file information as the file to be released.

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, according to the variable bound when the configuration is performed on each piece of information, each release item configuration information of the release work order, and further display the information, so that a user may perform a corresponding operation, or perform further limitation based on a release item configuration template. For example, acquiring each release item configuration information of the release item template by an item number in a release item template variable; a list of target tags is obtained by publishing tag variables, and so on.

Step S103, acquiring a confirmation issuing instruction, and asynchronously executing issuing tasks of all files to be issued in the issuing work order according to the confirmation issuing instruction.

In this embodiment, the terminal device obtains a confirmation issue instruction issued by a user on the 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 a state in issue by using a framework method, executes issue tasks of each file to be issued in the issue work order in an asynchronous manner, that is, executes the issue tasks by using a cell framework in an asynchronous manner, invokes a corresponding task function by using the cell framework, and executes the issue tasks for 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 to a detection identifier corresponding to each task to be released, and prevent repeated release of the task within a preset time by setting the detection identifier. The preset time can be set according to the user requirement, and when at least two task release requests of the same detection mark are detected within the preset time of the terminal equipment, the release task of the task to be released corresponding to the detection mark is not performed.

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

Optionally, after the release is completed, the terminal device will obtain the release result, the terminal device 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, detailed release information and release process log on the corresponding visual interface of the terminal device.

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

and step S201, when the release configuration information comprises auditing authority information, notifying auditing personnel in the auditing authority information by using a preset communication mode, and displaying release configuration information of a file to be released in the release work order.

In this embodiment, since security is to be ensured during file updating and the public faced during information configuration in this solution is improved, auditing rights can be added during configuration, so that personnel without technical background, such as operators, can also issue relevant codes. The method comprises the steps that auditing authority information in user authority information can be configured in corresponding items when a release project template is configured, after a terminal device generates a release work order, the terminal device detects that release configuration information in the release project template used by the release work order comprises the auditing authority information, the work order is required to be audited by corresponding auditors, the current state of the release work order can be set to be an auditing state, the corresponding auditors in the auditing authority information are notified by utilizing a communication mode preset in the terminal device, and each release configuration information of a file to be released in the release work order is displayed so that the auditors can review.

Optionally, each item of release configuration information of the file to be released in the display release work order can be displayed in real time after notifying the auditor; the method comprises the steps of displaying an operation instruction of an auditor, acquiring the operation instruction of the auditor by the auditor, judging whether the current auditor accords with the preset audit authority information in the auditor, judging whether the state of the current auditor is an audit state, and displaying the release configuration information of the corresponding release worksheet according to the instruction of the auditor when the auditor accords with the preset audit authority information in the auditor and the state of the current release worksheet is the audit state. When an auditor inputs an audit passing instruction at the interface of the terminal equipment for displaying each item of release configuration information of the release work order, the terminal equipment acquires the audit passing instruction, changes the release state of the release work order into the audit passing state according to the audit passing instruction, stores the audit passing state and waits for the file release operation.

Optionally, the terminal device can identify the auditing personnel according to the account number and password information input by the auditing personnel, and determine whether the auditing personnel accords with the auditing authority information in the current release work order.

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

step S301, determining a first distributing identification of the file to be distributed according to a hash algorithm.

Step S302, determining the file release position of the file to be released according to the release configuration information.

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

And step S304, when the first distribution identifier is not equal to the second distribution identifier, the first homologous file is moved to a preset storage path.

In this embodiment, since the problem may occur in the process of publishing the file to be published, or the effect of the file to be published is not expected to be good, the files that can be covered under the same directory may be backed up before the file to be published is published, and the files that can be covered are the same name files. The unique MD5 value of the file to be published, i.e. the first published identification, can be calculated using a hash algorithm. Determining a file release position of a file to be released according to release configuration information in the release work order, judging whether a first identical file with the name of the file to be released exists in the file release position, if so, calculating a unique MD5 value of the file by using a hash algorithm, namely a second release identifier, comparing the two calculated release identifiers, and if the first release identifier is equal to the second release identifier, considering that the file to be released corresponding to the first release identifier is the same file as the first identical file corresponding to the second release identifier, and the file to be released does not release the file; if the first publishing identifier is not equal to the second publishing identifier, the file to be published corresponding to the first publishing identifier and the first homologous file corresponding to the second publishing identifier are considered to be different files, but because the file names are the same, in order to avoid the original file being covered, namely the first homologous file is covered, the first homologous file needs to be backed up, namely a storage path is preset in advance, the first homologous file is moved to the position below the preset storage path, and then the file publishing task of the file to be published is carried out.

It can be understood that if the file release position does not have the first identical file, the backup operation is not needed, and the file release task of the file to be released is directly performed. The new added files or the updated file information after deleting the original files can be recorded in the corresponding database according to the actual situation and stored.

Optionally, when the first homologous file moves to a preset storage path, the file name of the first homologous file may be modified, so as to facilitate searching for the backup file during the rollback operation. For example, the time stamp and the second publication identification are added on the basis of the original file name.

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

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

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

In this embodiment, when each published file in the current published work order to be rolled back performs the rolling back task, it is determined whether there is a second same name file corresponding to the name of the published file to be rolled back in the storage path corresponding to the published file to be rolled back, for example, the second same name file name may be a timestamp obtained by adding the name of the published file to be rolled back and the calculated published identifier, and how the specific name corresponds may be set according to the user requirement, which is not limited herein. If the second same-name file exists, moving the second same-name file to a file release position of the released file needing to be rolled back, and deleting the newly released file, namely the released file needing to be rolled back; and if the second same name file does not exist, the released file needing to be rolled back is directly deleted from the file release position.

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

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

step S501, when the task of issuing the file to be issued fails, acquiring a reissue instruction, and determining an issue work order to be reissued from the issue record according to the reissue instruction.

Step S502, when the fact that the current user information is consistent with the release authority information in the release configuration information is detected, the re-release task of each released file in the release work order needing re-release is asynchronously executed.

In this embodiment, after the task of publishing the file to be published fails, the user may perform the operation of re-publishing the publishing work order on the premise that it is determined that the publishing work order is not failed due to the publishing of the project configuration information. The terminal equipment obtains a reissue instruction issued by a user on a reissue operation interface, determines an reissue work order to be reissued, detailed information of the reissue work order and the state of the reissue work order according to the reissue instruction, and when judging that the issue state of the reissue work order is a failure state and the user information of the current reissue instruction is consistent with the user information in the issue authority information in the issue configuration information, the terminal equipment enters a process of reissue the reissue work order and modifies the state of the work order into the issue state so that the user can know the current state of the reissue work order in real time when consulting the current state of the reissue work order, executes a reissue task by using a cell frame in an asynchronous mode, and executes the reissue task for each reissue task needing reissue in the reissue work order by calling a corresponding task function by the cell frame. After the re-release is completed, the terminal equipment acquires the re-release result, checks the task re-release result in an asynchronous mode, stores the result in a corresponding database, and can check the re-release result, detailed re-release information and a re-release process log on a corresponding visual interface of the terminal equipment.

Optionally, step S103 includes:

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

In this embodiment, after the user issues the file, some operations are required to be performed on the server that issues the file, so that the server can normally use the updated file, for example, after the file is issued, the process of the server is restarted, if the process is restarted by manually performing related operations after each file is issued, the overall operation is time-consuming and labor-consuming, and when the repetitive operations are performed manually, misoperation may occur, so that related flow operations may be set in the issue configuration in advance, so that the file can be directly performed without user operations after the file is issued. Therefore, the terminal device can judge whether the release flow information, such as the post operation information, exists in the release item configuration information in the release work order when executing the release task. If the file terminal equipment contains the release flow information, the file terminal equipment needs to acquire configuration information required by the flow from corresponding release item configuration information, namely release flow information and flow parameters preset by a user, and call an execution script interface of a third-party operating system, the release flow information and the flow parameters preset by the user are sent 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 of file release of a file to be released. For example, the process of the server that issued the file is restarted.

Optionally, when the terminal device performs task release of the file to be released, it detects information included in the release item configuration information, performs a corresponding task operation according to the release item configuration information, specifically, determines that the task to be performed currently is a transmission file through a special field in the release item configuration information, that is, an action field, if the action field is identified, then a transmission file interface of the third-party operating system is called, the release item configuration information is transferred to the operating system, and the operating system recalls a client monitoring port corresponding to the server to perform the file transmission task. And when judging that the task to be performed currently is to execute the flow operation, calling an execution script interface of the third-party operating system, acquiring flow parameters, sending the flow parameters to the third-party operating system, and causing the third-party operating system to call a client of a corresponding server to execute a corresponding script according to the acquired information, wherein the terminal equipment can check the operation result of the task in an asynchronous mode and update and store the operation result in a corresponding database in the terminal equipment no matter whether the file is transmitted or the execution script receives the operation result after the task operation is completed.

Optionally, the terminal device capable of issuing the file includes a file issuing interface and a rollback interface. Because the current user groups with file release demands are more, and the file release contents corresponding to different users are different, a worker for releasing the file can send an HTTP request about file release to a release interface of terminal equipment similar to a release system for implementing release master control according to the user terminals such as a mobile phone and a computer, the file release request comprises various request information of the file to be released, the terminal equipment acquires and responds to the file release request, judges whether the file to be released carried in the request information is verified, and if so, the terminal equipment further carries out file release when receiving a command passing verification; if judging that the auditing 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, item numbers in the release name information, release tag information, a current operation domain account number, a key of a terminal device, current operation user account information, numbers of files to be released and release tag information, user authority information of the files, file list information, release parameters corresponding to a flow, and the like; it can be understood that the corresponding published item template can be obtained according to the item number, and whether the file currently requested to be published needs to be checked or not is judged according to the user authority information.

Optionally, if the current user side sends an HTTP request for the rollback operation of the published file to the rollback interface of the terminal device implementing the publishing master control, where the published file rollback request includes various request information of the published file, the terminal device obtains and responds to the published file rollback request, and immediately performs the published file rollback operation. The request information includes, but is not limited to, a published work order number of a published file, a current operation domain account number, a key of a 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 feedback file publishing or rollback result includes a request success result after the terminal device responds, or a request failure result after the terminal device does not respond, a publishing or rollback success result after the publishing or rollback is successful, and a current publishing work order number, or a publishing or rollback failure result of the publishing or rollback failure, and related log information of the publishing or rollback failure; the related log information of the publishing or rollback failure includes failure reasons, failure prompts and the like.

Optionally, each file to be distributed in the above-mentioned distribution work order may be distinguished by different separators, so as to facilitate user operation.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.

Corresponding to a file publishing method described above, fig. 6 is a schematic structural diagram of a file publishing device 6 according to an embodiment of the present application, and as shown in fig. 6, the file publishing device 6 may include:

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

The generating module 602 is 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 issue work order from issue configuration information of the file to be issued.

And the execution module 603 is configured to obtain a confirmation issuing instruction, and asynchronously execute the issuing task of each file to be issued in the issuing work order according to the confirmation issuing instruction.

Optionally, the file issuing apparatus 6 may further include:

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

Optionally, the file issuing apparatus 6 may further include:

The first determining identification module is used for determining a first distributing identification of the file to be distributed according to a hash algorithm.

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

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

And the moving module is used for moving the first homologous file to a preset storage path when the first issuing identifier is not equal to the second issuing identifier.

Optionally, the file issuing apparatus 6 may further include:

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

Optionally, the rollback module may include:

and the deleting unit is used for moving the second same-name file to the file release position of the released file to be rolled back when the second same-name file corresponding to the released file to be rolled back exists in the storage path, and deleting the released file to be rolled back from the file release position.

Optionally, the file issuing apparatus 6 may further include:

and the acquisition module is used for acquiring a reissue instruction when the release task of the file to be released fails, and determining a release work order to be reissued from the release record according to the reissue instruction.

And the reissuing module is used for asynchronously executing the reissuing task of each released file in the release work order to be reissued when detecting that the current user information is consistent with the release authority information in the release configuration information.

Optionally, the executing module 603 may include:

and the determining unit is used for acquiring the flow parameters when the release configuration information comprises release flow 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 flow parameters and the release flow information to a preset operating system so that the operating system can execute corresponding operation on the server according to the flow parameters and the release flow information.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the apparatus and modules described above may refer to corresponding procedures in the foregoing system embodiments and method embodiments, which 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 relevant 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, when executing the computer program 702, implements the steps in the respective file distribution method embodiments described above, such as steps S101 to S103 shown in fig. 1. Alternatively, the processor 700, when executing the computer program 702, performs the functions of the modules in the apparatus embodiments described above, for example, the functions of the modules 601 to 603 shown in fig. 6.

By way of example, 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 perform the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions for describing the execution 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, where each module specifically functions as follows:

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

the generating module 602 is 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 issue work order from issue configuration information of the file to be issued;

The terminal device 7 may include, but is not limited to, a processor 700, a memory 701. It will be appreciated by those skilled in the art that fig. 7 is merely an example of the terminal device 7 and is not limiting of the terminal device 7, and may include more or less components than illustrated, or may combine some components, or different components, such as may also include input and output devices, network access devices, buses, etc.

The processor 700 may be a central processing unit (Central Processing Unit, CPU), the processor 700 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 701 may in some embodiments be an internal storage unit of the terminal device 7, such as a hard disk or a memory of the terminal device 7. The memory 701 may in other embodiments 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) or the like, which are provided on the terminal device 7. Further, the memory 701 may also include both an internal storage unit and an external storage device of the terminal device 7. The memory 701 is used to store an operating system, application programs, boot loader (BootLoader), data, and other programs, etc., such as program code 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-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

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 solution. 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 manners. For example, the apparatus/terminal device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, 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 device/terminal apparatus, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A document issuing method, comprising:

acquiring a first trigger instruction, determining a release title of a current latest file from preset release item templates according to the first trigger instruction, selecting the preset release item templates after determining the release title, and determining release configuration information of the current latest file from the selected release item templates; the release title is used for naming the whole process of the current file updating operation; the release configuration information comprises release name information, release label information, release file source address information, release file address information, user authority information and release flow information;

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

before asynchronously executing the issuing tasks of each file to be issued in the issuing work order according to the confirmed issuing instruction, the method comprises the following steps:

determining the MD5 value of the file to be distributed according to a hash algorithm to obtain a first distribution identifier;

when the file release position has a first identical file with the file name to be released, determining an MD5 value of the first identical file according to the hash algorithm to obtain a second release identifier;

and when the first publishing identifier is not equal to the second publishing identifier, the file to be published corresponding to the first publishing identifier and the first homologous file corresponding to the second publishing identifier are considered to be different files, and the first homologous file is moved to a preset storage path.

2. The file distribution method according to claim 1, wherein after generating a distribution work order from the distribution configuration information of the file to be distributed, comprising:

3. The file distribution method according to claim 1, wherein after asynchronously executing the distribution tasks of the respective files to be distributed in the distribution work order according to the confirmation distribution instruction, comprising:

4. The file publishing method of claim 3, wherein asynchronously executing the rollback tasks for each published file in the publication worksheet to be rolled back comprises:

5. The file distribution method according to claim 1, wherein after asynchronously executing the distribution tasks of the respective files to be distributed in the distribution work order according to the confirmation distribution instruction, further comprising:

6. The file distribution method according to any one of claims 1 to 5, wherein the asynchronously executing the distribution tasks of the respective files to be distributed in the distribution work order according to the confirmation distribution instruction includes:

7. A document issuing apparatus, characterized by comprising:

the determining module is used for acquiring a first trigger instruction, determining a release title of a current latest file from preset release project templates according to the first trigger instruction, selecting the preset release project templates after determining the release title, and determining release configuration information of the current latest file from the selected release project templates; the release title is used for naming the whole process of the current file updating operation; the release configuration information comprises release name information, release label information, release file source address information, release file address information, user authority information and release flow information;

the execution module is used for acquiring the confirmation and release instruction, and asynchronously executing the release tasks of each file to be released in the release work order according to the confirmation and release instruction;

wherein, the file issuing device further includes:

The first determining identification module is used for determining the MD5 value of the file to be distributed according to a hash algorithm to obtain a first distribution identification;

the position determining module is used for determining the file release position of the file to be released according to the release configuration information;

the second determining and identifying module is used for determining the MD5 value of the first homologous file according to the hash algorithm when the first homologous file with the same name as the file to be distributed exists at the file distribution position, so as to obtain a second distribution identifier;

and the moving module is used for considering that the file to be distributed corresponding to the first distribution identifier and the first same-name file corresponding to the second distribution identifier are not the same files when the first distribution identifier is not equal to the second distribution identifier, and moving the first same-name file to a preset storage path.

8. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of a file distribution method according to any of claims 1 to 6 when the computer program is executed.

9. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of a file distribution method according to any of claims 1 to 6.