Method for providing code information, electronic apparatus supporting thereof, and non-transitory computer-readable recording medium comprising program for performing the method
Patent Information
- Application Number
- TW114124688
- Authority / Receiving Office
- TW · TW
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-08-17
- Filing Date
- 2023-08-11
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2043-08-10
AI Technical Summary
In multi-developer projects, identifying the source of code conflicts during merging is difficult, leading to productivity issues.
An electronic device and method that tracks code changes by providing build operation information to operators, including branch and task information, allowing for efficient management and identification of code modifications.
Enhances productivity by enabling operators to systematically track and manage code changes, improving the efficiency of multi-developer projects.
Smart Images

Figure TWG2TB001920668_001 
Figure TWG2TB001920668_002 
Figure TWG2TB001920668_003
Abstract
Description
[Technical Field]
[0001] This invention relates to an electronic device and method for providing code-related information, and more specifically, to an electronic device and method for providing information related to code written and built by operators. [Previous Technology]
[0002] Since the fourth industrial revolution, a new generation of industrial revolution achieved through the convergence of information and communication technologies, became a core topic, the importance of software technology has become prominent. Software technology can be used in various fields, such as ubiquitous computing, the Internet of Things, autonomous vehicles, artificial intelligence, robotics, and blockchain. The development of software products that reflect market goals and user needs is an inevitable trend, and development projects involving multiple developers are becoming increasingly common.
[0003] Development projects involving multiple developers combine the work outputs of each developer to complete a single project. However, in larger development projects, merging the source code from different developers' work into the project may result in conflicts or failures during the merging process. In such cases, it is difficult to identify which developer's source code caused the problem. Various solutions have been proposed by the industry to systematically improve the productivity of multi-developer projects.
[0004] For related content, please refer to previous documents such as KR1020210147354A and KR1020210090575A. [Summary of the Invention]
[0005] [Problem to be Solved by the Invention] The object of the present invention is to provide an electronic device and method for providing code information to operators, in order to solve the above-mentioned problem.
[0006] Specifically, the aim is to provide a method and electronic device that, during the operation of a case-related process performed by multiple operators, enables each operator to modify and update the case-related code in their respective branch, thereby systematically tracking changes that occur when multiple operators modify the code of the same case.
[0007] The technical problem to be solved by this invention is not limited to the technical problems mentioned above. Those skilled in the art can clearly understand other technical problems not mentioned based on the following description. [Technical Means for Solving the Problem]
[0008] Various embodiments may provide a method for providing code-related information and an electronic device supporting the method.
[0009] The method for providing code-related information of the electronic device in various embodiments disclosed in this specification may include the following steps: corresponding to the start of a build operation of first code information executed in the server, obtaining first information from the server, the first information including information of the build operation and branch information corresponding to the first code information; corresponding to the end of the build operation, obtaining second information from the server including at least information of the result of the build operation; and providing a build operation information directory to the operator's device, the build operation information directory including a first item generated based on the first information and the second information.
[0010] In the embodiment, the first information may further include at least a portion of the following: requesting the operator information for the job creation from the server, branch identification information corresponding to the first code information, commit information corresponding to the first code information, and task identification information corresponding to the first code information.
[0011] In the embodiments, the branch identification information may correspond to one or more task identification information, and the task identification information may correspond to one or more branch identification information.
[0012] In an embodiment, the above-mentioned code-related information providing method may further include the following steps: providing information on one or more tasks, wherein the information on one or more tasks is confirmed based on the above-mentioned branch identification information and corresponds to the branch corresponding to the above-mentioned first code information.
[0013] In an embodiment, the above-mentioned code-related information providing method may further include the following steps: providing information on one or more branches, wherein the information on one or more branches is confirmed based on the above-mentioned task identification information and corresponds to the task corresponding to the above-mentioned first code information.
[0014] In the embodiment, the second information may further include at least a portion of the capacity information of the package generated by the server corresponding to the establishment operation, the version information of the package corresponding to the establishment operation, and the time required corresponding to the establishment operation.
[0015] In the embodiment, the above-mentioned code-related information provision method may further include the following steps: confirming whether the above-mentioned establishment operation is abnormal based on the above-mentioned required time information confirmed based on the above-mentioned second information and the required time information of one or more establishment operations confirmed based on the above-mentioned establishment operation information directory; and providing the above-mentioned abnormality information to the above-mentioned one or more operators based on the above-mentioned branch information and the above-mentioned establishment abnormality information.
[0016] In the embodiment, the above-mentioned code-related information providing method may further include the following steps: based on the required time information corresponding to each of the plurality of creation jobs and the version information of the program package corresponding to each of the plurality of creation jobs, obtain the creation time information corresponding to each version information; based on the creation time information corresponding to each version information and the required time information confirmed based on the second information, confirm whether the creation job of the first code information is abnormal.
[0017] In the embodiment, the above-mentioned code-related information provision method may further include the following steps: confirming whether the above-mentioned creation operation is abnormal based on the above-mentioned capacity information confirmed based on the above-mentioned second information and the capacity information of one or more creation operation packages confirmed based on the above-mentioned creation operation information directory; and providing the above-mentioned abnormality information to the above-mentioned one or more operators based on the above-mentioned branch information and the above-mentioned creation abnormality information.
[0018] In the embodiment, the above-mentioned code-related information providing method may further include the following steps: based on the capacity information corresponding to each of the plurality of creation jobs and the version information of the program package corresponding to each of the plurality of creation jobs, obtain capacity information corresponding to each version information; based on the capacity information corresponding to each version information and the capacity information confirmed based on the above-mentioned second information, confirm whether the creation job of the above-mentioned first code information is abnormal.
[0019] In an embodiment, the above-mentioned code-related information provision method may further include the following steps: providing information on one or more operators confirmed based on the above-mentioned branch information.
[0020] In the embodiment, the above-mentioned code-related information providing method may further include the following steps: providing result information to the operator device, the result information including at least a part of the above-mentioned second information and at least including the information of the result of the above-mentioned establishment of the operation, the operator device corresponding to one or more operator information confirmed based on the above-mentioned branch information.
[0021] In the embodiment, the above-mentioned code-related information providing method may further include the following steps: providing task status information related to the progress status of the task, wherein the task corresponds to the above-mentioned first code information confirmed based on the above-mentioned task identification information.
[0022] In an embodiment, the above-mentioned code-related information providing method may further include the following steps: providing the above-mentioned first code information to the operator device in response to a code information request corresponding to the first item received from the operator device.
[0023] In an embodiment, the first item may include path information of the code information of a package, the package being generated by the server in relation to the creation operation and including at least the first code information, and the method for providing the code-related information may further include the following steps: providing the code information of the package to the operator device based on the path information.
[0024] In the embodiments, the above-mentioned code-related information provision method may further include the following steps: obtaining branch identification information and one or more operator information; and generating a branch directory including branch information based on a request received from the operator device, wherein the branch information is obtained by mapping the above-mentioned branch identification information and the above-mentioned one or more operator information.
[0025] In an embodiment, the code information of the program package generated by the server in response to the above-mentioned establishment job and including the above-mentioned first code information may include source code, which is used to perform A / B testing in response to the code information of the generated program package. The method of providing the above-mentioned code-related information may further include the following steps: providing the result information of the above-mentioned A / B test confirmed based on the above-mentioned first information.
[0026] The electronic device of various embodiments disclosed in this specification includes: memory; transceiver; and processor; the processor can be configured as follows: corresponding to the start of a build operation of first code information executed in the server, it obtains first information from the server, the first information including information of the build operation and branch information corresponding to the first code information; corresponding to the end of the build operation, it obtains second information from the server including at least information of the result of the build operation; and provides a build operation information directory to the operator's device, the build operation information directory including a first item generated based on the first information and the second information. [Effects of the Invention]
[0027] According to the method of the present invention, the method and electronic device for providing code-related information can confirm information related to the establishment operation of a plurality of program codes related to the case and provide it to the operator, thereby notifying the status of the establishment operation and improving the productivity of the case.
[0028] Furthermore, the electronic device and method of the present invention for providing code information can intuitively provide operators with information on the progress of a case by providing them with the current status of the operation related to the case.
[0029] The effects obtained in this invention are not limited to those mentioned above. Those skilled in the art to which this invention pertains can clearly understand other effects not mentioned based on the following description.
Implementation Method
[0031] The following embodiments are combinations of the constituent elements and features of various embodiments in a prescribed manner. Unless otherwise expressly stated, each constituent element or feature may be considered optional. Each constituent element or feature may be implemented in combination with other constituent elements or features. Furthermore, a portion of the constituent elements and features may be combined to constitute various embodiments. The order of actions described in various embodiments may be changed. A portion of a constituent element or feature of one embodiment may be included in other embodiments, or may replace the corresponding constituent element or feature of other embodiments.
[0032] In the description of the drawings, procedures or steps that may obscure the essence of various embodiments are not described, nor are procedures or steps that can be understood by one of common sense in the art.
[0033] Throughout this specification, when a part comprises or includes a constituent element, unless otherwise described, it means that other constituent elements may be included, not excluded. Furthermore, the terms “…part,” “…device,” “module,” etc., used in the specification refer to a unit that performs at least one function or action, which can be implemented by hardware or software or a combination of hardware and software. Also, unless explicitly stated otherwise, “a (or an),” “one,” “the,” and similar conjunctions are used in the context of describing various embodiments (particularly in the context of the following claims) to mean both singular and plural.
[0034] Hereinafter, preferred embodiments of various embodiments will be described in detail with reference to the accompanying drawings. The accompanying drawings and the detailed description disclosed below are intended to illustrate exemplary embodiments of various embodiments, and not to represent the only embodiments.
[0035] Furthermore, the specific terms used in the various embodiments are provided to facilitate understanding of the various embodiments, and the use of such specific terms may be changed to other forms without departing from the technical concept of the various embodiments.
[0036] At this point, it should be understood that the combination of the blocks of the flowchart and the flowchart itself can be performed by computer program instructions. These computer program instructions can be installed in the processor of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that instructions executable by the processor of the computer or other programmable data processing device generate components for performing the functions described in the flowchart blocks. To implement the functions in a specific manner, these computer program instructions can be stored in a computer-usable or computer-readable memory of a specified computer or other programmable data processing device. Therefore, the instructions stored in the computer-usable or computer-readable memory can also generate an article of manufacture containing instructions for performing the functions described in the flowchart blocks. Since the computer program instructions can be loaded onto a computer or other programmable data processing device, a series of action steps are performed on the computer or other programmable data processing device to produce a flow executed by the computer. The instructions of the processor of the computer or other programmable data processing device provide steps for performing the functions described in the flowchart blocks.
[0037] Furthermore, each block may represent a portion of a module, segment, or code comprising one or more executable instructions for performing a specific logical function. It should also be noted that in some alternative implementations, the functions mentioned in the blocks may not occur sequentially. For example, two blocks shown consecutively may actually occur simultaneously, or may occur in reverse order according to their respective functions.
[0038] Figure 1 is a diagram illustrating a code information providing system 100, which can implement a method for providing code-related information by electronic devices in various embodiments.
[0039] Referring to FIG1, the code information providing system 100 of various embodiments can be implemented in various devices. For example, the code information providing system 100 can be implemented in electronic device 101, operator device 102, and server 103. In other words, electronic device 101, operator device 102, and server 103 can perform the operations of various embodiments of the present invention based on the code information providing system 100 implemented in each device. On the other hand, the code information providing system 100 of various embodiments is not limited to that shown in FIG1 above, and can also be implemented in various electronic devices and servers.
[0040] The electronic device 101 in various embodiments may be a device that enables wired and wireless communication with one or more operator devices 102 (e.g., first operator device 102-1, second operator device 102-2, ..., nth operator device 102-n) and / or server 103, and includes a storage device with a large unit storage capacity. For example, the electronic device 101 may be a cloud device connected to one or more operator devices 102 and / or server 103.
[0041] The operator device 102 in various embodiments can be a desktop personal computer, tablet computer, mobile terminal or other device that can be used by an individual user. In addition, other electronic devices that perform similar functions can be used as the operator device 102.
[0042] The server 103 in various embodiments may be a device that enables wired and wireless communication with one or more operator devices 102 (e.g., first operator device 102-1, second operator device 102-2, ..., nth operator device 102-n) and / or electronic devices 101, and includes a storage device with a large unit storage capacity. For example, the electronic device 101 may be a cloud device connected to one or more operator devices 102 and / or electronic devices 101.
[0043] The code information providing system 100 in various embodiments may include various modules for operation. The modules included in the code information providing system 100 may be computer code or one or more instructions, which are implemented in a manner that enables the physical device (e.g., electronic device 101) of the code information providing system 100 (or, included in the physical device) to perform specified actions. In other words, the physical device implementing the code information providing system 100 may store a plurality of modules in memory in the form of computer code. When the plurality of modules stored in memory are executed, the plurality of modules can cause the physical device to perform specified actions corresponding to the plurality of modules.
[0044] According to an embodiment, the code information providing system 100 may further include a network that supports the transmission and reception of information between at least some of the electronic device 101, server 103, one or more operator devices 102 and other external devices.
[0045] On the other hand, throughout the embodiment, the electronic device 101, one or more operator devices 102, and server 103 are referred to as separate devices and servers, but this can be a logically separate configuration, implemented by functions separate from a single device or server. For example, at least a portion of the operator device 102 and server 103 may be included in or integrated with the electronic device 101. However, even in this case, a series of code information provision methods implemented by data transmission and reception between the electronic device 101, operator devices 102, and server 103 can be similarly implemented. In the case of a device included in or integrated with the electronic device 101, communication with the electronic device 101 can be understood as a process of exchanging data between various components within the device (e.g., with the processor of the electronic device 101).
[0046] For ease of explanation, the following description is given of an embodiment in which the operator device 102 and the server 103 exist as devices or servers independent of the electronic device 101. The following description is also applicable to the case in which at least a part of the operator device 102 and the server 103 is included in the electronic device 101 or is integrated with the electronic device 101.
[0047] According to one embodiment, the electronic device 101, the operator device 102, and the server 103 may include multiple computer systems or computer software implemented by a network server. For example, at least a portion of the electronic device 101, the operator device 102, and the server 103 may refer to a computer system and computer software that connects to a lower-level device to receive a job execution request, executes the job execution request, and provides the execution result. The lower-level device may communicate with other network servers via a computer network such as an intranet or the Internet. Furthermore, at least a portion of the electronic device 101, the operator device 102, and the server 103 can be understood as a broad concept, including a series of applications that can operate on the network server and various internally constructed databases. For example, at least a portion of the electronic device 101, the operator device 102, and the server 103 may be implemented using various network server programs provided by operating systems such as Disk Operating System (DOS), Windows Operating System, Linux Operating System, UNIX Operating System, or Macintosh Operating System (MacOS).
[0048] Figure 2 is a diagram showing the configuration of electronic devices, operator devices and servers in various embodiments.
[0049] Referring to FIG2, the electronic device 101, one or more operator devices 102 and server 103 may include an input / output unit 210, a communication unit 220, a storage unit 230 and a processor 240.
[0050] The input / output unit 210 may be various interfaces or ports for receiving user input or outputting information to the user. The input / output unit 210 may include an input module and an output module, and the input module receives user input from the user. User input may be implemented in various forms such as keypad input, touch input, and voice input. Examples of input modules that can receive such user input may include: a conventional keypad or keyboard, a mouse, a touch sensor that senses the user's touch, a microphone that receives voice signals, a camera that recognizes gestures by image recognition, a proximity sensor that senses the user's approach, including at least one of an illuminance sensor or an infrared sensor, a motion sensor that recognizes user operations by an accelerometer or a gyroscope sensor, and various other types of input mechanisms that sense or receive user input in various other forms. According to an embodiment of the present invention, the input module may include at least one of the above-mentioned devices. Here, the touch sensor can be implemented using piezoelectric or electrostatic touch sensors that sense touch via a touch panel or touch film mounted on the display panel, or optical touch sensors that sense touch via optical means. Furthermore, the input module can also be implemented as an input interface (USB (Universal Serial Bus) port, PS / 2 (Personal System 2) port, etc.) connected to an external input device that receives user input, rather than being a device that senses user input itself. Additionally, the output module can output various types of information. The output module may include at least one of the following: a display that outputs images, a speaker that outputs sound, a haptic device that generates vibration, and various other types of output mechanisms. Furthermore, the output module can also be implemented as a port-type output interface connected to the aforementioned individual output mechanisms.
[0051] For example, the output module of the display form can display text, still images, and videos. The display may include at least one of the following: liquid crystal display (LCD), light emitting diode (LED) display, organic light emitting diode (OLED) display, flat panel display (FPD), transparent display, curved display, flexible display, 3D display, holographic display, projector, and other devices of various forms capable of performing image output functions. Such a display may also be a touch display integrated with the touch sensor of the input module.
[0052] The communication unit 220 can communicate with other devices. Therefore, the electronic device 101, the operator device 102, and the server 103 can send and receive information with other devices through the communication unit. For example, the electronic device 101, the operator device 102, and the server 103 can use the communication unit to communicate with each other or with other devices.
[0053] Here, communication, i.e., the transmission and reception of data, can be achieved via wired or wireless means. For this purpose, the communication unit may include: a wired communication module connected to the Internet via a LAN (Local Area Network); a mobile communication module connected to a mobile communication network via a mobile communication base station to transmit and receive data; a short-range communication module using a WLAN (Wireless Local Area Network) communication method such as Wireless Fidelity (Wi-Fi) or a WPAN (Wireless Personal Area Network) communication method such as Bluetooth or Zigbee; a satellite communication module using GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System); or a combination thereof.
[0054] Storage 230 can store various types of information. Storage can store data temporarily or semi-permanently. For example, the storage of electronic device 101 can store: the operating system (OS) used to drive electronic device 101, data used to manage websites, or data related to programs or applications used to generate Braille (e.g., website applications). Furthermore, storage can store the modules described above as computer code.
[0055] Examples of storage devices 230 include: Hard Disk Drive (HDD), Solid State Drive (SSD), flash memory, Read-Only Memory (ROM), Random Access Memory (RAM), etc. Such storage devices can be provided in either an internal or removable form.
[0056] The processor 240 controls the overall operation of the electronic device 101, the operator device 102, and the server 103. To this end, the processor 240 can perform various information calculations and processing, and control the operation of the constituent elements of the electronic device 101. For example, the processor 240 can execute programs or applications that provide code-related information. The processor 240 can be implemented using a computer or similar device, depending on the hardware, software, or a combination thereof. In terms of hardware, the processor 240 can be implemented as an electronic circuit that processes electrical signals to perform control functions; in terms of software, it can be implemented as a program that drives the hardware processor 240. On the other hand, unless specifically mentioned in the following description, it can be interpreted that the operation of the electronic device 101, the operator device 102, and the server 103 is performed by the control of the processor 240. That is, when the module implemented in the above code information providing system 100 is executed, the module can be interpreted as the processor 240 controlling the electronic device 101, the operator device 102 and the server 103 to perform the following actions.
[0057] In summary, various embodiments can be implemented by various mechanisms. For example, various embodiments can be implemented by hardware, firmware, software, or a combination thereof.
[0058] In the case of implementation by hardware, the methods of various embodiments can be implemented by one or more ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.
[0059] When implemented using firmware or software, the methods of various embodiments can be implemented in the form of modules, programs, or functions that perform the functions or operations described below. For example, software code can be stored in memory and driven by a processor. The memory can be located inside or outside the processor and exchanges data with the processor through various known mechanisms.
[0060] Hereinafter, various embodiments will be described in more detail based on the technical concept described above. The foregoing content can be applied to the various embodiments described below. For example, actions, functions, terms, etc., not defined in the various embodiments described below can be implemented and described based on the foregoing content.
[0061] In the following description, various embodiments are described on the premise that the electronic device 101 performs the action of providing code-related information. According to various embodiments, the electronic device 101 can send and receive information related to the action of providing code information with the operator device 102 and / or the server 103.
[0062] Figure 3 is a diagram illustrating the material structure of the case providing code information in various embodiments.
[0063] Figure 3 is a diagram illustrating the material structure 30 of a case 300 providing code information in various embodiments disclosed in this specification. Referring to Figure 3, a master branch (MB), a develop branch (DB), a first feature branch (FB1), and a second feature branch (FB2) can be derived from a case 300. However, the material structure 30 shown in Figure 3 is merely an example to aid in understanding the present invention and is not intended to limit the material structure 30 for providing code information according to embodiments of the present invention. The material structure 30 can be adaptively configured according to the objectives of the case 300.
[0064] The main branch MB can be a branch used to manage the release history related to case 300, and can manage the set of files in the releaseable state. As shown in Figure 3, the main branch MB including the first main file set 310 and the second main file set 320 can be published from the first program built from the first main file set 310 or the second program built from the second main file set 320. The second program can be other versions of the first program. The plurality of files included in the first main file set 310 and the second main file set 320 can each be a file submitted to the server 103 through the first to nth operator devices 102-1, 102-2, ..., 102-n.
[0065] The development branch DB can be a branch used to implement a merge, which is used to develop various functions related to case 300. When the file set related to the development branch DB includes all functions related to the released program, and the bugs have been fixed and it is in a stable state that can be released, the development branch DB can be merged into the main branch MB. The first to third development file sets 311, 312, and 313 in Figure 3 may each include a plurality of files used to develop various functions related to the program corresponding to the second main file set 320. In the embodiment, the second development file set 312 may be a file set from the first development file set 311, the third development file set 313 may be a file set of an updated version of the second development file set 312, or the first to third development file sets 311, 312, and 313 may each be a file set used to implement independent functions related to the program corresponding to the second main file set 320. The plurality of files included in each of the first to third development file sets 311, 312, and 313 can be files submitted to the server 103 by the first to nth operator devices 102-1, 102-2, ..., 102-n.
[0066] Feature branch FB1 and feature branch FB2 can be branches derived from development branch DB to develop new features and fix bugs related to case 300. When the work related to feature branch FB1 and feature branch FB2 is completed, the file sets related to feature branch FB1 and feature branch FB2 can be merged into development branch DB. Figure 3 illustrates material structure 30, where the work related to feature branch FB2 is completed, at least one of feature file set 312_1 and feature file set 312_2 is merged into development branch DB, and the work related to feature branch FB1 is in progress.
[0067] Furthermore, in cases where urgent corrections occur to the release branch branched from the development branch DB in preparation for a product release, the material structure 30 of embodiment 300 of the present invention may further include at least one of the hotfix branches branched from the self-branch MB. The branch information referred to in this specification may be information about at least one of the main branch MB, development branch DB, feature branches FB1, FB2, release branch, and hotfix branch related to embodiment 300, and the branch information may include information about the file set associated with that branch. Furthermore, the file information referred to in this specification may include code information of at least one file included in the file set, and the file information may include information about the program code associated with that file.
[0068] On the other hand, in this embodiment, each file set can be merged into the main branch MB based on a request from the operator device 102. For example, corresponding to the submission of a file set to the server 103 by the operator device 102, the server 103 can merge the submitted file set into the main branch MB and perform a build. The build operation may include the action of packaging one or more source code files and distributing them. Packaging may include the action of generating a package data, which includes at least the submitted file set and outputs it. The operator device 102 can complete the file set operation and submit it, corresponding to which the build request is transmitted to the server 103, and the server 103 can perform the build operation corresponding to the file set and generate the package. The server 103 can perform a push operation based on the submission information. The push operation may refer to the operation of storing added file information or edited file information in a remote storage (e.g., server 103). Server 103 can be a development server or a CI (continuous integration) server. For example, server 103 can continuously build and publish code information pushed from each of the more than one operator devices 102 each time a push is executed. Server 103 can perform a build operation corresponding to the pushed files. For example, for the first development file set 311, when operator device 102 submits it, server 103 can perform a build operation corresponding to the pushed file set at the same time as submission, generating a first package P1 corresponding to the first development file set 311. As another example, for the second-second development file set 311, when operator device 102 submits the second-second feature file set 312_2 to server 103, server 103 can perform a build operation at the same time as submission, generating a second package P2 corresponding to the second-second feature file set 312_2. In this embodiment, package P1 and package P2 can be identified as versions of the same program as the first program assembled from the first main file set 310. Package P1 and package P2 can be assigned the same identification number as the version of the first program, and can be identified as versions different from the second program assembled from the second main file set 320. Server 103 can distribute the created packages. Packages continuously created before and after version updates (such as package P1 and package P2) can be the objects of alpha-testing and / or beta-testing. Electronic device 101, operator device 102, server 103 and / or other electronic devices can perform alpha-testing and beta-testing on each package. Electronic device 101 can obtain information on the alpha-testing and beta-testing results.
[0069] In this embodiment, each branch may correspond to one or more tasks. A task can be understood as a conceptual / functional development unit. As one or more functional components included in Case 300, each task may correspond to one or more branches. For example, the first task T1 may include tasks related to the shopping cart function, and the second task T2 may include tasks related to the checkout window function. The first feature branch FB1 and the second feature branch FB2 may include source code corresponding to the first task T1, and the second feature branch FB2 may include source code corresponding to the second task T2. Corresponding identification information may be assigned to each task, and the electronic device 101 may confirm the status information of the task based on the task identification information. For example, the electronic device 101 may confirm the progress information of the sub-task units included in the task, or confirm the status information of the task based on the status information of one or more branches corresponding to the task. Electronic device 101 can confirm the information of the branch corresponding to the task based on task information, and conversely, it can confirm the information of the task corresponding to each branch based on the information of each branch. In an embodiment, when operator device 102 submits a file set, submission information including at least a portion of the submission message can be transmitted to server 103. The submission information may include information of the task corresponding to the file set. These development and code construction units may have different structures depending on the operator.
[0070] Figure 4 is a flowchart of the operation of electronic devices providing code-related information in various embodiments.
[0071] According to various embodiments, one or more worker devices 102 may transmit a setup request 41 to the server 103. The worker device 102 may submit a file set to the server 103, and the server 103 may merge the submitted file set into the main branch MB, generating a package corresponding to the submitted file set. In embodiments, the setup request may include the file set transmitted by the worker device 102 to the server 103 and a submission request. The file set submitted by the worker device 102 may include one or more code information sets. The submission request may include a submission message corresponding to the file set. The worker device 102 of the requesting worker may generate a submission message. In embodiments, the worker device 102 may write and transmit a submission message to the server 103, and the electronic device 101 may obtain the submission message from the server.
[0072] According to various embodiments, server 103 may initiate a creation job 42 for the submitted file sets. The creation job may include a packaging job that merges the submitted file sets to produce a single package.
[0073] According to various embodiments, the electronic device 101 may obtain first information from the server 103 in response to the start 42 of the creation operation on the server 103 (S401). In embodiments, the first information may include information related to code information (e.g., a file set). The first information may include information obtained immediately after the code information is pushed to the server 103. The first information may include one or more meta information related to the code information that is the object of creation. For example, the first information may include at least a portion of information such as the date of the creation request, task information corresponding to the code information, branch information, version information, and commit information.
[0074] In an embodiment, the task information may include at least a portion of task identification information corresponding to the code information and information on the task's progress status. According to one embodiment, each task may correspond to one or more branches. The electronic device 101 and / or server 103 may store correspondence information between branches corresponding to each task, or confirm the correspondence between tasks and branches based on task-branch correspondence information stored in an external electronic device. The electronic device 101 may confirm information about the branch corresponding to a task based on the task identification information.
[0075] In an embodiment, branch information may include identification information of the branch corresponding to the code information. Each branch may correspond to more than one task. Electronic device 101 and / or server 103 may store the correspondence information of branches corresponding to each task, or confirm the correspondence between tasks and branches based on the task-branch correspondence information stored in an external electronic device. Electronic device 101 may confirm the information of the branch corresponding to the task based on the branch identification information. According to one embodiment, each branch information may include operator information corresponding to the branch. More than one operator may be assigned to each branch, and the branch-operator correspondence information may be stored in electronic device 101, server 103 or other external devices. Electronic device 101 may confirm the information of more than one operator corresponding to a branch based on the branch identification information. Operator information may include at least a portion of: operator identification information, operator device 102 information corresponding to the operator, operator contact information, branch information corresponding to the operator, and task information corresponding to the operator. In this embodiment, the electronic device 101 can identify the operator corresponding to the branch information based on the branch information, and identify the task information corresponding to the operator. In this embodiment, the electronic device 101 can identify one or more task information corresponding to a branch based on the branch information, and identify the operator information corresponding to the task based on the information of one or more tasks. In this embodiment, the electronic device 101 can identify one or more branch information corresponding to a task based on the task information, and identify the operator information corresponding to the branch information based on one or more branch information.
[0076] In an embodiment, the submission information may include at least a portion of the following: submission message, submission job information, information of the submitted file set (code information), and identification information associated with the submitted file set. For example, the submission information may include task information corresponding to the submitted code information. In an embodiment, the identification information associated with the submitted file set may include information related to code information written, modified, altered, or generated by an operator in the file set. For example, source code information may include location information of the written, modified, altered, or generated code information in the file set and / or information on the main writing details. In an embodiment, the submission information may include identification information corresponding to the submission job. For example, when code information is submitted by operator device 102, operator device 102 or server 103 may generate and / or allocate identification information for the submission job.
[0077] In the embodiment, the server 103 may provide the first information to the electronic device 101 in response to the start of the setup job 42, and at the same time perform the setup job corresponding to the code information pushed.
[0078] According to various embodiments, server 103 may terminate the establishment job 43. The termination of the establishment job may include establishment failure or establishment success. Server 103 may confirm whether the establishment was successful in response to the termination of the establishment job 43. Server 103 may generate a program package corresponding to the pushed code information when the establishment is successful.
[0079] According to various embodiments, electronic device 101 may obtain second information from server 103 in response to the completion of the creation operation 43 (S402). The second information may include information generated by server 103 or obtained by electronic device 101 in response to the completion of the creation operation. In embodiments, the second information may include information related to the result of the creation operation. For example, the second information may include at least a portion of information such as whether the creation was successful, the date of creation completion, the time required for creation, and the capacity of the created package. In embodiments, server 103 may provide the second information to electronic device 101 in response to the completion of the creation operation.
[0080] According to various embodiments, electronic device 101 may generate a first item. The first item may refer to an item included in a job creation information directory. The job creation information directory may include one or more pieces of information related to a job creation, generated from at least a portion or a combination of the first and second information, corresponding to each job creation. According to one embodiment, the first item included in the job creation information directory may include at least a portion of: branch information corresponding to the pushed code information, operator information, submission information, information on whether the creation was successful, task information, version information, and package size information. Electronic device 101 may generate the first item based on the first and second information.
[0081] On the other hand, in an embodiment, the first information or the second information may include a request to generate the first item. The electronic device 101 may obtain the first and second information from the server 103 in response to the start or end of the establishment operation of the server 103. In this case, the first or second information may include a request related to generating the first item. For example, the server 103 may transmit a request to the electronic device 101 to generate the first item in response to the establishment operation 42 at the same time as starting the establishment operation 42. At this time, the electronic device 101 may generate the first item based on the request related to the first item included in the first information (S403). At this time, the electronic device 101 may, in response to obtaining the second information from the server 103, allocate the data confirmed based on the first and second information to the first item.
[0082] According to various embodiments, electronic device 101 may provide a creation job information catalog to operator device 102 (S404). Electronic device 101 may provide operator device 102 with a creation job information catalog including the generated first item. The creation job information catalog may include one or more items generated based on one or more creation requests. In embodiments, the creation job information catalog may include a page format, and electronic device 101 may provide code-related information confirmed or generated based on the first information and the second information to operator device 102 through the creation job information catalog page.
[0083] According to various embodiments, electronic device 101 may receive a package code information request from operator device 102 (S405). The package code information request may include a request for the provision of the source code of the package. According to one embodiment, a first item may include path information of the code information of the package, the package including at least code information corresponding to the first item. The path information may include URL information. External electronic device 102 may confirm the path information based on the first item and may request package code information from electronic device 101 based on the path information. Electronic device 101 may provide the package code information to operator device 102 based on the package code information request (S406).
[0084] In an embodiment, server 103 and / or electronic device 101 may provide information about the result of the job creation to operator device 102. In one embodiment, server 103 and / or electronic device 101 may provide operator device 102 with a result message that includes at least information about the result of the job creation. Server 103 and / or electronic device 101 may confirm operator information corresponding to the code information requested for creation, and provide the result message to operator device 102 based on the confirmed operator information. Electronic device 101 may confirm operator information corresponding to a branch based on the first information, and provide the result message to operator device 102 corresponding to the branch based on the operator information. The result message may include at least information about whether the job creation was successful or failed, and may include the operator information that requested the creation. In an embodiment, the result message may include information about the first item. For example, the result message may include at least a portion of the first information and / or the second information corresponding to the first item. The result message may include information about the access path to the first item. For example, an access path may refer to the access path of resources (such as storage) of electronic device 101 in operator device 102 for confirming the first item from electronic device 101. Access path information may include, for example, URL (user resource location) information.
[0085] On the other hand, in this embodiment, the electronic device 101 can register information about new branches. For example, when a worker creates a new branch, the branch information can be registered to the electronic device 101. The electronic device 101 can receive at least a portion of the branch identification information corresponding to the new branch, the task information corresponding to the branch, and the worker information corresponding to the branch from the worker device 102. The electronic device 101 can generate a branch directory including mapping information in response to the worker request received from the worker device 102 for registering a branch. This mapping information is obtained by mapping the worker information and / or task information corresponding to the branch to the branch identification information.
[0086] On the other hand, in this embodiment, the electronic device 101 can register information about new tasks. For example, when a worker generates a new task, the task information can be registered to the electronic device 101. The electronic device 101 can receive from the worker device 102 at least a portion of task identification information corresponding to the new task, one or more branch information corresponding to the task, and worker information corresponding to the task. The electronic device 101 can generate a task directory including mapping information in response to a worker request received from the worker device 102 for registering a task. This mapping information is obtained by mapping the worker information and / or branch information corresponding to the task to the task identification information.
[0087] On the other hand, in an embodiment, the electronic device 101 can perform A / B testing (A / B test, alpha / beta test) on a program package generated based on the creation operation. The A / B test may include a series of operations: distributing a different set of users to the program built based on the created program package and distributing a different set of users to the program used as a comparison (e.g., a previous version of the program); comparing usage information obtained by the electronic device 101 during program usage by each user set; and generating test result information based on the usage information. According to one embodiment, the code information of the created program package may at least partially include the source code for the A / B test. The source code for the A / B test may include: actions to distinguish between user sets affected by the released program package, unaffected user sets (the user sets may be further divided into more than two), actions to collect result information corresponding to different user sets, and instructions to compare the result information. The electronic device 101 can confirm the A / B test result information of the establishment operation based on the first information corresponding to the specific establishment operation, and provide the A / B test result information to the operator device 102.
[0088] Figure 5 is an exemplary diagram illustrating a catalog of creation operation information provided by an electronic device according to various embodiments.
[0089] Referring to FIG5, the electronic device 101 can provide the establishment job information catalog 500 to the operator device 102. The establishment job information catalog 500 may include more than one item, such as item 1 510, item 2 520, item 3 530, and item 4 540. Each item may be an item generated by the electronic device 101 corresponding to an establishment job requested by the operator 102 and executed in the server 103. For example, item 1 510 may be an item generated based on an establishment request corresponding to first code information, item 2 520 may be an item generated based on an establishment request corresponding to second code information, item 3 530 may be an item generated based on an establishment request corresponding to third code information, and item 4 540 may be an item generated based on an establishment request corresponding to fourth code information. The electronic device 101 can generate each item included in the establishment job information catalog 500 based on the first information and the second information. For example, electronic device 101 can generate a first item 510 based on the first information and the second information corresponding to the first code information, generate a second item 520 based on the first information and the second information corresponding to the second code information, generate a third item 530 based on the first information and the second information corresponding to the third code information, and generate a fourth item 540 based on the first information and the second information corresponding to the fourth code information.
[0090] In this embodiment, the items included in the job information directory 500 may include at least a portion of the first information and the second information and / or a combination thereof. Referring to FIG5, each item is related to the job creation corresponding to the code information requested for creation, and may include at least a portion of the following: Date information section, Name / ID information section, Dev information section, Branch information section, Last commit information section, Status information section, Task information section, Version information section, and Package size information section.
[0091] The Date section may include information such as the date on which the operation is requested or the date on which the operation is completed, corresponding to each code information. The electronic device 101 may generate the date section data based on the first information or the second information obtained from the server 103.
[0092] The Name / ID section may include the name of case 300 or the name or identification information of a program or application built on case 300.
[0093] The Personnel Information (Dev) section may include information about the personnel who submitted code information corresponding to each project. The Personnel Information (Dev) section may include at least a portion of: personnel identification information, information about the personnel device 102 corresponding to the personnel, personnel contact information, branch information corresponding to the personnel, and task information corresponding to the personnel. In an embodiment, the Personnel Information (Dev) section may include personnel identification information. For example, the electronic device 101 may, in item 510, confirm the personnel identification information corresponding to the first code information based on the Personnel Information (Dev), and confirm the personnel contact information and the branch or task information corresponding to the personnel based on the personnel identification information.
[0094] In this embodiment, the established job information directory 500 may include user interfaces (e.g., links) corresponding to the worker information (Dev) section by item. The electronic device 101 may provide worker information through the user interface corresponding to the worker information section. For example, in the example of the first item 510, the electronic device 101 may display the worker's identification information (presto) in the worker section corresponding to the first code information, and provide the worker's identification information in the form of a user interface including hyperlinks. The electronic device 101 may generate the data for the worker information section based on the first information obtained from the server 103.
[0095] The Branch information section may include branch information. The Branch information section may include information about the branch corresponding to the submitted code information for each item. The Branch information section may include at least a portion of: branch identification information, code information corresponding to the branch, operator information for one or more operators corresponding to the branch, and task information corresponding to the branch. In an embodiment, the Branch information section may include branch identification information. For example, the electronic device 101 may, in item 510, identify the branch identification information corresponding to the first code information based on the Branch information, and identify the operator information and / or task information corresponding to the branch based on the branch identification information.
[0096] In this embodiment, the job information directory 500 may include user interfaces (e.g., links) corresponding to branch information sections by item. The electronic device 101 may provide branch information through the user interface corresponding to the branch information section. For example, in the example of the first item 510, the electronic device 101 may display the branch identification information in the branch section corresponding to the first code information and provide the branch identification information in the form of a user interface including hyperlinks. The electronic device 101 may generate the data for the branch information section based on the first information obtained from the server 103.
[0097] The Last commit section may include commit information. The Last commit section may include commit information corresponding to each project. The Last commit section may include at least a portion of the following: commit identification information, commit message, commit job information, information of the committed file set (code information), and identification information associated with the committed file set. For example, the commit information may include task information corresponding to the committed code information. In an embodiment, the identification information associated with the committed file set may include information related to code information written, modified, altered, or generated by an operator in the file set. For example, source code information may include location information of the written, modified, altered, or generated code information in the file set and / or information on the main write details. In an embodiment, the commit information may include identification information corresponding to the commit job. For example, when code information is committed by operator device 102, operator device 102 or server 103 may generate and / or allocate identification information for the commit job. In this embodiment, the Last commit section may include commit identification information and / or commit message. For example, electronic device 101 may identify the commit identification information corresponding to the first code information based on the data included in the Last commit section of item 510, and confirm the commit information based on the commit identification information. In this embodiment, the commit message may at least partially include the commit identification information. In this embodiment, the commit message may at least partially include task information.
[0098] In this embodiment, the job information directory 500 may include user interfaces (e.g., links) corresponding to the Last commit section by item. The electronic device 101 may provide commit information through the user interface corresponding to the commit information section. For example, in the example of the first item 510, the electronic device 101 may display the commit identification information in the commit section corresponding to the first code information and provide the commit identification information in the form of a user interface including hyperlinks. The electronic device 101 may generate the commit information section data based on the first information obtained from the server 103.
[0099] The Status section may include information on whether the corresponding creation operation was successful, categorized by item. For example, in the example of Figure 5, the electronic device 101 may display "Success" in the Status section when the creation is successful and the program package corresponding to the code information requesting the creation operation is generated normally, and display "Fail" when the creation operation fails. The electronic device 101 may generate the data in the Status section based on the second information obtained from the server 103.
[0100] The Task Information (BTS) section may include task information. The Task Information (BTS) section may include information about the task corresponding to each item and the submitted code information. The Task Information (BTS) section may include at least a portion of: task identification information, information about one or more branches corresponding to the task, operator information about one or more operators corresponding to the task, and information about the task's progress status. In an embodiment, the Task Information (BTS) section may include task identification information. For example, the electronic device 101 may, in item 510, confirm the task identification information corresponding to the first code information based on the Task Information (BTS), and confirm the operator information corresponding to the task and / or the task information corresponding to the task based on the task identification information.
[0101] In this embodiment, the job information directory 500 may include user interfaces (e.g., links) corresponding to the task information (BTS) section by item. The electronic device 101 may provide task information through the user interface corresponding to the task information section. For example, in the example of item 4 540, the electronic device 101 may display the identification information (MPI-390 and IOS-6826) of the two tasks corresponding to the fourth code in the task section corresponding to the fourth code information, and provide the identification information of each task in the form of a user interface including hyperlinks. The electronic device 101 may generate the data of the task information section based on the first information obtained from the server 103.
[0102] The Version information section and the Size information section may sequentially include version information corresponding to the package generated based on the creation operation and package size information, respectively. According to one embodiment, the electronic device 101 may generate the Version information section based on the first information obtained from the server 103. According to one embodiment, the electronic device 101 may confirm the version information based on the second information. For example, in the event of creation failure, version identification information corresponding to the pushed code information may not be generated. The electronic device 101 may display or not display the version information based on whether the creation was successful. According to one embodiment, the electronic device 101 may generate the Package Size information section based on the first information obtained from the server 103. According to one embodiment, the electronic device 101 may confirm the Package Size information based on the second information. For example, in the event of creation failure, a package corresponding to the pushed code information may not be generated, and the size information itself may not exist. Conversely, if the creation is successful, a package is generated, and the electronic device 101 can verify the package's capacity information. Referring to Figure 5, in the example of item 520, corresponding to the failure of the creation of the second code information, the Status section displays "Fail," and it can be confirmed that no version information section and package capacity information section were generated.
[0103] In this embodiment, the job creation information directory 500 may include user interfaces (Actions) for providing package code information. The electronic device 101 may allocate path information for package code information to the job creation information directory 500, the package being generated by the server corresponding to the job creation and including at least code information. For example, the user interfaces (Actions) for providing code information may include interfaces implemented as links, which provide path information for obtaining the package code corresponding to each item. For example, in the case of "Download," it may be a link for downloading the package code information of the corresponding item; in the case of "Copy," it may be a link for copying the code information; and in the case of "QR Code," it may be a link for providing the QR code corresponding to the link. Each link may include path information for at least partially obtaining the package code information. Electronic device 101 can provide code information of the program package corresponding to each item to operator device 102 based on operator input received through user interface (Actions) used to provide code information. At this time, the user interface (Actions) used to provide code information can be activated or deactivated for each item based on the second information. For example, if the operation is successfully established, electronic device 101 can activate the user interface (Actions) used to provide code information for the corresponding item; if the operation fails, the user interface (Actions) used to provide code information for the corresponding item can be deactivated.
[0104] Figure 6 is an example of numerical information related to the establishment of an operation provided by an electronic device in various embodiments.
[0105] Figure 7 is an example of numerical information related to the establishment of an operation provided by an electronic device in various embodiments.
[0106] Referring to Figures 6 and 7, the electronic device 101 can provide numerical information related to the creation operation. The numerical information may be generated based on the first information, the second information, and / or the creation operation information directory. The numerical information may include, for example, at least a portion of the numerical information related to the time required for the creation operation as shown in Figure 6, and the capacity information related to the capacity of the program package generated as a result of the creation operation as shown in Figure 7.
[0107] According to various embodiments, the electronic device 101 can generate time-related numerical information based on the first information, the second information, and / or the creation job information directory. For example, the electronic device 101 can confirm the required time information corresponding to each creation job based on the second information. According to one embodiment, the electronic device 101 can confirm the creation time information required for each version based on the first information and the second information. For example, the electronic device 101 can confirm the creation time information corresponding to each of the creation jobs confirmed based on version identification information, and confirm the required creation time by version. The creation time information required by version can be confirmed corresponding to a specified period. The creation time information required by version can be confirmed by summing all creation jobs required by version, or by the average value based on the number of creations. According to embodiments, the electronic device 101 can confirm the creation time information not only for each of the creation jobs confirmed based on version, but also for each of the creation jobs confirmed based on task information, branch information, and / or operator information. The electronic device 101 can generate historical information related to the time required for establishment based on the time required for each of the plurality of establishment operations.
[0108] Referring to Figure 6, the electronic device 101 can provide time-related numerical information 600.
[0109] In this embodiment, the electronic device 101 may confirm the information 601 of the total number of creations. For example, the electronic device 101 may confirm at least a portion of the total number of creations, the total number of creations corresponding to a specified period, and the number of creations by version, based on the creation job information catalog.
[0110] In this embodiment, the electronic device 101 may provide historical information 602 on the time required for creation. For example, the electronic device 101 may, based on the creation job information catalog, confirm at least a portion of the time required for all creation jobs, the total time required for creation jobs corresponding to a specified period, the time required for creation jobs by version, and the average time required for all creation jobs.
[0111] In this embodiment, the electronic device 101 may provide progress information 603 on the time required for establishment. For example, the electronic device 101 may, based on the establishment job information catalog, confirm the time required for all establishment jobs, confirm the total time required for all establishment jobs corresponding to one or more specified periods, and generate progress information 603 on the time required for establishment based on the comparison results.
[0112] According to one embodiment, electronic device 101 can provide information 604 on the number of download requests for code information transmitted from operator device 102 to electronic device 101 by establishing a job information catalog 500.
[0113] In an embodiment, the electronic device 101 can provide a required time chart 605, which visualizes numerical information related to the required creation time. An example in Figure 6 could be a chart of creation time required by version. The electronic device 101 can determine the required creation time by version based on version identification information and creation time information confirmed according to each item, and generate a chart of the required creation time by version. Referring to Figure 6, the horizontal axis of the required time chart 605 can be version information, and the vertical axis can be the average required time. The chart in Figure 6 is an example of a required time chart; the electronic device 101 can obtain numerical information based on various data from the first information and / or the second information, and generate a chart based on the numerical information.
[0114] According to various embodiments, the electronic device 101 can generate numerical information related to the capacity of the created package based on the first information, the second information, and / or the creation job information directory. For example, the electronic device 101 can confirm the capacity information of the created package corresponding to each creation job based on the second information. According to one embodiment, the electronic device 101 can confirm the capacity information of the package created by version based on the first information and the second information. For example, the electronic device 101 can confirm the capacity information of the created package corresponding to each of one or more creation jobs confirmed based on version identification information, and confirm the capacity of the package created by version. The capacity information of the package created by version can be confirmed corresponding to a specified period. The capacity information of the package created by version can be confirmed by summing all creation jobs performed by version, or by the average value based on the number of creations. According to the embodiment, the electronic device 101 can not only correspond to one or more creation operations confirmed based on version, but also to one or more creation operations confirmed based on task information, branch information, and / or operator information, and confirm the created package capacity information. The electronic device 101 can generate historical information related to the package capacity based on the package capacity information generated corresponding to the plurality of creation operations.
[0115] In this embodiment, the electronic device 101 can provide a required time chart 700, which visualizes numerical information related to the capacity of the created package. An example in Figure 7 could be a chart of the capacity of a package created by version. The electronic device 101 can determine the capacity information of the package created by version based on version identification information confirmed according to each item and the capacity information of the created package, and generate a chart of the required capacity of the created package by version. Referring to Figure 7, the horizontal axis of the required time chart 700 can be version information, and the vertical axis can be the average package capacity. The chart in Figure 7 is an example of a capacity information chart. The electronic device 101 can obtain numerical information based on various data from the first information and / or the second information, and generate a chart based on the numerical information.
[0116] In this embodiment, the electronic device 101 can confirm whether the creation operation is abnormal based on the required time information. The electronic device 101 can confirm the time consumed during the creation operation based on the creation request. The electronic device 101 can confirm the required time of the corresponding creation operation based on the second information. The electronic device 101 can confirm the required time information corresponding to other existing creation operations based on the creation operation information directory, such as historical information on the required time. The electronic device 101 can confirm whether the creation operation is abnormal based on the required time of the creation operation confirmed according to the second information and the historical information on the required time. For example, if the required time of the creation operation exceeds or does not reach the threshold specified for the required time of creation based on historical information, the electronic device 101 can confirm whether the creation operation is abnormal. For example, the creation operation is successful and generates a program package, but this is unrelated to whether the program package runs normally. In this case, if the required time is too short or too long, the created program package may be abnormal regardless of whether the creation is successful. Electronic device 101 can identify one or more operators corresponding to a creation job identified based on the creation job information directory, based on whether the identified creation job is abnormal. The operator device 102 corresponding to the identified operator provides information on whether the abnormality is detected. This abnormality information may include at least a portion of branch information, task information, submission information, and information displaying whether the abnormality is detected, all corresponding to the creation job. According to one embodiment, historical information on the required time for comparison with the performed creation job can be identified based on the creation job information directory. This historical information on required time can be generated based on creation time information corresponding to creation jobs different from the performed creation job. For example, it may include at least a portion of information on required time by version, progress information on required creation time, and information on required time for creation jobs performed within a specified period.
[0117] In this embodiment, the electronic device 101 can confirm whether the creation operation is abnormal based on package capacity information. The electronic device 101 can confirm the package capacity information at the time of the creation operation based on the creation request. The electronic device 101 can confirm the package capacity of the corresponding creation operation based on the second information. The electronic device 101 can confirm the package capacity information corresponding to other existing creation operations based on the creation operation information directory, such as historical package capacity information. The electronic device 101 can confirm whether the creation operation is abnormal based on the package capacity of the creation operation confirmed according to the second information and the historical package capacity information. For example, if the package capacity of the creation operation exceeds or falls below a threshold set based on historical information regarding the package capacity, the electronic device 101 can confirm that the creation operation is abnormal. For example, the creation operation may succeed and generate a package, but this is unrelated to whether the package runs normally. At this time, if the package size is too large or too small, the created package may be abnormal regardless of whether the creation is successful. Electronic device 101 can identify one or more operators corresponding to the creation operation identified based on the creation operation information directory, and the operator device 102 corresponding to the identified operator can provide information on whether the operation is abnormal. The information on whether the operation is abnormal may include at least a portion of the branch information, task information, submission information, and information displaying whether the operation is abnormal, all corresponding to the creation operation. According to one embodiment, historical information on the package size, which serves as a comparison object for the performed creation operation, can be identified based on the creation operation information directory. Historical information on package size can be generated based on the package size information corresponding to creation operations different from the performed creation operation. For example, it may include at least a portion of information on package size by version, progress information on package size creation, and information on package size of creation operations performed within a specified period. [Simplified Explanation of the Diagram]
[0030] Figure 1 is a diagram illustrating a code information providing system 100, which can implement methods for providing code-related information by electronic devices in various embodiments. Figure 2 is a diagram showing the configuration of electronic devices, operator devices, and servers in various embodiments. Figure 3 is a diagram showing the material structure of a case for providing code information in various embodiments. Figure 4 is a flowchart of the operation of electronic devices providing code-related information in various embodiments. Figure 5 is a diagram illustrating, exemplarily, a catalog of creation job information provided by electronic devices in various embodiments. Figure 6 is an example of numerical information related to creation job provided by electronic devices in various embodiments. Figure 7 is an example of numerical information related to creation job provided by electronic devices in various embodiments.
Claims
1. A method for providing code-related information, performed by an electronic device, comprising the following steps: obtaining information about a first creation operation from a server corresponding to the completion of a creation operation; confirming whether the first creation operation is abnormal based on at least one of historical information on the required time of one or more creation operations and historical information on the package capacity of one or more creation operations, and the information about the first creation operation; and providing the abnormality information to an operator device, wherein the abnormality of the first creation operation corresponds to at least one of an abnormality associated with the required time of the first creation operation and an abnormality associated with the package capacity of the first creation operation.
2. The method for providing code-related information as requested in Request 1, wherein the information regarding the first creation operation includes at least a portion of information about the result of the first creation operation, information about the capacity of the package generated by the server corresponding to the first creation operation, information about the version of the package corresponding to the first creation operation, and information about the time required corresponding to the first creation operation.
3. As in the method for providing code-related information in request item 2, the step of confirming whether the first creation job is abnormal includes the following steps: based on the historical information of the required time of more than one creation job, confirming the threshold value of the required time of the creation job; and based on the threshold value of the required time of the creation job and the required time information corresponding to the first creation job, confirming whether the first creation job is abnormal.
4. As in the method for providing code-related information in request item 3, the step of confirming whether the first creation job is abnormal includes the following steps: Based on the historical information of the required time of more than one creation job, confirm the threshold value of the required time of the creation job corresponding to the version information of the above package; and based on the threshold value of the required time of the creation job corresponding to the version information and the required time information corresponding to the first creation job, confirm whether the first creation job is abnormal.
5. As in the method for providing code-related information in request item 2, the step of confirming whether the first creation job is abnormal includes the following steps: based on the historical information of the package capacity of one or more creation jobs, confirming the threshold value of the package capacity; and based on the threshold value of the package capacity and the capacity information of the package generated by the server to correspond to the first creation job, confirming whether the first creation job is abnormal.
6. As in the method for providing code-related information in request item 5, the step of confirming whether the first creation job is abnormal includes the following steps: based on the historical information of the package capacity of one or more creation jobs, confirming the threshold value of the package capacity corresponding to the version information of the package; and based on the threshold value of the package capacity corresponding to the version information of the package and the capacity information of the package generated by the server for the first creation job, confirming whether the first creation job is abnormal.
7. The method for providing code-related information as requested in claim 2, wherein the first creation job is associated with the first code, and wherein the information regarding the first creation job further includes at least a portion of the following: information on the operator requesting the first creation job from the server, branch identification information corresponding to the first code, submission information corresponding to the first code, and task identification information corresponding to the first code.
8. The method for providing code-related information as requested in item 7 further includes the following steps: providing information on one or more tasks, the information on one or more tasks being confirmed based on the aforementioned branch identification information and corresponding to the branch corresponding to the aforementioned first code.
9. The method for providing code-related information as requested in item 7 further includes the following steps: providing information on one or more branches, the information on one or more branches being confirmed based on the task identification information and corresponding to the task corresponding to the first code.
10. The method for providing code-related information as requested in item 7 further includes the following steps: providing task status information related to the progress status of a task, the task corresponding to the first code identified based on the task identification information.
11. An electronic device comprising: Memory; A transceiver; and a processor; the processor is configured to: obtain information about the first establishment job from the server in response to the completion of the establishment job; determine whether the first establishment job is abnormal based on at least one of historical information on the required time of one or more establishment jobs and historical information on the package capacity of one or more establishment jobs, and the information about the first establishment job; and provide the abnormality information to the operator's device, wherein the abnormality of the first establishment job corresponds to at least one of the abnormality associated with the required time of the first establishment job and the abnormality associated with the package capacity of the first establishment job.
12. A non-transitory computer-readable recording medium recording a program for performing the method as described in claim 1 on a computer.
Citation Information
Patent Citations
Software test support device and software test support program
JP2016076162A
Program development support system and program development support method
JP2021105866A
Program managing device and program managing method
JP2022108452A
Quick predictor override method and micro processor
TW202217575A
