CN108897677B - Log construction method and system - Google Patents
Log construction method and system Download PDFInfo
- Publication number
- CN108897677B CN108897677B CN201810602092.9A CN201810602092A CN108897677B CN 108897677 B CN108897677 B CN 108897677B CN 201810602092 A CN201810602092 A CN 201810602092A CN 108897677 B CN108897677 B CN 108897677B
- Authority
- CN
- China
- Prior art keywords
- code
- log
- variable
- platform
- plug
- 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
Classifications
-
- 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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a log construction method and a system, wherein variables are defined in a code compiling platform, log contents in the code compiling platform are read, the log contents are assigned to the variables, and the variables are returned to a code warehouse through a plug-in the code compiling platform, so that logs corresponding to the log contents can be constructed in the code warehouse.
Description
Technical Field
The invention relates to the technical field of computer software, in particular to a log construction method and a log construction system.
Background
The code warehouse has a plurality of branches, one branch is often required to be merged to another branch, the branch merging has certain risks, in order to know the risks in advance, the corresponding codes in the code warehouse need to be merged and tested through the code compiling platform, and then the test results of the code compiling platform are returned to the code warehouse for displaying.
However, the current return result is fixed content or an environment variable of the code compiling platform itself, a log constructed by the code compiling platform according to the test result cannot be seen in the code warehouse, and the code compiling platform needs to be additionally logged to check log error information, so that the operation complexity is high.
Disclosure of Invention
In view of the above, the present invention provides a log construction method and system.
Specifically, the invention is realized by the following technical scheme:
according to a first aspect of the embodiments of the present invention, there is provided a log construction method, including: defining variables in a code compiling platform; reading the log content in the code compiling platform, and assigning the log content to the variable; and returning the variable to a code warehouse through a plug-in a code compiling platform so as to construct a log corresponding to the log content in the code warehouse.
Optionally, before assigning the log content to the variable, the method further comprises: reading a line break in the log; and replacing the line break with a line break recognizable by the code warehouse.
Optionally, the step of reading the log content of the code compiling platform includes: acquiring a task identifier of a compiling task executed by the code compiling platform; calling an API of the code compiling platform according to the task identifier; and acquiring the log content of the code compiling platform through the API.
Optionally, the step of assigning the log content to the variable comprises: useful information is screened out from the log content; and assigning the useful information to the variable.
Optionally, before returning the variable to the code repository through a plug-in the code compilation platform, the method further comprises: converting the variable into a format recognizable by the plug-in.
Optionally, the method further comprises: and saving the log content in a code compiling platform.
Optionally, the log content is a log constructed by the code compiling platform executing the compiling task last time.
Optionally, the plug-in is an envInject API plug-in.
Optionally, the code compiling platform is Jenkins, and the code repository is Gitlab.
According to a second aspect of an embodiment of the present invention, there is provided a log construction system including: the variable definition module is used for defining variables in the code compiling platform; the assignment module is used for reading the log content in the code compiling platform and assigning the log content to the variable; and the log construction module is used for returning the variable to a code warehouse through a plug-in a code compiling platform so as to construct a log corresponding to the log content in the code warehouse.
Optionally, the system further comprises: the reading module is used for reading the line feed character in the log; and the replacing module is used for replacing the line break with a line break which can be identified by the code warehouse.
Optionally, the assignment module includes: the obtaining unit is used for obtaining a task identifier of a compiling task executed by the code compiling platform; the calling unit is used for calling the API of the code compiling platform according to the task identifier; and the acquisition unit is used for acquiring the log content of the code compiling platform through the API.
Optionally, the assignment module further includes: the screening unit is used for screening useful information from the log contents; and the assignment unit is used for assigning the useful information to the variable.
Optionally, the system further comprises: and the format conversion module is used for converting the variable into a format which can be recognized by the plug-in.
Optionally, the system further comprises: and the storage module is used for storing the log content in the code compiling platform.
Optionally, the log content is a log constructed by the code compiling platform executing the compiling task last time.
Optionally, the plug-in is an envInject API plug-in.
Optionally, the code compiling platform is Jenkins, and the code repository is Gitlab.
According to a third aspect of embodiments of the present invention, there is provided a computer readable storage medium, having stored thereon a computer program which, when executed by a processor, performs the steps of the method of any of the embodiments.
According to a fourth aspect of embodiments of the present invention, there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of any of the embodiments when executing the program.
By applying the scheme of the embodiment of the invention, the variable is defined in the code compiling platform, the log content in the code compiling platform is read, the log content is assigned to the variable, and the variable is returned to the code warehouse through the plug-in the code compiling platform, so that the log corresponding to the log content can be constructed in the code warehouse.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Drawings
Fig. 1 is a schematic diagram illustrating an interaction process between a code compiling platform and a code warehouse according to an exemplary embodiment of the present invention.
Fig. 2 is a flowchart illustrating a log construction method according to an exemplary embodiment of the present invention.
Fig. 3 is a logical structure diagram illustrating a log construction method according to an exemplary embodiment of the present invention.
Fig. 4 is a general flow diagram illustrating a branch merge process in accordance with an exemplary embodiment of the present invention.
Fig. 5 is a block diagram illustrating a structure of a log construction system according to an exemplary embodiment of the present invention.
Fig. 6 is a schematic structural diagram of a computer device according to an exemplary embodiment of the present invention.
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 embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification 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. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present invention. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Fig. 1 is a schematic diagram illustrating an interaction process between a code compiling platform and a code warehouse according to an exemplary embodiment of the present invention. In this embodiment, various types of codes may be stored in the code repository, and the code compiling platform is used to provide an environment framework required for code compiling. The code warehouse and the code compiling platform can perform data interaction, and the interaction process can comprise the following steps:
in step 101, the code repository sends the software code to be compiled to the code compilation platform.
In step 102, the code compiling platform compiles the code to obtain a log, and the log can record a compiling result.
In step 103, the code compiling platform may send some environment variables or fixed contents to the code repository, and the user may directly view the logs corresponding to these environment variables or fixed contents in the code repository.
In step 104, if the user needs to view the log constructed by the code compiling platform, the user needs to log in the code compiling platform for viewing.
Through the process, the logs constructed by the code compiling platform according to the test results cannot be seen in the code warehouse, and the code compiling platform needs to be additionally logged to check the log error information, so that the operation complexity is high.
Based on this, an embodiment of the present invention provides a log construction method, as shown in fig. 2, the method may include the following steps:
and step 203, returning the variable to a code warehouse through a plug-in a code compiling platform so as to construct a log corresponding to the log content in the code warehouse.
In step 201, variables may be defined by a variable definition plug-in the code compilation platform. The variable definition plug-in can provide custom environment variable functionality. The variable and the variable value set according to the need of the plug-in may be in a key value format.
In step 202, the log content in the code compiling platform may be content in a log constructed by the code compiling platform after compiling the code in the code warehouse. For example, a code compilation platform may fail to compile the code and may generate an error log. The log content may be a string of characters.
In step 203, the plug-in the code compiling platform may be a plug-in with variable return function, which may be pre-installed into the code compiling platform. The plug-in with the variable return function in this step and the plug-in with the variable definition function may be the same plug-in or two different plug-ins. Since the log content has been assigned to the variable, in this step, the variable is returned to the code repository, so that the code repository can acquire the variable value, that is, the log content. The code repository may construct a log according to the obtained log content.
According to the embodiment of the invention, the log is directly constructed in the software warehouse without additionally logging in a code compiling platform to check the log, so that the operation complexity is low, and the user can conveniently check the log content. Moreover, according to the scheme of the embodiment of the invention, the corresponding logs can be dynamically constructed in the code warehouse according to the compiling result, and the obtained log contents are different when the compiling result is different every time, so that the log constructing result in the code warehouse is different.
In one embodiment, before assigning the log content to the variable, the method further comprises: reading a line break in the log; and replacing the line break with a line break recognizable by the code warehouse. Because the code type recognizable by the code warehouse and the code type recognizable by the code compiling platform may be different, if the code type recognizable by the code warehouse and the code type recognizable by the code compiling platform do not have to be converted, the log displayed in the code warehouse cannot recognize the codes of different lines in the original log, so that the contents in the log constructed by the code warehouse are connected into pieces (for example, the contents may be long characters in a line) and are inconvenient to view. Through the conversion, the line break can be replaced by the line break which can be recognized by the code warehouse, so that formatted contents which are the same as those of the original log are displayed in the log of the code warehouse (for example, 5 lines of log contents exist in the original log, and correspondingly 5 lines of contents exist in the newly-constructed log), and the user can check the contents more conveniently.
In one embodiment, the step of reading the log content of the code compiling platform comprises: acquiring a task identifier of a compiling task executed by the code compiling platform; calling an API (Application Programming Interface) of the code compiling platform according to the task identifier; and acquiring the log content of the code compiling platform through the API. The compiling task executed by the code compiling platform can be called a "Job", and the task identifier of the compiling task can be a task name. When the codes in the code warehouse need to be compiled, the code compiling platform can create a compiling task, and each compiling task can generate a log respectively. Therefore, the corresponding log can be quickly found through the task identifier of the compiling task.
In one embodiment, the step of assigning the log content to the variable comprises: useful information is screened out from the log content; and assigning the useful information to the variable. Because one log may include many contents, but not all the contents include useful information required by the user, the contents of the log can be filtered to filter out useless information, thereby saving the time for the user to view the log. During screening, a section of code can be imported in the log compiling platform, and the code can be implemented by adopting the existing code. The code may include a number or range of numbers of lines in the log of the desired log content.
In one embodiment, before returning the variable to the code repository through a plug-in the code compilation platform, the method further comprises: converting the variable into a format recognizable by the plug-in.
In one embodiment, the log content may also be saved in a code compilation platform. In particular, log contents assigned to variables may be stored in a new file and stored in the code compilation platform for archiving.
In one embodiment, the log content is a log constructed by the code compiling platform executing a compiling task last time. The software warehouse constructs the logs generated by the latest compiling of the code compiling platform each time, corresponding logs can be dynamically constructed in the code warehouse according to compiling results, the obtained log contents are different due to different compiling results each time, and therefore the log constructing results in the code warehouse are different.
In one embodiment, the code compiling platform is Jenkins and the code repository is Gitlab. In one embodiment, the plug-in is an EnvInject API plug-in.
The following describes the scheme of the present invention by taking a specific application example as an example. As shown in fig. 3, the log construction method according to the embodiment of the present invention may include the following steps:
Step 302: obtaining log content, wherein the log content is a character string comprising a line break.
Step 303: the line feed character in the string is replaced with < br/>.
Step 304: and assigning the replaced character string to a version variable, wherein the format of the variable is 'ssss < br/> ssss', and the 'ssss' is log content.
Step 305: the contents of step 304 are stored in a new file.
Step 306: and reading the content of the new file after Jenkins construction is completed.
Step 307: the plug-in references $ { version } to get the log content back to Gitlab, where $ { version } is a variable that the plug-in corresponding to the version variable can recognize.
The general flow of the branch merging process in the above manner in Gitlab is shown in fig. 4, and may include the following steps:
step 401: the user submits merge request in the Gitlab to execute the branch merge test request.
Step 402: and triggering Job corresponding to Jenkins according to the merge request.
Step 403: jenkins builds, i.e., compiles code in Jenkins to generate logs.
Step 404: optionally, fixed content or Jenkins environment variables are imported into the Gitlab.
Step 405: and constructing the logs generated by Jenkins into Gitlab.
Step 405 may be implemented by steps 301 to 307. The fixed content or environment variable described in step 404 may also be imported into Gitlab via the log in step 405.
After the log is constructed in the code warehouse by the embodiment of the invention, the display interface of the Gitlab can comprise the fixed content returned from Jenkins and the log content returned by Jenkins.
As shown in fig. 5, the present invention further provides a log construction system, which includes:
a variable definition module 501, configured to define a variable in a code compiling platform;
an assigning module 502, configured to read log content in the code compiling platform, and assign the log content to the variable;
the log building module 503 is configured to return the variable to a code repository through a plug-in the code compiling platform, so as to build a log corresponding to the log content in the code repository.
The implementation process of the functions and actions of each unit in the system is specifically described in the implementation process of the corresponding step in the method, and is not described herein again.
In one embodiment, the invention also provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the method of any of the above embodiments.
In one embodiment, the present invention also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any one of the above embodiments when executing the program. As shown in FIG. 6, FIG. 6 is a block diagram illustrating a computer device 600 for log construction according to an exemplary embodiment.
Referring to fig. 6, the computer device 600 includes a processing component 601 that further includes one or more processors and memory resources, represented by memory 602, for storing instructions, such as application programs, that are executable by the processing component 601. The application programs stored in memory 602 may include one or more modules that each correspond to a set of instructions. Further, the processing component 601 is configured to execute instructions to perform the above described method.
The computer device 600 may also include a power component 603 configured to perform power management of the computer device 600, a wired or wireless network interface 604 configured to connect the computer device 600 to a network, and an input output (I/O) interface 605. The computer device 600 may operate based on an operating system stored in the memory 602.
Wherein the instructions in the memory 602, when executed by the processing component 601, enable the computer device 600 to perform the method of any of the embodiments described above.
Embodiments of the subject matter and the functional operations described in this specification can be implemented in: digital electronic circuitry, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a tangible, non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode and transmit information to suitable receiver apparatus for execution by the data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.
The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform corresponding functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Computers suitable for executing computer programs include, for example, general and/or special purpose microprocessors, or any other type of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory and/or a random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer does not necessarily have such a device. Moreover, a computer may be embedded in another device, e.g., a mobile telephone, a Personal Digital Assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device such as a Universal Serial Bus (USB) flash drive, to name a few.
Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., an internal hard disk or a removable disk), magneto-optical disks, and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. In other instances, features described in connection with one embodiment may be implemented as discrete components or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Thus, particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Further, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (12)
1. A log construction method, the method comprising:
defining variables in a code compiling platform;
reading the log content in the code compiling platform, and assigning the log content to the variable;
and returning the variable to a code warehouse through a plug-in a code compiling platform so as to construct a log corresponding to the log content in the code warehouse.
2. The method of claim 1, wherein prior to assigning the log content to the variable, the method further comprises:
reading a line break in the log;
and replacing the line break with a line break recognizable by the code warehouse.
3. The method of claim 1, wherein reading the log contents of the code compilation platform comprises:
acquiring a task identifier of a compiling task executed by the code compiling platform;
calling an API of the code compiling platform according to the task identifier;
and acquiring the log content of the code compiling platform through the API.
4. The method of claim 1, wherein assigning the log content to the variable comprises:
useful information is screened out from the log content;
and assigning the useful information to the variable.
5. The method of claim 1, wherein prior to returning the variable to a code repository through a plug-in a code compilation platform, the method further comprises:
converting the variable into a format recognizable by the plug-in.
6. The method of claim 1, further comprising:
and saving the log content in a code compiling platform.
7. The method of claim 1, wherein the log content is a log constructed by the code compilation platform last executed a compilation task.
8. The method according to any of claims 1 to 7, wherein the plug-in is an EnvInject API plug-in.
9. The method of any one of claims 1 to 7, wherein the code compilation platform is Jenkins and the code repository is Gitlab.
10. A log construction system, the system comprising:
the variable definition module is used for defining variables in the code compiling platform;
the assignment module is used for reading the log content in the code compiling platform and assigning the log content to the variable;
and the log construction module is used for returning the variable to a code warehouse through a plug-in a code compiling platform so as to construct a log corresponding to the log content in the code warehouse.
11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 10.
12. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method according to any of claims 1 to 10 are implemented when the processor executes the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810602092.9A CN108897677B (en) | 2018-06-12 | 2018-06-12 | Log construction method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810602092.9A CN108897677B (en) | 2018-06-12 | 2018-06-12 | Log construction method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108897677A CN108897677A (en) | 2018-11-27 |
| CN108897677B true CN108897677B (en) | 2022-04-15 |
Family
ID=64344901
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810602092.9A Active CN108897677B (en) | 2018-06-12 | 2018-06-12 | Log construction method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108897677B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111309506A (en) * | 2020-02-12 | 2020-06-19 | 中国平安人寿保险股份有限公司 | Method, equipment, server and readable storage medium for positioning compiling errors |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106021583A (en) * | 2016-06-02 | 2016-10-12 | 北京京东尚科信息技术有限公司 | Statistical method and system for page flow data |
| CN106294151A (en) * | 2016-08-09 | 2017-01-04 | 合智能科技（深圳）有限公司 | Daily record method of testing and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140270115A1 (en) * | 2013-03-12 | 2014-09-18 | J. Stephen Burnett | Electronic Message Aggregation and Sharing System and Apparatus |
-
2018
- 2018-06-12 CN CN201810602092.9A patent/CN108897677B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106021583A (en) * | 2016-06-02 | 2016-10-12 | 北京京东尚科信息技术有限公司 | Statistical method and system for page flow data |
| CN106294151A (en) * | 2016-08-09 | 2017-01-04 | 合智能科技（深圳）有限公司 | Daily record method of testing and device |
Non-Patent Citations (3)
| Title |
|---|
| Jenkins gitlab持续集成打包平台搭建;meng_philip123;《简书》;20160725;第4-8页 * |
| Jenkins+gitlab自动化编译部署方案;冒雨ing;《博客园》;20180518;第2页 * |
| Jenkins-client实现方式;贝克田庄;《博客园》;20180429;第1-2页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108897677A (en) | 2018-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107861870B (en) | Interface test and test data generation method, device, terminal and storage medium | |
| CN109542399B (en) | Software development method and device, terminal equipment and computer readable storage medium | |
| CN108845930B (en) | Interface operation test method and device, storage medium and electronic device | |
| CN109408375B (en) | Method and device for generating interface document | |
| CN112416318B (en) | Micro-service development method and device, storage medium and electronic equipment | |
| CN105573734B (en) | method and equipment for providing SDK file | |
| CN110888720A (en) | Task processing method and device, computer equipment and storage medium | |
| CN106991100B (en) | Data import method and device | |
| CN107404418B (en) | Internet product testing method, device, equipment and storage medium | |
| CN111596927B (en) | Service deployment method and device and electronic equipment | |
| CN110955715A (en) | ERP system, data conversion method and device of target platform and electronic equipment | |
| CN111090582A (en) | Error code positioning method and device, storage medium and electronic equipment | |
| US20160321069A1 (en) | Effective feature location in large legacy systems | |
| US10430802B2 (en) | Screen-image based classification | |
| KR20200046078A (en) | Scalable techniques for executing custom algorithms on media items | |
| CN111124420A (en) | Compiling method, device, electronic equipment and readable storage medium | |
| CN111124480B (en) | Method and device for generating application program package, electronic equipment and storage medium | |
| CN108897677B (en) | Log construction method and system | |
| CN113268229B (en) | Code generation method and code generation device | |
| CN111858020B (en) | User resource limiting method and device and computer storage medium | |
| CN114911479A (en) | Interface generation method, device, equipment and storage medium based on configuration | |
| CN114169311A (en) | Data analysis method and device | |
| CN108734149B (en) | Text data scanning method and device | |
| CN114371866A (en) | Version reconfiguration test method, device and equipment of service system | |
| CN111399806B (en) | Component management 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 |