KR20180061590A - Software build system and software build method using the system - Google Patents

Abstract

Disclosed are a software build system capable of reducing a cost and a time required for building and testing a source, and a software build method using the software build system. The software build system includes at least one user terminal, a source storage device, and a build automation server. The user terminal changes a source for developing software while generating monitoring information through source creation monitoring. The source storage device receives the changed source from the user terminal and stores the received source. The build automation server generates a source build unit by using the monitoring information received from the user terminal, and builds and tests the source received from the source storage unit in the source build unit. Accordingly, a server control unit is previously generated through the source creation monitoring, so that a time required for generating the source build unit is minimized while the cost is prevented from being increased due to unnecessary generation of the source build unit.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software building system,

The present invention relates to a software build system and a software build method using the software build system, and more particularly, to a software build system capable of building an original source created by a developer to generate an execution source and a software build method using the software build system.

When a software developer completes a software original source in accordance with a grammar of a specific programming language, the original source needs to be changed to an execution source that operates in an actual operating environment. Thus, changing the original source to the execution source is called software build.

Software development can be done by one or two developers if the software they want to develop has simple functionality. However, when the software to be developed has a wide variety of functions, it is inevitable for a plurality of developers to create a source by dividing each function or each field. Therefore, software development by the plurality of developers can be performed after synthesizing the sources developed by each developer.

In addition, software already developed may change some of the contents of existing sources. In this way, when some contents of an existing source are changed, software building should be performed again with the entire source including the changed contents.

Meanwhile, the conventional software building process, in particular, the software building process in the case of changing some contents of the existing source, is as follows.

First, when a developer changes a source using his / her development PC, the changed source is transferred from the development PC to the source repository. The source repository changes the pre-stored original source using the source received from the development PC, and then transmits the original source to the CI (Continuos Integration) server. The CI server builds the original source changed in the source repository into an execution source to be operated in the distribution environment, and then tests the execution source. If it is determined that there is no problem in the test result of the execution source, the CI server can transfer the execution source to the distribution environment, that is, the distribution server and execute the execution source.

Preferably, the CI server is always present for building and testing a source provided from the source repository. However, if the CI server is a cloud-based server, the cost may be increased by the time the CI server is present.

Therefore, if the CI server exists only at a necessary time, that is, at a time when the source stored in the source repository is changed, the cost can be reduced accordingly. However, since the time at which the CI server is generated, i.e., the loading time, is required, the required time may be generated.

SUMMARY OF THE INVENTION Accordingly, the present invention has been made to solve the above problems, and it is an object of the present invention to provide a software build system capable of reducing cost and time required for building and testing.

It is another object of the present invention to provide a software building method using the software build system.

The software build system according to the first embodiment of the present invention includes at least one user terminal, a source storage device, and a build automation server.

The user terminal changes the source for software development while generating monitoring information through source creation monitoring. The source storage device receives and stores the changed source from the user terminal. The build automation server generates a source build unit using the monitoring information received from the user terminal, and then builds and tests a source received from the source storage unit in the source build unit.

The build automation server may include a server control unit for receiving the monitoring information from the user terminal and analyzing the monitoring information to determine whether to generate the source build unit.

Next, a software build system according to a second embodiment of the present invention includes at least one user terminal, a source storage device, and a build automation server.

The user terminal changes the source for software development while generating monitoring information through source creation monitoring, and generates a server generation request signal using the monitoring information. The source storage device receives and stores the changed source from the user terminal. The build automation server generates a source build unit using the server generation request signal received from the user terminal, and then builds and tests a source received from the source storage unit in the source build unit.

The user terminal analyzes the monitoring information and generates the server generation request signal when it is determined that the source build unit needs to be generated. In this case, the build automation server may include a server controller for generating the source build unit in response to the server creation request signal received from the user terminal.

Meanwhile, at least one user terminal generates monitoring information through source creation monitoring and transmits the monitoring information to a server control unit of a build automation server according to a first embodiment of the present invention. Generating a source build unit using the monitoring information by the server control unit; The user terminal generating the changed source and transmitting the changed source to the source storage device; Transmitting the stored source to the source build unit after the source storage apparatus stores the changed source; And the source build unit building and testing the stored source.

Wherein the generating of the source build unit by the server control unit comprises: analyzing the monitoring information to determine whether to generate the source build unit; And generating the server control unit according to an analysis result.

In a software building method according to a second embodiment of the present invention, after at least one user terminal generates a server creation request signal using the monitoring information generated through the source creation monitoring, To a server control unit of the server; The server control unit generating a source build unit in response to the server generation request signal; The user terminal generating the changed source and transmitting the changed source to the source storage device; Transmitting the stored source to the source build unit after the source storage apparatus stores the changed source; And the source build unit building and testing the stored source.

Wherein the transmitting the server creation request signal to the server controller comprises: generating monitoring information through source creation monitoring while changing a source; Analyzing the monitoring information to determine whether to generate the source build unit; And transmitting the server creation request signal to the server controller after generating the server creation request signal if it is determined that the source build unit needs to be generated.

According to the software building system and the software building method using the software building system according to the present invention, the user terminal generates monitoring information through the source creation monitoring and transmits the monitoring information to the server control unit of the build automation server, By creating the build part, the source build part can build and test the provided source from the source storage device.

Also, the user terminal generates a server creation request signal using the monitoring information generated through the source creation monitoring and transmits the server creation request signal to the server control section of the build automation server, and the server control section generates the source build section in response to the server creation request signal Thus, the source build part can build and test the source provided from the source storage device.

In this manner, the monitoring information generated through the source creation monitoring is analyzed to predict the completion time of the source creation, and the source build unit is generated in advance for the build and test corresponding to the predicted time, The time required for generating the source build unit can be minimized while preventing the cost from increasing.

1 is a block diagram illustrating a software build system according to a first embodiment of the present invention.
FIG. 2 is a block diagram illustrating a process in which a user terminal generates and transmits monitoring information among software building methods performed by the software building system of FIG. 1. FIG.
FIG. 3 is a block diagram illustrating a process of generating a source build unit using a monitoring information by a server control unit of a build automation server in the software build method of FIG. 2. FIG.
FIG. 4 is a block diagram illustrating a process of transmitting a changed source from a user terminal in the software building method of FIG.
FIG. 5 is a block diagram for explaining a process of storing and transmitting a source in which a source storage device is changed in the software building method of FIG. 2. FIG.
FIG. 6 is a block diagram illustrating a process in which a source build unit builds and tests and distributes a source among the software build methods of FIG. 2; FIG.
7 is a block diagram for explaining a process of analyzing monitoring information and transmitting a server generation request signal from a software building method performed by a software building system according to a second embodiment of the present invention.
8 is a block diagram illustrating a process of generating a source build unit in response to a server creation request signal by a server control unit of a build automation server in the software build method of FIG.

The present invention is capable of various modifications and various forms, and specific embodiments are illustrated in the drawings and described in detail in the text.

It should be understood, however, that the invention is not intended to be limited to the particular forms disclosed, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. The terms first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprising" or "having ", and the like, are intended to specify the presence of stated features, integers, steps, operations, elements, parts, or combinations thereof, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, parts, or combinations thereof.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

≪ Example 1 >

1 is a block diagram illustrating a software build system according to a first embodiment of the present invention.

Referring to FIG. 1, a software build system according to the present embodiment includes at least one user terminal 100, a source storage device 200, and a build automation server 400.

The user terminal 100 may be a desktop computer, a notebook computer, a tablet PC, or the like as an apparatus for software development by any developer. When the development of the software is performed by a plurality of developers, a plurality of the user terminals 100 may exist.

The source storage device 200 is connected to the user terminal 100 through a wired / wireless network, for example, the Internet, and can exchange signals. When receiving the source from the user terminal 100, the source storage device 200 may store the source or change the stored source.

For example, the source storage device 200 may include GitHub, a web hosting service supporting a project using a distributed version management tool Git. That is, when the project for software development is performed by the source storage device 200, when a plurality of developers simultaneously modify the source, a problem occurs when the modified source is a different version, It may be a system that has been modified so that it can be used in a way that is useful for its use in cases where the source software has been modified by the source several times and the program is not running.

The build automation server 300 may be directly connected to the source storage device 200 to exchange signals, or may exchange signals through a wire / wireless network, for example, the Internet. For example, the build automation server 300 may be a cloud based server. The build automation server 300 receives the source stored in the source storage device 200 from the source storage device 200, and builds and tests the received source, and if it is determined that there is no problem with the test result It is possible to transmit the built source to a distribution environment composed of one or a plurality of distribution apparatuses 400. At this time, the distribution device 400 may be a personal computer such as a server computer or a desktop computer, a notebook computer, a tablet PC, a smart phone, or the like.

Meanwhile, the build automation server 300 can test whether it operates properly in a plurality of operating systems, for example, Windows, Linux, iOS, and Android.

Also, the build automation server 300 may be a Continuos Integration (CI) server. Accordingly, the build automation server 300 can consistently integrate and verify the sources stored in the source storage device 200, thereby checking whether the latest source is always in a healthy state, and by shortening the integration cycle, The cause can be quickly identified.

Hereinafter, a software building method performed in the software build system described above will be described in detail.

FIG. 2 is a block diagram illustrating a process in which a user terminal generates and transmits monitoring information among software building methods performed by the software building system of FIG. 1. FIG.

Referring to FIG. 2, the user terminal 100 generates monitoring information through source creation monitoring (S10). That is, the user terminal 100 can perform coding for software development by an arbitrary developer, and generate monitoring information through source creation monitoring. Meanwhile, the user terminal 100 may create a new full source or modify or add some of the stored sources. The source stored in the user terminal 100 may be a source of the latest version transmitted from the source storage device 200.

Then, the user terminal 100 transmits the monitoring information to the server control unit 310 of the build automation server 300 via a wired or wireless network, for example, the Internet (S20). The user terminal 100 may transmit the monitoring information in real time, but may transmit the monitoring information at predetermined time points or by a predetermined event, for example, an action of a user informing completion prediction of source creation.

FIG. 3 is a block diagram illustrating a process of generating a source build unit using a monitoring information by a server control unit of a build automation server in the software build method of FIG. 2. FIG.

Referring to FIG. 3, the server control unit 310 analyzes the monitoring information transmitted from the user terminal 100 to determine whether to generate the source build unit 320 (S30).

If it is determined that the source build unit 320 needs to be generated as a result of analyzing the monitoring information, the server control unit 310 generates the source build unit 320 at step S40. The generation of the source build unit 320 is performed such that the source build unit 320 is functionally activated, that is, loaded so as to be connected to the source storage device 200 and can perform a build and test operation It can mean. The source build unit 320 may be at least one server controlled by the server bare unit 310, for example.

When the server control unit 310 generates the source build unit 320, the server control unit 310 generates a server generation notification signal and transmits the signal to the user terminal 100 in operation S50.

FIG. 4 is a block diagram illustrating a process of transmitting a changed source from a user terminal in the software building method of FIG.

Referring to FIG. 4, the user terminal 100 completes the change of the source to generate a changed source (S60). That is, an arbitrary developer can perform coding for software development through the user terminal 100 to generate a whole new source, or modify or add some contents from the entire source that has been created. At this time, the user terminal 100 may display to the user that the build server unit 320 has been created using the server creation notification signal transmitted from the server control unit 310, before completing the change of the source.

Then, after receiving the server creation notification signal, the user terminal 100 transmits the changed source to the source storage device 200 (S70).

FIG. 5 is a block diagram for explaining a process of storing and transmitting a source in which a source storage device is changed in the software building method of FIG. 2. FIG.

Referring to FIG. 5, the source storage device 200 stores the changed source transmitted from the user terminal 100 (S80). For example, the source storage device 200 may newly store the changed source, or may change and store the previously stored source.

Then, the source storage apparatus 200 transmits the stored source to the source build unit 320 generated in the build automation server 300 (S90). For example, when the source is changed and stored, the source storage device 200 may transmit the stored source to the source build unit 320 or may transmit the stored source to the imaginary source build unit 320 at a predetermined time, Lt; / RTI >

FIG. 6 is a block diagram illustrating a process in which a source build unit builds and tests and distributes a source among the software build methods of FIG. 2; FIG.

Referring to FIG. 6, the source build unit 320 builds and tests the stored source transmitted from the source storage device 200 (S100). For example, the source build unit 320 can test whether it operates properly in a plurality of operating systems, for example, Windows, Linux, iOS, and Android.

The source build unit 320 transmits the built source to the distribution apparatus 400 when it is determined that the test result of the built source is a pass, that is, no problem (S110).

According to the present exemplary embodiment, the user terminal 100 generates the monitoring information through the source creation monitoring and transmits the monitoring information to the server control unit 310, and the server control unit 310 transmits the monitoring information to the server control unit 310, The source build unit 320 generates the source build unit 320 and the source build unit 320 builds and tests the source transferred from the source storage unit 200 to minimize the cost and time spent in the build and test .

That is, the server control unit 310 analyzes the monitoring information generated through the source creation monitoring to predict the completion time of the source creation, and the source build unit 320 for building and testing corresponding to the predicted time The time required for generating the source build unit 320 can be minimized while preventing the source build unit 320 from being unnecessarily generated and increasing the cost.

≪ Example 2 >

7 is a block diagram illustrating a process of analyzing monitoring information and transmitting a server creation request signal among software building methods performed by a software building system according to a second embodiment of the present invention, 7 is a block diagram illustrating a process of generating a source build unit in response to a server creation request signal by a server control unit of a build automation server in the software build method of FIG.

The software build system and method according to the present embodiment are substantially the same as the software build system and method according to the first embodiment except for the analysis of the monitoring information and the generation process of the build server unit, Are denoted by the same reference numerals, and a detailed description thereof will be omitted.

Referring to FIGS. 7 and 8, the user terminal 100 generates monitoring information in real time or at a certain point in time through the source creation monitoring (S12). That is, the user terminal 100 can perform coding for software development by an arbitrary developer, and generate monitoring information through source creation monitoring. Meanwhile, the user terminal 100 may create a new full source or modify or add some of the stored sources. The source stored in the user terminal 100 may be a source of the latest version transmitted from the source storage device 200.

Then, the user terminal 100 analyzes the monitoring information and determines whether to generate the source build unit 320 in the build automation server 300 (S22).

If it is determined that the source build unit 320 needs to be generated as a result of analyzing the monitoring information, the user terminal 100 generates a server creation request signal, And transmits the server control unit 310 of the automation server 300 (S32). At this time, the user terminal 100 may transmit the server creation request signal to the server control unit 310 via a wired or wireless network, for example, the Internet.

Then, the server control unit 310 generates the source build unit 320 in response to the server creation request signal transmitted from the user terminal 100 (S42). The generation of the source build unit 320 is performed such that the source build unit 320 is functionally activated, that is, loaded so as to be connected to the source storage device 200 and can perform a build and test operation It can mean. The source build unit 320 may be at least one server controlled by the server bare unit 310, for example.

When the server control unit 310 generates the source build unit 320, the server control unit 310 generates a server generation notification signal and transmits the signal to the user terminal 100 in operation S50.

Meanwhile, the subsequent steps are substantially the same as the steps S60 to S110 of the first embodiment described with reference to FIGS. 4, 5 and 6, and a detailed description thereof will be omitted.

As described above, according to the present embodiment, the user terminal 100 generates the server creation request signal using the monitoring information generated through the source creation monitoring and transmits the server creation request signal to the server control unit 310, 310 generates the source build unit 320 in response to the server creation request signal and as the source build unit 320 builds and tests the transmitted source from the source storage device, Thereby minimizing the cost and time required for the operation.

That is, the user terminal 100 analyzes the monitoring information generated through the source creation monitoring to predict the completion time of the source creation, and the server control unit 310 determines whether or not the source It is possible to minimize the time required for generating the source build unit 320 while preventing the source build unit 320 from being unnecessarily generated and increasing the cost by generating the source build unit 320 in advance have.

While the present invention has been described in connection with what is presently considered to be practical and exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

100: user terminal 200: source storage device
300: Build Automation Server 400: Deployment Device

Claims (8)

At least one user terminal that changes the source for software development while generating monitoring information through source creation monitoring;
A source storage device for receiving and storing a changed source from the user terminal; And
And a build automation server that generates and builds a source build unit using the monitoring information received from the user terminal and then builds and tests a source received from the source storage unit in the source build unit. The system of claim 1, wherein the build automation server
And a server control unit for receiving the monitoring information from the user terminal and analyzing the monitoring information to determine whether to generate the source build unit. At least one user terminal for changing a source for software development while generating monitoring information through source creation monitoring and generating a server generation request signal using the monitoring information;
A source storage device for receiving and storing a changed source from the user terminal; And
And a build automation server that generates and builds a source build unit using the server creation request signal received from the user terminal and then builds and tests a source received from the source storage unit in the source build unit, system. 4. The method of claim 3, wherein the user terminal
Generates the server creation request signal when it is determined that the source build unit needs to be generated by analyzing the monitoring information,
The build automation server
And a server controller for generating the source build unit in response to the server creation request signal received from the user terminal. At least one user terminal generates monitoring information through source creation monitoring and transmits the monitoring information to a server control unit of a build automation server;
Generating a source build unit using the monitoring information by the server control unit;
The user terminal generating the changed source and transmitting the changed source to the source storage device;
Transmitting the stored source to the source build unit after the source storage apparatus stores the changed source; And
Wherein the source build unit builds and tests the stored source. 6. The method of claim 5, wherein the server control unit
Analyzing the monitoring information to determine whether to generate the source build unit; And
And generating the server control unit according to an analysis result. The at least one user terminal generates a server creation request signal using the monitoring information generated through the source creation monitoring and transmits the server creation request signal to the server control section of the build automation server;
The server control unit generating a source build unit in response to the server generation request signal;
The user terminal generating the changed source and transmitting the changed source to the source storage device;
Transmitting the stored source to the source build unit after the source storage apparatus stores the changed source; And
Wherein the source build unit builds and tests the stored source. The method of claim 7, wherein the transmitting the server creation request signal to the server controller
Generating monitoring information through source creation monitoring while changing the source;
Analyzing the monitoring information to determine whether to generate the source build unit; And
And transmitting the server creation request signal to the server controller after generating the server creation request signal if it is determined that the source build unit needs to be generated.

Images