WO2024038951A1

WO2024038951A1 - Method for providing code information and electronic device for supporting same

Info

Publication number: WO2024038951A1
Application number: PCT/KR2022/015077
Authority: WO
Inventors: 리우한란
Original assignee: 쿠팡 주식회사
Priority date: 2022-08-17
Filing date: 2022-10-07
Publication date: 2024-02-22
Also published as: KR20240024573A

Abstract

Disclosed is a method for an electronic device to provide code-related information, the method comprising the steps of: acquiring first information from a server in response to the initiation of a build operation pertaining to first code information and performed on the server, the first information including information about the build operation and branch information corresponding to the first code information; acquiring second information, including at least information about the result of the build operation, from the server in response to the completion of the build operation; and providing, to an operator device, a build operation information list including a first item generated on the basis of the first information and the second information.

Description

Methods for providing code information and electronic devices that support them

The present 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 an operator.

Since the Fourth Industrial Revolution, the next-generation industrial revolution achieved through the convergence of information and communication technologies, has emerged as a key topic, the importance of software technology has emerged. Software technology can be used in a variety of fields such as ubiquitous computing, Internet of Things, self-driving cars, artificial intelligence, robots, and blockchain, and the trend of implementing software products by reflecting market goals and user needs has led to a large number of developers. Development projects involving people are flourishing.

Development projects involving multiple developers merge the results of tasks assigned to each individual developer to complete one project. However, if the scale of the development project is large, problems may occur when merging the source code worked by each developer into the project, such as the source code worked by different developers causing conflicts or build failure during the merging process. In this case, it is difficult to identify which developer's source code caused the problem. Various methods are being proposed to systematically improve the productivity of projects by multiple developers.

In relation to this, prior documents such as KR1020210147354A and KR1020210090575A may be referred to.

The purpose of the present disclosure is to provide an electronic device and method for providing code information to an operator in order to solve the above-mentioned problems.

Specifically, in the process of work related to a project performed by multiple workers, each worker modifies and updates the code related to the project in his or her own branch. As a result, multiple workers work on the same project. The purpose is to provide a method and electronic device that can systematically track changes that occur as code is modified.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below. You will be able to.

Various embodiments may provide a method of providing code-related information and an electronic device that supports the same.

A method of providing code-related information of an electronic device according to various embodiments disclosed in this document includes, in response to the start of a build task related to first code information performed on a server, the build task from the server. Obtaining first information including information about and branch information corresponding to the first code information; Obtaining second information including at least information about the result of the build task from the server in response to the end of the build task; And it may include providing a build task information list including a first item generated based on the first information and the second information to the worker device.

In an embodiment, the first information includes worker information that requested the build task to the server, branch identification information corresponding to the first code information, commit information corresponding to the first code information, and the It may further include at least some of the task identification information corresponding to the first code information.

In an embodiment, 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.

In an embodiment, the method of providing code-related information may further include providing information about one or more tasks corresponding to a branch corresponding to the first code information, identified based on the branch identification information. there is.

In an embodiment, the method of providing code-related information may further include providing information about one or more branches corresponding to a task corresponding to the first code information, identified based on the task identification information. there is.

In an embodiment, the second information includes at least some of capacity information of the package generated by the server in response to the build task, version information of the package corresponding to the build task, and time required information corresponding to the build task. It can be included.

In an embodiment, the method of providing code-related information is based on the time required information confirmed based on the second information and information about the time required for one or more build tasks confirmed based on the build task information list. Checking whether the build task is abnormal; And it may further include providing information about whether the build is abnormal to the one or more workers based on information about one or more workers confirmed based on the branch information and information about whether the build is abnormal.

In an embodiment, the method of providing code-related information may include, based on time required information corresponding to each of a plurality of build tasks and version information of a package corresponding to each of the plurality of build tasks, the build time required for each version information. Obtain information about the build time corresponding to each version information and whether the build operation related to the first code information is abnormal based on the time information confirmed based on the second information. Additional confirmation steps may be included.

In an embodiment, the method of providing the code-related information includes the build based on the capacity information of the package for one or more build tasks identified based on the capacity information confirmed based on the second information and the build task information list. Checking whether the operation is abnormal; And it may further include providing information about whether the build is abnormal to the one or more workers based on information about one or more workers confirmed based on the branch information and information about whether the build is abnormal.

In an embodiment, the method of providing code-related information includes information about capacity corresponding to each version information, based on capacity information corresponding to each of a plurality of build tasks and version information of a package corresponding to each of the plurality of build tasks. Obtaining and confirming whether there is an abnormality in the build operation related to the first code information based on the capacity information corresponding to each version information and the capacity information confirmed based on the second information. can do.

In an embodiment, the method of providing code-related information may further include providing one or more worker information identified based on the branch information.

In an embodiment, the method of providing code-related information may include sending a result message that includes at least part of the second information and at least information about a result of the build operation, and one or more branches identified based on the branch information. The step of providing worker information to a corresponding worker device may be further included.

In an embodiment, the method of providing code-related information may further include providing task status information regarding the progress status of a task corresponding to the first code information identified based on the task identification information.

In an embodiment, the method of providing code-related information may further include providing the first code information to the worker device in response to a request for code information corresponding to the first item received from the worker device.

In an embodiment, the first item includes path information about code information of a package generated by a server in response to the build task and including at least the first code information, and the method of providing code-related information includes: Based on the path information, the method may further include providing code information of the package to the worker device.

In an embodiment, the method for providing code-related information includes obtaining branch identification information and one or more worker information; And it may further include generating a branch list including branch information mapping the branch identification information and the one or more worker information based on a request received from a worker device.

In an embodiment, the code information of the package generated by the server in response to the build task and including at least the first code information is source code for performing an A/B test in response to the code information of the generated package. Including, the method of providing code-related information may further include providing result information of the A/B test confirmed based on the first information.

An electronic device according to various embodiments disclosed in this document includes a memory; transceiver; and a processor, wherein the processor receives information about the build task and the first code information from the server in response to the start of a build task related to the first code information, which is performed on the server. Obtain first information including branch information corresponding to, obtain second information including at least information about the result of the build task from the server in response to completion of the build task, and obtain the first information including information about the result of the build task. It may be set to provide a build work information list including information and a first item generated based on the second information to the worker device.

According to the method of the present invention, the method and electronic device for providing code-related information confirm the information related to the build task for a plurality of program codes related to the project and provide this to the operator, thereby notifying the status of the build task. This can improve project productivity.

In addition, the electronic device and method for providing code information according to the present disclosure can intuitively provide information on the project progress to the worker by providing the worker with the status of work related to the project.

The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art from the description below. will be.

FIG. 1 is a diagram illustrating a code-related information providing system 100 in which a method of providing code-related information by an electronic device according to various embodiments of the present invention can be implemented.

FIG. 2 is a diagram illustrating the configuration of an electronic device, an operator device, and a server according to various embodiments.

Figure 3 is a diagram showing the data structure of a project in which code information is provided according to various embodiments.

FIG. 4 is a flowchart of an operation in which an electronic device provides code-related information according to various embodiments.

FIG. 5 exemplarily illustrates a list of build task information provided by an electronic device according to various embodiments.

FIG. 6 is an example of numerical information related to a build task provided by an electronic device according to various embodiments.

FIG. 7 is an example of numerical information related to a build task provided by an electronic device according to various embodiments.

The following embodiments combine components and features of various embodiments in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form that is not combined with other components or features. Additionally, various embodiments may be configured by combining some components and features. The order of operations described in various embodiments may change. Some features or features of one embodiment may be included in another embodiment or may be replaced with corresponding features or features of another embodiment.

In the description of the drawings, procedures or steps that may obscure the gist of the various embodiments are not described, and procedures or steps that can be understood at the level of a person with ordinary knowledge in the relevant technical field are not described. did.

Throughout the specification, when a part is said to “comprise or include” a certain element, this means that it does not exclude other elements but may further include other elements, unless specifically stated to the contrary. do. In addition, terms such as "... unit", "... unit", and "module" used in the specification refer to a unit that processes at least one function or operation, which refers to hardware, software, or a combination of hardware and software. It can be implemented as: Additionally, the terms “a or an,” “one,” “the,” and similar related terms are used herein in the context of describing various embodiments (particularly in the context of the claims below). Unless otherwise indicated or clearly contradicted by context, it may be used in both singular and plural terms.

Hereinafter, preferred embodiments according to various embodiments will be described in detail with reference to the attached drawings. The detailed description set forth below in conjunction with the accompanying drawings is intended to describe exemplary embodiments of various embodiments and is not intended to represent the only embodiment.

Additionally, specific terms used in various embodiments are provided to aid understanding of the various embodiments, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the various embodiments.

At this time, it will be understood that each block of the processing flow diagram diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on the corresponding function.

FIG. 1 is a diagram illustrating a code information providing system 100 in which a method of providing code-related information by an electronic device according to various embodiments of the present invention can be implemented.

Referring to FIG. 1, a code information providing system 100 according to various embodiments may be implemented in various types of devices. For example, the code information providing system 100 may be implemented in the electronic device 101, the operator device 102, and the server 103. In other words, the electronic device 101, the operator device 102, and the server 103 can perform operations according to various embodiments of the present disclosure based on the code information providing system 100 implemented in each device. there is. Meanwhile, the code information providing system 100 according to various embodiments is not limited to what is shown in FIG. 1, and may be implemented in a wider variety of electronic devices and servers.

The electronic device 101 according to various embodiments includes one or more worker devices 102 (e.g., a first worker device 102_1, a second worker device 102_2, etc., an nth worker device 102_n), and/ Alternatively, it may be a device that performs wireless and wired communication with the server 103 and includes storage with a large storage capacity. For example, the electronic device 101 may be a cloud device connected to one or more worker devices 102 and/or servers 103.

The worker device 102 according to various embodiments may be a device that can be used by an individual user, such as a desktop PC, tablet PC, or mobile terminal. In addition, other electronic devices that perform similar functions may be used as the operator device 102.

The server 103 according to various embodiments may include one or more worker devices 102 (e.g., a first worker device 102_1, a second worker device 102_2, etc., an nth worker device 102_n), and/or It may be a device that performs wireless and wired communication with the electronic device 101 and includes storage with a large storage capacity. For example, the electronic device 101 may be one or more worker devices 102 and/or a cloud device connected to the electronic device 101.

The code information providing system 100 according to various embodiments may include various modules for operation. The modules included in the code information providing system 100 enable the physical device (e.g., electronic device 101) on which the code information providing system 100 is implemented (or included in the physical device) to perform a specified operation. It may be implemented computer code or one or more instructions. In other words, the physical device in which the code information providing system 100 is implemented stores a plurality of modules in a memory in the form of computer code, and when the plurality of modules stored in the memory are executed, the physical device is a plurality of modules. It is possible to perform designated operations corresponding to .

Depending on the embodiment, the code information providing system 100 further includes a network network supporting information transmission and reception between at least some of the electronic device 101, the server 103, one or more worker devices 102, and other external devices. can do.

Meanwhile, throughout the embodiment, the electronic device 101, the one or more worker devices 102, and the server 103 are referred to as separate devices and servers, but this may be a logically divided structure, and may be separated from one device or server. It can be implemented by the provided function. For example, at least some of the worker device 102 and the server 103 may be included in the electronic device 101 or may be combined with the electronic device 101 to form an integrated unit. However, even in this case, the method of providing a series of code information performed by transmitting and receiving data between the electronic device 101, the operator device 102, and the server 103 can be performed similarly. In the case of a device included in or integrated with the electronic device 101, communication with the electronic device 101 may occur within the device and between its components (e.g., the processor of the electronic device 101). Wow) It can be understood as a process of exchanging data.

Hereinafter, for convenience of explanation, embodiments in which the worker device 102 and the server 103 exist as a separate device or server from the electronic device 101 will be described. However, the following description describes the worker device 102 and the server ( 103) may be applied mutatis mutandis even when at least some of them are included in the electronic device 101 or are combined with the electronic device 101 to form an integrated unit.

According to one embodiment, the electronic device 101, the operator device 102, and the server 103 may include a plurality of computer systems or computer software implemented as network servers. For example, at least some of the electronic device 101, worker device 102, and server 103 are connected to subordinate devices that can communicate with other network servers through a computer network such as an intranet or the Internet to request task performance. It can refer to computer systems and computer software that receive data, perform work on it, and provide performance results. In addition, at least some of the electronic device 101, operator device 102, and server 103 are understood as a broad concept that includes a series of application programs that can operate on a network server and various databases built therein. It can be. For example, at least some of the electronic device 101, worker device 102, and server 103 may run DOS, Windows, Linux, UNIX, or MacOS. It can be implemented using various network server programs provided depending on the operating system.

Referring to FIG. 2, the electronic device 101, one or more operator devices 102, and the server 103 may include an input/output unit 210, a communication unit 220, a storage 230, and a processor 240. You can.

The input/output unit 210 may be various interfaces or connection ports that receive user input or output 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 can take various forms, including key input, touch input, and voice input. Examples of input modules that can receive such user input include traditional keypads, keyboards, and mice, as well as touch sensors that detect the user's touch, microphones that receive voice signals, cameras that recognize gestures through image recognition, etc. A proximity sensor including at least one of an illumination sensor or an infrared sensor that detects user approach, a motion sensor that recognizes user movement through an acceleration sensor or gyro sensor, and various other types of sensors that detect or receive user input. There is an input means, and the input module according to an embodiment of the present disclosure may include at least one of the devices listed above. Here, the touch sensor may be implemented as a piezoelectric or capacitive touch sensor that detects touch through a touch panel or touch film attached to the display panel, or an optical touch sensor that detects touch by an optical method. In addition, the input module may be implemented in the form of an input interface (USB port, PS/2 port, etc.) that connects an external input device that receives user input instead of a device that detects user input itself. Additionally, the output module can output various information. The output module may include at least one of a display that outputs an image, a speaker that outputs sound, a haptic device that generates vibration, and various other types of output means. In addition, the output module may be implemented in the form of a port-type output interface that connects the individual output means described above.

As an example, a display-type output module can display text, still images, and moving images. Displays include liquid crystal display (LCD), light emitting diode (LED) display, organic light emitting diode (OLED) display, flat panel display (FPD), and transparent display. Among various types of devices that can perform image output functions such as display, curved display, flexible display, 3D display, holographic display, projector, and other It can contain at least one. This display may be in the form of a touch display integrated with the touch sensor of the input module.

The communication unit 220 can communicate with other devices. Accordingly, the electronic device 101, the operator device 102, and the server 103 can transmit and receive information with other devices through the communication unit. For example, the electronic device 101, the operator device 102, and the server 103 may communicate with each other or with other devices using a communication unit.

Here, communication, that is, transmission and reception of data, can be accomplished wired or wirelessly. To this end, the communication department includes a wired communication module that connects to the Internet, etc. through a LAN (Local Area Network), a mobile communication module that transmits and receives data by connecting to a mobile communication network through a mobile communication base station, and a WLAN (Wireless Local Area Network) such as Wi-Fi. A short-distance communication module using an Area Network-type communication method or a WPAN (Wireless Personal Area Network)-type communication method such as Bluetooth or Zigbee, and a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System) ) may be composed of a satellite communication module using a satellite communication module or a combination thereof.

Storage 230 can store various types of information. Storage can store data temporarily or semi-permanently. For example, the storage of the electronic device 101 includes an operating program (OS: Operating System) for driving the electronic device 101, a program for generating data or Braille for hosting a website, or an application (e.g., Data related to web applications) may be stored. Additionally, the storage may store modules in the form of computer code as described above.

Examples of storage 230 include hard disk drive (HDD), solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This can be. This storage can be provided as a built-in or detachable type.

The processor 240 controls the overall operation of the electronic device 101, operator device 102, and server 103. To this end, the processor 240 can perform computation and processing of various information and control the operation of components of the electronic device 101. For example, the processor 240 may execute a program or application to provide code-related information. The processor 240 may be implemented as a computer or similar device using hardware, software, or a combination thereof. In hardware, the processor 240 may be implemented in the form of an electronic circuit that processes electrical signals to perform a control function, and in software, it may be implemented in the form of a program that drives the hardware processor 240. Meanwhile, unless otherwise specified in the following description, the operations of the electronic device 101, operator device 102, and server 103 may be interpreted as being performed under the control of the processor 240. That is, when the modules implemented in the above-described code information providing system 100 are executed, the modules enable the processor 240 to perform the following operations on the electronic device 101, the operator device 102, and the server 103. It can be interpreted as controlling.

In summary, various embodiments may be implemented through various means. For example, various embodiments may be implemented by hardware, firmware, software, or a combination thereof.

In the case of hardware implementation, methods according to various embodiments include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and FPGAs ( It can be implemented by field programmable gate arrays, processors, controllers, microcontrollers, microprocessors, etc.

In the case of implementation by firmware or software, methods according to various embodiments may be implemented in the form of modules, procedures, or functions that perform the functions or operations described below. For example, software code can be stored in memory and run by a processor. The memory may be located inside or outside the processor, and may exchange data with the processor through various known means.

Below, various embodiments will be described in more detail based on the above technical idea. The contents described above may be applied to various embodiments described below. For example, operations, functions, terms, etc. that are not defined in various embodiments described below may be performed and explained based on the contents described above.

In the following description, various embodiments are described on the premise that the electronic device 101 performs an operation of providing code-related information. According to various embodiments, the electronic device 101 performs an operation of providing code information. Information may be transmitted to and received from operator device 102 and/or server 103.

FIG. 3 is a diagram illustrating the data structure 30 of the project 300 in which code information is provided according to various embodiments disclosed in this document. Referring to FIG. 3, from one project 300, a master branch (MB), a development branch (DB), a first feature branch (FB1), and a second feature branch ( FB2) can be derived. However, the data structure 30 shown in FIG. 3 is only an example to aid understanding of the present disclosure, and does not limit the data structure 30 in which code information is provided according to an embodiment of the present disclosure, and the data structure ( 30) can be adaptively built according to the goals of the project 300.

The master branch (MB) may be a branch for managing release history related to the project 300 and may manage a set of files in a deployable state. 3 shows a master branch (MB) including a first master file set 310 and a second master file set 320, and the first program or second master constructed from the first master file set 310 A second program built from file set 320 may be distributed, and the second program may be another version of the first program. Each of the plurality of files included in the first master file set 310 and the second master file set 320 is committed to the server 103 by the first to nth worker devices 102_1, 102_2, ..., 102_n. It may be a (committed) file.

The development branch (DB) may be a branch for merging branches for developing various functions related to the project 300. If the set of files associated with the development branch (DB) contains all features related to the program to be deployed, bugs have been fixed and it is in a stable state ready for deployment, the development branch (DB) can be merged into the master branch (MB). . Each of the first to third development file sets 311, 312, and 313 of FIG. 3 may include a plurality of files for developing various functions related to the program corresponding to the second master file set 320, embodiments. In, the second development file set 312 may be a set of files from the first development file set 311, the third development file set 313 may be an updated version of the second development file set 312, or the first development file set 311 may be a set of files from the first development file set 311. Each of the to third development file sets 311, 312, and 313 may be a file set for implementing independent functions related to the program corresponding to the second master file set 320. Each of the plurality of files included in each of the first to third development file sets (311, 312, 313) is committed to the server 103 by the first to nth worker devices (102_1, 102_2, ..., 102_n). It could be a file.

The first feature branch (FB1) and the second feature branch (FB2) may be branches branched from the development branch (DB) to develop new functions and fix bugs related to the project 300. When work related to the first feature branch (FB1) and the second feature branch (FB2) is completed, the file sets related to the first feature branch (FB1) and the second feature branch (FB2) are merged into the development branch (DB). It can be. 3 shows that work related to the second feature branch (FB2) is completed, and at least one of the 2-1 feature file set (312_1) and the 2-2 feature file set (312_2) is merged into the development branch (DB). , shows the data structure 30 when work related to the first feature branch (FB1) is in progress.

In addition, the data structure 30 of the project 300 according to the embodiment of the present disclosure includes a release branch branching from the development branch (DB) and urgent modifications to the distributed product version in order to prepare the product release version. When this occurs, at least one of hotfix branches branching from the master branch (MB) may be further included to handle this. The branch information referred to in this specification may be information corresponding to at least one of a master branch (MB), development branch (DB), feature branch (FB1, FB2), distribution branch, and hotfix branch related to the project 300, Branch information may include information about a set of files related to the branch. Additionally, file information referred to in this specification may include code information about at least one file included in the file set, and the file information may include information about program code related to the file.

Meanwhile, in an embodiment, each file set may be merged into the master branch (MB) based on a request from the worker device 102. For example, in response to the file set being committed to the server 103 by the worker device 102, the server 103 may merge the committed file set into the master branch (MB) and proceed with build. The build task may include packaging and distributing files for one or more source codes. Packaging may include the operation of creating one package of output data that includes at least a set of committed files. The worker device 102 completes and commits work on a set of files and, in response, sends a build request to the server 103, and the server 103 performs a build task corresponding to that set of files to build the package. can be created. The server 103 may perform a push operation based on commit information. A push operation may mean saving added file information or edited file information to a remote storage (e.g., server 103). Server 103 may be a development server or continuous integration (CI) server. For example, the server 103 may continuously build and distribute code information pushed from each of the one or more worker devices 102 as each push is made. The server 103 may perform a build task in response to the pushed file. For example, with respect to the first development file set 311, when the worker device 102 commits, the server 103 performs a build operation corresponding to the pushed file set at the same time as the commit, thereby creating the first development file set 311 A first package (P1) corresponding to can be created. As another example, for the 2-2 development file set 311, when the worker device 102 commits the 2-2 feature file set 312_2 to the server 103, the server 103 commits the commit and At the same time, a build operation may be performed to generate a second package (P2) corresponding to the 2-2 feature file set (312_2). In an embodiment, the first package (P1) and the second package (P2) are identified as the same version as the first program built from the first master file set 310, so that the first package (P1) and the second package ( P2) may be assigned the same identification number as the version of the first program, and may be identified as a different version from the second program constructed from the second master file set 320. The server 103 can distribute the built package. Each continuously built package (e.g., first package (P1), second package (P2)) before and after a version update may be subject to alpha-test and/or beta-test. The electronic device 101, worker device 102, server 103, and/or other external electronic devices may perform alpha testing and beta testing for each package, and the electronic device 101 may perform alpha testing. and beta test result information can be obtained.

In an embodiment, each branch may correspond to one or more tasks. A task can be understood as a conceptual/functional development unit. As a unit of development for one or more functional components included in the project 300, each task may correspond to one or more branches. For example, the first task (T1) may include a task related to the shopping cart function, and the second task (T2) may include a task related to the payment 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). May include source code. Each task may be assigned corresponding identification information, and the electronic device 101 may check information about the status of the task based on the identification information of the task. For example, the electronic device 101 may check progress information for each subtask included in the task, or may check information about the status of the task based on status information of one or more branches corresponding to the task. The electronic device 101 can check information about the branch corresponding to the task based on the task information, and conversely, it can check information about the task corresponding to the branch based on each branch information. In an embodiment, when worker device 102 commits a set of files, it may transmit commit information that includes at least part of a commit message to server 103, wherein the commit information includes information about the task corresponding to the file set. It can be included. These development and code structural units may have different structures depending on the operator.

According to various embodiments, one or more worker devices 102 may forward a build request to the server 103 (41). Worker device 102 may commit a set of files to server 103, and server 103 may merge the committed set of files into the master branch (MB), creating a package corresponding to the set of committed files. there is. In an embodiment, a build request may include a set of files that the worker device 102 sends to the server 103 and a commit request. The set of files that worker device 102 commits may include one or more code information. A commit request may include a commit message corresponding to the fileset. The commit message may be generated by the worker device 102 of the worker requesting the commit. In an embodiment, the commit message may be written by the worker device 102 and transmitted to the server 103, and the electronic device 101 may obtain the commit message from the server.

According to various embodiments, the server 103 may initiate a build task for the committed file set (42). The build task may include a packaging task that merges a set of committed files to create a single package.

According to various embodiments, the electronic device 101 may obtain first information from the server 103 in response to the start of the build task (42) of the server 103 (S401). In an embodiment, the first information may include information related to code information (eg, file set). The first information may include information that can be obtained immediately after the code information is pushed to the server 103. The first information may include one or more meta information related to code information that is the target of the build. For example, the first information may include at least some of information about the date and time when the build was requested, task information corresponding to code information, branch information, version information, and commit information.

In an embodiment, the task information may include at least part of identification information of the task corresponding to the code information and information about the progress of the task. According to one embodiment, each task may correspond to one or more branches. The electronic device 101 and/or the server 103 can store correspondence information about the branch corresponding to each task, or check the correspondence relationship between tasks and branches based on correspondence information between tasks and branches stored in an external electronic device. there is. The electronic device 101 may check information on the branch corresponding to the task based on the identification information of the task.

In an embodiment, the branch information may include identification information of the branch corresponding to the code information. Each branch may correspond to one or more tasks. The electronic device 101 and/or the server 103 can store correspondence information about the branch corresponding to each task, or check the correspondence relationship between tasks and branches based on correspondence information between tasks and branches stored in an external electronic device. there is. The electronic device 101 may check information on the branch corresponding to the task based on the branch identification information. According to one embodiment, each branch information may include worker information corresponding to the branch. Each branch may be assigned one or more workers, and correspondence information between branches and workers may be stored in the electronic device 101, the server 103, or other external devices. The electronic device 101 may check information on one or more workers corresponding to the branch based on the branch identification information. The worker information may include at least some of the following: identification information about the worker, information about the worker device 102 corresponding to the worker, contact information about the worker, branch information corresponding to the worker, and task information corresponding to the worker. In an embodiment, the electronic device 101 may check the worker corresponding to the branch information based on the branch information and check task information corresponding to the worker. In an embodiment, the electronic device 101 may check one or more task information corresponding to a branch based on branch information and may check worker information corresponding to a task based on information on one or more tasks. In an embodiment, the electronic device 101 may check one or more branch information corresponding to a task based on task information and check worker information corresponding to the branch information based on one or more branch information.

In an embodiment, the commit information may include at least some of a commit message, information about a commit operation, information about a set of committed files (code information), and identification information related to a set of committed files. For example, commit information may include task information corresponding to committed code information. In embodiments, identification information regarding a set of committed files may include information regarding code information created, modified, altered, or created by an operator in the set of files. For example, information about source code may include location information in a file set of code information that has been created, modified, changed, or created, and/or information about major creation history. In embodiments, the commit information may include identification information corresponding to the commit operation. For example, when the worker device 102 commits code information, the worker device 102 or the server 103 may generate and/or assign identification information for the commit task.

In an embodiment, the server 103 may provide first information to the electronic device 101 in response to the start of the build task 42 and proceed with the build task corresponding to the code information pushed at the same time or at the same time.

According to various embodiments, the server 103 may terminate the build task (43). Termination of a build task may include build failure or build success. The server 103 may check whether the build was successful in response to the end of the build task (43). The server 103 may create a package corresponding to the pushed code information when the build is successful.

According to various embodiments, the electronic device 101 may obtain second information from the server 103 in response to the end of the build task (43) (S402). The second information may include information that can be generated by the server 103 or acquired by the electronic device 101 in response to the end of the build task. In an embodiment, the second information may include information related to the results of the build operation. For example, the second information may include at least some of information about whether the build was successful, information about the date and time the build was completed, build time, and capacity information of the built package. In an embodiment, the server 103 may provide second information to the electronic device 101 in response to the end of the build task (43).

According to various embodiments, the electronic device 101 may generate a first item. The first item may mean one item included in the build task information list. The build task information list may include one or more pieces of information related to the build task that are generated from at least part of the first information and second information or a combination thereof, corresponding to each build task. According to one embodiment, the first item included in the build task information list is branch information corresponding to the pushed code information, worker information, commit information, information on whether the build was successful, task information, version information, and package capacity information. It may include at least some of them. The electronic device 101 may generate the first item based on the first information and the second information.

Meanwhile, in an embodiment, the first information or the second information may include a request for creating the first item. The electronic device 101 may obtain first information and second information from the server 103 in response to the start or end of a build operation of the server 103, and at this time, the first information or the second information may include the first item. Requests for creation may be included. For example, while starting a build job (43), the server 103 may transmit a request to create a first item in response to the build job to be started to the electronic device 101. At this time, the electronic device 101 may generate the first item based on the request for generating the first item included in the first information (S403). At this time, in response to obtaining the second information from the server 103, the electronic device 101 may allocate data confirmed based on the first information and the second information to the first item.

According to various embodiments, the electronic device 101 may provide a list of build task information to the worker device 102 (S405). The electronic device 101 may provide a build task information list including the generated first item to the worker device 102. The build task information list may include one or more items generated based on one or more build requests. In an embodiment, the build task information list may include a page format, and the electronic device 101 may display code-related information confirmed or generated based on the first information and the second information through the build task information list page to the worker device. It can be provided at (102).

According to various embodiments, the electronic device 101 may receive a package code information request from the operator device 102. A package code information request may include a request for provision of the source code of the package. According to one embodiment, the first item may include path information regarding code information of a package that includes at least code information corresponding to the first item. Path information may include URL information. The external electronic device 102 can check path information based on the first item and request package code information from the electronic device 101 based on the path information. The electronic device 101 may provide code information about the package to the operator device 102 based on a request for package code information.

In embodiments, server 103 and/or electronic device 101 may provide operator device 102 with information regarding the results of a build operation. In one embodiment, the server 103 and/or the electronic device 101 may provide a result message containing at least information about the result of the build task to the operator device 102. The server 103 and/or the electronic device 101 may check worker information corresponding to the code information requested to build and provide a result message to the worker device 102 based on the confirmed worker information. The electronic device 101 can check the information of the worker corresponding to the branch based on the first information and provide a result message to the worker device 102 corresponding to the branch based on the worker information. The result message may include at least information about whether the build task succeeded or failed, and may include information about the operator who requested the build. In embodiments, the resulting message may include information about the first item. For example, the result message may include at least a portion of first information and/or second information corresponding to the first item. The resulting message may include information about the access path to the first item. For example, the access path may mean an access path to a resource (eg, storage) of the electronic device 101 in order for the worker device 102 to check the first item from the electronic device 101. Information about the access path may include, for example, URL (user resource location) information.

Meanwhile, in an embodiment, the electronic device 101 may register information about a new branch. For example, when a worker creates a new branch, information about the branch may be registered in the electronic device 101. The electronic device 101 may receive at least some of branch identification information corresponding to the new branch, task information corresponding to the branch, and worker information corresponding to the branch from the worker device 102. In response to the worker request for branch registration received from the worker device 102, the electronic device 101 creates a branch list including mapping information that maps worker information and/or task information corresponding to the branch to branch identification information. can be created.

Meanwhile, in an embodiment, the electronic device 101 may register information about a new task. For example, when a worker creates a new task, information about the task may be registered in the electronic device 101. The electronic device 101 may receive at least some 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 from the worker device 102. In response to the worker request for task registration received from the worker device 102, the electronic device 101 creates a task list including mapping information that maps worker information and/or branch information corresponding to the task to task identification information. can be created.

Meanwhile, in an embodiment, the electronic device 101 may perform an A/B test (alpha/beta test) on a package generated based on a build task. A/B testing differs between the set of users who will distribute the program built based on the built package and the set of users who will distribute the program being compared (e.g., previous version of the program), and determines the use of the program by each set of users. It may include a series of operations of comparing usage information acquired by the electronic device 101 and generating test result information based on the usage information. According to one embodiment, the code information of the built package may include source code related to A/B testing at least in part. The source code for A/B testing is the operation of distinguishing between the user set to which the distributed package is applied and the non-user set (the user set may be further divided into two), and collecting result information corresponding to each of the different user sets. It may include instructions related to operations and operations to compare each result information. The electronic device 101 can check the A/B test result information of the build task based on the first information corresponding to the specific build task and provide the A/B test result information to the worker device 102. You can.

Referring to FIG. 5 , the electronic device 101 may provide a build task information list 500 to the operator device 102. The build task information list 500 may include one or more items, such as a first item 510, a second item 520, a third item 530, and a fourth item 540. Each item may be an item created by the electronic device 101 in response to a build task requested from the worker 102 and performed in the server 103. For example, the first item 510 is an item created based on a build request corresponding to first code information, and the second item 520 is an item created based on a build request corresponding to second code information. The third item 530 may be an item created based on a build request corresponding to third code information, and the fourth item 540 may be an item created based on a build request corresponding to fourth code information. The electronic device 101 may generate each item to be included in the build task information list 500 based on the first information and the second information. For example, the electronic device 101 generates the first item 510 based on the first information and second information corresponding to the first code information, and based on the first information and second information corresponding to the second code information. The second item 520 is generated, the third item 530 is generated based on the first and second information corresponding to the third code information, and the first and second items corresponding to the fourth code information are generated. The fourth item 540 can be created based on the second information.

In an embodiment, each item included in the build task information list 500 may include at least a portion of the first information and the second information and/or a combination thereof. Referring to FIG. 5, each item includes a date information (Date) section, a name information (Name/ID) section, a worker information (Dev) section, and a branch in relation to the build task corresponding to the build requested code information. At least part of the information (Branch) column, commit information (Last commit) column, status information (Status) column regarding whether the build was successful, task information (BTS) column, version information (Version) column, and package capacity information (Size) column. may include.

The date information (Date) column may include information about the date and time when the build task was requested or the date and time when the build task was completed, corresponding to each code information. The electronic device 101 may generate data in the time information column based on the first information or second information obtained from the server 103.

The name information (Name/ID) field may include the name of the project 200 or name information or identification information of a program or application built based on the project 200.

The worker information (Dev) field may include information about the worker who committed the code information corresponding to each item. The worker information (Dev) field may include at least some of identification information about the worker, information about the worker device 102 corresponding to the worker, contact information of the worker, branch information corresponding to the worker, and task information corresponding to the worker. You can. In an embodiment, the worker information (Dev) field may include the worker's identification information. For example, the electronic device 101 checks the worker identification information corresponding to the first code information based on the worker information (Dev) in the first item 510, and provides the worker's contact information and worker information based on the worker identification information. You can check information about the corresponding branch or task.

In an embodiment, the build task information list 500 may include a user interface (e.g., link) corresponding to a worker information (Dev) column for each item, and the electronic device 101 may include a user interface corresponding to the worker information column. Worker information can be provided through . For example, in the example of the first item 510, the electronic device 101 displays the worker's identification information (presto) in the worker column corresponding to the first code information, and displays the worker's identification information in a link containing a hyperlink. It can be provided as a user interface. The electronic device 101 may generate data in the worker information column based on the first information obtained from the server 103.

The branch information (Branch) column may include information about the branch. The branch information (Branch) column may include information about the branch corresponding to the committed code information corresponding to each item. The branch information (Branch) column may include at least some of identification information about the branch, information about code corresponding to the branch, worker information about one or more workers corresponding to the branch, and task information corresponding to the branch. In an embodiment, the branch information (Branch) field may include identification information of the branch. For example, the electronic device 101 checks the branch identification information corresponding to the first code information based on the branch information (Branch) in the first item 510, and determines the worker information corresponding to the branch based on the branch identification information and /Or you can check task information corresponding to the branch.

In an embodiment, the build task information list 500 may include a user interface (e.g., link) corresponding to a branch information column for each item, and the electronic device 101 may include a user interface corresponding to the branch information column. Branch information can be provided through . For example, in the example of the first item 510, the electronic device 101 displays branch identification information in the branch column corresponding to the first code information, and uses the branch identification information as a user interface including a hyperlink. can be provided. The electronic device 101 may generate data in the branch information column based on the first information obtained from the server 103.

The commit information (Last commit) column may include information about the commit. The commit information (Last commit) column may include information about the commit corresponding to each item. The commit information (Last commit) field may include at least some of the following: identification information about the commit, commit message, information about the commit operation, information about the committed file set (code information), and identification information related to the committed file set. there is. For example, commit information may include task information corresponding to committed code information. In embodiments, identification information regarding a set of committed files may include information regarding code information created, modified, altered, or created by an operator in the set of files. For example, information about source code may include location information in a file set of code information that has been created, modified, changed, or created, and/or information about major creation history. In embodiments, the commit information may include identification information corresponding to the commit operation. For example, when the worker device 102 commits code information, the worker device 102 or the server 103 may generate and/or assign identification information for the commit task. In an embodiment, the commit information (Last commit) field may include identification information of the commit and/or a commit message. For example, the electronic device 101 checks the commit identification information corresponding to the first code information based on the data included in the commit information (Last commit) column in the first item 510, and commits the commit based on the commit identification information. You can check the information. In embodiments, the commit message may include commit identification information at least in part. In an embodiment, the commit message may include task information at least in part.

In an embodiment, the build task information list 500 may include a user interface (e.g., link) corresponding to a commit information (Last commit) column for each item, and the electronic device 101 may display a user interface (e.g., link) corresponding to the commit information column. Commit information can be provided through the interface. For example, in the example of the first item 510, the electronic device 101 displays commit identification information in the commit column corresponding to the first code information, and displays the commit identification information as a user interface including a hyperlink. can be provided. The electronic device 101 may generate data in the commit information column based on the first information obtained from the server 103.

The status information (Status) column may include information regarding the success or failure of the corresponding build task for each item. For example, in the example of FIG. 5, when the build is successful and a package corresponding to the code information for which the build task has been requested has been successfully created, the electronic device 101 displays “Success” in the status information field, and the build task is completed. In case of failure, it can be marked as "Fail". The electronic device 101 may generate data in the status information column based on the second information obtained from the server 103.

The task information (BTS) column may include information about the task. The task information (BTS) column may include information about the task corresponding to committed code information corresponding to each item. The task information (BTS) field contains at least some of the following: identification information for the task, information about one or more branches corresponding to the task, worker information about one or more workers corresponding to the task, and information about the progress status of the task corresponding to the task. may include. In an embodiment, the task information (BTS) field may include identification information of the task. For example, the electronic device 101 checks task identification information corresponding to the first code information based on the task information (BTS) in the first item 510, and operator information corresponding to the task based on the task identification information and /Or you can check task information corresponding to the task.

In an embodiment, the build task information list 500 may include a user interface (e.g., link) corresponding to a task information (BTS) column for each item, and the electronic device 101 may include a user interface corresponding to the task information column. Task information can be provided through . For example, in the example of the fourth item 540, the electronic device 101 displays identification information (MPI-390 and IOS-6826) of each of the two tasks corresponding to the fourth code in the task column corresponding to the fourth code information. ) can be displayed, and identification information for each task can be provided as a user interface including a hyperlink. The electronic device 101 may generate data in the task information column based on the first information obtained from the server 103.

The version information (Version) column and the capacity information (Size) column may respectively include version information corresponding to the package created based on the build task and information about the capacity of the package. According to one embodiment, the electronic device 101 may generate data in the version information column based on the first information obtained from the server 103. According to one embodiment, the electronic device 101 may check version information based on the second information. For example, if the build fails, version identification information corresponding to the pushed code information may not be generated. The electronic device 101 may or may not display version information based on whether the build is successful. According to one embodiment, the electronic device 101 may generate data in the package capacity information (Size) column based on the first information obtained from the server 103. According to one embodiment, the electronic device 101 may check package capacity information based on the second information. For example, if the build fails, a package corresponding to the pushed code information may not be created, and the capacity information itself may not exist. Conversely, if the build is successful, a package is created and the electronic device 101 can check the capacity information of the package. Referring to FIG. 5, in the example of the second item 520, in response to the build of the second code information failing, the status information column is displayed as "Fail", and the version information column and package capacity information You can confirm that the data in the column is not created.

In an embodiment, the build task information list 500 may include a user interface (Actions) for providing package code information. The electronic device 101 may allocate path information regarding code information of a package that includes at least code information and is generated by a server in response to a build task to the build task information list 500. For example, a user interface (Actions) for providing code information may include an interface implemented as a link for providing path information for obtaining code information for the package code corresponding to each item. For example, "Download" is a link to download code information for the package of the corresponding item, "Copy" is a link to copy code information, and "QRCode" provides a QR code corresponding to the link. It may be a link for doing so, and each link may include at least part of the path information for obtaining code information about the package code. The electronic device 101 may provide code information on the package corresponding to each item to the operator device 102 based on operator input received through a user interface (Actions) for providing code information. At this time, the user interface (Actions) for providing code information for each item may be activated or deactivated based on the second information. For example, if the build task is successful, the electronic device 101 activates a user interface (Actions) to provide code information of the corresponding item, and if the build task fails, the electronic device 101 activates a user interface (Actions) to provide code information of the corresponding item. (Actions) can be disabled.

Referring to FIGS. 6 and 7 , the electronic device 101 may provide numerical information related to the build task. Numerical information may be generated based on the first information, second information, and/or build task information list. The numerical information may include at least some of, for example, numerical information related to the time required for the build operation as shown in FIG. 6 and capacity information related to the capacity of the package generated as a result of the build operation as shown in FIG. 7 .

According to various embodiments, the electronic device 101 may generate numerical information related to time based on the first information, second information, and/or build task information list. For example, the electronic device 101 may check time required information corresponding to each build task based on the second information. According to one embodiment, the electronic device 101 may check build time information for each version based on the first information and the second information. For example, the electronic device 101 may check build time information corresponding to each of one or more build tasks identified based on the version identification information and check the build time required for each version. Build time information for each version can be confirmed in response to a specified period. Build time information required for each version can be confirmed by adding up all build tasks required for each version, or can be confirmed as an average value based on the number of builds. According to an embodiment, the electronic device 101 may check build time information for each of one or more build tasks identified based on task information, branch information, and/or worker information as well as the version. The electronic device 101 may generate history information related to the build time required, based on time required information generated in response to each of the plurality of build tasks.

Referring to FIG. 6, the electronic device 101 may provide time-related numerical information 600.

In an embodiment, the electronic device 101 may check information 601 regarding the total number of builds. For example, based on the build task information list, the electronic device 101 may check at least some of the total number of build tasks, the total number of build tasks corresponding to a specified period, and the number of build tasks for each version.

In an embodiment, the electronic device 101 may provide history information 602 about the build time. For example, based on the build task information list, the electronic device 101 corresponds to the time required for the entire build task, the time required for all build tasks corresponding to a specified period, the time required for the build task by version, and the entire build task. You can check at least part of the average time required.

In an embodiment, the electronic device 101 may provide trend information 603 about build time. For example, based on the build task information list, the electronic device 101 checks the time required for all build tasks and the time required for all build tasks corresponding to each of one or more specified periods, and builds based on the comparison result. Trend information 603 about the time required can be generated.

According to one embodiment, the electronic device 101 provides information 604 about the number of download requests for code information transmitted from the worker device 102 to the electronic device 101 through the build task information list 500. can do.

In an embodiment, the electronic device 101 may provide a time graph 605 that visualizes numerical information related to build time. The example in FIG. 6 may be a graph regarding the build time required for each version. The electronic device 101 checks information about the build time for each version based on the version identification information and build time information confirmed based on each item, and generates a graph about the build time for each version. You can. Referring to FIG. 6, the horizontal axis of the time required graph 605 may be version information, and the vertical axis may be the average time required. The graph in FIG. 6 is an example of a graph regarding the time required, and the electronic device 101 acquires numerical information based on various data based on the first information and/or second information and generates a graph based on the numerical information. You can.

According to various embodiments, the electronic device 101 may generate numerical information related to the built package capacity based on the first information, second information, and/or build task information list. For example, the electronic device 101 may check built package capacity information corresponding to each build task based on the second information. According to one embodiment, the electronic device 101 may check package capacity information built for each version based on the first information and the second information. For example, the electronic device 101 may check built package capacity information corresponding to each of one or more build tasks identified based on the version identification information and check the built package capacity for each version. Package capacity information built for each version can be confirmed in response to a specified period. Package capacity information built for each version can be confirmed by adding up all build tasks performed for each version, or can be confirmed as an average value based on the number of builds. According to an embodiment, the electronic device 101 may check built package capacity information in response to each of one or more build tasks confirmed based on task information, branch information, and/or worker information as well as the version. The electronic device 101 may generate history information related to package capacity based on package capacity information generated in response to each of a plurality of build tasks.

In an embodiment, the electronic device 101 may provide a time required graph 700 that visualizes numerical information related to the capacity of the built package. The example in FIG. 7 may be a graph regarding the capacity of packages built for each version. The electronic device 101 checks information about the capacity of the built package for each version based on the version identification information and the capacity information of the built package confirmed based on each item, and the capacity of the built package required for each version. You can create a graph about . Referring to FIG. 7, the horizontal axis of the time required graph 700 may be version information, and the vertical axis may be average package capacity. The graph in FIG. 7 is an example of a graph related to capacity information, and the electronic device 101 acquires numerical information based on various data based on the first information and/or second information and generates a graph based on the numerical information. You can.

In an embodiment, the electronic device 101 may check whether the build task is abnormal based on time required information. The electronic device 101 can check information on the time required for a build task based on the build request. The electronic device 101 may check the time required for the corresponding build task based on the second information. Based on the build task information list, the electronic device 101 may check required time information corresponding to other existing build tasks, for example, history information about the required time. The electronic device 101 may check whether the build task is abnormal based on the time required for the build task and history information about the time, which is confirmed based on the second information. For example, the electronic device 101 may check whether the progress of the build task is abnormal when the time required for the build task exceeds or falls short of a specified threshold in relation to the build time, which is set based on history information. You can. For example, the build task was successful and the package was created, but this may have nothing to do with whether the package operates normally. At this time, if the time required is too short or too long, there is a possibility that there is an error in the built package regardless of whether the build was successful or not. The electronic device 101 determines one or more workers corresponding to the build task identified based on the build task information list, based on whether the confirmed build task is abnormal, and provides a worker device 102 corresponding to the confirmed worker. Information on abnormalities can be provided. The information regarding abnormality may include at least some of branch information corresponding to the build task, task information, commit information, and information indicating abnormality. According to one embodiment, history information regarding the time required for comparison with the performed build task may be confirmed based on the build task information list. History information regarding the time required may be generated based on build time information corresponding to another build task that is different from the performed build task. For example, it may include at least some of information about the time required for each version, trend information about the time required to build, and information about the time required for build tasks performed within a specified period.

In an embodiment, the electronic device 101 may check whether the build task is abnormal based on package capacity information. The electronic device 101 can check package capacity information during build work based on the build request. The electronic device 101 may check the package capacity of the corresponding build job based on the second information. Based on the build task information list, the electronic device 101 may check package capacity information corresponding to other existing build tasks, for example, history information about package capacity. The electronic device 101 may check whether the build job is abnormal based on the package capacity of the build job and history information about the package capacity, which are confirmed based on the second information. For example, when the package capacity of the build job exceeds or falls short of a specified threshold related to the build package capacity, which is set based on history information, the electronic device 101 checks whether the progressed build job is abnormal. You can. For example, the build task was successful and the package was created, but this may have nothing to do with whether the package operates normally. At this time, if the package capacity is too large or too small, there is a possibility that there is an error in the built package regardless of whether the build was successful or not. The electronic device 101 determines one or more workers corresponding to the build task identified based on the build task information list, based on whether the confirmed build task is abnormal, and provides a worker device 102 corresponding to the confirmed worker. Information on abnormalities can be provided. The information regarding abnormality may include at least some of branch information corresponding to the build task, task information, commit information, and information indicating abnormality. According to one embodiment, history information regarding the package capacity to be compared with the performed build task may be confirmed based on the build task information list. History information about package capacity may be generated based on build package capacity information corresponding to another build task that is different from the performed build task. For example, it may include at least some of information about package capacity by version, trend information about build package capacity, and information about package capacity of build tasks performed within a specified period.

Claims

In a method of providing code-related information of an electronic device,

In response to the start of a build task related to the first code information performed on the server, information about the build task from the server and branch information corresponding to the first code information are included. Obtaining first information;

Obtaining second information including at least information about the result of the build task from the server in response to the end of the build task; and

A method of providing code-related information, including providing a build task information list including a first item generated based on the first information and the second information to a worker device.
According to paragraph 1,

The first information includes worker information that requested the build task to the server, branch identification information corresponding to the first code information, commit information corresponding to the first code information, and the first code information. A method of providing code-related information further including at least some of the task identification information corresponding to.
According to paragraph 2,

The branch identification information corresponds to one or more task identification information,

A method of providing code-related information, wherein the task identification information corresponds to one or more branch identification information.
According to paragraph 2,

The method of providing information related to the above code is:

A method of providing code-related information further comprising providing information on one or more tasks corresponding to a branch corresponding to the first code information, which is identified based on the branch identification information.
According to paragraph 2,

The method of providing information related to the above code is:

A method of providing code-related information further comprising providing information on one or more branches corresponding to a task corresponding to the first code information, which is identified based on the task identification information.
According to paragraph 1,

The second information is code-related, further comprising at least part of capacity information of the package generated by the server in response to the build task, version information of the package corresponding to the build task, and time required information corresponding to the build task. How to provide information.
According to clause 6,

The method of providing information related to the above code is:

Checking whether the build task is abnormal based on the time required information confirmed based on the second information and information about the time required for one or more build tasks confirmed based on the build task information list; and

A method of providing code-related information, further comprising providing information about whether the build is abnormal to the one or more workers based on information about one or more workers confirmed based on the branch information and information about whether the build is abnormal.
According to clause 6,

The method of providing information related to the above code is:

Based on time required information corresponding to each of the plurality of build tasks and version information of the package corresponding to each of the plurality of build tasks, obtain information about the build time corresponding to each version information,

Further comprising the step of checking whether a build operation related to the first code information is abnormal based on the information about the build time corresponding to each version information and the time information confirmed based on the second information. How to provide information about your code.
According to clause 6,

The method of providing information related to the above code is:

Checking whether the build task is abnormal based on the capacity information confirmed based on the second information and the capacity information of a package for one or more build tasks confirmed based on the build task information list; and

A method of providing code-related information, further comprising providing information about whether the build is abnormal to the one or more workers based on information about one or more workers confirmed based on the branch information and information about whether the build is abnormal.
According to clause 6,

The method of providing information related to the above code is:

Based on capacity information corresponding to each of the plurality of build tasks and version information of the package corresponding to each of the plurality of build tasks, obtain information about the capacity corresponding to each version information,

Code-related information further comprising the step of checking whether a build operation related to the first code information is abnormal based on the capacity information corresponding to each version information and the capacity information confirmed based on the second information. How to provide.
According to paragraph 1,

The method of providing information related to the above code is:

A method of providing code-related information further comprising providing one or more worker information identified based on the branch information.
According to paragraph 1,

The method of providing information related to the above code is:

Providing a result message including at least part of the second information and at least information about a result of the build operation to a worker device corresponding to one or more worker information identified based on the branch information. How to provide code-related information, including more information.
According to paragraph 1,

The method of providing information related to the above code is:

A method of providing code-related information further comprising providing task status information regarding a progress status of a task corresponding to the first code information identified based on the task identification information.
According to paragraph 1,

The method of providing information related to the above code is:

A method of providing code-related information further comprising providing the first code information to a worker device in response to a request for code information corresponding to the first item received from the worker device.
According to clause 14,

The first item includes path information about code information of a package generated by a server in response to the build task and including at least the first code information,

The method of providing information related to the above code is:

A method of providing code-related information further comprising providing code information of the package to the worker device based on the path information.
According to paragraph 1,

The method of providing information related to the above code is:

Obtaining branch identification information and one or more worker information; and

A method of providing code-related information further comprising generating a branch list including the branch identification information and branch information mapping the one or more worker information based on a request received from a worker device.
According to paragraph 1,

The code information of the package generated by the server in response to the build task and including at least the first code information includes source code for performing an A/B test in response to the code information of the generated package,

The method of providing information related to the above code is:

The method of providing code-related information further includes providing result information of the A/B test confirmed based on the first information.
In electronic devices,

Memory;

transceiver; and

Includes a processor,

The processor,

In response to the start of a build task related to first code information performed on a server, it includes information about the build task from the server and branch information corresponding to the first code information. Obtain the first information,

Obtaining second information including at least information about the result of the build task from the server in response to the end of the build task,

An electronic device configured to provide a build work information list including a first item generated based on the first information and the second information to a worker device.
A non-transitory computer-readable recording medium that records a program for executing the method of claim 1 on a computer.