Automated forwarding method and device, electronic equipment and storage medium

Abstract

The application discloses an automatic single conversion method and device, electronic equipment and a storage medium, and the method comprises the following steps: determining task single configuration information corresponding to a target task single based on the target task single in a first running environment; verifying the target task single based on the task single configuration information and a target verification mode; the target verification mode comprises task single state verification, task single overall verification and task single module verification; if the target task single passes the verification, the target task single is sent to a second running environment, and a target product is determined based on the target task single, so that resources are published based on the target product. Based on the technical scheme, the arrangement and implementation of the pipeline are completely separated, thereby ensuring efficient progression from the development test environment to the production environment, reducing repetitive labor, and avoiding risks that may be caused by manual operation.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to an automated order transfer method, apparatus, electronic device, and storage medium. Background Technology

[0002] During the development and maintenance of software projects, software needs to run on multiple environments, allowing developers to test and modify the software in different environments so that the final software can meet the development requirements.

[0003] However, since the development processes in different environments are independent of each other in the existing methods, it is necessary to set up development processes separately in different environments, which increases the workload of developers and may cause differences in the execution logic between the two environments, leading to production problems. Summary of the Invention

[0004] This invention provides an automated order transfer method, apparatus, electronic device, and storage medium, which realizes the verification of task order configuration information based on the target task order, the determination of target products based on the verified task order, and the release of resources, thereby realizing the rapid order transfer of task orders under different environments.

[0005] In a first aspect, embodiments of the present invention provide an automated order transfer method, including:

[0006] Based on the target task list in the first operating environment, determine the task list configuration information corresponding to the target task list;

[0007] The target task order is verified based on the task order configuration information and the target verification method; wherein, the preset verification method includes task order status verification, task order overall verification, and task order module verification;

[0008] If the target task order is verified, the target task order is sent to the second runtime environment, and the target artifact is determined based on the target task order, so as to publish resources based on the target artifact.

[0009] Secondly, embodiments of the present invention also provide an automated order transfer device, the device comprising:

[0010] The configuration information determination module is used to determine the task order configuration information corresponding to the target task order based on the target task order in the first operating environment.

[0011] The verification module is used to verify the target task based on the task configuration information and the target verification method; wherein, the preset verification method includes task status verification, task overall verification, and task module verification;

[0012] The artifact determination module is used to send the target task order to the second runtime environment if the target task order is verified, and determine the target artifact based on the target task order, so as to publish resources based on the target artifact.

[0013] Thirdly, embodiments of the present invention also provide an electronic device, the device comprising:

[0014] One or more processors; and

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to implement the automated order transfer method as described in any embodiment of the present invention.

[0017] Fourthly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the automated order transfer method as described in any of the embodiments of the present invention.

[0018] The technical solution of this invention determines task order configuration information corresponding to a target task order based on a target task order in a first operating environment. The target task order is then verified based on the task order configuration information and a target verification method. If the target task order passes verification, it is sent to a second operating environment, and a target artifact is determined based on the target task order. Resources are then released based on the target artifact. This technical solution achieves complete separation of pipeline orchestration and implementation, ensuring efficient progression from the development / testing environment to the production environment, reducing repetitive work, and mitigating risks that may arise from manual operations.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1This is a flowchart illustrating an automated order transfer method provided in an embodiment of the present invention;

[0022] Figure 2 This is a flowchart of an automated order transfer method provided in an embodiment of the present invention;

[0023] Figure 3 This is a structural diagram of the task order module verification provided in an embodiment of the present invention;

[0024] Figure 4 This is a structural block diagram of an automated order transfer device provided in an embodiment of the present invention;

[0025] Figure 5 This is a schematic diagram of the structure of the electronic device provided in an embodiment of the present invention. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] Example 1

[0029] Figure 1This is a flowchart illustrating an automated order transfer method provided in an embodiment of the present invention. This embodiment is applicable to performing status verification based on the task order configuration information corresponding to the task order in a preset operating environment. When the verification is successful, the target task order is sent to a second operating environment to determine the target product based on the task order in the second operating environment. This method can be executed by an automated order transfer device. The target data determination device can be implemented in hardware / software form. The device can be configured in an electronic device, which can be a PC or a server, etc.

[0030] like Figure 1 As shown, the method includes:

[0031] S110. Based on the target task list in the first operating environment, determine the task list configuration information corresponding to the target task list;

[0032] The first runtime environment can be a pre-configured runtime environment used for application development and testing. The target task order can be understood as a task order that needs to be transferred to another task order. This means there can be one or more target task orders; the user can select a task order as the target task order based on their needs, or all task orders in the first runtime environment can be used as target task orders for transfer processing. The task order configuration information can be the configuration information corresponding to the target task order.

[0033] Specifically, based on the target task in the first operating environment, the task configuration information corresponding to the target task is determined. For example, based on the target task selected by the user, the task identification information corresponding to the target task is obtained, and the task configuration information corresponding to the target task is obtained from the pre-set database based on the task identification information. Alternatively, all task tasks in the first operating environment can be used as target task tasks, and then the corresponding task configuration information can be retrieved from the preset database based on the identification information of the target task.

[0034] Based on the above technical solution, the step of determining the task order configuration information corresponding to the target task order based on the target task order in the first operating environment includes: obtaining the task order identifier corresponding to the target task order, and obtaining the task order configuration information corresponding to the task order identifier from a preset database based on the task order identifier.

[0035] The task order identifier can be understood as identification information used to identify the target task order. The preset database can be a pre-set database for storing task order-related information, such as a MySQL database. Task order configuration information includes applicant information, task order title, service catalog information, task order type information, task order status information, change order number information, and pre-release status information. Applicant information can be the relevant information of the applicant corresponding to the current target task order. The task order title can be understood as the title information of the current task order, which can be the main purpose of the current target task order. The service catalog information can be the name of the application system corresponding to the target task order, such as the name of the service platform. The task order type information can be the type of the current target task order, such as a data change task or a program change task. The task order status information can be understood as the current state of the task order, used to indicate the environment in which the current target task order is located. The change order number information can be the change order number corresponding to the current target task order. The pre-release status information can be understood as the orchestration and execution status corresponding to the current target task order.

[0036] Specifically, the process involves obtaining the task order identifier corresponding to the target task order, and then retrieving the corresponding task order configuration information from the preset database based on the task order identifier. It should be noted that a task order can be a number used to mark a pipeline, while a change order refers to a number used to modify the functionality of a software system during its development and maintenance. It is associated with the content of the change, the name of the software system, and how the change will be implemented. Once the change order is approved, a corresponding task order is generated based on the change order. However, one change order may correspond to one or more task orders. For example, a software system change may include both data changes and program changes, and each can be orchestrated using a separate task order.

[0037] S120. Verify the target task based on the task configuration information and the target verification method.

[0038] The target verification method can be a specific approach to verifying a task order. Target verification methods include task order status verification, overall task order verification, and task order module verification. Task order status verification can be understood as verifying the status of the current target task order. Overall task order verification can be understood as verifying the overall process of the current target task order. Task order module verification can be understood as verifying the specific execution modules within the current target task order.

[0039] Specifically, the target task is verified based on the task configuration information and the target verification method. For example, the status information of the target task can be verified based on the task status verification. After the status information is verified, the overall process of the current target task is verified based on the overall task verification. After the overall process of the task is verified, the specific execution modules in the current target task are verified based on the task module verification, thereby completing the verification of the target task.

[0040] Based on the above technical solution, before verifying the target task order based on the task order configuration information and the target verification method, the method includes: determining the target change order corresponding to the target task order based on the task order configuration information, and obtaining the change order status information corresponding to the target change order; if the change order status information matches the preset change order status information, then verifying the target task order based on the task order configuration information and the preset verification method.

[0041] The target change order can be a change order corresponding to the change order number. Change order status information can be understood as information used to identify the current status of the change order, such as whether it has been approved or not. Preset change form status information can be a pre-defined change form status, such as whether it has been approved.

[0042] Specifically, before verifying the target task order, it is necessary to determine the corresponding target change order based on the target task order's configuration information and obtain the change order status information. Only when the target change order's status information matches the preset change order transition status information will the target task order be verified based on the task order configuration information and the preset verification method. It should be noted that a change order can be understood as approval information corresponding to the current task order. Only after the change order is approved can the relevant operations on the task order be performed. Therefore, before verifying the task order, the change order's status information must be verified first. After the change order's status information is verified successfully, the target task order's status information can be set to "transferred."

[0043] Based on the above technical solution, the step of verifying the target task order based on the task order configuration information and the target verification method includes: if the target verification method is task order status verification, then obtaining the task order status information corresponding to the target task order; if the task order status information matches the preset task order status, then the target task order status verification passes.

[0044] The preset task order status information can be a pre-set task order status, such as a pre-sent status or a transferred status.

[0045] Specifically, if the target verification method is task order status verification, the task order status information corresponding to the target task order is retrieved from the task order configuration information. If the task order status information matches the preset task order status, that is, if the current target task order is in the pre-issue or transferred state, then the status verification of the current target task order has passed. It should be noted that when a task order is in the pre-issue or transferred state, it means that the task order in the production environment is in the initialization stage and can be transferred to achieve creation or modification. However, when a production task order is in the execution state, in order to maintain consistency between the two environments, transfer is not allowed.

[0046] Based on the above technical solution, the step of verifying the target task based on the task configuration information and the target verification method includes: if the target verification method is overall task verification, then obtaining the pre-release status information corresponding to the target task; constructing topology information corresponding to the target task based on the pre-release status information; if the topology information matches the preset topology, then the overall verification of the target task passes.

[0047] The topology information can be the arrangement structure information of the current target task list. The preset topology can be pre-set structure information, such as a directed acyclic graph.

[0048] Specifically, if the target verification method is overall task order verification, then the pre-release status information corresponding to the target task order is obtained. Based on this pre-release status information, a topology structure corresponding to the target task order is constructed. If the topology structure matches the preset topology structure, the overall verification of the target task order passes, meaning the task order is validated as a whole. This overall validation can also be called pipeline topology checking. Pipeline topology checking verifies the arrangement structure of the work steps. Since a directed graph represents the execution order of the work steps, a circular structure with consecutive beginnings and endings is not allowed. Such an infinite loop would pose a significant risk in a production environment, and the verification passes when no loop exists.

[0049] Based on the above technical solution, the step of verifying the target task based on the task configuration information and the target verification method includes: if the target verification method is task module verification, then obtaining task type information corresponding to the target task; determining the target verification steps based on the task type information, and performing task module verification based on the target verification steps and preset step information.

[0050] The target verification step can be a specific step in the target task sheet, such as a step that has undergone data changes and / or program changes. Preset step information can be understood as pre-set step information used to verify the target verification step.

[0051] Specifically, if the target verification method is task order module verification, then the task order type information corresponding to the target task order is obtained. Based on the task order type information, the target verification steps are determined, and task order module verification is performed based on the target verification steps and preset steps. This means verifying both the program and data modules of the task order, and performing module verification according to the individualized requirements of program and data changes. For example, to prevent system unavailability due to program change failures, program change steps must correspond to program rollback steps, and data change steps must include pre-change backup, post-change backup, and data rollback operations.

[0052] S130. If the target task order is verified, the target task order is sent to the second runtime environment, and the target artifact is determined based on the target task order, so as to publish resources based on the target artifact.

[0053] The second operating environment can be a production environment. The target artifact can be understood as the artifact determined in the second operating environment based on the target task sheet; it can be a program artifact or a data artifact. Resource publishing can be the process of pushing the target artifact.

[0054] Specifically, if the target task order passes verification, it means that the current target task order meets the conditions for transfer. The target task order can then be sent to the second runtime environment, where the target artifact is generated based on the target task order, and resources are then deployed based on the target artifact. It should be noted that to ensure the final generated target artifact can be directly deployed, additional operations such as alarm suppression, load balancing settings, and configuration activation are required when sending the target task order to the second runtime environment.

[0055] Based on the above technical solution, the step of sending the target task order to the second operating environment and determining the target product based on the target task order includes: obtaining topology information corresponding to the target task order and determining the data information to be applied based on the topology information; and determining the target product corresponding to the target task order based on the topology information and the data information to be applied.

[0056] The data to be applied can be data used to generate the target product. This data includes database information, data path information, and script information. Database information can be understood as the database corresponding to the current topology information. Data path information can be the path information corresponding to the data resources. Script information can be understood as the script information corresponding to the topology information.

[0057] Specifically, by acquiring the topology information corresponding to the target task order, and determining the data information to be applied corresponding to each operation step based on the topology information, the target product information is obtained by filling in the topology information and the data information to be applied. For example, the production environment retains the already arranged topology information and the correspondence between the operation steps and data scripts in the topology information, and automatically replaces the database information, data path information, and script information to be applied with the content corresponding to the test and development environment, thereby obtaining the target product corresponding to the second running environment. It should be noted that when the development and test environment package is inconsistent with the production package, two resource packages need to be generated simultaneously for release in the development and test environment and the production environment, respectively. Since the resource packages of the development and test environment and the production are mapped through "order transfer", the naming of the resource packages must conform to the specifications: the products of the development and test environment are stored in the abc-preprod library of the product library, and the program package name contains the word "PREPROD". When the development and test environment pipeline is transferred during order transfer, the production pipeline will automatically obtain the resource package selected during the development and test environment and replace "PREPROD" in the resource package and program package name with "PROD". When production is released, the production line will download resource packages with the word "PROD" from the production environment product library abc-prod and release them.

[0058] The technical solution of this invention determines task order configuration information corresponding to a target task order based on a target task order in a first operating environment. The target task order is then verified based on the task order configuration information and a target verification method. If the target task order passes verification, it is sent to a second operating environment, and a target artifact is determined based on the target task order. Resources are then released based on the target artifact. This technical solution achieves complete separation of pipeline orchestration and implementation, ensuring efficient progression from the development / testing environment to the production environment, reducing repetitive work, and mitigating risks that may arise from manual operations.

[0059] Example 2

[0060] Figure 2 This is a flowchart of an automated order transfer method provided by an embodiment of the present invention. This embodiment further optimizes the above-described automated order transfer method. For specific implementation details, please refer to the technical solution of this embodiment. Technical terms that are the same as or corresponding to those in the above embodiments will not be repeated here.

[0061] like Figure 2 As shown, the steps in this embodiment of the invention include:

[0062] Obtain task order configuration information: Specifically, read the task order configuration information of the development and testing environment. This mainly involves the basic information of the task order, including task number, applicant information, task order title, service directory (i.e., application system name), task order type, template type, template number, task order status (pre-release indicates development and testing environment, transferred order indicates it has been reused in production), change order number, and other information such as pre-release status (describing the orchestration and execution status of the pipeline in the development and testing environment).

[0063] Verify the status of change orders and task orders: Specifically, after passing verification, reuse the pipeline task orders that have been executed and verified in the development and testing environments. Copy the basic information of the task orders to the production environment, and set the task orders in both environments to "transferred." When a task order is in a pre-release or transferred state, it indicates that the task order in the production environment is in the initialization stage and can be transferred to create or modify a new task. However, when a production task order is in the execution state, to maintain consistency between the two environments, transfer is not allowed.

[0064] Overall task check: Specifically, overall check can also be called pipeline topology check. Pipeline topology check verifies the arrangement structure of the task steps. Since the directed graph represents the execution order of the task steps, a circular structure with the beginning and end connected is not allowed. Such an infinite loop would pose a significant risk if it appeared in a production environment, and the check would pass if no loop exists.

[0065] Task order module verification: Specifically, such as Figure 3 As shown, the task order undergoes verification of both program and data modules, with module verification tailored to the specific requirements of program and data changes. For instance, to prevent system unavailability due to program change failures, each program change step must correspond to a program rollback step; data changes must include pre-change backups, post-change backups, and data rollback operations.

[0066] Orchestration to Production: Specifically, orchestration reuse is performed by copying the pipeline orchestration from the development and testing environment to the production environment, and adding operations such as alarm masking, load balancing settings, and configuration activation.

[0067] Determine the target artifact: Specifically, when the development / testing environment package differs from the production package, two resource packages need to be generated simultaneously, one for the development / testing environment and the other for the production environment. Since the resource packages for the development / testing environment and production are mapped through a "transfer order," the naming of the resource packages must conform to the following specifications: the artifacts for the development / testing environment are stored in the abc-preprod library of the artifact repository, and the package name contains the word "PREPROD." During the transfer order process, after the development / testing environment pipeline is transferred, the production pipeline will automatically obtain the resource package selected during the development / testing environment process and replace "PREPROD" with "PROD" in the resource package and package name. During production release, the production pipeline will download the resource package containing "PROD" from the production environment artifact repository abc-prod library for release. The production environment retains the already arranged topology diagram and the correspondence between the job steps and data scripts in the topology diagram, automatically replacing the database information, data resource package paths, and scripts filled in the job steps with the content corresponding to the development / testing environment.

[0068] It should be noted that a change order refers to a number indicating a change to the functionality of a software system during development and maintenance. It includes the change content, the software system name, and how the change will be implemented. Data changes refer to operations that modify application data in a database, primarily involving adding, deleting, and modifying data, usually accomplished by executing SQL scripts. The SQL script file used for data change execution connects to the database and, based on data artifacts, performs the add, delete, and modify operations. Program changes refer to operations that modify or alter the software program, primarily involving updating or replacing the program's installation package. On-premises programs use package replacement, while cloud-based programs use updated software images. Program artifacts refer to program installation packages built, compiled, and packaged based on a code baseline, generally categorized as on-premises packages and cloud images. A job step represents an automated operation; the "Data Execution" job step represents the execution of a data script on the database. By dragging and dropping job steps, the implementation steps of data changes can be arranged, making the data change process visual. Through job arrangement, job steps form directed graph links, and the job steps and these links together constitute the pipeline itself. A task order is a number that marks a pipeline. Generally, one change order corresponds to one or more task orders. For example, a software system change may include both data changes and program changes, and each can be arranged into a pipeline using a task order.

[0069] The technical solution of this invention determines task order configuration information corresponding to a target task order based on a target task order in a first operating environment. The target task order is then verified based on the task order configuration information and a target verification method. If the target task order passes verification, it is sent to a second operating environment, and a target artifact is determined based on the target task order. Resources are then released based on the target artifact. This technical solution achieves complete separation of pipeline orchestration and implementation, ensuring efficient progression from the development / testing environment to the production environment, reducing repetitive work, and mitigating risks that may arise from manual operations.

[0070] Example 3

[0071] Figure 4 This is a structural block diagram of an automated order transfer device provided in an embodiment of the present invention. The device includes: a configuration information determination module 410, a verification module 420, and a product determination module 430.

[0072] The configuration information determination module 410 is used to determine the task order configuration information corresponding to the target task order based on the target task order in the first operating environment.

[0073] The verification module 420 is used to verify the target task based on the task configuration information and the target verification method; wherein, the preset verification method includes task status verification, task overall verification and task module verification.

[0074] The artifact determination module 430 is used to send the target task order to the second runtime environment if the target task order is verified, and determine the target artifact based on the target task order, so as to publish resources based on the target artifact.

[0075] Based on the above technical solution, the configuration information determination module is used to obtain a task order identifier corresponding to the target task order, and to obtain task order configuration information corresponding to the task order identifier from a preset database based on the task order identifier; wherein, the task order configuration information includes applicant information, task order title, service catalog information, task order type information, task order status information, change order number information, and pre-issuance status information.

[0076] Based on the above technical solution, the verification module includes: a change order status verification unit, used to determine a target change order corresponding to the target task order based on the task order configuration information and the target verification method before verifying the target task order based on the task order configuration information and the target verification method, and to obtain change table status information corresponding to the target change order; if the change table status information matches the preset change table status information, then the target task order is verified based on the task order configuration information and the preset verification method.

[0077] Based on the above technical solution, the verification module includes: a task order status verification unit, used to obtain task order status information corresponding to the target task order if the target verification method is task order status verification; if the task order status information matches a preset task order status, the target task order status verification passes.

[0078] Based on the above technical solution, the verification module includes: a task order overall verification unit, which, if the target verification method is task order overall verification, obtains pre-release information corresponding to the target task order; constructs topology information corresponding to the target task order based on the pre-release information; and if the topology information matches a preset topology, the overall verification of the target task order passes.

[0079] Based on the above technical solution, the verification module includes: a task order module verification unit, used to obtain task order type information corresponding to the target task order if the target verification method is task order module verification; determine the target verification step based on the task order type information; and perform task order module verification based on the target verification step and preset step information.

[0080] Based on the above technical solution, the product determination module is specifically used to obtain the topology information corresponding to the target task order, and determine the data information to be applied based on the topology information; wherein, the data information to be applied includes database information, data path information, and script information to be applied; and the target product corresponding to the target task order is determined based on the topology information and the data information to be applied.

[0081] The technical solution of this invention determines task order configuration information corresponding to a target task order based on a target task order in a first operating environment. The target task order is then verified based on the task order configuration information and a target verification method. If the target task order passes verification, it is sent to a second operating environment, and a target artifact is determined based on the target task order. Resources are then released based on the target artifact. This technical solution achieves complete separation of pipeline orchestration and implementation, ensuring efficient progression from the development / testing environment to the production environment, reducing repetitive work, and mitigating risks that may arise from manual operations.

[0082] The automated order transfer device provided in this embodiment of the invention can execute the automated order transfer method provided in any embodiment of this disclosure, and has the corresponding functional modules and beneficial effects of the method execution.

[0083] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this disclosure.

[0084] Example 4

[0085] Figure 5 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0086] like Figure 5As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0087] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0088] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as automated order processing methods.

[0089] In some embodiments, the automated order transfer method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the automated order transfer method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the automated order transfer method by any other suitable means (e.g., by means of firmware).

[0090] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0091] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0092] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0093] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0094] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0095] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0096] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0097] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. An automated transmittal method, characterized by, The method comprises the following steps: determining task sheet configuration information corresponding to the target task sheet based on the target task sheet under the first running environment; verifying the target task sheet based on the task sheet configuration information and a target verification method; the target verification method comprises task sheet state verification, task sheet overall verification, and task sheet module verification; if the target task sheet passes the verification, sending the target task sheet to a second running environment and determining a target product based on the target task sheet to publish resources based on the target product; before the step of verifying the target task sheet based on the task sheet configuration information and the target verification method, the method comprises the following steps: determining a target change sheet corresponding to the target task sheet based on the task sheet configuration information and obtaining change sheet state information corresponding to the target change sheet; if the change sheet state information matches preset change sheet state information, verifying the target task sheet based on the task sheet configuration information and a preset verification method; the step of verifying the target task sheet based on the task sheet configuration information and the target verification method comprises the following steps: if the target verification method is task sheet overall verification, obtaining pre-release situation information corresponding to the target task sheet; constructing topology structure information corresponding to the target task sheet based on the pre-release situation information, and if the topology structure information matches a preset topology structure, the overall verification of the target task sheet passes; the step of verifying the target task sheet based on the task sheet configuration information and the target verification method comprises the following steps: if the target verification method is task sheet module verification, obtaining task sheet type information corresponding to the target task sheet; determining a target verification step based on the task sheet type information and performing task sheet module verification based on the target verification step and preset step information.

2. The method of claim 1, wherein, the step of determining task sheet configuration information corresponding to the target task sheet based on the target task sheet under the first running environment comprises the following steps: obtaining a task sheet identifier corresponding to the target task sheet, and obtaining task sheet configuration information corresponding to the task sheet identifier from a preset database based on the task sheet identifier; the task sheet configuration information comprises applicant information, task sheet title, service directory information, task sheet type information, task sheet state information, change sheet number information, and pre-release situation information.

3. The method of claim 1, wherein, the step of verifying the target task sheet based on the task sheet configuration information and the target verification method comprises the following steps: if the target verification method is task sheet state verification, obtaining task sheet state information corresponding to the target task sheet; if the task sheet state information matches a preset task sheet state, the target task sheet state verification passes.

4. The method of claim 1, wherein, the step of sending the target task sheet to the second running environment and determining a target product based on the target task sheet comprises the following steps: Obtain topology structure information corresponding to the target task sheet, and determine to-be-applied data information based on the topology structure information; wherein, the to-be-applied data information comprises database information, data path information, and to-be-applied script information; Determine a target product corresponding to the target task sheet based on the topology structure information and the to-be-applied data information.

5. An automated transcribing device, characterized by, Comprise: A configuration information determination module configured to determine task sheet configuration information corresponding to a target task sheet based on the target task sheet in a first running environment; A verification module configured to verify the target task sheet based on the task sheet configuration information and a target verification mode; wherein, the target verification mode comprises task sheet state verification, task sheet overall verification, and task sheet module verification; A product determination module configured to, if the target task sheet passes the verification, send the target task sheet to a second running environment, and determine a target product based on the target task sheet, so as to publish resources based on the target product; The verification module comprises: a change sheet state verification unit configured to, before verifying the target task sheet based on the task sheet configuration information and the target verification mode, determine a target change sheet corresponding to the target task sheet based on the task sheet configuration information, and obtain change table state information corresponding to the target change sheet; if the change table state information matches preset change table state information, verify the target task sheet based on the task sheet configuration information and a preset verification mode; The verification module comprises: a task sheet overall verification unit configured to, if the target verification mode is task sheet overall verification, obtain pre-release situation information corresponding to the target task sheet; construct topology structure information corresponding to the target task sheet based on the pre-release situation information, and if the topology structure information matches a preset topology structure, the overall verification of the target task sheet passes; wherein, the topology structure information is the arrangement structure information of the current target task sheet; The verification module comprises: a task sheet module verification unit configured to, if the target verification mode is task sheet module verification, obtain task sheet type information corresponding to the target task sheet; determine a target verification step based on the task sheet type information, and perform task sheet module verification based on the target verification step and preset step information.

6. An electronic device, comprising: The electronic device comprises: At least one processor; and A memory connected in communication with the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the automatic change sheet method in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for enabling the processor to execute the automatic change sheet method in any one of claims 1-4 when executed.

Images