CN109828781B - Source code version positioning method, device, medium and equipment for problem troubleshooting - Google Patents
Source code version positioning method, device, medium and equipment for problem troubleshooting Download PDFInfo
- Publication number
- CN109828781B CN109828781B CN201811635965.2A CN201811635965A CN109828781B CN 109828781 B CN109828781 B CN 109828781B CN 201811635965 A CN201811635965 A CN 201811635965A CN 109828781 B CN109828781 B CN 109828781B
- Authority
- CN
- China
- Prior art keywords
- information
- code
- modification
- feedback
- object array
- 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.)
- Active
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The present disclosure provides a method, an apparatus, a medium, and a device for locating a source code version for problem troubleshooting, including: carrying out code warehouse copying on project information to be constructed; acquiring modification mark information in the code warehouse, and generating an object array according to the modification mark information; and performing problem troubleshooting according to the feedback problem information and the object array. By the method, when receiving the feedback problem, an engineer can directly obtain the Commit information of the source code without manually inquiring the Tag information and the Commit information of the version. By automatically writing the Commit information of each source code library into the generated platform installation package in the packaging process, an engineer can quickly restore the problem field according to the Commit information from the feedback to efficiently check the problem field when receiving the feedback. And the Tag information does not need to be inquired when the Tag creation of the version and the problem feedback are manually carried out each time the version is released.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a medium, and an electronic device for locating a source code version for problem troubleshooting.
Background
With the development of mobile internet technology, various apps are more and more popular in application, but each App needs to be updated through continuous version to complete corresponding service items, generally, after the apps are online, users can feed back various problems, enterprises can repair the problems fed back by the users, troubleshoot related problems, and update the apps.
The basic flow for checking the relevant problems is that an engineer queries the version Tag corresponding to the source code library according to the App version number of the feedback problem, finds out the Commit information of the source code used in packaging according to the version Tag information, pulls down the source code corresponding to the found Commit information, and analyzes the code level. At present, the processes need manual processing by engineers, the efficiency is low, and the requirement for updating the App version cannot be met.
Disclosure of Invention
The present disclosure is directed to a method, an apparatus, a medium, and an electronic device for locating a source code version for problem troubleshooting, which can solve at least one of the above-mentioned technical problems. The specific scheme is as follows:
according to a specific embodiment of the present disclosure, in a first aspect, the present disclosure provides a method for locating a source code version for problem troubleshooting, including: carrying out code warehouse copying on project information to be constructed; acquiring modification mark information in the code warehouse, and generating an object array according to the modification mark information; and performing problem troubleshooting according to the feedback problem information and the object array.
Optionally, the performing code warehouse replication on the project information to be constructed includes: copying a code warehouse to the main item information to be constructed; and if the dependent item information exists, carrying out code warehouse replication on the dependent item information.
Optionally, the obtaining modification flag information in the code repository, and generating an object array according to the modification flag information includes: acquiring main item modification mark information of all items in the code warehouse; acquiring dependent item modification marking information of all items in the code warehouse; and generating an object array according to the main item modification mark information and the dependent item modification mark information.
Optionally, the obtaining modification flag information in the code repository, and generating an object array according to the modification flag information, then includes: packaging the object array into a software package.
Optionally, performing problem troubleshooting according to the feedback problem information and the object array, including: reporting the feedback problem information and the object array as the same parameter; directly positioning the modification mark information according to the report; and performing problem troubleshooting according to the modification mark information.
According to a second aspect, the present disclosure provides a source code version locating device for problem troubleshooting, including: the copying unit is used for copying the code warehouse of the project information to be constructed; the generating unit is used for acquiring modification mark information in the code warehouse and generating an object array according to the modification mark information; and the troubleshooting unit is used for performing problem troubleshooting according to the feedback problem information and the object array.
Optionally, the copying unit is further configured to: copying a code warehouse to the main item information to be constructed; and if the dependent item information exists, carrying out code warehouse replication on the dependent item information.
Optionally, the generating unit is further configured to: acquiring main item modification mark information of all items in the code warehouse; acquiring dependent item modification marking information of all items in the code warehouse; and generating an object array according to the main item modification mark information and the dependent item modification mark information.
According to a third aspect, the present disclosure provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of any one of the above.
According to a fourth aspect thereof, the present disclosure provides an electronic device, comprising: one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out a method as claimed in any preceding claim.
Compared with the prior art, the scheme of the embodiment of the disclosure at least has the following beneficial effects: according to the method, the device, the medium and the electronic equipment for locating the source code version for problem troubleshooting, when an engineer receives a feedback problem, the engineer can directly obtain the Commit information of the source code without manually inquiring the Tag information and the Commit information of the version. By automatically writing the Commit information of each source code library into the generated platform installation package in the packaging process, an engineer can quickly restore the problem field according to the Commit information from the feedback to efficiently check the problem field when receiving the feedback. And the Tag information does not need to be inquired when the Tag creation of the version and the problem feedback are manually carried out each time the version is released.
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. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty. In the drawings:
Fig. 1 is a schematic diagram illustrating steps of a source code version positioning method for problem troubleshooting according to an embodiment of the disclosure;
FIG. 2 shows a flowchart of a source code version location method for problem troubleshooting in accordance with an embodiment of the disclosure;
fig. 3 shows a reporting flow chart of a source code version positioning method for problem troubleshooting according to an embodiment of the disclosure;
fig. 4 shows a schematic structural diagram of a source code version positioning apparatus for problem troubleshooting according to an embodiment of the disclosure;
fig. 5 shows an electronic device connection structure schematic according to an embodiment of the present disclosure.
Detailed Description
To make the objects, technical solutions and advantages of the present disclosure clearer, the present disclosure will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present disclosure, rather than all embodiments. All other embodiments, which can be derived by one of ordinary skill in the art from the embodiments disclosed herein without making any creative effort, shall fall within the scope of protection of the present disclosure.
The terminology used in the embodiments of the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in the disclosed embodiments and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise, and "a plurality" typically includes at least two.
It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.
It should be understood that although the terms first, second, third, etc. may be used to describe … … in embodiments of the present disclosure, these … … should not be limited to these terms. These terms are used only to distinguish … …. For example, the first … … can also be referred to as the second … … and, similarly, the second … … can also be referred to as the first … … without departing from the scope of embodiments of the present disclosure.
The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
It is also noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that an 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 article or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in the article or device in which the element is included.
Description of key terms
The source code version management tool is a tool for managing source codes, and each time the codes are added or deleted, the records are recorded, and the representative tools are Git and SVN.
Source code repository-a repository for holding source code, similar to a database of source code.
Commit is used to record one Commit of a source code modification (add/delete operation).
Tag-marking operation is carried out on a Commit. It is understood that a certain Commit (Commit) of the source code library is tagged and can be used to obtain the particular Commit of the source code library directly from the tag when packaging.
And packaging, namely acquiring the source code of the specific Commit of the source code library, and generating an installable file of the specific platform (Android \ iOS) based on the source code.
JsonAlrray, a data structure, similar to an array.
Alternative embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.
Example 1
As shown in fig. 1, according to a specific embodiment of the present disclosure, in a first aspect, the present disclosure provides a source code version locating method for problem troubleshooting, including the following steps:
s102: carrying out code warehouse copying on project information to be constructed;
optionally, as shown in fig. 2, the performing code warehouse replication on the project information to be constructed includes: copying a code warehouse to the main item information to be constructed; and judging whether the dependent item information exists, and if so, copying the code warehouse of the dependent item information. Wherein the code repository includes a collection of all codes that can execute the corresponding project. Usually, an App is composed of a plurality of projects, each project has a code warehouse, main project information refers to a main department capable of completing a corresponding functional unit, and dependent project information includes some project information that the main project information needs to call when executing a corresponding task.
S104: acquiring modification mark information in the code warehouse, and generating an object array according to the modification mark information;
Optionally, the obtaining modification flag information in the code repository, and generating an object array according to the modification flag information includes: acquiring main item modification mark information of all items in the code warehouse; acquiring dependent item modification marking information of all items in the code warehouse; and generating an object array according to the main item modification mark information and the dependent item modification mark information.
The step S104 is in the packing stage, as shown in fig. 2, a specific example is as follows:
step S1041: when the item is initially packaged, the item source code and the dependent item source code (if any dependency exists) are acquired, and Commit information of all the source codes is acquired through a Git command.
Step S1042: after obtaining the Commit information, a jsonnarrray object is generated, and the Commit information of each item (main item and dependent items) is saved, such as:
{ "main item": c23d45' }, { "dependent item 1": e12f67"}, {" dependent item 2": u12y78" }.
Step S1043: compiling and packaging items are carried out, and the JSonAlrray object generated in the above mode is written into a packaged product. For example, in an Android packaged apk file, the contents of the JSonAlray object are written into the meta file of the apk file.
Step S1044: and (6) packaging is completed.
And S106, performing problem troubleshooting according to the feedback problem information and the object array.
Optionally, performing problem troubleshooting according to the feedback problem information and the object array, including: reporting the feedback problem information and the object array as the same parameter; directly positioning the modification mark information according to the report; and performing problem troubleshooting according to the modification mark information. The commit information is automatically carried during the problem feedback, the problem code site can be restored according to the commit information, and then specific reasons are found out by developers according to the commit modification information and the like.
The step S106 is in the reporting stage, as shown in fig. 3, a specific example is as follows:
step S1061: in order to support reporting information carrying Commit information, the Commit information needs to be added to the code logic of problem feedback/problem reporting as a reporting parameter.
Step S1062: when the user performs the question feedback, the user clicks the question feedback button, and the feedback content containing the Commit information (JSonAlrray in the packaging stage) is sent to the engineer.
Step S1063: and the engineer positions the problem of which project source code is according to the feedback content, directly acquires the warehouse code of the corresponding version according to the Commit information, and performs problem troubleshooting.
In this way, in the packaging process, the information of each source code library Commi is automatically written into the generated platform installation package. In the problem feedback stage, reporting the Commit information of each source code library as a parameter together with the feedback problem. The accuracy and the high efficiency of troubleshooting are provided.
According to the method for locating the source code version for problem troubleshooting, when an engineer receives a feedback problem, the engineer can directly obtain the Commit information of the source code without manually inquiring the Tag information and the Commit information of the version. By automatically writing the Commit information of each source code library into the generated platform installation package in the packaging process, an engineer can quickly restore the problem field according to the Commit information from the feedback to efficiently check the problem field when receiving the feedback. And the Tag information does not need to be inquired when the Tag creation of the version and the problem feedback are manually carried out each time the version is released.
Example 2
As shown in fig. 4, according to a specific embodiment of the present disclosure, in a second aspect, the present disclosure provides a source code version locating device for problem troubleshooting, including: a copying unit 402, a generating unit 404 and a checking unit 406. The above units may be implemented by software or hardware circuit, and are not limited to this. The details are as follows
A copying unit 402, configured to perform code warehouse copying on project information to be constructed;
optionally, as shown in fig. 2, the performing code warehouse replication on the project information to be constructed includes: copying a code warehouse to the main item information to be constructed; and judging whether the dependent item information exists, and if so, copying the code warehouse of the dependent item information.
The generation unit 404: the system comprises a code warehouse, a storage unit and a database, wherein the code warehouse is used for storing modification mark information of a code, and generating an object array according to the modification mark information;
optionally, the obtaining modification flag information in the code repository, and generating an object array according to the modification flag information includes: acquiring main item modification mark information of all items in the code warehouse; acquiring dependent item modification marking information of all items in the code warehouse; and generating an object array according to the main item modification mark information and the dependent item modification mark information.
An example of the specific working steps of the generating unit 404 is as follows, as shown in fig. 2,
when the item is initially packaged, the item source code and the dependent item source code (if any dependency exists) are acquired, and Commit information of all the source codes is acquired through a Git command.
After obtaining the Commit information, a jsonnacray object is generated, and Commit information of each item (main item and dependent items) is saved, for example:
{ "main item": c23d45' }, { "dependent item 1": e12f67"}, {" dependent item 2": u12y78" }.
Compiling and packaging items are carried out, and the JSonAlrray object generated in the above mode is written into a packaged product. For example, in an Android packaged apk file, the contents of the JSonAlray object are written into the meta file of the apk file.
And (6) packaging is completed.
And the troubleshooting unit 406 is used for performing problem troubleshooting according to the feedback problem information and the object array.
Optionally, performing problem troubleshooting according to the feedback problem information and the object array, including: reporting the feedback problem information and the object array as the same parameter; directly positioning the modification mark information according to the report; and performing problem troubleshooting according to the modification mark information.
The above-mentioned troubleshooting unit 406 is in the reporting stage, as shown in fig. 3, a specific working example is as follows:
in order to support reporting information carrying Commit information, the Commit information needs to be added to the code logic of problem feedback/problem reporting as a reporting parameter.
When the user performs the question feedback, the user clicks the question feedback button, and the feedback content containing the Commit information (JSonAlrray in the packaging stage) is sent to the engineer.
And the engineer positions the problem of which project source code is according to the feedback content, directly acquires the warehouse code of the corresponding version according to the Commit information, and performs problem troubleshooting.
In this way, in the packaging process, the Commit information of each source code library is automatically written into the generated platform installation package. In the problem feedback stage, reporting the Commit information of each source code library as a parameter together with the feedback problem. The accuracy and the high efficiency of troubleshooting are provided.
According to the source code version positioning device for problem troubleshooting, when an engineer receives a feedback problem, the engineer can directly obtain the Commit information of the source code without manually inquiring the Tag information and the Commit information of the version. By automatically writing the Commit information of each source code library into the generated platform installation package in the packaging process, an engineer can quickly restore the problem field according to the Commit information from the feedback to efficiently check the problem field when receiving the feedback. And the Tag information does not need to be inquired when the Tag creation of the version and the problem feedback are manually carried out each time the version is released.
Example 3
As shown in fig. 5, the present embodiment provides an electronic device, where the electronic device is used in a source code version positioning method for problem troubleshooting, and the electronic device includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the one processor to cause the at least one processor to perform the method of: carrying out code warehouse copying on project information to be constructed; acquiring modification mark information in the code warehouse, and generating an object array according to the modification mark information; and performing problem troubleshooting according to the feedback problem information and the object array.
Optionally, the performing code warehouse replication on the project information to be constructed includes: copying a code warehouse to the main item information to be constructed; and if the dependent item information exists, carrying out code warehouse replication on the dependent item information.
Optionally, the obtaining modification flag information in the code repository, and generating an object array according to the modification flag information includes: acquiring main item modification mark information of all items in the code warehouse; acquiring dependent item modification marking information of all items in the code warehouse; and generating an object array according to the main item modification mark information and the dependent item modification mark information.
Optionally, the obtaining modification flag information in the code repository, and generating an object array according to the modification flag information, and then includes: and packaging the object array into a software package.
Optionally, performing problem troubleshooting according to the feedback problem information and the object array, including: reporting the feedback problem information and the object array as the same parameter; directly positioning the modification mark information according to the report; and performing problem troubleshooting according to the modification mark information.
In this way, in the packaging process, the Commit information of each source code library is automatically written into the generated platform installation package. In the problem feedback stage, reporting the Commit information of each source code library as a parameter together with the feedback problem. The accuracy and the high efficiency of troubleshooting are provided.
According to the method for locating the source code version for problem troubleshooting, when an engineer receives a feedback problem, the engineer can directly obtain the Commit information of the source code without manually inquiring the Tag information and the Commit information of the version. By automatically writing the Commit information of each source code library into the generated platform installation package in the packaging process, an engineer can quickly restore the problem field according to the Commit information from the feedback to efficiently check the problem field when receiving the feedback. And the Tag information does not need to be inquired when the Tag creation of the version and the problem feedback are manually carried out each time the version is released.
Example 4
The embodiment of the disclosure provides a non-volatile computer storage medium, where a computer executable instruction is stored, and the computer executable instruction may execute the source code version locating method for problem troubleshooting in any of the above method embodiments.
Example 5
Referring now to FIG. 5, a block diagram of an electronic device 500 suitable for use in implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 5 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. 5, electronic device 500 may include a processing means (e.g., central processing unit, graphics processor, etc.) 501 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage means 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the electronic apparatus 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
Generally, the following devices may be connected to the I/O interface 505: input devices 506 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 507 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage devices 508 including, for example, magnetic tape, hard disk, etc.; and a communication device 509. The communication means 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. While fig. 5 illustrates an electronic device 500 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 509, or installed from the storage means 508, or installed from the ROM 502. The computer program performs the above-described functions defined in the methods of the embodiments of the present disclosure when executed by the processing device 501.
It should be noted that the computer readable medium of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, 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), an optical fiber, 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. In contrast, in the present disclosure, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring at least two internet protocol addresses; sending a node evaluation request comprising the at least two internet protocol addresses to node evaluation equipment, wherein the node evaluation equipment selects the internet protocol addresses from the at least two internet protocol addresses and returns the internet protocol addresses; receiving an internet protocol address returned by the node evaluation equipment; wherein the obtained internet protocol address indicates an edge node in the content distribution network.
Alternatively, the computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a node evaluation request comprising at least two internet protocol addresses; selecting an internet protocol address from the at least two internet protocol addresses; returning the selected internet protocol address; wherein the received internet protocol address indicates an edge node in the content distribution network.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, 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 and/or flowchart illustration, and combinations of blocks in the block diagrams and/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.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".
Claims (10)
1. A method for locating a source code version for problem troubleshooting, comprising:
performing code warehouse replication on project information to be constructed, comprising: code warehouse replication is carried out on main project information to be constructed, and if dependent project information exists, code warehouse replication is carried out on the dependent project information;
acquiring modification mark information in the code warehouse, and generating an object array according to the modification mark information;
and performing problem troubleshooting according to the feedback problem information and the object array.
2. The method of claim 1, wherein the dependent project information comprises project information that the main project information needs to call when executing the corresponding task.
3. The method of claim 2, wherein obtaining modification tag information in the code repository and generating an object array from the modification tag information comprises: acquiring main item modification mark information of all items in the code warehouse;
Acquiring dependent item modification marking information of all items in the code warehouse;
and generating an object array according to the main item modification mark information and the dependent item modification mark information.
4. The method of claim 1, wherein obtaining modification flag information in the code repository and generating an object array according to the modification flag information, then comprises:
packaging the object array into a software package.
5. The method of claim 1, wherein performing problem troubleshooting based on feedback problem information and the array of objects comprises:
reporting the feedback problem information and the object array as the same parameter;
directly positioning the modification mark information according to the report;
and performing problem troubleshooting according to the modification mark information.
6. A source code version locator for problem troubleshooting, comprising:
the copying unit is used for copying the code warehouse of the project information to be constructed, and comprises: the system comprises a code warehouse, a database and a database, wherein the code warehouse is used for copying the main project information to be constructed, and if the dependent project information exists, the code warehouse is used for copying the dependent project information;
The generating unit is used for acquiring modification mark information in the code warehouse and generating an object array according to the modification mark information;
and the troubleshooting unit is used for performing problem troubleshooting according to the feedback problem information and the object array.
7. The apparatus of claim 6, wherein the dependent project information comprises project information that the main project information needs to call when executing the corresponding task.
8. The apparatus of claim 7, wherein the generating unit is further configured to: acquiring main item modification mark information of all items in the code warehouse;
acquiring dependent item modification marking information of all items in the code warehouse;
and generating an object array according to the main item modification mark information and the dependent item modification mark information.
9. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out the method according to any one of claims 1 to 5.
10. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811635965.2A CN109828781B (en) | 2018-12-29 | 2018-12-29 | Source code version positioning method, device, medium and equipment for problem troubleshooting |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811635965.2A CN109828781B (en) | 2018-12-29 | 2018-12-29 | Source code version positioning method, device, medium and equipment for problem troubleshooting |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109828781A CN109828781A (en) | 2019-05-31 |
| CN109828781B true CN109828781B (en) | 2022-06-07 |
Family
ID=66860070
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811635965.2A Active CN109828781B (en) | 2018-12-29 | 2018-12-29 | Source code version positioning method, device, medium and equipment for problem troubleshooting |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109828781B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254066B (en) * | 2021-05-31 | 2024-05-10 | 浪潮通用软件有限公司 | Construction packaging method and system for generating patch file package |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103092761A (en) * | 2013-02-05 | 2013-05-08 | 烽火通信科技股份有限公司 | Method and device of recognizing and checking modifying code blocks based on difference information file |
| CN106776231A (en) * | 2017-01-09 | 2017-05-31 | 武汉斗鱼网络科技有限公司 | Android crash logs optimization method and system based on Git |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060168569A1 (en) * | 2005-01-26 | 2006-07-27 | Microsoft Corporation | Beta parser |
-
2018
- 2018-12-29 CN CN201811635965.2A patent/CN109828781B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103092761A (en) * | 2013-02-05 | 2013-05-08 | 烽火通信科技股份有限公司 | Method and device of recognizing and checking modifying code blocks based on difference information file |
| CN106776231A (en) * | 2017-01-09 | 2017-05-31 | 武汉斗鱼网络科技有限公司 | Android crash logs optimization method and system based on Git |
Non-Patent Citations (1)
| Title |
|---|
| 使用git bisect快速定位引入错误的版本;W25632;《CSDN博客 https://blog.csdn.net/w25632/article/details/84013724》;20110907;第1页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109828781A (en) | 2019-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9268672B1 (en) | Automated test case generation for applications | |
| CN110502222B (en) | AAR method, apparatus, medium, and device for outbound dependency on internal base repository | |
| US20160147633A1 (en) | Generation of software test code | |
| CN110889263A (en) | Document backlog generation method, device, equipment and storage medium | |
| CN109491646B (en) | Message entry method and device, electronic equipment and readable medium | |
| CN110750545A (en) | Dynamic library hot update method, device, medium and equipment | |
| CN110764941A (en) | Method, device, medium and equipment for acquiring call stack frame instruction offset | |
| CN110990346A (en) | File data processing method, device, equipment and storage medium based on block chain | |
| CN111258998A (en) | Data verification method, device, medium and electronic equipment | |
| CN112732300A (en) | Data packet updating method and device, electronic equipment and readable storage medium | |
| CN109902726B (en) | Resume information processing method and device | |
| CN109828781B (en) | Source code version positioning method, device, medium and equipment for problem troubleshooting | |
| CN110716804A (en) | Method and device for automatically deleting useless resources, storage medium and electronic equipment | |
| CN111506904B (en) | Method and device for online bug repair | |
| CN111666098A (en) | Method and system for creating ToB project based on service component | |
| CN111625232B (en) | Method and device for generating application program installation package, readable medium and electronic equipment | |
| CN111241368B (en) | Data processing method, device, medium and equipment | |
| CN113656050B (en) | Method and apparatus for generating version number | |
| CN114153462A (en) | Client source code processing method and device, storage medium and electronic equipment | |
| CN113504904A (en) | User-defined function implementation method and device, computer equipment and storage medium | |
| CN112905211A (en) | Firmware upgrade file updating method, system, equipment and storage medium | |
| KR20220035610A (en) | System and method for providing integrated machine learning platform based on pipeline | |
| CN111897827B (en) | Data updating method and system for data warehouse and electronic equipment | |
| CN110647331A (en) | Development tool acquisition method and device, storage medium and electronic equipment | |
| CN115658374B (en) | Platform compatibility problem repairing method and device, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |