CN115421775A - Data processing method and device, electronic equipment and storage medium - Google Patents
Data processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115421775A CN115421775A CN202211084640.6A CN202211084640A CN115421775A CN 115421775 A CN115421775 A CN 115421775A CN 202211084640 A CN202211084640 A CN 202211084640A CN 115421775 A CN115421775 A CN 115421775A
- Authority
- CN
- China
- Prior art keywords
- code
- production
- current
- version
- branch
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 31
- 238000004519 manufacturing process Methods 0.000 claims abstract description 235
- 238000012795 verification Methods 0.000 claims abstract description 86
- 238000007689 inspection Methods 0.000 claims abstract description 34
- 238000000034 method Methods 0.000 claims abstract description 26
- 230000010354 integration Effects 0.000 claims description 37
- 230000002085 persistent effect Effects 0.000 claims description 23
- 230000015654 memory Effects 0.000 claims description 20
- 238000012545 processing Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 10
- 238000010200 validation analysis Methods 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims description 3
- 238000013524 data verification Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 11
- 238000011161 development Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000011981 development test Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 239000003550 marker Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a data processing method and device, electronic equipment and a storage medium, and belongs to the technical field of data verification. The method comprises the following steps: receiving a checking request of the current production version sent by the application layer; acquiring a production branch code of a current production version, a current service verification branch code and a historical production code from the remote code warehouse according to the inspection request; and when the main code of the production branch code is the same as that of the current business verification branch code and the main code of the production branch code is different from that of the historical production code, determining that the current production version passes the verification, wherein the main code is a code excluding version configuration information in the code. The method can solve the problem that the product production errors caused by inconsistent code versions are avoided under the condition that the code versions are inconsistent.
Description
Technical Field
The present application relates to the field of data verification technologies, and in particular, to a data processing method and apparatus, an electronic device, and a storage medium.
Background
With the development of computer technology, the version of a computer system is continuously updated iteratively, and the iterative updating speed is faster and faster, which brings many problems to the production of program products. For example, the development test environment, the business verification environment and the production environment of program products often have the problem of inconsistent code versions, which finally results in incorrect production versions, thereby causing production accidents. The problem of inconsistent code versions includes, for example, the following: 1) Generating a historical version; 2) The production version is inconsistent with the development environment and the service verification environment; 3) Production version code reviews are inadequate.
For the problem of inconsistent code versions, developers generally check the code versions to avoid the inconsistent code versions. However, the excessive code amount causes the problems of high cost and code omission of manual inspection.
Therefore, how to solve the problem of inconsistent code versions, thereby avoiding the problem of product production errors caused by inconsistent code versions due to inconsistent code versions is still considered.
Disclosure of Invention
The application provides a data processing method and device, an electronic device and a storage medium, which are used for solving the problem of inconsistent code versions and avoiding the problem of production errors caused by inconsistent code versions.
In one aspect, the present application provides a data processing method applied to a service layer of an electronic device, where the electronic device further includes an application layer and a remote code repository, and the method includes:
receiving a checking request of a current production version sent by the application layer;
obtaining a production branch code of a current production version, a current business verification branch code and a historical production code from the remote code warehouse according to the inspection request;
and when the main code of the production branch code is the same as the main code of the current business verification branch code and the main code of the production branch code is different from the main code of the historical production code, determining that the current production version passes the verification, wherein the main code is a code excluding version configuration information in the code.
In one embodiment, the obtaining the production branch code, the current business verification branch code and the historical production code of the current production version from the remote code warehouse according to the verification request includes:
acquiring a continuous integration tool according to the inspection request;
obtaining, by a persistent integration tool, a production branch code, a current business validation branch code, and a historical production code from the remote code repository.
In one embodiment, the persistent integration tool comprises Jenkins.
In one embodiment, the acquiring the persistent integration tool according to the inspection request includes:
and invoking an inspection strategy according to the inspection request so as to acquire the continuous integration tool based on the inspection strategy.
In one embodiment, the obtaining, by the persistent integration tool, the production branch code, the current business verification branch code, and the historical production code from the remote code repository includes:
sending a remote code command to the remote code repository through a persistent integration tool to obtain a production branch code, a current business verification branch code and a historical commissioning code from the remote code repository, wherein the remote code command is a Git command, and Git is a code management tool of the remote code repository.
In one embodiment, the method further comprises:
comparing the current production version with the historical production version to obtain a change file and a newly added file of the current production version;
and generating a change code list according to the change file and the added file.
In one embodiment, the method further comprises:
determining that the current commissioning version check fails when the main code of the production branch code and the main code of the current business verification branch code are different.
In another aspect, the present application provides a data processing apparatus applied to a service layer of an electronic device, where the electronic device further includes an application layer and a remote code repository, and the apparatus includes:
the communication module is used for receiving a checking request of the current production version sent by the application layer;
the acquisition module is used for acquiring a production branch code of a current production version, a current service verification branch code and a historical production code from the remote code warehouse according to the inspection request;
and the checking module is used for determining that the current production version passes the checking when the main code of the production branch code is the same as the main code of the current business verification branch code and the main code of the production branch code is different from the main code of the historical production code, wherein the main code is a code excluding version configuration information in the code.
In one embodiment, the obtaining module is specifically configured to:
acquiring a continuous integration tool according to the inspection request;
production branch codes, current business validation branch codes, and historical production codes are obtained from the remote code repository through a persistent integration tool.
In one embodiment, the persistent integration tool comprises Jenkins.
In one embodiment, the obtaining module is specifically configured to:
and invoking an inspection strategy according to the inspection request so as to obtain the continuous integration tool based on the inspection strategy.
In one embodiment, the obtaining module is specifically configured to:
sending, by a persistent integration tool, a remote code command to the remote code repository to obtain a production branch code, a current business verification branch code, and a historical commissioning code from the remote code repository, the remote code command being a Git command, git being a code management tool of the remote code repository.
In one embodiment, the processing module is further configured to:
comparing the current production version with the historical production version to obtain a change file and a newly added file of the current production version;
and generating a change code list according to the change file and the added file.
In one embodiment, the processing module is further configured to:
determining that the current commissioning version verification fails when the main code of the production branch code and the main code of the current business verification branch code are different.
In another aspect, the present application provides an electronic device comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to implement the data processing method of the first aspect.
In another aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions that, when executed, cause a computer to perform the data processing method according to the first aspect.
In another aspect, the present application provides a computer program product, which when executed by a processor implements the data processing method according to the first aspect
The data processing method provided by the embodiment of the application receives a checking request of a current production version sent by the application layer, acquires a production branch code, a current business verification branch code and a historical production code of the current production version from the remote code warehouse according to the checking request, and then judges whether a main code of the production branch code of the current production version is the same as a main code of the current business verification branch code. And if the main code of the production branch code of the current production version is the same as the main code of the current business verification branch code, judging whether the main code of the production branch code is the same as the main code in the historical production code. And when the main code of the production branch code is the same as that of the current business verification branch code and the main code of the production branch code is different from that of the historical production code, determining that the current production version passes the verification.
Therefore, the method provided by the embodiment of the application can be used for inspecting the production versions before production, so that a production version inspection assembly line is formed, and the problem of product production errors caused by inconsistent code versions is avoided under the condition that the code versions are inconsistent. In addition, the problems of high cost and code missing caused by manual inspection due to overlarge code amount are solved, and the inspection accuracy of the production version is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic view of an application scenario of the data processing method provided in the present application;
fig. 2 is a schematic flow chart of a data processing method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a data processing method according to another embodiment of the present application;
FIG. 4 is a partial flow diagram of a data processing method according to another embodiment of the present application;
FIG. 5 is a partial flow diagram of a data processing method according to another embodiment of the present application;
FIG. 6 is a schematic diagram of a data processing apparatus provided by an embodiment of the present application;
fig. 7 is a schematic diagram of an electronic device provided in an embodiment of the present application.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. The drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the disclosed concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the disclosure, as detailed in the appended claims.
In the description of the present application, it is to be understood that the terms "first", "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implying any number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
The terms referred to in this application are explained first:
and MD5: the MD5 Message Digest Algorithm (english: MD5 Message-Digest Algorithm), a widely used cryptographic hash function, can generate a 128-bit (16-byte) hash value (hash value) to ensure the integrity of the Message transmission.
Git tag: tag is a marker of the Git version library that points to a pointer to a Commit. tag is mainly used for managing release versions, and after one version is released, we can tag Git.
Version baseline: the baseline is a "snapshot" of each artifact version in the project repository over a particular period of time. It provides a formal standard upon which subsequent work is based and which can only be altered after authorization.
Continuous integration: team development members often integrate their jobs, usually at least once per member per day, meaning that multiple integrations may occur per day. Each integration is verified by automated build (including compile, release, automated test) to discover integration errors as quickly as possible.
Jenkins: jenkins is an open source software project, is a continuous integration tool developed based on Java, is used for monitoring continuous and repeated work, and aims to provide an open and easy-to-use software platform so that the software project can be continuously integrated.
With the development of computer technology, the version of a computer system is continuously updated iteratively, and the iterative updating speed is faster and faster, which brings many problems to the production of program products. For example, the development test environment, the business verification environment and the production environment of program products often have the problem of inconsistent code versions, which finally results in incorrect production versions, thereby causing production accidents. The problem of inconsistent code versions includes, for example, the following: 1) Generating a historical version; 2) The production version is inconsistent with the development environment and the service verification environment; 3) Production version code reviews are inadequate.
For the problem of inconsistent code versions, developers generally check the code versions to avoid the inconsistent code versions. However, the excessive code amount causes the problems of high cost and code omission of manual inspection.
Based on the above, the application provides a data processing method, a data processing device, an electronic device and a storage medium. The data processing method is applied to a service layer of the electronic equipment, and the electronic equipment further comprises an application layer and a remote code repository. The data processing method comprises the following steps: receiving a checking request of the current production version sent by the application layer; obtaining a production branch code of a current production version, a current business verification branch code and a historical production code from the remote code warehouse according to the checking request; and when the main code of the production branch code is the same as that of the current business verification branch code and the main code of the production branch code is different from that of the historical production code, determining that the current production version passes the verification, wherein the main code is a code excluding version configuration information in the code.
The data processing method can be used for inspecting the production versions before production, so that a production version inspection assembly line is formed, and the problem of product production errors caused by inconsistent code versions due to inconsistent code versions is avoided. In addition, the problems of high cost and code missing caused by manual inspection due to overlarge code amount are solved, and the inspection accuracy of the production version is improved.
The data processing method provided by the application is applied to electronic equipment such as a computer, a server used in a laboratory and the like. Fig. 1 is an application schematic diagram of the data processing method provided in the present application, in which a service layer in the electronic device receives a checking request of a current production version sent by an application layer, and obtains a production branch code, a current service verification branch code, and a historical production branch code of the current production version from a remote code repository (Git layer) according to the checking request. And when the main code of the production branch code is the same as that of the current business verification branch code and the main code of the production branch code is different from that of the historical production code, determining that the current production version passes the verification.
Referring to fig. 2, an embodiment of the present application provides a data processing method applied to a Service layer (Service layer) of an electronic device, where the electronic device further includes an application layer (WEB) and a remote code repository (GIT).
S210, receiving a checking request of the current production version sent by the application layer.
The application layer is responsible for receiving the check request and then sending the check request to the service layer. The verification request may be understood as an integration request of a production version, and the service layer creates a continuous integration task according to the integration request to verify the production branch code of the current production version.
And S220, acquiring the production branch code, the current business verification branch code and the historical production code of the current production version from the remote code warehouse according to the checking request.
Upon receiving the verification request, a production branch code, a current business validation branch code, and a historical production code are obtained from the remote code repository. The remote code repository, i.e. the Git repository, stores therein the production branch codes corresponding to the production versions, also stores the historical production codes (production branch codes of the historical production versions), and also stores the current business verification branch codes.
In an alternative embodiment, after receiving the verification request, a persistent integration tool (e.g., jenkins, but other tools are also possible) is obtained, and then the production branch code, the current service verification branch code, and the historical production code are obtained from the remote code repository through the persistent integration tool. Optionally, the service layer integrates a checking policy of the persistent integration pipeline, and after receiving the checking request, the service layer invokes the checking policy according to the checking request to obtain the persistent integration tool based on the checking policy. The retrieved persistent integration tool is, for example, jenkins, and the service layer sends the instruction of the execution pipeline (i.e., the instruction to start execution of the check) to Jenkins, and Jenkins distributes the check steps step by step.
In an alternative embodiment, when the checking step is distributed step by Jenkins, a remote code command (Git command) is sent to the remote code repository (Git library), in particular by the Jenkins, to obtain from the remote code repository the production branch code of the current production version, the current business verification branch code and the historical production code.
More specifically, as shown in fig. 3, after receiving the verification request, the service layer sends a remote code command (Git command) to the remote code repository (Git library) through Jenkins, obtains the production branch code of the current production version at the Git layer, and then obtains the current service verification branch code. And generating a Git tag command, acquiring a last production version of the current production version by using the Git tag command, and acquiring the historical production code of the current production version according to a baseline of the last production version.
And S230, when the main code of the production branch code is the same as the main code of the current business verification branch code and the main code of the production branch code is different from the main code of the historical production code, determining that the current production version passes the verification, wherein the main code is a code excluding the version configuration information in the code.
After the production branch code, the current service verification branch code and the historical production code are obtained, the main codes in the production branch code, the current service verification branch code and the historical production code are respectively obtained, and then the main codes in the production branch code, the current service verification branch code and the historical production code are compared. The main code of the production branch code refers to a code excluding version configuration information in the production branch code, the main code of the current business verification branch code refers to a code excluding version configuration information in the current business verification branch code, and the main code of the historical production code refers to a code excluding version configuration information in the current business verification branch code.
And when the main code of the production branch code is the same as that of the current business verification branch code and the main code of the production branch code is different from that of the historical production code, determining that the current production version passes the verification. Determining that the current commissioning version check fails when the main code of the production branch code and the main code of the current business verification branch code are different.
More specifically, referring to fig. 3 and 4, a verified version md5 code of the main code of the production branch code, a verified version md5 code of the main code of the current business verification branch code, and a verified version md5 code of the main code of the historical production version are generated, respectively. Calling a version check script to perform multiple md5 checks on the main code of the production branch code, the main code of the current business verification branch code and the main code of the historical production version to determine whether the main code of the production branch code and the main code of the current business verification branch code are the same and whether the main code of the production branch code and the main code of the historical production version are the same.
And when the verification version md5 code of the main code of the production branch code is equal to the verification version md5 code of the main code of the current business verification branch code, determining that the main code of the production branch code is the same as the main code of the current business verification branch code. On the basis that the main code of the production branch code is the same as the main code of the current business verification branch code, if the verification version md5 code of the main code of the production branch code is not equal to the verification version md5 code of the main code of the historical production version, the current production version is determined to be checked to be passed. On the basis that the main code of the production branch code is the same as the main code of the current business verification branch code, if the verification version md5 code of the main code of the production branch code is equal to the verification version md5 code of the main code of the historical production version, determining that the current production version fails to be checked.
In addition, when the verification version md5 code of the main code of the production branch code is not equal to the verification version md5 code of the main code of the current service verification branch code, if the main code of the production branch code is determined to be different from the main code of the current service verification branch code, it can be directly determined that the current production version check fails.
In summary, the data processing method provided in this embodiment receives the check request of the current production version sent by the application layer, obtains the production branch code, the current business verification branch code, and the historical production code of the current production version from the remote code repository according to the check request, and then determines whether the main code of the production branch code of the current production version is the same as the main code of the current business verification branch code. And if the main code of the production branch code of the current production version is the same as the main code of the current business verification branch code, judging whether the main code of the production branch code is the same as the main code in the historical production code. And when the main code of the production branch code is the same as that of the current business verification branch code and the main code of the production branch code is different from that of the historical production code, determining that the current production version passes the verification.
Therefore, the method provided by the embodiment of the application can be used for inspecting the production versions before production, so that a production version inspection assembly line is formed, and the problem of product production errors caused by inconsistent code versions is avoided under the condition that the code versions are inconsistent. In addition, the problems of high cost and code missing caused by manual inspection due to overlarge code amount are solved, and the inspection accuracy of the production version is improved.
Referring to fig. 5, in an optional embodiment, the data processing method provided in the present application may further compare the current production version with the historical production version, that is, compare the version code of the current production version with the version code of the historical production version to obtain the changed file and the newly added file of the current production version, and generate a changed code list according to the changed file and the newly added file. The historical production version can be the last production version or any previous production version. Specifically, after the change file and the new file of the current production version are obtained, a change code list is generated by using a script command such as Linux awk.
Furthermore, the change code list can also be exported in a text form, and the changed file and the added file are marked (for example, marked by the star) in the exported change code list. The identification of the changed file and the newly added file is convenient for manual examination of whether the changed contents (the changed file and the newly added file) completely cover the requirement of the preset service, and is also convenient for manual check whether the current production version has code abnormal change or not more quickly and more accurately.
Referring to fig. 6, an embodiment of the present application further provides a data processing apparatus 10, which is applied to a service layer of an electronic device, where the electronic device further includes an application layer and a remote code repository. The data processing apparatus 10 includes:
and the communication module 11 is configured to receive a verification request of the current production version sent by the application layer.
And the obtaining module 12 is used for obtaining the production branch code of the current production version, the current business verification branch code and the historical production code from the remote code warehouse according to the checking request.
And the checking module 13 is configured to determine that the current production version passes the checking when the main code of the production branch code is the same as the main code of the current business verification branch code and the main code of the production branch code is different from the main code of the historical production code, where the main code is a code excluding version configuration information in the code.
The obtaining module 12 is specifically configured to obtain a persistent integration tool according to the inspection request; production branch codes, current business validation branch codes, and historical production codes are obtained from the remote code repository through a persistent integration tool. The persistent integration tool includes Jenkins.
The obtaining module 12 is specifically configured to invoke an inspection policy according to the inspection request, so as to obtain the persistent integration tool based on the inspection policy.
The obtaining module 12 is specifically configured to send a remote code command to the remote code repository through the persistent integration tool to obtain a production branch code, a current service verification branch code, and a historical commissioning code from the remote code repository, where the remote code command is a Git command, and Git is a code management tool of the remote code repository.
The processing module 13 is further configured to compare the current production version with the historical production version to obtain a modified file and a newly added file of the current production version; and generating a change code list according to the change file and the added file.
The processing module 13 is further configured to determine that the current commissioning version check fails when the main code of the production branch code and the main code of the current business verification branch code are different.
Referring to fig. 7, the present application further provides an electronic device 20 including a processor 21 and a memory 22 communicatively coupled to the processor. The memory 22 stores computer-executable instructions, and the processor 21 executes the computer-executable instructions stored in the memory 22 to implement the data processing method as provided in any one of the above embodiments.
The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the instructions are executed, the instructions cause a processor to execute the instructions, so as to implement the data processing method provided by any one of the above embodiments.
The present application also provides a computer program product comprising a computer program which, when executed by a processor, implements the data processing method as provided in any of the above embodiments.
The computer-readable storage medium may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a magnetic Random Access Memory (FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical Disc, or a Compact Disc Read-Only Memory (CD-ROM). And may be various electronic devices such as mobile phones, computers, tablet devices, personal digital assistants, etc., including one or any combination of the above memories.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one of 8230, and" comprising 8230does not exclude the presence of additional like elements in a process, method, article, or apparatus comprising the element.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, and an optical disk), and includes several instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method described in the embodiments of the present application.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.
Claims (11)
1. A data processing method applied to a service layer of an electronic device, the electronic device further comprising an application layer and a remote code repository, the method comprising:
receiving a checking request of a current production version sent by the application layer;
acquiring a production branch code of a current production version, a current service verification branch code and a historical production code from the remote code warehouse according to the inspection request;
and when the main code of the production branch code is the same as that of the current business verification branch code and the main code of the production branch code is different from that of the historical production code, determining that the current production version passes the verification, wherein the main code is a code excluding version configuration information in the code.
2. The method of claim 1, wherein obtaining a current production branch code, a current business validation branch code, and a historical production code for a current production version from the remote code repository based on the verification request comprises:
acquiring a continuous integration tool according to the inspection request;
obtaining, by a persistent integration tool, a production branch code, a current business validation branch code, and a historical production code from the remote code repository.
3. The method of claim 2, wherein the persistent integration tool comprises Jenkins.
4. The method of claim 2, wherein obtaining persistent integration tools based on the inspection request comprises:
and invoking an inspection strategy according to the inspection request so as to acquire the continuous integration tool based on the inspection strategy.
5. The method of any of claims 2-4, wherein obtaining, by the persistent integration tool, the production branch code, the current business validation branch code, and the historical production code from the remote code repository comprises:
sending, by a persistent integration tool, a remote code command to the remote code repository to obtain a production branch code, a current business verification branch code, and a historical commissioning code from the remote code repository, the remote code command being a Git command, git being a code management tool of the remote code repository.
6. The method of claim 1, further comprising:
comparing the current production version with the historical production version to obtain a change file and a newly added file of the current production version;
and generating a change code list according to the change file and the added file.
7. The method of claim 1, further comprising:
determining that the current commissioning version check fails when the main code of the production branch code and the main code of the current business verification branch code are different.
8. A data processing apparatus, applied to a service layer of an electronic device, the electronic device further comprising an application layer and a remote code repository, the apparatus comprising:
the communication module is used for receiving a checking request of the current production version sent by the application layer;
the acquisition module is used for acquiring the production branch code of the current production version, the current service verification branch code and the historical production code from the remote code warehouse according to the inspection request;
and the checking module is used for determining that the current production version passes the checking when the main code of the production branch code is the same as the main code of the current business verification branch code and the main code of the production branch code is different from the main code of the historical production code, wherein the main code is a code excluding version configuration information in the code.
9. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer execution instructions;
the processor executes computer-executable instructions stored by the memory to implement the data processing method of any one of claims 1 to 7.
10. A computer-readable storage medium having stored therein computer-executable instructions that, when executed, cause a computer to perform the data processing method of any one of claims 1 to 7.
11. A computer program product, characterized in that the computer program realizes the data processing method of any one of claims 1 to 7 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211084640.6A CN115421775A (en) | 2022-09-06 | 2022-09-06 | Data processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211084640.6A CN115421775A (en) | 2022-09-06 | 2022-09-06 | Data processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115421775A true CN115421775A (en) | 2022-12-02 |
Family
ID=84202827
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211084640.6A Pending CN115421775A (en) | 2022-09-06 | 2022-09-06 | Data processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115421775A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109683908A (en) * | 2017-08-28 | 2019-04-26 | 北京恒华伟业科技股份有限公司 | A kind of application dissemination method and device |
| CN110490483A (en) * | 2019-08-26 | 2019-11-22 | 中国建设银行股份有限公司 | Operation method, apparatus, equipment and storage medium |
| CN110968342A (en) * | 2019-11-29 | 2020-04-07 | 中国银行股份有限公司 | Version comparison method, device and system |
| WO2021217868A1 (en) * | 2020-04-30 | 2021-11-04 | 平安科技（深圳）有限公司 | Git-based project version release method and apparatus, device, and medium |
| CN114840429A (en) * | 2022-05-16 | 2022-08-02 | 中国工商银行股份有限公司 | Method, apparatus, device, medium and program product for identifying version conflicts |
-
2022
- 2022-09-06 CN CN202211084640.6A patent/CN115421775A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109683908A (en) * | 2017-08-28 | 2019-04-26 | 北京恒华伟业科技股份有限公司 | A kind of application dissemination method and device |
| CN110490483A (en) * | 2019-08-26 | 2019-11-22 | 中国建设银行股份有限公司 | Operation method, apparatus, equipment and storage medium |
| CN110968342A (en) * | 2019-11-29 | 2020-04-07 | 中国银行股份有限公司 | Version comparison method, device and system |
| WO2021217868A1 (en) * | 2020-04-30 | 2021-11-04 | 平安科技（深圳）有限公司 | Git-based project version release method and apparatus, device, and medium |
| CN114840429A (en) * | 2022-05-16 | 2022-08-02 | 中国工商银行股份有限公司 | Method, apparatus, device, medium and program product for identifying version conflicts |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101161493B1 (en) | Method of Examining Malicious Codes and Dangerous Files in Android Terminal Platform | |
| CN108196878B (en) | Method and device for generating application program installation package, electronic equipment and storage medium | |
| CN109344657B (en) | Privacy risk assessment method and device | |
| CN111353143A (en) | Sensitive authority detection method and device and storage medium | |
| CN115543429A (en) | Project environment building method, electronic equipment and computer readable storage medium | |
| CN113434254B (en) | Client deployment method, client deployment apparatus, computer device, and storage medium | |
| CN115437915A (en) | Vehicle-based version testing method and device and electronic equipment | |
| CN114528201A (en) | Abnormal code positioning method, device, equipment and medium | |
| CN115421775A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN112306041A (en) | Vehicle configuration information writing method and device and electronic equipment | |
| US11762650B1 (en) | Method and apparatus for secure offline software update | |
| US10489137B1 (en) | Software verification system and methods | |
| CN110750270A (en) | Method and device for deploying packaged software | |
| CN116028077A (en) | Application installation method based on mobile terminal, ecological service system and electronic equipment | |
| CN110795100B (en) | Branch merging method and device | |
| CN101295314A (en) | File management system, file management method, support device thereof, and program thereof | |
| CN114239054A (en) | iOS application construction method, device, computer equipment and storage medium | |
| CN114168108A (en) | Code merging method and device, electronic equipment and computer readable storage medium | |
| CN114253906A (en) | Method and device for managing configuration file, configuration distribution system and storage medium | |
| CN113342660A (en) | File testing method, device, system, electronic equipment and readable storage medium | |
| CN113126998A (en) | Incremental source code acquisition method and device, electronic equipment and storage medium | |
| CN112764774A (en) | Product information management method, management system, electronic device and storage medium | |
| CN110825406A (en) | Software upgrading method and related equipment | |
| CN112165512B (en) | File release method and device, terminal equipment and storage medium | |
| CN113672278B (en) | Service node version control method and device under micro-service architecture |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |