WO2023249156A1 - Dispositif électronique pour la fourniture d'informations de code et procédé associé - Google Patents

Dispositif électronique pour la fourniture d'informations de code et procédé associé Download PDF

Info

Publication number
WO2023249156A1
WO2023249156A1 PCT/KR2022/010049 KR2022010049W WO2023249156A1 WO 2023249156 A1 WO2023249156 A1 WO 2023249156A1 KR 2022010049 W KR2022010049 W KR 2022010049W WO 2023249156 A1 WO2023249156 A1 WO 2023249156A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
conflict
code
branch
worker
Prior art date
Application number
PCT/KR2022/010049
Other languages
English (en)
Korean (ko)
Inventor
이상용
김선우
Original Assignee
쿠팡 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 쿠팡 주식회사 filed Critical 쿠팡 주식회사
Publication of WO2023249156A1 publication Critical patent/WO2023249156A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3664—Environments for testing or debugging software
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3692—Test management for test results analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management

Definitions

  • This disclosure relates to an electronic device and method for providing code information. More specifically, the present disclosure relates to an electronic device and method for providing conflict information about code written by a plurality of workers for a project.
  • 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.
  • the present disclosure aims to provide an electronic device and method for providing project-related work status information to workers.
  • the code information providing method when a first worker input corresponding to the first conflict information list is obtained, provides code part information in which a conflict occurred with respect to file information corresponding to the first worker input to the first worker terminal. It further includes steps provided to.
  • the code information providing method further includes obtaining worker identification information from the at least one worker terminal and providing a second conflict information list corresponding to the worker identification information to the at least one worker terminal. do.
  • the code information providing method further includes obtaining branch identification information from the at least one worker terminal and providing a third conflict information list corresponding to the branch identification information to the at least one worker terminal. do.
  • the code conflict information includes a list of worker information that performed work on the same file, and the worker information list includes branch information corresponding to the file, tag information corresponding to the branch information, and information corresponding to the file. Contains at least some of the commit information,
  • the code conflict information includes a list of branch information derived from master branch information.
  • the merge combination may include a merge combination of the at least two branch information, a merge combination of the at least two pieces of file information related to the first branch information, and a merge combination of the program code included in the first file information.
  • the computer program obtains project information from at least one worker terminal, and the at least one Obtaining at least two branch information corresponding to the project information from a worker terminal, confirming a merge combination based on the combination of the at least two branch information for conflict testing, and performing the conflict test on the merge combination. Based on the results, code conflict information is provided to the at least one worker terminal.
  • the electronic device and method for providing code information according to the present disclosure check in advance conflict information generated by individual modification of each code related to the project before the build process for service distribution for a plurality of program codes related to the project. And by providing this to workers, conflict situations can be notified in advance to preemptively resolve conflicts and improve project productivity.
  • 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.
  • FIG. 1 is a diagram illustrating a system for providing code information according to an embodiment of the present disclosure.
  • Figure 3 is a flowchart for explaining a method of providing code information according to an embodiment of the present disclosure.
  • 4A to 4C are diagrams showing a page providing code information according to a first function according to an embodiment of the present disclosure.
  • 5A and 5B are diagrams showing a page providing code information according to a second function according to an embodiment of the present disclosure.
  • FIG. 6 is a diagram illustrating a page that provides code information according to a third function according to an embodiment of the present disclosure.
  • FIG. 7 is a diagram illustrating an electronic device for providing code information according to an embodiment of the present disclosure.
  • first and/or second used in this specification may be used to describe various components, but are only used for the purpose of distinguishing one component from other components. It is not intended to be limited to the components referred to by that term.
  • a first component may be named a second component, and the second component may also be named a first component.
  • module refers to a unit that processes at least one function or operation, which may be implemented as hardware or software, or as a combination of hardware and software.
  • embodiments of the present disclosure may be represented by functional block configurations and various processing steps. These functional blocks may be implemented in various numbers of hardware or/and software configurations that execute specific functions.
  • embodiments of the present disclosure include memory, processing, logic, look-up tables, etc. that can execute various functions under the control of one or more microprocessors or other control devices. Direct circuit configurations can be employed.
  • embodiments of the present disclosure include various algorithms implemented as combinations of data structures, processes, routines or other programming constructs, including: It can be implemented in a programming or scripting language such as C, C++, Java, assembler, etc. Functional aspects may be implemented as algorithms running on one or more processors. Additionally, the present embodiment may employ prior art for at least one of electronic environment setting, signal processing, and data processing. Terms such as “mechanism,” “element,” “means,” and “configuration” are broadly used. It can be used and is not limited to mechanical and physical components. The term may include the meaning of a series of software routines in connection with a processor, etc.
  • Each block of the processing flow diagrams attached to this specification and combinations of the flow diagram diagrams may 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 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. It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s).
  • the “electronic device” or “terminal” referred to in this specification may be implemented as a computer or portable terminal that can connect to a server or other terminal through a network.
  • the computer includes, for example, a laptop, desktop, laptop, etc. equipped with a web browser
  • the portable terminal is, for example, a wireless communication device that guarantees portability and mobility.
  • all types of communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution), smartphones, tablet PCs, etc. It may include a handheld-based wireless communication device.
  • the "electronic device” or “terminal” referred to in this specification includes a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a touch panel, User interface devices such as keys, buttons, etc. may also be included.
  • the electronic device 110 can be understood as a broad concept that includes a series of application programs that can operate on a network server and various databases built therein.
  • the electronic device 110 uses a network server program provided in various ways depending on the operating system, such as DOS, Windows, Linux, Unix, or MacOS. This can be implemented.
  • the code conflict information provided from the electronic device 110 to at least one of the first to nth worker terminals 120_1, 120_2, ..., 120_n includes branch information where the code conflict occurred, code Information on the file where the conflict occurred, information on the worker who performed work on the file where the code conflict occurred, information on the code part where the code conflict occurred, code change information on which the modification was performed, tag information corresponding to branch information, and file information. It may include at least some of the commit information corresponding to .
  • a commit operation may refer to the operation of storing added file information or edited file information in a storage, and in an embodiment of the present disclosure, the commit information may include information related to the commit operation.
  • code conflict information provided from the electronic device 110 to at least one of the first to nth worker terminals 120_1, 120_2, ..., 120_n may vary depending on the function provided by the electronic device 110. Code conflict information provided according to the function of the electronic device 110 will be described in detail in FIGS. 4A to 6 to be described later.
  • Work status information related to the project can be derived from project-related information and project history information stored in the server, and is provided to at least one of the first to nth worker terminals (120_1, 120_2, ..., 120_n) in response to the worker's request. It can be.
  • conflict information arising from individual modifications of each code is provided to the worker, thereby notifying the conflict situation in advance and preemptively resolving the conflict. This can improve the productivity of the project.
  • by providing work status related to the project to the worker information on the project progress can be intuitively provided to the worker. A detailed description of the method for providing code information according to an embodiment of the present disclosure will be described later with reference to FIGS. 2 to 7.
  • FIG. 2 is a diagram illustrating the data structure 20 of the project 200 in which code information is provided according to an embodiment of the present disclosure.
  • a master branch (MB), a development branch (DB), a first feature branch (FB1), and a second feature branch ( FB2) can be derived from one project 200.
  • MB master branch
  • DB development branch
  • FB1 first feature branch
  • FB2 second feature branch
  • the data structure 20 shown in FIG. 2 is only an example to aid understanding of the present disclosure, and does not limit the data structure 20 in which code information is provided according to an embodiment of the present disclosure, and the data structure ( 20) can be adaptively built according to the goals of the project 200.
  • the master branch (MB) may be a branch for managing release history related to the project 200 and may manage a set of files in a deployable state.
  • 2 shows a master branch (MB) including a first master file set 210 and a second master file set 220, and the first program or second master built from the first master file set 210 A second program built from fileset 220 may be distributed, where the second program may be another version of the first program.
  • Each of the plurality of files included in the first master file set 210 and the second master file set 220 may be a file committed by the first to nth worker terminals (120_1, 120_2, ..., 120_n). .
  • the second set of development files 212 may be from the first set of development files 211
  • the third set of development files 213 may be an updated version of the second set of development files 212
  • the set of files from the first set of development files 211 may be an updated version of the first set of development files 211.
  • Each of the to third development file sets 211, 212, and 213 may be a set of files for implementing independent functions related to the program corresponding to the second master file set 220.
  • Each of the plurality of files included in each of the first to third development file sets 211, 212, and 213 may be a file committed by the first to nth worker terminals 120_1, 120_2, ..., 120_n.
  • 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 200.
  • DB development branch
  • the sets of files associated with the first feature branch (FB1) and the second feature branch (FB2) are merged into the development branch (DB). It can be. 2 shows that work related to the second feature branch FB2 is completed, and at least one of the 2-1 feature file set 212_1 and the 2-2 feature file set 212_2 is merged into the development branch DB.
  • a branch within a project may have a different structure depending on the worker, and the embodiment of the present specification checks the entire branch list related to the project and merges each combination of branches in the branch list. ) can be checked in advance to determine whether a conflict has occurred.
  • Figure 3 is a flowchart for explaining a method of providing code information according to an embodiment of the present disclosure.
  • the electronic device 110 may obtain project information from at least one of the first to nth worker terminals 120_1, 120_2, ..., 120_n.
  • Project information may include a basic file information set related to the project, and the basic file information set may include a plurality of program codes for implementing a program related to the project.
  • a simple merge combination of at least two branch information may be a combination of a first branch and a second branch to implement different functions.
  • a merge combination of at least two pieces of file information related to one branch information may be a combination of first file information and second file information related to first branch information.
  • the merge combination for the program code included in one file information may be the first code line and the second code line included in the program code included in the first file information.
  • the merge combination confirmed from the electronic device 110 may be a combination of entities that have a physical or logical relationship between branches, files, or code lines.
  • the electronic device 110 may perform a conflict test on the confirmed merge combination.
  • Conflict testing can be performed by checking whether a physical or logical conflict occurs for the merge combination.
  • a physical conflict can be a conflict that can occur when multiple workers modify a code line in the same location, and a logical conflict can be a conflict that can occur due to the relationship between at least two code lines in different locations. You can.
  • the electronic device 110 may perform a conflict test on all merge combinations confirmed in step S330.
  • the electronic device 110 may perform a conflict test on some selected merge combinations to reduce the load. Specifically, in step S320, first branch information and second branch information are obtained, the first branch information includes modification information for the first file related to the first branch, and the second branch information is related to the second branch. If the modified second file contains modification information, the electronic device 110 may perform a conflict test by selecting a merge combination related to the first branch and the second branch.
  • step S350 the electronic device 110 according to an embodiment of the present disclosure sends code conflict information to one of the first to nth worker terminals 120_1, 120_2, ..., 120_n based on the result of the conflict test performed in step S340.
  • Code conflict information includes information on the branch where the code conflict occurred, information on the file where the code conflict occurred, information on the worker who performed work on the file where the code conflict occurred, information on the code part where the code conflict occurred, information on the code change on which the modification was performed, and branch information. It may include at least part of tag information corresponding to the information and commit information corresponding to the file information.
  • detailed items of code conflict information provided by the electronic device 110 to at least one of the first to nth worker terminals 120_1, 120_2, ..., 120_n are related to the function provided by the electronic device 110. It may vary depending on the condition. Meanwhile, in an embodiment, conflict information may be provided to each worker for the branch combination in which the conflict occurred.
  • Conflict tests according to embodiments of the present disclosure may be performed at regular intervals.
  • the conflict test may be performed in response to a cycle preset by the administrator of the electronic device 110, and the merge combination may be confirmed prior to the conflict test.
  • a conflict test according to another embodiment of the present disclosure can be performed when commit information related to a program is obtained. Commit information can be obtained when a worker completes work on a corresponding file and provides completed work information to the electronic device 110.
  • FIGS. 4A to 4C are diagrams showing a page providing code information according to a first function according to an embodiment of the present disclosure.
  • the first function may be a function for providing code conflict information that occurs regarding a merge combination.
  • the first page 40a for providing code conflict information according to the first function shown in FIG. 4A may be provided in response to an operator's input on the first tab 400 corresponding to the first function.
  • the first page 40a includes a first input unit 410 for obtaining project identification information from an operator, a conflict information list 420 including code conflict information provided in response to the project identification information, It may include a second input unit 430 for obtaining worker identification information from the worker and a third input unit 440 for obtaining branch identification information from the worker.
  • the electronic device 110 may obtain project identification information through the first input unit 410 and provide a conflict information list 420 corresponding to the project identification information on the first page 40a.
  • the conflict information list 420 may include information related to program code in which a conflict occurred, based on the results of a conflict test.
  • the conflict information list 420 includes the first branch information 421 where the conflict occurred, tag information 422 corresponding to the first branch information, file information 423 where the conflict occurred, and the first branch and the conflict occurred. It may include second branch information 424, and the tag information 422 may include version information related to the first branch information 421.
  • the conflict information list 420 may include an icon 425 to provide detailed information about the conflict situation.
  • the electronic device 110 can provide detailed information about the conflict situation to the worker through the worker terminal, a detailed description of which will be described later with reference to FIG. 4B.
  • a list of conflict information corresponding to the operator input can be provided to the operator through the operator terminal, and a detailed description of this is shown in Figure 2. This is described later in 4c.
  • the first subpage 40b shown in FIG. 4B may be provided to the worker terminal in response to an operator input to the icon 425 on the first page 40a for providing code conflict information according to the first function.
  • the first subpage 40b may include code conflict detailed information 450, and the code conflict detailed information 450 may include information on the code portion in which the conflict occurred. Specifically, information on the code portion in which a conflict occurred in the program code related to the first branch may be provided, and the code portion information may be highlighted.
  • the code conflict details 450 may include code line information before the modification operation and code line information after the modification operation.
  • 5A and 5B are diagrams showing a page providing code information according to a second function according to an embodiment of the present disclosure.
  • the second function may be a function for providing information on a worker who performed work on a file related to a conflict that arises for a merge combination.
  • a second page 50a for providing code conflict information according to the second function shown in FIG. 5A may be provided in response to an operator's input on the second tab 500 corresponding to the second function.
  • the second page 50a may include a conflict information list 510 for each file, and the conflict information list 510 for each worker may include file information 511 in which a conflict occurred, and edit information for the file.
  • worker information 512 who performed the work commit information 513 obtained in relation to work on the file, branch information 515 corresponding to the file, and tag information 516 corresponding to the branch information. may include.
  • the conflict information list 510 for each file may include an icon 514 to provide detailed information about the conflict situation.
  • the electronic device 110 can provide detailed information about the conflict situation to the worker through the worker terminal, a detailed description of which will be described later in FIG. 5B.
  • the file-specific conflict information list 510 provided to the worker terminal according to the second function performs work on files in which conflicts occur within a specified period in response to the worker's period information input. Can contain one worker information.
  • the second subpage 50b shown in FIG. 5B may be provided to the worker terminal in response to an operator input to the icon 514 on the second page 50a for providing code conflict information according to the second function.
  • the second subpage 50b may include code conflict details 520 and 530, and the code conflict details 520 and 530 may include information on the code portion in which the conflict occurred. Specifically, information on the code part where the conflict occurred may be provided, and the code part information may be highlighted.
  • code conflict details 520 and 530 may include at least some of change information and comparison information for program code.
  • FIG. 6 is a diagram illustrating a page that provides code information according to a third function according to an embodiment of the present disclosure.
  • the third function may be a function for providing branch information related to a specific branch.
  • a third page 60 for providing code conflict information according to the third function shown in FIG. 6 may be provided in response to an operator's input on the third tab 600 corresponding to the third function.
  • the third page 60 may include a conflict information list 610 including a plurality of branch information related to the first branch.
  • Each of the plurality of branch information included in the conflict information list 610 may include branch path information.
  • the branch path information may indicate which master branch (MB) the corresponding branch is derived from, and in some embodiments, the conflict information list 610 contains at least some of the information about a plurality of branches branched from the corresponding master branch (MB). It can be included.
  • Code conflict information provided according to the third function may be indirect information for the operator to determine the conflict. Specifically, the rule is that when work on a specific branch is completed, the existing branch is deleted, but if deletion is not performed, the worker must determine whether the conflict caused by the undeleted branch is a conflict that can be ignored, or whether it is a conflict that requires attention. Whether there is a conflict can be determined based on code conflict information provided according to the third function. Additionally, based on code conflict information provided according to the third function, workers can set a branch combination to perform conflict testing. Specifically, the operator can set to exclude branches on which a deletion operation has not been performed from the conflict test performance target based on code conflict information provided according to the third function.
  • conflict determination is performed by comparing files in the corresponding branch with each other, so it is necessary to check the conflict of other files that are logically related to a specific file. In this case, by user settings, it is possible to periodically check whether a conflict has occurred in files other than the same file, and conflict information can also be provided to each worker.
  • FIG. 7 is a diagram illustrating an electronic device 110 for providing code information according to an embodiment of the present disclosure.
  • the electronic device 110 may include a transceiver 710, a processor 720, and a memory 730.
  • the processor 720 may include at least one device described above with reference to FIGS. 1 to 6 or may store information for performing at least one method described with reference to FIGS. 1 to 6 . Additionally, the processor 720 can control the electronic device 110 to execute programs and provide code information.
  • the memory 730 may include at least one of volatile memory and non-volatile memory. Additionally, the memory 730 may store the code of a program executed by the processor 720. Meanwhile, although not shown, an interface for providing information from the electronic device 110 to an external terminal may be further included.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Data Mining & Analysis (AREA)
  • Credit Cards Or The Like (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un dispositif électronique pour la fourniture d'informations de code et un procédé associé. Le procédé de fourniture d'informations de code par un dispositif électronique selon un mode de réalisation de la présente invention comprend les étapes consistant à : obtenir des informations de projet provenant d'au moins un terminal de travailleur ; obtenir au moins deux éléments d'informations de branche correspondant aux informations de projet provenant du ou des terminaux de travailleur ; vérifier, pour un test de conflit, une combinaison de fusion sur la base d'une combinaison desdits au moins deux éléments d'informations de branche ; et fournir des informations de conflit de code au ou aux terminaux de travailleur sur la base d'un résultat de réalisation du test de conflit sur la combinaison de fusion.
PCT/KR2022/010049 2022-06-24 2022-07-11 Dispositif électronique pour la fourniture d'informations de code et procédé associé WO2023249156A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2022-0077471 2022-06-24
KR1020220077471A KR20240000809A (ko) 2022-06-24 2022-06-24 코드 정보 제공을 위한 전자 장치 및 그 방법

Publications (1)

Publication Number Publication Date
WO2023249156A1 true WO2023249156A1 (fr) 2023-12-28

Family

ID=89380168

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2022/010049 WO2023249156A1 (fr) 2022-06-24 2022-07-11 Dispositif électronique pour la fourniture d'informations de code et procédé associé

Country Status (2)

Country Link
KR (1) KR20240000809A (fr)
WO (1) WO2023249156A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130036400A1 (en) * 2011-08-02 2013-02-07 International Business Machines Corporation Pre-merge conflict avoidance
KR20130020135A (ko) * 2011-08-19 2013-02-27 인크로스 주식회사 통합 개발 환경에서의 코드 동시 개발자 리스트 제공 시스템 및 방법
KR20160000761A (ko) * 2014-06-25 2016-01-05 주식회사 포워드벤처스 소스 관리 장치, 시스템 및 방법, 컴퓨터 판독 가능한 기록 매체
KR102305845B1 (ko) * 2020-12-21 2021-09-29 쿠팡 주식회사 코드의 검증을 위한 전자 장치 및 그 방법
KR20210147354A (ko) * 2020-05-28 2021-12-07 삼성에스디에스 주식회사 소스 코드 자동 머지 방법 및 그 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130036400A1 (en) * 2011-08-02 2013-02-07 International Business Machines Corporation Pre-merge conflict avoidance
KR20130020135A (ko) * 2011-08-19 2013-02-27 인크로스 주식회사 통합 개발 환경에서의 코드 동시 개발자 리스트 제공 시스템 및 방법
KR20160000761A (ko) * 2014-06-25 2016-01-05 주식회사 포워드벤처스 소스 관리 장치, 시스템 및 방법, 컴퓨터 판독 가능한 기록 매체
KR20210147354A (ko) * 2020-05-28 2021-12-07 삼성에스디에스 주식회사 소스 코드 자동 머지 방법 및 그 장치
KR102305845B1 (ko) * 2020-12-21 2021-09-29 쿠팡 주식회사 코드의 검증을 위한 전자 장치 및 그 방법

Also Published As

Publication number Publication date
KR20240000809A (ko) 2024-01-03

Similar Documents

Publication Publication Date Title
US8140905B2 (en) Incremental problem determination and resolution in cloud environments
FI106752B (fi) Järjestelmä ohjelmiston vaihtamiseksi tietokoneen käytön aikana
US5717950A (en) Input/output device information management system for multi-computer system
US10346161B2 (en) Automatic detection of potential merge errors
WO2020134633A1 (fr) Procédé et dispositif de développement de programme d'application, et outil de développement intégré
US20130007709A1 (en) Software configuration management
WO2016111525A1 (fr) Procédé de commande de transfert de code source, programme informatique et support d'enregistrement associés
CN113434158B (zh) 一种大数据组件的自定义管理方法、装置、设备及介质
US9311077B2 (en) Identification of code changes using language syntax and changeset data
US20230259358A1 (en) Documentation enforcement during compilation
WO2022181958A1 (fr) Procédé d'analyse de données de migration en nuage utilisant des informations de processus système, et système associé
WO2024090932A1 (fr) Appareil de profilage de chargement de données et procédé de traitement automatique de données collectées
WO2014185627A1 (fr) Dispositif et procédé pour la sécurité d'un système de traitement des données
WO2023249156A1 (fr) Dispositif électronique pour la fourniture d'informations de code et procédé associé
WO2009116748A2 (fr) Procédé et appareil de développement de logiciels basés sur un contenant de composants réservés
WO2019074155A1 (fr) Système de reproduction intégré en temps réel entre bases de données
WO2024038944A1 (fr) Procédé et dispositif permettant de télécharger un code source
WO2023219194A1 (fr) Système de plateforme de service pour générer un flux de travail et procédé de génération de flux de travail
WO2023085738A1 (fr) Système et procédé de service de modèle ai
WO2023234449A1 (fr) Dispositif électronique conçu pour fournir des informations se rapportant à un travail de livraison et procédé associé
WO2024038939A1 (fr) Procédé et appareil de gestion de modèle d'intelligence artificielle associé à un service
EP4102357A1 (fr) Organisateur d'environnement de développement avec commutation et partage d'état améliorés
WO2024005246A1 (fr) Dispositif électronique destiné à fournir des informations de vérification de code et procédé associé
WO2024038951A1 (fr) Procédé de fourniture d'informations de code et dispositif électronique le prenant en charge
WO2024106621A1 (fr) Dispositif électronique et procédé pour fournir des informations relatives à un script

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22948090

Country of ref document: EP

Kind code of ref document: A1