CN114461268A

CN114461268A - Program production method, device, electronic equipment, storage medium and product

Info

Publication number: CN114461268A
Application number: CN202210123263.6A
Authority: CN
Inventors: 梁汨
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2022-02-09
Filing date: 2022-02-09
Publication date: 2022-05-10

Abstract

The present disclosure provides a program production method, which can be applied to the technical field of computer programs, the financial field or other fields. The program production method comprises the following steps: responding to the entity content of the target program release version, and recording the production time of the target program release version, wherein the target program release version is provided with a version identification mark; generating a production scheme according to the production scheme template and the production time, wherein the production scheme corresponds to the release version of the target program; generating a merging list according to the version identification mark of the target program release version; and sending the entity content of the corresponding target program release version to an online operation unit according to the merging list, and performing online operation on the entity content by the online operation unit according to a production scheme.

Description

Program production method, device, electronic equipment, storage medium and product

Technical Field

The present disclosure relates to the field of computer program technology, and more particularly, to a program production method, an apparatus, an electronic device, a readable storage medium, and a computer program product.

Background

In the related art, a program or software has different versions before the program or software is put on line for testing. Because an application system has a plurality of service groups, one service group has a plurality of publishing units, one publishing unit corresponds to the Git source code library, and each publishing unit constructs a version package, when in production, a handover pipeline is generated for each version package, and corresponding personnel are needed to confirm the corresponding handover pipeline, thereby increasing the workload of production handover. In addition, when a production plan is implemented, each handover line needs to be manually triggered, when a plurality of handover lines exist, the production time is increased, and particularly when the production time window is small, errors are more likely to occur during production.

Disclosure of Invention

In view of the above, the present disclosure provides a program commissioning method, apparatus, electronic device, readable storage medium, and computer program product.

According to a first aspect of the present disclosure, there is provided a program commissioning method, the method including but not limited to: responding to entity content of a target program release version, and recording the production time of the target program release version, wherein the target program release version is provided with a version identification mark; generating a production scheme according to the production scheme template and the production time, wherein the production scheme corresponds to the release version of the target program; generating a merging list according to the version identification mark of the target program release version; and sending the corresponding entity content of the target program release version to an online operation unit according to the merging list, and performing online operation on the entity content by the online operation unit according to the production scheme.

In some exemplary embodiments of the present disclosure, the version identifier includes a responsible object identifier and an application system identifier, and the generating a merged manifest according to the version identifier of the release version of the target program includes: acquiring a responsible object identifier and an application system identifier in the version identification identifier; and generating a merging list of version information of the target program release versions belonging to the same responsible object identifier and the same application system identifier.

In some exemplary embodiments of the present disclosure, the sending, according to the merged manifest, the entity content of the corresponding target program release version to an online running unit includes: acquiring the merging list; determining entity content of the corresponding target program release version in the merged list; generating a handover pipeline according to the entity content of the target program release version; and sending the handover assembly line to an online operation unit.

In some exemplary embodiments of the present disclosure, before generating a handover pipeline, the sending, according to the merged list, the entity content of the corresponding target program release version to an online execution unit further includes: and performing first confirmation on the merged list to confirm whether the entity content of the target program release version contained in the merged list is correct or not.

In some exemplary embodiments of the present disclosure, after generating a handover pipeline, the sending, according to the merged list, the entity content of the corresponding target program release version to an online execution unit further includes: performing a second confirmation on the handover pipeline to confirm whether the handover pipeline contains the entity contents of all target program release versions in the merged list; and sending the entity content of the determined at least one target program release version in the handover pipeline to an online operation unit.

In some exemplary embodiments of the present disclosure, the generating a commissioning solution according to a commissioning solution template and the commissioning time comprises: at least obtaining the production actions in the production scheme template; and determining the execution time of the production action according to the production time to generate a production scheme.

In some exemplary embodiments of the present disclosure, before said generating a commissioning plan according to a commissioning plan template and said commissioning time, further comprising determining whether the commissioning plan template has been maintained; and if the production scheme template is not maintained, sending a maintenance instruction to a tester, and prompting that the production scheme is failed to generate.

In some exemplary embodiments of the present disclosure, before the generating a commissioning plan according to the commissioning plan template and the commissioning time, further comprises: judging whether the production scheme is generated or not; if the production scheme is generated, the production scheme corresponding to the target program release version is not generated; and if the production scheme is not generated, generating the production scheme corresponding to the release version of the target program.

According to a second aspect of the present disclosure, there is provided a program commissioning apparatus including, but not limited to: the response module is configured to respond to the entity content of the target program release version and record the production time of the target program release version, and the target program release version has a version identification mark; the first generation module is configured to generate a production scheme according to a production scheme template and the production time, wherein the production scheme corresponds to the target program release version; the second generation module is configured to generate a merging list according to the version identification identifier of the target program release version; and the sending module is configured to send the corresponding entity content of the target program release version to an online running unit according to the merged list, and the online running unit carries out online running on the entity content according to the production scheme.

In some exemplary embodiments of the present disclosure, the version identification includes a responsible object identification and an application system identification, and the program commissioning apparatus further includes a merge submodule configured to: acquiring a responsible object identifier and an application system identifier in the version identification identifier; and generating a merging list of version information of the target program release versions belonging to the same responsible object identifier and the same application system identifier.

In some exemplary embodiments of the disclosure, the program commissioning device further comprises a sending submodule configured to: acquiring the merging list; determining entity content of the corresponding target program release version in the merged list; generating a handover pipeline according to the entity content of the target program release version; and sending the handover assembly line to an online operation unit.

In some exemplary embodiments of the present disclosure, the program commissioning apparatus further includes a first confirmation module, where the first confirmation module is configured to perform a first confirmation on the merged list before generating a handover pipeline, so as to confirm whether entity contents of the target program release version included in the merged list are correct.

In some exemplary embodiments of the disclosure, the program commissioning apparatus further includes a second confirmation module configured to perform a second confirmation on the handover pipeline after generating the handover pipeline to confirm whether the handover pipeline contains the physical contents of all target program release versions in the merged list; and sending the entity content of the determined at least one target program release version in the handover pipeline to an online operation unit.

In some exemplary embodiments of the present disclosure, the program commissioning device further comprises a generation submodule configured to obtain at least commissioning actions in the commissioning scheme template; and determining the execution time of the production action according to the production time to generate a production scheme.

In some exemplary embodiments of the present disclosure, the program commissioning device further includes a first determining module configured to determine whether a commissioning scheme template has been maintained before the commissioning scheme is generated according to the commissioning scheme template and the commissioning time; and if the production scheme template is not maintained, sending a maintenance instruction to a tester, and prompting that the production scheme is failed to generate.

In some exemplary embodiments of the present disclosure, the program commissioning device further comprises a second judging module configured to judge whether the commissioning scheme has been generated before the commissioning scheme is generated according to the commissioning scheme template and the commissioning time; if the production scheme is generated, the production scheme corresponding to the target program release version is not generated; and if the production scheme is not generated, generating the production scheme corresponding to the release version of the target program.

According to a third aspect of the present disclosure, there is provided an electronic device comprising: one or more processors; a storage device for storing executable instructions that, when executed by the processor, implement the method according to the above.

According to a fourth aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon executable instructions which, when executed by a processor, implement a method according to the above.

According to a fifth aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a method according to the above.

According to the embodiment of the disclosure, before the program is operated online, the merging list is generated according to the version identification mark of the target program release version, so that the operation steps of sending the entity content to the online operation unit can be reduced, and the online operation time is effectively saved. In addition, the entity content is sent to the online operation unit according to the merged list, so that the risk of handover omission during production handover can be reduced.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:

fig. 1 schematically shows a schematic diagram of a system architecture to which the program commissioning method of an embodiment of the present disclosure may be applied;

FIG. 2 schematically shows a flow chart of a program commissioning method according to an embodiment of the present disclosure;

fig. 3 schematically shows a flowchart of a program commissioning method according to an embodiment of the present disclosure at operation S230;

fig. 4 schematically shows a flowchart of sending entity content to an online execution unit according to a program commissioning method of an embodiment of the present disclosure;

fig. 5 schematically shows a flow of the program commissioning method according to an embodiment of the present disclosure before operation S430;

fig. 6 schematically shows a flow of the program commissioning method according to an embodiment of the present disclosure after operation S430;

fig. 7 schematically shows a flow at operation S220 of a program commissioning method according to an embodiment of the present disclosure;

fig. 8 schematically shows a flow of the program commissioning method according to an embodiment of the present disclosure before operation S220;

fig. 9 schematically shows another flow of the program commissioning method according to an embodiment of the present disclosure before operation S220;

FIG. 10 schematically shows a block diagram of a program launch device according to an embodiment of the disclosure; and

fig. 11 schematically shows a block diagram of an electronic device adapted to implement the program commissioning method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, necessary security measures are taken, and the customs of the public order is not violated.

In the related art, as DevOps (combination words of Development and Operations) transformation projects advance, various applications make continuous delivery standardization improvement, and publishing unit combing and improvement are an important part in continuous delivery standardization improvement, and many applications make publishing improvement of publishing units currently. The release unit is the minimum unit of application software component and deployment, and is the expression of the code to the physical node in operation. One application system is provided with a plurality of service groups, one service group can be provided with a plurality of publishing units, one publishing unit corresponds to one Git source code library, and each publishing unit constructs one version package. After each application is subjected to continuous delivery standardization transformation, one service group corresponds to one independent sub-application, and the effect of reducing the space occupation of the edition entity content can be achieved during edition sending, but the following problems are also generated:

first, it results in a dramatic increase in commissioning solution maintenance. An application system using a master application number, such as F-ABCD, only needs to maintain a single commissioning scenario before continuing delivery standardization. After the continuous delivery standardization transformation, one application service group corresponds to one sub-application, and one application system has a plurality of service groups, so that besides the original application number, the application system also has a plurality of sub-application numbers, such as F-ABCD-EF, F-ABCD-XY and the like, each sub-application number needs to maintain a production scheme, the amount of the maintenance production scheme is increased greatly, and the workload is increased.

Secondly, the number of production switching pipelines increases dramatically, and the manual processing content increases. An application system using a master application number, such as F-ABCD, only needs to generate and validate a handover pipeline before continuing delivery standardization; after the continuous delivery standardization transformation, one application service group corresponds to one sub-application, and one application system has a plurality of service groups, so that one application system has a plurality of sub-application numbers, such as F-ABCD-EF, F-ABCD-XY and the like, besides the original one application number, each sub-application number needs to generate and confirm a production delivery assembly line, which increases the workload of production delivery, for example, a plurality of delivery assembly lines need to be generated, and a plurality of delivery assembly lines need to be confirmed one by one.

In addition, the production and production implementation switching assembly line is increased sharply, the manual processing steps are increased, and the production time is prolonged. Before the continuous delivery standardization, an application system uses a main application number, such as F-ABCD, and only one handover pipeline needs to be processed when production and production are carried out; after continuous delivery standardization transformation, one application service group corresponds to one sub-application, and one application system is provided with a plurality of service groups, so that one application system is provided with a plurality of sub-application numbers such as F-ABCD-EF and F-ABCD-XY besides the original application number, each sub-application number is provided with a handover assembly line, the original handover assembly line is changed into a plurality of handover assembly lines in production commissioning implementation, each handover assembly line needs to be triggered manually, the whole commissioning time is increased, and the risk that the commissioning time window is not enough exists

After the release unit is transformed, the number of sub application numbers is increased sharply, the manual operation contents of the handover link and the production link are increased, the processing time of the whole handover is increased, the whole production time is increased, and the risk of missing a production scheme, the risk of missing a handover assembly line and the risk of not enough production time windows exist.

In this regard, the present disclosure provides a program commissioning method, including but not limited to: responding to the entity content of the target program release version, and recording the production time of the target program release version, wherein the target program release version is provided with a version identification mark; generating a production scheme according to the production scheme template and the production time, wherein the production scheme corresponds to the release version of the target program; generating a merging list according to the version identification mark of the target program release version; and sending the entity content of the corresponding target program release version to an online operation unit according to the merging list, and performing online operation on the entity content by the online operation unit according to a production scheme.

Fig. 1 schematically shows a schematic diagram of a system architecture to which the program production method of the embodiment of the present disclosure can be applied. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios. It should be noted that the program production method and apparatus provided by the embodiments of the present disclosure may be used in the related aspects of the computer program technology field and the financial field, and may also be used in any field other than the financial field.

As shown in fig. 1, an exemplary system architecture 100 to which the method of application delivery may be applied may include

terminal devices

101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

10l, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as a file handling type application, a shopping type application, a web browser application, a search type application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only).

The

terminal devices

101, 102, 103 may be various electronic devices having display screens and supporting functions of data analysis, data processing, web browsing, etc., including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, etc.

The server 105 may be a server that provides various services, such as a background management server that provides support for a website that a user acquires or browses using the

terminal devices

101, 102, 103 (just an example). The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device. The file or the like transmitted by the user may be analyzed or processed, and the terminal device may be controlled based on the processing result, for example, access of the terminal device may be restricted.

It should be noted that the program commissioning method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the program production device provided by the embodiment of the present disclosure may be generally disposed in the server 105. The program commissioning method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the program production device provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The program commissioning method of the disclosed embodiment will be described in detail below by means of fig. 2 to 9.

As shown in fig. 2, the commissioning method 200 of the embodiment of the present disclosure includes operations S210 to S240.

In operation S210, in response to the entity content of the target program release version, the production time of the target program release version is recorded, and the target program release version has a version identification.

In the embodiment of the present disclosure, the target program release version refers to a version of a program that needs to be put into production, and in program design and use, the target program version is different for different system environments or different devices such as different clients and servers, and meanwhile, during the use of the program, bug repair or function upgrade needs to be performed. Therefore, the version of the target program needs to be updated. The entity content of the target program release version refers to entity content such as a program package or an installation package of the version. The entity content may be, for example, a relevant version of a release by a software development center in a software process and management system.

And after the entity content of the target program release version is released, responding to the entity content of the target program release version, and recording the production time of the target program release version, namely determining when the target program release version is operated online. Before the target program release version is put into production, the target program release version can be tested and the like.

In an embodiment of the present disclosure, the target program release version has a version identification identifier, and different information, for example, different versions of responsible objects and application systems, are determined according to the version identification identifier, so that different operations are performed according to the different responsible objects and application systems. The responsible object is, for example, the main technical department responsible for the release version. The application system may be, for example, a published application number.

In the embodiment of the present disclosure, the commissioning time of the target program release version may be a preset time, or may be a time manually set by a worker. After the entity content of the target program release version is generated, the production time corresponding to the target program release version can be generated according to the preset time, and an input interface can also be generated for a worker to input the set production time. In other alternative embodiments, in order to improve the operation efficiency of the program production method, the production time may be automatically generated according to the set time.

In operation S220, a production schedule is generated according to the production schedule template and the production time, where the production schedule corresponds to the release version of the target program.

In an embodiment of the present disclosure, a commissioning solution template includes elements that generate a commissioning solution that are necessary to generate the commissioning solution. For example, elements in a production scenario template may include a production time element, a production action element, a production description element, and a production deployment program element. The production scheme can be generated by automatically acquiring and filling the element content in the production scheme template. And generating a production scheme corresponding to the release version of the target program according to each release version of the target program.

In other embodiments, when the commissioning scheme template of a certain target program release version is different from the general template, the requirement of different target program release versions can be met by manual adjustment of a worker.

In operation S230, a merged manifest is generated according to the version identifier of the release version of the target program.

In the embodiment of the present disclosure, the entity content of the release version of the target program has a plurality of, for example, has a plurality of release versions. In this case, when the plurality of programs are put into production, if the target program release version is put into production once, the operation content of the target program release version is greatly increased in the production link, which increases the processing time of the entire link and also increases the error rate due to the increase of the operation content.

In the subsequent program production link, the operations such as handover, online operation and the like are performed on the entity content of the program release version according to the merge list, so that the operation content of the program production link can be reduced in reply, the processing time is reduced, and the error rate is reduced.

In operation S240, the entity content of the corresponding target program release version is sent to the online operation unit according to the merged list, and the online operation unit performs online operation on the entity content according to the production scheme.

In the embodiment of the disclosure, the merged list has a plurality of corresponding target program release versions, and the entity content of the plurality of corresponding target program release units in the merged list is sent to the online running unit without sending each target program version once, so that the number of times of sending the entity content of the target program release versions to the online running unit can be effectively reduced.

In addition, according to the above, when the production schedule is generated, a production schedule is correspondingly generated for each target program release version, and after different target program release versions are sent to the online operation unit, the target program release versions are operated online for the entity content according to the corresponding production schedule, so that the efficiency of online operation can be effectively improved. In the online operation process, manual maintenance of workers can be omitted, automatic operation is completed, online operation time is effectively saved, and the risk that a production time window is insufficient is reduced.

Fig. 3 schematically shows a flowchart of a program commissioning method according to an embodiment of the present disclosure at operation S230.

In an embodiment of the present disclosure, the version identification includes a responsible object identification and an application system identification. The responsible object identifies the responsible technical department representing the release version of the target program. The application system identifier indicates an application number corresponding to the version release of the target program release version, and may be, for example, content such as an application number name.

As shown in fig. 3, generating the merged manifest according to the version identification of the release version of the target program in operation S230 includes operations S231 to S232.

In operation S231, a responsible object identification and an application system identification in the version identification are acquired.

And each target program release version correspondingly has a responsible object identification and an application system identification. Therefore, subsequent operations are realized by acquiring the responsible object identifier and the application system identifier corresponding to the target program release version.

After operation S231 is completed, operation S232 is performed. In operation S232, a merged list is generated from version information of target program release versions belonging to the same responsible object id and belonging to the same application system id.

For example, the application system identification is the primary application number and the responsible object identification is the responsible technology department. And merging the version information of the target program release version of the same main application number under the same application system in charge of the same technical department according to the main application number to generate a merged list.

And for version information of different responsible object identifications or target program release versions which do not belong to the same application system identification, not merging. For example, version information of the release version of the target program of different sub-application numbers of the same application system is responsible for different technical departments, only the version information corresponding to the technical department in which the main application number is responsible is merged, and the version information corresponding to the sub-application numbers in which other technical departments are responsible is not merged.

Fig. 4 schematically shows a flowchart of sending entity content to an online execution unit according to a program commissioning method of an embodiment of the present disclosure.

As shown in fig. 4, the process 400 of sending the entity content of the corresponding target program release version to the online execution unit according to the merged list includes operations S410 to S440.

In operation S410, a merge list is acquired. The merged list corresponds to the entity content of the target program release versions, and each target program release version corresponds to one entity content.

In operation S420, the entity content of the corresponding target program release version in the merged manifest is determined.

For example, if the merged list has version information of multiple target program release versions, the entity content of the corresponding target program release version may be determined according to each version information, and the entity content may be operated.

In operation S430, a handover pipeline is generated according to the entity content of the target program release version.

In the embodiment of the disclosure, the handover pipeline includes entity content corresponding to the version information of the target program release version in the merged list. For example, the handover pipeline may be a compressed file package containing file contents of a plurality of target program release versions corresponding to the merge list.

In operation S440, the handover pipeline is transmitted to the on-line execution unit.

After the handover pipeline is sent to the online operation unit, the online operation unit performs online operation on a plurality of entity contents in the handover pipeline.

Fig. 5 schematically shows a flow of the program commissioning method according to an embodiment of the present disclosure before operation S430.

As shown in fig. 5, before generating the handover pipeline, sending the corresponding entity content of the target program release version to the online running unit according to the merge list further includes an operation S500, and in the operation S500, performing a first confirmation on the merge list to confirm whether the entity content of the target program release version included in the merge list is correct.

For example, the merge list includes version information of a plurality of target program release versions, and each version information corresponds to the entity content of the target program release version. By first validating the merge list, errors in generating the handoff pipeline may be reduced. In the embodiment of the present disclosure, the first confirmation may be set to be performed automatically, so as to improve efficiency while reducing an error rate.

Fig. 6 schematically shows a flow of the program commissioning method according to an embodiment of the present disclosure after operation S430.

As shown in fig. 6, after the handover pipeline is generated, the process 600 of sending the entity content of the corresponding target program release version to the online execution unit according to the merged list further includes operations S610 to S620.

In operation S610, the handover pipeline is checked for a second time to determine whether the handover pipeline contains the physical contents of all target program release versions in the merged list.

In the embodiment of the present disclosure, the handover pipeline includes the entity contents of all target program release versions corresponding to the merge list. In the process of generating the handover pipeline, the problem that the entity content is lost or damaged due to improper operation may exist, and for this reason, by determining the entity content, the possibility of error can be further reduced, and the success rate can be improved.

In operation S620, the physical contents of the at least one target program release version determined in the handover pipeline are transmitted to the online execution unit.

In the embodiment of the present disclosure, the handover pipeline includes entity contents of multiple target program release versions, and after the entity contents are sent to the online operation unit, the online operation unit may determine one or more entity contents finally, which may be selected according to actual needs to determine the entity contents of at least one target program release version to be operated online.

Fig. 7 schematically shows a flow at operation S220 of a program commissioning method according to an embodiment of the present disclosure.

As shown in fig. 7, the process S220 of generating the commissioning scheme according to the commissioning scheme template and the commissioning time may include operations S221 to S222.

In operation S221, at least a commissioning action in the commissioning scenario template is obtained.

In an embodiment of the present disclosure, a commissioning scenario template includes a plurality of elements therein. When a production scheme is generated according to a production scheme target, at least obtaining production actions in a production scheme template for a plurality of elements, wherein the production actions are used for determining specific online running actions of entity content corresponding to a target program release version.

In other embodiments, the method further comprises obtaining other elements in the production schedule template, and generating the production schedule according to the obtained other elements and the production actions.

In operation S222, the execution time of the commissioning action is determined according to the commissioning time, and a commissioning plan is generated.

And after the production operation is obtained, generating a production scheme according to the production time determined by the entity content corresponding to the target program release version, wherein the production scheme is used for determining the specific online running mode and time of the entity content corresponding to the target program release version.

Fig. 8 schematically shows a flow of the program commissioning method according to an embodiment of the present disclosure before operation S220.

As shown in fig. 8, before generating the commissioning scheme according to the commissioning scheme template and the commissioning time, the method further includes a process S800, in operation S800, it is determined whether the commissioning scheme template is maintained, and if the commissioning scheme template is not maintained, a maintenance instruction is sent to a tester, and a failure in generating the commissioning scheme is prompted.

For example, if the commissioning scheme template is not maintained, a maintenance instruction is sent to the corresponding tester in a manner of e-mail or the like, and the tester is prompted to maintain the commissioning scheme template, for example, the element content required by the commissioning scheme target is determined, so that the commissioning scheme can be automatically generated subsequently. In addition, as the target of the production scheme is not maintained, the production scheme cannot be generated, and the corresponding staff production scheme is prompted on the display interface to fail to generate. And if the production scheme template and the maintenance are carried out, generating a production scheme according to the corresponding content.

Fig. 9 schematically shows another flow of the program commissioning method according to an embodiment of the present disclosure before operation S220.

As shown in fig. 9, before generating the production schedule according to the production schedule template and the production time, a process 900 is further included, and the process 900 includes operations S910 to S930.

In operation S910, it is determined whether a commissioning plan has been generated.

If the production plan is generated, operation S920 is performed, and the production plan corresponding to the release version of the target program is not generated.

If the production plan is not generated, operation S930 is performed to generate a production plan corresponding to the release version of the target program.

According to the embodiment of the disclosure, repeated steps are reduced and the efficiency is improved by judging whether the production scheme corresponding to the release version of the target program is generated before the production scheme is generated.

According to the program production method, the merging list is generated according to the version identification mark of the target program release version before the program is subjected to online operation, so that the operation steps of sending the entity content to the online operation unit can be reduced, and the online operation time is effectively saved. In addition, the entity content is sent to the online operation unit according to the merged list, so that the risk of handover omission during production handover can be reduced.

Fig. 10 schematically shows a block diagram of a program production apparatus according to an embodiment of the present disclosure.

As shown in fig. 10, the program production apparatus 1000 of the embodiment of the present disclosure includes a response module 1010, a first generation module 1020, a second generation module 1030, and a sending module 1040.

The response module 1010 is configured to respond to the entity content of the target program release version, and record the production time of the target program release version, where the target program release version has a version identification. In an embodiment, the response module 1010 may be configured to perform the operation S210 described above, which is not described herein again.

The first generating module 1020 is configured to generate a production schedule according to the production schedule template and the production time, where the production schedule corresponds to the release version of the target program. The first generating module 1020 may be configured to perform the operation S220 described above, and will not be described herein again.

And a second generating module 1030 configured to generate the merged list according to the version identification of the release version of the target program. The second generating module 1030 may be configured to perform the operation S230 described above, which is not described herein again.

The sending module 1040 is configured to send the entity content of the corresponding target program release version to the online running unit according to the merged list, and the online running unit performs online running on the entity content according to the production scheme. The sending module 1040 may be configured to perform the operation S240 described above, and is not described herein again.

In some exemplary embodiments of the present disclosure, the version identification identifier includes a responsible object identifier and an application system identifier, and the program commissioning apparatus further includes a merging submodule configured to: acquiring a responsible object identifier and an application system identifier in the version identification identifier; and generating a merging list of version information of the target program release versions belonging to the same responsible object identifier and the same application system identifier.

In some exemplary embodiments of the present disclosure, the program commissioning device further includes a sending submodule configured to: acquiring a merging list; determining entity content of a corresponding target program release version in the merged list; generating a handover pipeline according to the entity content of the target program release version; and sending the handover assembly line to an online operation unit.

In some exemplary embodiments of the disclosure, the program commissioning device further includes a first confirmation module configured to perform a first confirmation on the merged list before generating the handover pipeline, so as to confirm whether the entity content of the target program release version contained in the merged list is correct.

In some exemplary embodiments of the disclosure, the program commissioning device further comprises a second confirmation module configured to perform a second confirmation of the handover pipeline after the handover pipeline is generated, to confirm whether the handover pipeline contains the physical contents of all target program release versions in the merged list; and sending the entity content of the determined at least one target program release version in the handover pipeline to the online operation unit.

In some exemplary embodiments of the present disclosure, the program commissioning device further includes a generation submodule configured to obtain at least commissioning actions in the commissioning scheme template; and determining the execution time of the production action according to the production time, and generating a production scheme.

In some exemplary embodiments of the present disclosure, the program commissioning device further includes a first determining module configured to determine whether the commissioning scheme template has been maintained before generating the commissioning scheme according to the commissioning scheme template and the commissioning time; and if the production scheme template is not maintained, sending a maintenance instruction to a tester, and prompting that the production scheme is failed to generate.

In some exemplary embodiments of the disclosure, the program commissioning device further comprises a second determination module configured to determine whether a commissioning plan has been generated before generating the commissioning plan according to the commissioning plan template and the commissioning time; if the production scheme is generated, the production scheme corresponding to the release version of the target program is not generated; and if the production scheme is not generated, generating the production scheme corresponding to the release version of the target program.

According to an embodiment of the present disclosure, any multiple modules of the response module 1010, the first generation module 1020, the second generation module 1030, the sending module 1040, the merging sub-module, the sending sub-module, the first confirmation module, the second confirmation module, the generation sub-module, the first judgment module, and the second judgment module may be combined and implemented in one module, or any one module may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to the embodiment of the disclosure, at least one of the response module 1010, the first generation module 1020, the second generation module 1030, the transmission module 1040, the merging sub-module, the transmission sub-module, the first confirmation module, the second confirmation module, the generation sub-module, the first judgment module, and the second judgment module may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementation manners of software, hardware, and the same or by a suitable combination of any of the three. Alternatively, at least one of the response module 1010, the first generation module 1020, the second generation module 1030, the sending module 1040, the merging sub-module, the sending sub-module, the first confirmation module, the second confirmation module, the generation sub-module, the first judgment module, and the second judgment module may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.

Fig. 11 schematically shows a block diagram of an electronic device adapted to implement the program commissioning method according to an embodiment of the present disclosure. The electronic device shown in fig. 11 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 11, an electronic device 1100 according to an embodiment of the present disclosure includes a processor 1101, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1102 or a program loaded from a storage section 1108 into a Random Access Memory (RAM) 1103. The processor 1101 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 1101 may also include on-board memory for caching purposes. The processor 1101 may comprise a single processing unit or a plurality of processing units for performing the different actions of the method flows according to the embodiments of the present disclosure.

In the RAM 1103, various programs and data necessary for the operation of the electronic device 1100 are stored. The processor 1101, the ROM 1102, and the RAM 1103 are connected to each other by a bus 1104. The processor 1101 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1102 and/or the RAM 1103. It is noted that the programs may also be stored in one or more memories other than the ROM 1102 and RAM 1103. The processor 1101 may also perform various operations of the method flows according to the embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 1100 may also include input/output (I/O) interface 1105, input/output (I/O) interface 1105 also connected to bus 1104, according to an embodiment of the disclosure. Electronic device 1100 may also include one or more of the following components connected to I/O interface 1105: an input portion 1106 including a keyboard, mouse, and the like; an output portion 1107 including a signal output unit such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 1108 including a hard disk and the like; and a communication section 1109 including a network interface card such as a LAN card, a modem, or the like. The communication section 1109 performs communication processing via a network such as the internet. A driver 1110 is also connected to the I/O interface 1105 as necessary. A removable medium 1111, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is installed on the drive 1110 as necessary, so that a computer program read out therefrom is installed into the storage section 1108 as necessary.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement a program commissioning method according to an embodiment of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 1102 and/or the RAM 1103 and/or one or more memories other than the ROM 1102 and the RAM 1103 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the program production method provided by the embodiment of the disclosure.

The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 1101. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via the communication part 1109, and/or installed from the removable medium 1111. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program can be downloaded and installed from a network through the communication portion 1109 and/or installed from the removable medium 1111. The computer program, when executed by the processor 1101, performs the above-described functions defined in the system of the embodiment of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. A program commissioning method, comprising:

responding to entity content of a target program release version, and recording the production time of the target program release version, wherein the target program release version is provided with a version identification mark;

generating a production scheme according to the production scheme template and the production time, wherein the production scheme corresponds to the target program release version;

generating a merging list according to the version identification mark of the target program release version;

and sending the corresponding entity content of the target program release version to an online operation unit according to the merging list, and performing online operation on the entity content by the online operation unit according to the production scheme.

2. The program production method according to claim 1,

the version identification comprises a responsible object identification and an application system identification,

the generating a merged list according to the version identification of the target program release version includes:

acquiring a responsible object identifier and an application system identifier in the version identification identifier;

and generating a merging list of version information of the target program release versions belonging to the same responsible object identifier and the same application system identifier.

3. The program production method according to claim 1,

the sending the entity content of the corresponding target program release version to an online operation unit according to the merge list comprises:

acquiring the merging list;

determining entity content of the corresponding target program release version in the merged list;

generating a handover pipeline according to the entity content of the target program release version;

and sending the handover assembly line to an online operation unit.

4. The program launch method of claim 3 wherein, prior to generating the handoff pipeline,

the sending the entity content of the corresponding target program release version to the online running unit according to the merged list further comprises:

and performing first confirmation on the merged list to confirm whether the entity content of the target program release version contained in the merged list is correct or not.

5. The program delivery method of claim 4, wherein, after the handoff pipeline is generated,

performing a second confirmation on the handover pipeline to confirm whether the handover pipeline contains the entity contents of all target program release versions in the merged list; and

and sending the entity content of the determined at least one target program release version in the handover pipeline to an online operation unit.

6. The program production method according to claim 1,

the generating a production schedule according to the production schedule template and the production time comprises:

at least obtaining the production actions in the production scheme template;

and determining the execution time of the production action according to the production time to generate a production scheme.

7. The program production method according to claim 1,

before generating a production schedule according to the production schedule template and the production time, judging whether the production schedule template is maintained;

and if the production scheme template is not maintained, sending a maintenance instruction to a tester, and prompting that the production scheme is failed to generate.

8. The program commissioning method of claim 1, wherein prior to said generating a commissioning scheme according to a commissioning scheme template and said commissioning time, further comprising:

judging whether the production scheme is generated;

if the production scheme is generated, the production scheme corresponding to the target program release version is not generated;

and if the production scheme is not generated, generating the production scheme corresponding to the release version of the target program.

9. A program production apparatus comprising:

the response module is configured to respond to the entity content of the target program release version and record the production time of the target program release version, and the target program release version is provided with a version identification mark;

the first generation module is configured to generate a production scheme according to a production scheme template and the production time, wherein the production scheme corresponds to the target program release version;

the second generation module is configured to generate a merging list according to the version identification identifier of the target program release version;

and the sending module is configured to send the corresponding entity content of the target program release version to an online running unit according to the merged list, and the online running unit carries out online running on the entity content according to the production scheme.

10. An electronic device, comprising:

one or more processors;

storage means for storing executable instructions that, when executed by the processor, implement the method of any one of claims 1 to 8.

11. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, implement the method of any one of claims 1 to 8.

12. A computer program product comprising a computer program that when processed and executed implements the method of any one of claims 1 to 8.