JP7189251B2 - Construction execution management device, construction execution management method, and program - Google Patents

Description

The present invention relates to technology for deploying software to devices.

CI/CD is one of software development techniques. CI/CD is an abbreviation of "Continuous Integration/Continuous Delivery", which means continuous integration/continuous delivery in Japanese.

CI/CD does not refer to a single technology, but refers to a software development method that constantly tests software changes and makes them automatically releasable to the production environment. "CD" is also sometimes used as an abbreviation for "continuous deployment." Continuous deployment is a very similar concept to continuous delivery, except that continuous delivery only prepares a state ready for deployment, while continuous deployment actually does the deployment to production.

https://www.ntt-tx.co.jp/column/cloudnative_days_tokyo_2019cicd/, searched on March 21, 2019

Regarding "Continuous Deployment", when deploying software in a commercial environment, Config information such as IP address is embedded in the software code. However, since the Config information differs for each user, it is necessary to manually embed appropriate values in the code at the time of deployment, which takes a lot of time and effort.

In addition, in order to prevent the user's business from stagnation, it is necessary to complete deployment or switchback within a fixed time even if trouble occurs, but if an error occurs in a certain process, the error location There is duplication of processing time in identifying and ensuring idempotence when re-executing, and it takes extra time.

Also, in order to proceed with prompt analysis when a problem occurs after construction, for example, as history management, it is conceivable to manually store config values and construction execution history for each user at the time of construction work in folders for each user. . However, with such a method, it is necessary to reflect and confirm the contents changed during construction each time, and it takes time for analysis.

In other words, in the conventional technology, construction work for deploying software to a construction target device could not be performed efficiently.

SUMMARY OF THE INVENTION The present invention has been made in view of the above points, and an object of the present invention is to provide a technique that enables efficient construction of deploying software to a construction target device.

According to the disclosed technology, a construction execution management device for executing construction for deploying software to a construction target device,
an information acquisition unit that acquires setting information from the construction target device;
an information management unit that reflects the setting information in the construction materials stored in the storage means;
a construction execution unit that executes construction on the construction target device using construction materials that reflect the setting information;
The information management unit creates a branch for the construction target device by copying a branch of the master code in the storage means, and reflects the setting information on the construction materials in the branch.
A construction execution management device is provided.

According to the disclosed technology, a technology is provided that enables efficient construction of deploying software to a construction target device.

1 is an overall configuration diagram of a system according to an embodiment of the present invention; FIG. It is a block diagram of a construction execution management apparatus. FIG. 10 is a sequence diagram for explaining the flow of processing; It is a figure which shows the example of the information stored in a construction material storage apparatus. It is a figure showing an example of a construction flow. It is a figure which shows the example of a construction flow. It is a figure which shows the hardware configuration example of an apparatus.

An embodiment (this embodiment) of the present invention will be described below with reference to the drawings. The embodiments described below are merely examples, and embodiments to which the present invention is applied are not limited to the following embodiments.

(System configuration example)
FIG. 1 shows an example of the overall configuration of a system according to this embodiment. As shown in FIG. 1, this system has a construction execution management device 100, a construction material storage device 200, a user terminal 300, and a construction target device 400. FIG. Each device is connected to a network and can communicate with each other.

The construction execution management apparatus 100 executes construction for the construction target apparatus 400 using the technology according to the present invention. In the present embodiment, “construction” refers to a series of processes for deploying software to the construction target device 400 . The construction execution management device 100 may be a device composed of one or more physical servers (computers), or may be a device composed of virtual machines on the cloud.

The construction material storage device 200 is a device that stores software and the like used for construction work. In this embodiment, software used for construction is called "construction material". The construction material storage device 200 also stores construction status and the like. The construction material storage device 200 may be a service on the cloud (eg Git) or a physical server. Also, the construction material storage device 200 may be a storage unit within the construction execution management device 100 . In the following description, it is assumed that the construction material storage device 200 is Git. The construction material storage device 200 may be called storage means.

The user terminal 300 is, for example, a terminal of a person who carries out construction work on the construction target apparatus 400, displays a GUI provided by the construction execution management apparatus 100, receives operations from the user, and issues instructions based on the user operations for construction execution management. Send to device 100 .

The construction target device 400 is a target device for deploying software. The work target device 400 is, for example, a device in a real machine environment that provides a network service for a user (company or the like). As shown in FIG. 1, the work target devices 400 are divided into groups for each user. In this embodiment, each group is called a tenant (abbreviated as TN). In the example of FIG. 1, three tenants (TN01, TN02, TN03) are shown.

(Configuration example of construction execution management device)
FIG. 2 shows an example of the functional configuration of the construction execution management device 100. As shown in FIG. As shown in FIG. 2 , the construction execution management device 100 has a GUI section 110 , an information acquisition section 120 , an information management section 130 and a construction execution section 140 .

A GUI unit 110 displays a GUI on the user terminal 300 . The GUI unit 110 may be a function operated by software in the construction execution management device 100, or may be a device such as a web server.

The information acquisition unit 120 acquires information such as Config information (setting information) from the work target device 400 . The information management unit 130 copies branches in the construction material storage device 200, acquires software (construction materials) from the construction material storage device 200, and sends construction execution history (construction status) and the like to the construction material storage device 200. Store.

The construction execution unit 140 uses construction materials acquired from the construction material storage device 200 to execute construction work on the construction target device 400 . The construction execution unit 140 also has a function of checking whether the construction work has been performed normally.

(operation sequence)
Next, an example of the operation sequence of the system according to this embodiment will be described with reference to FIG. First, it is assumed that a GUI is displayed on the user terminal 300 by the GUI unit 110 of the construction execution management device 100 . This GUI includes, for example, fields for inputting (or selecting) the type of construction work and the object of construction work.

The construction type includes, for example, software upgrade (“Verup”), software switchback to the previous version (“downgrade”), and the like. Also, in the present embodiment, the construction target is assumed to be a tenant unit. In other words, the tenant to be constructed is designated as the construction target.

In S101 of FIG. 3, the user designates the type of construction work and the object of construction work using the GUI, and the user terminal 300 instructs the construction execution management apparatus 100 to execute the construction work. Here, it is assumed that "upgrade" is specified as the construction type.

According to the instruction of S101, the construction execution management device 100 executes JOB1 and JOB2. JOB1 acquires Config information from the construction target device 400 of the specified tenant, clones the master code in the construction material storage device 200, customizes it using the Config information, and creates Git for the specified tenant. This is the procedure for creating a branch. JOB2 is a procedure for performing construction, updating construction status, and confirming after construction using construction materials in the designated tenant's branch.

In FIG. 3, S102 to S104 are shown as JOB1, and S105 to S107 are shown as JOB2. Each step will be described below.

In S102 and S103, the information acquisition unit 120 of the construction execution management device 100 sends a Config information acquisition request to the construction target device 400 of the designated tenant, and acquires the Config information from the construction target device 400.

In S104, the information management unit 130 transmits to the construction material storage device 200 a branch creation instruction for the specified tenant together with the Config information acquired in S103. As a result, the master code is duplicated in the construction material storage device 200, and a branch for the designated tenant is created. Also, the value of the Config information acquired in S103 is reflected in the Config information in the branch.

A branch indicates the structure of a directory in which data (here, programs and setting information that are construction materials) are stored. FIG. 4 shows an example of a master branch and a branch for a designated tenant created from the master branch in the construction material storage device 200 .

In the example of FIG. 4, the program under "(C) v2111_to_v2120" is a program for upgrading from v2111 to v2120, and the program under "(C) v2120_to_v2111" is for switching back from v2120 to v2111. program.

Programs under the "construction tool" are programs for construction (upgrade and cutback), and programs under the "check tool" are programs for checking whether the construction has been completed normally. .

The value of the Config information acquired from the construction target device 400 is reflected in the "hosts" and "Config" of the branch of the target tenant in FIG. Specifically, for example, the value of the Config information acquired from the construction target device 400 is given to the variable portions of “hosts” and “Config”.

In addition, in this embodiment, in order to easily grasp the construction details and construction process, one construction process is treated as one ticket and managed by the number of the ticket system. In this one ticket, the execution contents of each of "construction application (upgrade)" and "reverting (downgrade)" and progress management of construction material preparation are performed, and construction process management is performed for each ticket number. As a result, it is possible to confirm the contents of the work using a centralized ticket number in any phase, whether construction materials are being created, during construction, or after construction is complete.

In the example of FIG. 4, "2623", "2913", etc. described in each program name are examples of ticket numbers issued by the ticket system.

The construction execution management device 100 uses the program, setting information, and the like stored in the designated tenant's branch to perform construction, check, and the like for the construction target device 400 of the designated tenant.

In S105 of FIG. 3, the information management unit 130 of the construction execution management device 100 acquires construction materials (programs, setting information, etc.) of the specified tenant's branch from the construction material storage device 200. FIG. In S106, the construction execution unit 140 uses the construction materials to perform construction on the construction target device 400 and confirms whether the construction has been completed normally.

In S107, the information management unit 130 updates the construction status in the construction material storage unit 200 based on the construction progress. The construction status is information (status file) stored in the branch of the target tenant.

The setting information file (“hosts”, “Config”) customized by Job1 and the status file updated by Job2 are separate and exclusive files. As a result, the status information is not overwritten no matter how many times Job1 is executed.

As described with reference to FIG. 3, in this embodiment, only by the user specifying the construction type and construction target from the GUI and instructing execution, Job1 is automatically executed and the It is possible to execute Job2 using a branch in a series.

(Details of construction flow)
Next, a detailed example of the construction flow executed by the construction execution management device 100 will be described with reference to the flow charts of FIGS. 5 and 6. FIG. Here, assume that 2623 (ticket number) upgrades aaa (application name), and 2913 (ticket number) upgrades bbb (application name). Assume that "upgrade" is performed in the order of 2623→2913, and "downgrade" is performed in the order of 2913->2623.

<upgrade>
After the user specifies the construction target and the construction type, S201 in FIG. 5 is started. In S201, the information acquisition unit 120 executes Job1. That is, as described above, setting information is acquired from the construction target device 400 of the target tenant, a branch of the tenant is created in the construction material storage device 200, and the acquired setting information is reflected in the branch.

In S202, when Job2 with Verup specified starts to be executed, the information management unit 130 acquires construction materials for each construction process (with a ticket number of 1 process) from the branch of the specified tenant. In this example, a scenario file is obtained that describes "2623_up_aaa", "2913_up_bbb", and the execution order of the tickets for which construction work is to be performed. Here, the order of execution is 2623→2913.

When executing each construction process (ticket number), the construction execution unit 140 first confirms the construction status of that number via the information management unit 140 . The construction status is stored in the corresponding branch in the construction material storage device 200. FIG.

The construction status is managed by "Success" and "Fail". If a ticket number is set in "Success", it indicates that the construction of that ticket number was successful, and "Fail" indicates that the ticket If a number is set, it indicates that the work for that ticket number was carried out but failed in the middle. If the ticket number is not set for either "Success" or "Fail", it indicates that the construction has not yet been performed.

In the case of FIG. 5, that is, in the case of "construction application (upgrade)", as a result of checking the construction status, if the ticket number is not set to "Success" or is set to "Fail", If it is determined that the work has not been implemented or needs to be re-executed, the work will be processed. If the ticket number is set to "Success", it is determined that the work has been completed and succeeded, and the processing of the construction work with that ticket number is skipped.

Specifically, in S203 of FIG. 5, the construction execution unit 140 first confirms the construction status. If 2623 is set to "Success", proceed to the construction of the next ticket number. Run. If the construction is successful, 2623 is set in "Success" of the construction status of upgrade, and the construction of the next ticket number proceeds.

If the construction fails, 2623 is set to "Fail" in the upgrade construction status, and the process proceeds to S208.

In the construction of the next ticket number (2913) as well, the same processes as S203 and S204 are executed in S205 and S206.

However, since 2913 is the last ticket number here, if 2913 is in "Success" in S205, the process proceeds to S207 to check whether the construction work has been completed normally. If it is confirmed, the construction is finished, and if it is not confirmed that it was completed normally, the process proceeds to S208.

In S208, which is to be followed when the construction is unsuccessful or when normal completion is not confirmed, the cause of failure is manually checked. Note that the process of S208 may be automatically performed by using a tool for confirming the cause of failure.

If it is determined in S208 that the switchback should be performed, the process proceeds to the switchback process (FIG. 6). In the reprocessing after S202 at this time, according to the above-described logic, the work whose ticket number is set to "Success" is not executed, and the work whose ticket number is set to "Fail" is executed. Therefore, construction work can be carried out efficiently.

Although the ticket numbers have been set to "Success" for the construction work of all ticket numbers, if the process proceeds to S208 and proceeds to re-execution as a result of confirmation in S207, for example, the ticket set to "Success" Delete the number and try again.

<downgrade>
Next, the process of switchback when it is determined to perform switchback in FIG. 5 will be described with reference to FIG.

After the decision to switch back is made in S301, S302 of FIG. 6 is started. In S302, when execution of Job2 with downgrade specified starts, the information management unit 130 acquires construction materials for each construction process in downgrade (where the ticket number is 1 process) from the branch of the specified tenant. . In this example, a scenario file is obtained that describes "2913_down_bbb", "2623_down_aaa", and the execution order of tickets for which construction work is to be performed. Here, the order of execution is 2913→2623.

As in the case of upgrade, the construction execution unit 140 first confirms the construction status of that number via the information management unit 140 when executing each construction step (ticket number). In the case of FIG. 6, that is, in the case of "downgrade", if the ticket number is set to "Success" or "Fail", it is determined that switchback is necessary and processing is executed. . If the ticket number is not set in either "Success" or "Fail", it is determined that switchback is not necessary because it has not been performed, and the process is skipped.

Specifically, in S303 of FIG. 6, the construction execution unit 140 first confirms the construction status. If 2913 is not set to either "Success" or "Fail", proceed to construction of the next ticket number. 2913 is set to "Success" or "Fail", the process advances to S304 to execute downgrade construction. If the construction is successful, delete 2913 in the downgrade construction status and proceed to the construction of the next ticket number. If the construction in S304 fails, the process proceeds to S308.

In the construction of the next ticket number (2623) as well, the same processes as S303 and S304 are executed in S305 and S306.

However, since 2623 is the last ticket number here, if 2623 is neither "Success" nor "Fail" in S305, proceed to S307 to check whether the construction was completed normally. Then, if it is confirmed that the work has been completed normally, the construction is finished, and if it is not confirmed that it has been completed normally, the process proceeds to S308.

In S308, which is to be followed when the construction is unsuccessful or when normal completion is not confirmed, the cause of failure is manually checked. Note that the process of S308 may be automatically performed by using a tool for confirming the cause of failure.

If it is determined in S308 that re-execution is not possible, manual handling is performed in S309. If it is determined to continue the construction by re-executing the construction of the failed portion, the process returns to S302. At this time, in the reprocessing after S302, according to the above-described logic, the construction for which the ticket number is not set in either "Success" or "Fail" is not executed, and the ticket number is not set in "Success" or "Fail". The set work is carried out. Therefore, construction work can be carried out efficiently.

It should be noted that although the ticket number is not set for both "Success" and "Fail", as a result of confirmation in S307, if the process proceeds to S308 and proceeds to re-execution, for example, "Success" and "Fail" After returning the ticket number to the initial state (state at S301), the work is re-executed.

Each pattern that can occur when construction is performed according to the logic shown in FIGS. 5 and 6 will be described below.

<Pattern 1: 2623 and 2913 succeed>
Execution of construction type “upgrade” ・Execution of 2623 (success) → 2623 added to “Success” ・Execution of 2913 (success) → 2913 added to “Success” finish.

<Pattern 2: 2623 first failure, re-execution success, 2913 success>
Execution of construction type “upgrade” Execution of 2623 (failure) → Add 2623 to “Fail” Confirm the cause of the failure, and if it is decided that re-execution is OK, the construction worker will use the same execution method as the first execution. carry out construction work in

Execution of construction type "upgrade" ・2623 execution (success) → 2623 deleted from "Fail", 2623 added to "Success" ・2913 execution (success) → 2913 added to "Success" The ticket number is entered, and the construction is completed safely.

<Pattern 3: 2623 succeeds, 2913 fails, re-executes>
Execution of construction type “upgrade” ・Execution of 2623 (success) → 2623 added to “Success” ・Execution of 2913 (failure) → 2913 added to “Fail” Confirmed the cause of the failure and decided to re-execute Execution of construction type "upgrade" ・2623Skip
Execution of 2913 (Success) → Delete 2913 from "Fail" and add 2913 to "Success" Finally, all ticket numbers are entered only in "Success", and the construction is successfully completed.

<Pattern 4: Failed at 2623, execute switchback>
● Execution of construction type “upgrade” ・Execution of 2623 (failure) → 2623 added to “Fail” ● After confirming the cause of the failure and making a decision to revert, the contractor sets the construction type to “downgrade” Execution of construction type “downgrade” ・2913Skip
Execution of 2623 (success) → Deletion of 2623 from “Fail” Finally, all ticket numbers are neither Success nor Fail, and the switchback is completed.

<Pattern 5: 2623 succeeds, but 2913 fails and switches back>
Execution of construction type "upgrade" ・Execution of 2623 (success) → 2623 added to "Success" Execution of 2913 (failure) → 2913 added to "Fail" Confirm the cause of the failure, and when it is decided to switch back, The construction worker sets the construction type to “downgrade” and executes the construction. Execution of construction type “downgrade” ・Execution of 2913 (success) → Delete 2913 from “Fail” ・Execution of 2623 (success) → “Success” 2623 is deleted from Ultimately, all ticket numbers are neither Success nor Fail, and switchback is completed.

As described above, in this embodiment, the construction worker can execute the construction by specifying only the "construction type" and "construction target". Therefore, even if the process fails in the middle and "re-execute" or "revert" is executed, it can be executed in the same procedure without manually changing the execution content, and efficient execution is possible. is.

Also, even if the construction material is idempotent (even if the same operation is performed multiple times, the result after execution will be the same), the process will be skipped like pattern 3 and pattern 4. As a result, the construction time can be shortened.

Also, when confirming the implementation details after the construction work, by checking the branch for each user, it is possible to easily confirm the "construction implementation details (Config, materials)" and the "construction execution result (status)".

(Hardware configuration example)
The construction execution management device 100 can be implemented by, for example, causing a computer to execute a program. This computer may be a physical computer or a virtual machine on the cloud.

That is, the construction execution management device 100 can be realized by executing a program corresponding to the processing performed by the construction execution management device 100 using hardware resources such as a CPU and memory built into the computer. is. The above program can be recorded in a computer-readable recording medium (portable memory, etc.), saved, or distributed. It is also possible to provide the above program through a network such as the Internet or e-mail.

FIG. 7 is a diagram showing a hardware configuration example of the computer. The computer of FIG. 7 has a drive device 1000, an auxiliary storage device 1002, a memory device 1003, a CPU 1004, an interface device 1005, a display device 1006, an input device 1007, an output device 1008, etc., which are interconnected by a bus BS. Note that some of these devices may not be provided. For example, the display device 1006 may not be provided when no display is performed.

A program for realizing processing by the computer is provided by a recording medium 1001 such as a CD-ROM or a memory card, for example. When the recording medium 1001 storing the program is set in the drive device 1000 , the program is installed from the recording medium 1001 to the auxiliary storage device 1002 via the drive device 1000 . However, the program does not necessarily need to be installed from the recording medium 1001, and may be downloaded from another computer via the network. The auxiliary storage device 1002 stores installed programs, as well as necessary files and data.

The memory device 1003 reads and stores the program from the auxiliary storage device 1002 when a program activation instruction is received. The CPU 1004 implements functions related to the construction execution management apparatus 100 according to programs stored in the memory device 1003 . The interface device 1005 is used as an interface for connecting to a network and functions as a transmitter and a receiver. A display device 1006 displays a program-based GUI (Graphical User Interface) or the like. An input device 1007 is composed of a keyboard, a mouse, buttons, a touch panel, or the like, and is used to input various operational instructions. The output device 1008 outputs the calculation result.

(Summary of Embodiments, Effect)
As described above, the technology according to this embodiment mainly has the following three points.

(1) The construction execution management device 100 has a function of acquiring Config information on demand and a function of duplicating and customizing the master code. The function of acquiring Config information automatically acquires information necessary for application from the actual machine environment immediately before application to the production environment. The copy & customize function copies (clone) the code of the master branch of Git, and gives Config the information of the actual machine environment acquired in the previous stage to the variable part of the copied code. Furthermore, by creating a branch for each user environment, it is possible to manage Config and construction history limited to each user.

With these functions, it is possible to automatically create construction tools customized for individual users without affecting the code management of the master, so optimal automatic construction can be performed while minimizing operation and human error . In addition, when checking the construction history after construction is completed, the construction execution history is updated from Config generation without manual intervention. It allows instant confirmation.

(2) By automatically managing the process during deployment, even if an unexpected error occurs, the status of each code process is managed to improve the efficiency of isolating the error location and automatically determine the necessary status when re-executing. Since construction can be started or cut back from the point, it is possible to shorten the construction time when an unexpected error occurs.

(3) In order to easily grasp the construction details and construction process, one construction process is treated as one ticket, and managed by ticket system numbers. In this one ticket, the execution contents of each of "construction application (upgrade)" and "reverting (downgrade)" and progress management of construction material preparation are performed, and construction process management is performed for each ticket number. As a result, it is possible to confirm the contents of the work using a centralized ticket number in any phase, whether construction materials are being created, during construction, or after construction is complete.

From the above, it is possible to eliminate human errors in construction preparation operation, during construction, and construction management, and to complete construction within a predetermined time. Furthermore, it becomes possible to confirm the details of the construction work accurately and quickly after the construction work.

(Appendix)
This specification describes at least a construction execution management device, a construction execution management method, and a program described in each of the following items.
(Section 1)
A construction execution management device for executing construction for deploying software to a construction target device,
an information acquisition unit that acquires setting information from the construction target device;
an information management unit that reflects the setting information in the construction materials stored in the storage means;
A construction execution management device comprising: a construction execution unit that executes construction for the construction target device using construction materials reflecting the setting information.
(Section 2)
3. The construction execution according to claim 1, wherein the information management unit creates a branch for the construction target device by copying a branch of the master code in the storage means, and reflects the setting information in the construction materials in the branch. management device.
(Section 3)
A ticket number is assigned to each construction process performed using the construction material, and the information management unit manages the construction status based on the ticket number. management device.
(Section 4)
The information management unit sets the ticket number to the information indicating success in the construction status when the construction work with a certain ticket number succeeds, and sets the failure in the construction status when the construction work with a certain ticket number fails. The construction execution management device according to item 3, wherein the ticket number is set in the indicated information.
(Section 5)
Item 4. The construction work according to item 4, wherein when executing the construction work with a certain ticket number, if the ticket number is attached to the information indicating success in the construction status, the construction work execution unit skips the construction work. Work management unit.
(Section 6)
When executing the switchback of the construction work of a certain ticket number, if the ticket number is not set in either the information indicating success or the information indicating failure in the construction status, the construction execution unit The construction execution management device according to item 4 or 5, which skips switching back.
(Section 7)
A construction execution management method in a construction execution management device for executing construction for deploying software to a construction target device, comprising:
a step of acquiring setting information from the construction target device;
a step of reflecting the setting information in the construction materials stored in the storage means;
A construction execution management method comprising the step of executing construction for the construction target device using construction materials reflecting the setting information.
(Section 8)
A program for causing a computer to function as each unit in the construction execution management device according to any one of items 1 to 6.

Although the present embodiment has been described above, the present invention is not limited to such a specific embodiment, and various modifications and changes can be made within the scope of the gist of the present invention described in the claims. It is possible.

100 construction execution management device 110 GUI unit 120 information acquisition unit 130 information management unit 140 construction execution unit 200 construction material storage device 300 user terminal 400 construction target device 1000 drive device 1001 recording medium 1002 auxiliary storage device 1003 memory device 1004 CPU
1005 interface device 1006 display device 1007 input device 1008 output device

Claims (8)

A construction execution management device for executing construction for deploying software to a construction target device,
an information acquisition unit that acquires setting information from the construction target device;
an information management unit that reflects the setting information in the construction materials stored in the storage means;
a construction execution unit that executes construction on the construction target device using construction materials that reflect the setting information;
The information management unit creates a branch for the construction target device by copying a branch of the master code in the storage means, and reflects the setting information on the construction materials in the branch.
Construction execution management device. The construction execution management device according to claim 1 , wherein a ticket number is assigned to each construction process performed using the construction material, and the information management unit manages the construction status based on the ticket number. The information management unit sets the ticket number to the information indicating success in the construction status when the construction work with a certain ticket number succeeds, and sets the failure in the construction status when the construction work with a certain ticket number fails. The construction execution management device according to claim 2 , wherein the ticket number is set in the indicated information. 4. The construction work according to claim 3 , wherein when executing construction work with a certain ticket number, the construction execution unit skips the construction work if the ticket number is attached to information indicating success in the construction status. Work management unit. A construction execution management device for executing construction for deploying software to a construction target device,
an information acquisition unit that acquires setting information from the construction target device;
an information management unit that reflects the setting information in the construction materials stored in the storage means;
a construction execution unit that executes construction on the construction target device using construction materials that reflect the setting information.
A ticket number is assigned to each construction process performed using the construction material, and the information management unit manages the construction status based on the ticket number,
The information management unit sets the ticket number to the information indicating success in the construction status when the construction work with a certain ticket number succeeds, and sets the failure in the construction status when the construction work with a certain ticket number fails. Set the ticket number in the information shown,
When executing the switchback of the construction work of a certain ticket number, if the ticket number is not set in either the information indicating success or the information indicating failure in the construction status, the construction execution unit skip switchback of
Construction execution management device. A construction execution management method in a construction execution management device for executing construction for deploying software to a construction target device, comprising:
an information acquisition step of acquiring setting information from the construction target device;
an information management step of reflecting the setting information in the construction materials stored in the storage means;
a construction execution step of executing construction for the construction target device using construction materials reflecting the setting information;
In the information management step, a branch for the construction target device is created by copying a branch of the master code in the storage means, and the setting information is reflected in the construction materials in the branch.
Construction execution management methods. A construction execution management method in a construction execution management device for executing construction for deploying software to a construction target device, comprising:
an information acquisition step of acquiring setting information from the construction target device;
an information management step of reflecting the setting information in the construction materials stored in the storage means;
a construction execution step of executing construction for the construction target device using construction materials reflecting the setting information;
A ticket number is assigned to each construction process performed using the construction material, and in the information management step, the construction status is managed based on the ticket number,
In the information management step, when the construction of a certain ticket number succeeds, the ticket number is set as information indicating success in the construction status, and when the construction of a certain ticket number fails, the failure in the construction status is set. Set the ticket number in the information shown,
In the construction execution step, if the ticket number is not set in either the information indicating success or the information indicating failure in the construction status when executing the switchback of the construction work with a certain ticket number, the construction work is performed. skip switchback of
Construction execution management methods. A program for causing a computer to function as each unit in the construction execution management device according to any one of claims 1 to 5 .

Images