CN107608710B - Software project construction task configuration method and device based on Jenkins tool - Google Patents
Software project construction task configuration method and device based on Jenkins tool Download PDFInfo
- Publication number
- CN107608710B CN107608710B CN201710773700.8A CN201710773700A CN107608710B CN 107608710 B CN107608710 B CN 107608710B CN 201710773700 A CN201710773700 A CN 201710773700A CN 107608710 B CN107608710 B CN 107608710B
- Authority
- CN
- China
- Prior art keywords
- target
- jenkins
- task
- software
- construction task
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The method comprises the steps of compiling a construction task configuration file of a software project according to a developer, automatically configuring system resources (namely, a system environment) required by running a construction task according to the construction task configuration file, and automatically mounting the system resources to a Jenkins host. And automatically configuring software and Jenkins plug-ins depended by the construction tasks according to the dependency relationship in the construction task configuration file, and finally automatically creating the Jenkins construction tasks according to task definitions in the construction task configuration file. The user only needs to maintain the configuration file of the construction task, and the other processes automatically perform configuration and creation of the construction task by automatically analyzing the configuration file of the construction task by the system without the operation of the user on a graphical interface, so that the operation is simple and the efficiency is high; moreover, the user only needs to maintain and construct the task configuration file, and the maintenance cost is low.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a software project construction task configuration method and device based on Jenkins tools.
Background
In the Continuous Integration (CI), update codes are frequently integrated into a main program in a software project development phase, specifically, after a developer submits codes of update points, construction (i.e., compiling and packaging) and a first round of test are immediately performed, and whether the update point codes and the main codes can be correctly integrated is determined according to a test result, so that the developer is helped to quickly find errors, products can be quickly iterated, and high quality of the products is ensured. Jenkins is one of the commonly used construction tools.
The task scheme of the current Jenkins construction needs the following steps for creating a construction project:
1) establishing a construction project in a Jenkins master (on the premise that the Jenkins master exists);
2) installing and constructing Jenkins plug-ins which are task dependent;
3) applying for a virtual machine, a container or a bare machine of a specified mirror image required by a construction task;
4) installing software necessary for constructing tasks on a virtual machine, a container or a bare machine;
5) mounting a virtual machine, a container or a bare machine on a Jenkins master;
6) establishing a construction task, configuring the construction step, mainly comprising configuring nodes of the construction task, compiling a construction script, and adding the construction step;
7) if one software project comprises a plurality of construction tasks and one software project comprises a plurality of projects, the steps 1) to 6) are repeatedly executed.
Each step of the existing Jenkins construction task scheme needs to be manually configured on a Jenkins graphical interface by developers, and the operation is complex and the efficiency is low; moreover, the greater the number of software items, the greater the difficulty of maintenance.
The Jenkins backup or migration scheme has the same problem as the Jenkins construction task, and developers need to manually configure what needs to be backed up on a graphical interface of Jenkins.
Disclosure of Invention
In view of the above, the present invention provides a software project construction task configuration method and device based on Jenkins tool, so as to solve the technical problem that manual configuration must be performed on a Jenkins graphical interface when the existing Jenkins tool creates construction task, backups and migrates, and the technical scheme is as follows:
in a first aspect, the present application provides a software engineering configuration method based on Jenkins tool, including: when the code change of a code warehouse of a target software project is monitored, acquiring a target construction task configuration file corresponding to the target software project; analyzing the target construction task configuration file to obtain target system resources, dependency relationships and task definitions required by the construction task, wherein the target system resources comprise: the machine type, the machine specification and the operating system are depended on by the construction task, and the machine type comprises a virtual machine, a container, a bare metal or a physical machine; the dependency relationship is used for explaining software and Jenkins plug-ins on which the construction tasks depend; the task defines a build step and a trigger time for defining the build task; configuring a system resource matched with the target system resource; according to the dependency relationship, configuring target software and a target Jenkins plug-in which the construction task depends in the current system environment; and generating a construction task according to the task definition.
According to the software engineering configuration method based on the Jenkins tool, system resources (namely, system environment) required by running a construction task are automatically configured according to a construction task configuration file of a software project written by a developer, and the system resources are automatically mounted on a Jenkins host. And automatically configuring software and Jenkins plug-ins depended by the construction tasks according to the dependency relationship in the construction task configuration file, and finally, automatically creating the Jenkins construction tasks. The whole process automatically completes the configuration and the creation of the construction task by automatically analyzing the construction task configuration file by the system without the operation of a user on a graphical interface, and the method is simple to operate and high in efficiency.
In a possible implementation manner of the first aspect, the configuring a system resource that matches the target system resource includes: searching whether the target system resource exists in the current system environment; if the target system resource exists in the current system environment, executing a step of configuring software and Jenkins plug-ins on which the construction task depends in the current system environment according to the dependency relationship; and if the target system resource does not exist in the current system environment, creating the target system resource, and then executing the step of configuring the software and the Jenkins plug-in which the construction task depends in the current system environment according to the dependency relationship.
The software engineering configuration method based on the Jenkins tool can automatically search or create the system resource matched with the target system resource according to the target system resource appointed in the construction task configuration file.
In another possible implementation manner of the first aspect, the configuring, according to the dependency relationship, software and Jenkins plug-ins that the build task depends on in a current system environment includes: searching whether the target software is installed in the current operating system; if the target software is not installed in the current operating system, acquiring the target software according to a download address of the target software contained in the target construction task configuration file, and installing the target software; if the target software is installed in the current operating system, continuously searching whether the Jenkins tool is provided with the target Jenkins plug-in or not; if the target Jenkins plug-in is not installed in the Jenkins tool, acquiring the target Jenkins plug-in according to a download address of the target Jenkins plug-in contained in the target construction task configuration file, and installing the target Jenkins plug-in; and if the target Jenkins plug-in is installed in the Jenkins tool, determining that the target software and the target Jenkins plug-in are installed in the current system environment.
According to the software engineering configuration method based on the Jenkins tool, the target software and the target Jenkins can be automatically installed according to the target software and the target Jenkins plug-in which the specified construction tasks depend in the construction task configuration file, namely, the dependency relationship is automatically solved according to the construction task configuration file.
In another possible implementation manner of the first aspect, the generating a build task according to the task definition includes: creating or updating the construction task according to the task definition; and mounting the target system resource to a Jenkins host to run the construction task.
The software engineering configuration method based on the Jenkins tool can automatically create or update the construction tasks according to the task definitions in the construction task configuration file.
In yet another possible implementation manner of the first aspect, the method further includes: monitoring the running state of the Jenkins tool and monitoring the running state of the current operating system; when the running state of the current operating system is abnormal, generating alarm information; and when the operation state of the Jenkins tool is that the target system resource is disconnected, re-mounting the target system resource to the Jenkins host.
The software engineering configuration method based on the Jenkins tool provided by the implementation mode monitors the running state of the Jenkins tool and the running state of the current operating system in real time, and automatically generates alarm information after monitoring the state abnormity so as to provide a user to timely handle the abnormity. And when the target system resource running the current construction task is disconnected, the target system resource is mounted on the Jenkins host again.
In yet another possible implementation manner of the first aspect, the method further includes: and converting the created construction task into an initial construction task configuration file corresponding to the created construction task, wherein the initial construction task configuration file comprises a task definition corresponding to the created task, and system resources and software resources in the current system environment.
In a second aspect, the present application further provides a software engineering configuration apparatus based on Jenkins tool, including: the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring a target construction task configuration file corresponding to a target software project when the code change of a code warehouse of the target software project is monitored; the analysis unit is used for analyzing the target construction task configuration file to obtain target system resources, dependency relationships and task definitions required by the construction task, wherein the target system resources comprise: the machine type, the machine specification and the operating system are depended on by the construction task, and the machine type comprises a virtual machine, a container, a bare metal or a physical machine; the dependency relationship is used for explaining software and Jenkins plug-ins on which the construction tasks depend; the task defines a build step and a trigger time for defining the build task; the first configuration unit is used for configuring the system resource matched with the target system resource; the second configuration unit is used for configuring the target software and the target Jenkins plug-in which the construction task depends in the current system environment according to the dependency relationship; and the task generating unit is used for generating a construction task according to the task definition.
In a possible implementation manner of the second aspect, the first configuration unit includes: the first searching subunit is used for searching whether the target system resource exists in the current system environment; when the target system resource exists in the current system environment, the second configuration unit executes software and Jenkins plug-ins which depend on the construction task and are configured in the current system environment according to the dependency relationship; a creating subunit, configured to create the target system resource when the target system resource does not exist in the current system environment.
In another possible implementation manner of the second aspect, the second configuration unit includes: the second searching subunit is used for searching whether the target software depended by the construction task is installed in the current operating system; a first obtaining subunit, configured to, when the target software is not installed in the current operating system, obtain the target software according to a download address of the target software included in the target construction task configuration file, and install the target software; a third searching subunit, configured to, when the target software is installed in the current operating system, continue to search whether the Jenkins tool is installed with the target Jenkins plug-in; the second obtaining subunit is used for obtaining the target Jenkins plug-in according to the download address of the target Jenkins plug-in contained in the target construction task configuration file when the target Jenkins plug-in is not installed in the Jenkins tool, and installing the target Jenkins plug-in; and the first determining subunit is used for determining that the target software and the target Jenkins plug-in are installed in the current system environment when the target Jenkins plug-in is installed in the Jenkins tool.
In yet another possible implementation manner of the second aspect, the task generating unit includes: the task generation subunit is used for creating or updating the construction task according to the task definition; and the mounting subunit is used for mounting the target system resource to a Jenkins host so as to run the construction task.
In yet another possible implementation manner of the second aspect, the method further includes: the monitoring unit is used for monitoring the running state of the Jenkins tool and the running state of the current operating system; the alarm unit is used for generating alarm information when the running state of the current operating system is abnormal; and the re-mounting unit is used for re-mounting the target system resource to the Jenkins host when the operation state of the Jenkins tool is that the target system resource is disconnected.
In yet another possible implementation manner of the second aspect, the method further includes: the configuration file generating unit is used for converting the created construction task into an initial construction task configuration file corresponding to the created construction task, wherein the initial construction task configuration file comprises a task definition corresponding to the created task, and system resources and software resources in the current system environment.
In a third aspect, the present application further provides a computer device, where the computer device includes a processor and a memory, where the memory stores program instructions, and the processor implements the method described in any one of the possible implementation manners of the first aspect by executing the stored instructions in the memory.
In a fourth aspect, the present application further provides a computer-readable storage medium having stored therein instructions, which, when executed on a computer, cause the computer to perform the method according to any one of the possible implementation manners of the first aspect.
In a fifth aspect, the present application further provides a computer program product containing instructions that, when executed on a computer, cause the computer to perform the method according to any one of the possible implementation manners of the first aspect.
According to the software project construction task configuration method based on the Jenkins tool, developers write construction task configuration files of the software project, then system resources (namely, system environment) needed by running construction tasks are automatically configured according to the construction task configuration files, and the system resources are automatically mounted on a Jenkins host. And automatically configuring software and Jenkins plug-ins depended by the construction tasks according to the dependency relationship in the construction task configuration file, and finally automatically creating the Jenkins construction tasks according to task definitions in the construction task configuration file. The user only needs to maintain the configuration file of the construction task, and the other processes automatically perform configuration and creation of the construction task by automatically analyzing the configuration file of the construction task by the system without the operation of the user on a graphical interface, so that the operation is simple and the efficiency is high; moreover, the user only needs to maintain and construct the task configuration file, and the maintenance cost is low.
Drawings
FIG. 1 is a schematic diagram of a Jenkins system according to an embodiment of the present application;
FIG. 2 is a flowchart of a software project construction task configuration method based on Jenkins according to an embodiment of the present application;
FIG. 3 is a block diagram of a task configuration device for software project construction based on Jenkins according to an embodiment of the present application;
FIG. 4 is a block diagram of another task configuration device based on Jenkins software project construction according to an embodiment of the present application;
FIG. 5 is a block diagram of a software engineering configuration apparatus based on Jenkins tool according to another embodiment of the present application;
FIG. 6 is a block diagram of a computer device according to an embodiment of the present application.
Detailed Description
Each step of the traditional Jenkins construction task scheme needs to be manually configured on a Jenkins graphical interface by developers, and the operation is complex and the efficiency is low. According to the software project construction task configuration method based on the Jenkins tool, developers compile corresponding construction task configuration files for software projects, and then the Jenkins tool can configure system resources on which construction tasks depend according to the construction task configuration files; and automatically installing operating system software and Jenkins plug-ins which depend on the construction tasks according to the construction task configuration file, and finally automatically creating the construction tasks according to task definitions in the construction task configuration file. The establishment process of the construction task is automatically completed, a user does not need to perform any operation on a graphical interface, and the method is simple to operate and high in efficiency. Moreover, the user only needs to maintain and construct the task configuration file, and the maintenance cost is low.
Referring to fig. 1, a schematic diagram of a Jenkins system according to an embodiment of the present application is shown. As shown in fig. 1, the system includes: the system comprises a code warehouse, a management tool, a monitoring alarm service, a resource management service, a dependence management service, an engineering task management service, an engineering import service and a Jenkins cluster;
the Jenkins cluster includes a plurality of Jenkins masters and a plurality of Jenkins slave. The Jenkins master is used for managing each Jenkins slave, and each Jenkins slave is used for executing the creation and running work of the construction task.
The monitoring alarm service, the resource management service, the dependency management service, the engineering task management service and the engineering import service are software service names defined for convenience of description. The service name may not be defined in other embodiments of the present application.
The code warehouse is used for storing codes of the software projects submitted by developers and construction task configuration files corresponding to the software projects. The core of the method is a construction task configuration file of the software project, and the construction task configuration file defines system resources, dependency relations and task definitions of construction engineering dependence.
System resources on which engineering depends include dependent machine types, e.g., virtual machines, containers, bare machines, physical machines; mirror names or container names, such as centros 7.1, suse 11sp3, may also be custom mirrors, etc. For example, the specifications of the machine may be: high IO, compute intensive, 4U8G (i.e., CPU has 4 cores, memory is 8G), etc. Mirroring in this context refers to operating system mirroring.
The dependency relationship refers to that the name and the version number of software and the name and the version number of a Jenkins plug-in need to be respectively defined when operating system software and the Jenkins plug-in which tasks depend are constructed.
The task definition is a core part of the construction task, and defines steps, trigger time and the like of the construction task.
The monitoring alarm service is mainly responsible for monitoring the code change condition in the code warehouse, and when the code of the code warehouse changes, the construction task configuration file corresponding to the changed software project is injected into Jenkins to create or update the construction task.
The monitoring alarm service also monitors the running state of the construction task and the running state of the Jenkins current system in real time, once the running state of the construction task, the disk state of the current system, the CPU state and the IO state are found, alarms can be generated, and if the Jenkins slave node running the construction task is found to be disconnected, the resource management service of the management tool is informed to mount the Jenkins slave node again.
The resource management service is primarily responsible for creating the machines needed by the user to run the build tasks.
The dependency management service is mainly responsible for installing software and Jenkins plug-ins on which the construction tasks depend according to the dependency relationship in the construction task configuration file.
The project task management service is mainly responsible for mounting machines required by task operation on Jenkins master nodes, and injecting projects in the constructed task configuration files into Jenkins to generate Jenkins tasks.
The project import service mainly converts the existing Jenkins tasks in the system into a construction task configuration file, can identify operating system software and Jenkins plug-ins installed in the current system, and converts the construction task steps in Jenkins into task definitions in the construction task configuration file. This service applies to the following scenarios: the build task has been created using a traditional Jenkins tool, and then the built task is imported into the improved Jenkins provided by the present application.
Referring to fig. 2, a flowchart of a software project construction task configuration method based on Jenkins tool in the embodiment of the present application is shown, and the embodiment of the present application describes in detail a software project construction task automation creation process in combination with the Jenkins system framework shown in fig. 1.
S110, monitoring whether a construction task configuration file corresponding to a target software project in the alarm service monitoring code warehouse changes; if so, executing S120; if not, the current flow is ended.
A target item of software refers to any item of software. The code warehouse comprises software codes of the software projects and a construction task configuration file, and when the construction task configuration file changes, the execution of the method flow is triggered.
The software project developer writes a construction task configuration file according to the requirements of the software project, and the file specifies the dependent system resources, the dependency relationship and the task definition of the construction task. The build task profile is then stored in a code repository.
The monitoring alarm service can monitor the entry event when a user enters new code or builds a task profile in the code repository. Wherein the monitoring alarm service may detect whether there is a change in the code repository at preset time intervals (e.g., 30 s).
And S120, the management tool acquires a target construction task configuration file corresponding to the target software project.
When the monitoring alarm service monitors that the code warehouse changes, the monitoring alarm service notifies management to download software codes and constructs a task configuration file, and judges the changed part.
In an implementation manner of the present application, the management tool downloads all software codes and configuration files of the target software project from the server, and compares the downloaded software codes and configuration files with the locally stored software codes and configuration files, so as to obtain a changed part finally.
In another implementation of the present application, the management tool may request the changed part from the server through the interface, and may download the changed part to the local.
For example, the change of the construction task configuration file includes the following two cases: and newly adding a construction task configuration file corresponding to the target software project, or updating the construction task configuration file corresponding to the target software project.
And S130, the management tool constructs a task configuration file according to the latest target in the code warehouse and analyzes to obtain the dependency relationship, the target system resource and the task definition. The management tool sends the target system resource to the resource management service, sends the dependency relationship to the dependency management service, and sends the task definition to the engineering task management service.
S140, the resource management service checks whether the target system resource exists in the current system, and if the target system resource does not exist, S150 is executed; if so, S160 is performed.
In an embodiment of the present application, the resource management service first checks whether a specified target system resource exists in the current system environment, and if the specified specification and the system resource of the specified mirror exist, further checks whether the resources are enough (whether the specified specification and the system resource of the specified mirror in the system match with the target system resource specified in the build task configuration file, for example, if the capacity of the specified disk is 100G, then judges whether the resources available in the system are not less than 100G), and if not, then determines that the target system resource does not exist. And if the specified specification and the specified mirror image system resources are sufficient, determining that the target system resources exist in the current system environment.
S150, the resource management service creates the target system resource.
For example, a virtual machine of a specified specification, a specified image is automatically created, and the created virtual machine is mounted on a Jenkins host.
Constructing the system resources specified in the task configuration file includes: the type of machine required (e.g., virtual machine, container, bare machine, physical machine), the operating system relied upon, the machine specification, etc.
It should be noted that, the process implemented by the two steps S140 and S150 is a process of configuring a system resource matching the target system resource.
The created target system resource is the Jenkins slave node in the Jenkins cluster, in other words, the target system resource is the Jenkins slave node herein.
S160, the dependency management service checks whether the target software on which the construction task depends is installed in the current operating system according to the dependency relationship; if so, executing S180; if not, executing S170;
the current system environment comprises an operating system and a Jenkins tool, wherein the process of detecting whether target software and a target Jenkins plug-in are configured in the current system environment comprises the following steps: whether target software is installed in the current operating system or not is detected, and whether a target Jenkins plug-in is installed in the Jenkins tool or not is detected.
S170, the dependence management service acquires the target software according to the download address of the target software contained in the target construction task configuration file, and installs the target software.
The Jenkins system has different application scenes and different corresponding download addresses; for example, when the Jenkins system is installed in a local area network, the software on which Jenkins depends is downloaded from the corresponding official software warehouse of the software to the local area network, and the download address is a path for storing the target software in the local area network.
For example, the system where the Jenkins system is located can be directly connected with the official software warehouse of the software, and in such an application scenario, the download address of the target software is the link of the official software warehouse corresponding to the target software.
S180, checking whether a target Jenkins plug-in is installed in the current Jenkins tool or not depending on management service; if not, executing S190; if so, S200 is performed.
The method comprises the step of detecting whether a target Jenkins plug-in is installed in a Jenkins tool.
And S190, acquiring the target Jenkins plug-in according to the download address of the Jenkins plug-in contained in the target construction task configuration file by the dependence management service, and installing the target Jenkins plug-in.
And the process realized by S160-S190 is a process of configuring and constructing target software and a target Jenkins plug-in which the task depends in the current system environment according to the dependency relationship.
S200, the engineering task management service mounts the target system resource to a Jenkins master.
The target system resource is the Jenkins slave node in fig. 1, and the mounting of the target system resource on the Jenkins host is to establish communication connection between the Jenkins slave node and the Jenkins master node.
In an embodiment of the application, the Jenkins slave node can be mounted on the Jenkins master immediately after the Jenkins slave node is created; in another embodiment of the present application, after a build task is created or updated, the Jenkins slave node running the build task may be mounted on the Jenkins master.
S210, the project management task creates a construction task according to the task definition in the target construction task configuration file.
The project management task injects the task definition into Jenkins to generate a construction task, and the existing service is not interrupted in the process, namely Jenkins do not need to be turned off.
The process implemented by S200 and S210 is a build task process generated from task definitions.
Optionally, the software engineering configuration method based on Jenkins tool provided in this embodiment may further include the following steps:
s220, monitoring the running state of Jenkins by the alarm service, and monitoring the running state of the current operating system;
the running state of the current operating system comprises a disk state, a CPU state, an IO state and the like. The operation state of Jenkins refers to the operation state of Jenkins slave nodes for operating the construction tasks.
The monitoring alarm service monitors the construction task and the Jenkins state in real time through an interface service provided by the engineering management service.
And S230, generating alarm information when the running state of the current operating system is abnormal.
Once the monitoring alarm service finds that the running state, the disk state, the CPU state and the IO state of the current operating system are abnormal, alarm information is generated, and the alarm information is displayed to a user on a graphical interface; for example, the disk capacity is lower than a predetermined value, the CPU occupancy is higher than a predetermined value, and the IO occupancy is higher than a predetermined value.
S240, when the Jenkins slave node running the construction task is disconnected, the resource management service mounts the Jenkins slave node to the Jenkins master again.
And if the monitoring alarm service monitors that the Jenkins slave node running the construction task is disconnected, the resource management service is informed to mount the node again.
In addition, for the construction tasks which are already created in the traditional Jenkins tool, the method provided by the application can also be converted into corresponding initial construction task configuration files according to the already created construction tasks. Specifically, the corresponding task definition may be obtained according to the built task that has been created. And acquiring all software installed in the current system environment and all Jenkins plug-ins installed in the Jenkins tool. The user can write and obtain the final construction task configuration file corresponding to the established construction task on the basis of the initial construction task configuration file, so that the burden of software developers is reduced.
According to the software engineering configuration method based on the Jenkins tool, a developer writes a construction task configuration file of a software project, then system resources (namely, a system environment) required by running a construction task are automatically configured according to the construction task configuration file, and the system resources are automatically mounted on a Jenkins host. And automatically configuring software and Jenkins plug-ins depended by the construction tasks according to the dependency relationship in the construction task configuration file, and finally, automatically creating the Jenkins construction tasks. The whole process automatically completes the configuration and the creation of the construction task by automatically analyzing the construction task configuration file by the system without the operation of a user on a graphical interface, and the method is simple to operate and high in efficiency; moreover, the user only needs to define and maintain part of configuration files related to the project according to the requirement of the user, other extra things do not need to be concerned about, and the use, learning and maintenance cost of the user is reduced.
In addition, it should be noted that the construction task backup is a backup construction task configuration file, and only the content of the updated portion, that is, the incremental backup, needs to be backed up. The process of rebuilding the build task from the backup is then the process of creating the build task from the build task profile.
The construction task migration is to migrate the construction task to another Jenkins slave node, and the migration process is to recreate the construction task according to the construction task configuration file.
Therefore, the backup and migration processes of the construction task are the same as the creation process of the construction task, and are not described herein again.
The backup and migration process of the construction task does not need manual operation of a user on a graphical interface, and automatic backup and migration are achieved. Moreover, the backup and migration processes do not need to turn off the service, and online backup and migration are realized. After the construction task is migrated to a new operation node, the new operation node can be automatically mounted on the Jenkins master, and the efficiency is high.
Corresponding to the embodiment of the software engineering configuration method based on the Jenkins tool, the application also provides an embodiment of a software engineering configuration device based on the Jenkins tool.
Referring to fig. 3, a block diagram of a software engineering configuration apparatus based on Jenkins tool according to an embodiment of the present application is shown, where the apparatus is applied to a system installed with Jenkins tool, and as shown in fig. 3, the apparatus may include: a first obtaining unit 310, a parsing unit 320, a first configuration unit 330, a second configuration unit 340 and a task generating unit 350.
The first obtaining unit 310 is configured to obtain a target construction task configuration file corresponding to a target software project when a code change of a code repository of the target software project is monitored.
The software project developer writes a construction task configuration file according to the requirements of the software project, and the file specifies the dependent system resources, the dependency relationship and the task definition of the construction task. The build task profile is then stored in a code repository. The device will detect whether there is a change in the code repository at preset time intervals.
And the analyzing unit 320 is configured to analyze the target construction task configuration file to obtain target system resources, dependency relationships, and task definitions required by the construction task.
The target system resources include: the machine type, the machine specification and the operating system are depended on by the construction task, and the machine type comprises a virtual machine, a container, a bare metal or a physical machine.
The dependency relationship is used for explaining software and Jenkins plug-ins on which the construction tasks depend.
The task defines build steps and trigger times for defining the build task.
The first configuration unit 330 is configured to configure a system resource matching the target system resource.
In one embodiment of the present application, the first configuration unit includes a first lookup subunit and a creation subunit.
The first searching subunit is used for searching whether the target system resource exists in the current system environment; and if the target system resource exists in the current system environment, the second configuration unit continues to execute the corresponding step.
The creating subunit is configured to create the target system resource if the target system resource does not exist in the current system environment.
And the second configuration unit 340 is configured to configure, in the current system environment, the target software and the target Jenkins plug-ins on which the construction task depends according to the dependency relationship.
In an embodiment of the present application, the second configuration unit includes a second searching subunit, a first obtaining subunit, a third searching subunit, a second obtaining subunit, and a first determining subunit;
the second searching subunit is used for searching whether the target software is installed in the current operating system.
The first obtaining subunit is configured to, when the target software is not installed in the current operating system, obtain the target software according to the download address of the target software included in the target construction task configuration file, and install the target software.
The third searching subunit is used for continuously searching whether a target Jenkins plug-in is installed in the Jenkins tool or not when the target software is installed in the current operating system.
The second obtaining subunit is used for obtaining the target Jenkins plug-in according to the download address of the target Jenkins plug-in contained in the target construction task configuration file when the target Jenkins plug-in is not installed in the current operating system, and installing the target Jenkins plug-in.
The first determining subunit is used for determining that the target software and the target Jenkins plug-ins are installed in the current system environment when the target Jenkins plug-ins are installed in the current operating system.
And a task generating unit 350, configured to generate a build task according to the task definition.
In one embodiment of the application, the task generating unit comprises a task generating subunit and a mounting subunit;
the task generation subunit is used for creating or updating the construction task according to the task definition.
The mounting subunit is used for mounting the target system resource to a Jenkins host to run the construction task.
The target system resource is the Jenkins slave node in FIG. 1, and the mounting of the target system resource on the Jenkins host is to establish communication connection between the Jenkins slave node and the Jenkins master node, so that the Jenkins slave node operates and constructs a task.
According to the software engineering configuration device based on the Jenkins tool, developers write the construction task configuration file of the software project, and the Jenkins tool can automatically configure the system resources (namely, the system environment) required by the operation of the construction task according to the construction task configuration file and automatically mount the system resources to the Jenkins host. And automatically configuring software and Jenkins plug-ins depended by the construction tasks according to the dependency relationship in the construction task configuration file, and finally, automatically creating the Jenkins construction tasks. The whole process automatically completes the configuration and the creation of the construction task by automatically analyzing the construction task configuration file by the system without the operation of a user on a graphical interface, and the method is simple to operate and high in efficiency; moreover, the user only needs to define and maintain part of configuration files related to the project according to the requirement of the user, other extra things do not need to be concerned about, and the use, learning and maintenance cost of the user is reduced.
Referring to fig. 4, a block diagram of another software engineering configuration apparatus based on Jenkins tool according to the embodiment of the present application is shown, where the apparatus further includes, based on the embodiment shown in fig. 3: a monitoring unit 410, an alarm unit 420 and a re-mounting unit 430.
And the monitoring unit 410 is used for monitoring the running state of the Jenkins tool and monitoring the running state of the current operating system.
And an alarm unit 420, configured to generate alarm information when the running state of the current operating system is abnormal.
And a re-mounting unit 430, configured to re-mount the target system resource on the Jenkins host when the operation state of the Jenkins tool is that the target system resource is disconnected.
The software engineering configuration device based on the Jenkins tool provided by the embodiment can monitor the operation states of the Jenkins tool and the operation system in real time, can generate alarm information when the operation state of the operation system is abnormal, and can display the alarm information to a user on a graphical interface so that the user can timely find and process the abnormality. When the operation state of the Jenkins tool is that the Jenkins slave node running the current construction task is disconnected, the Jenkins slave node is mounted on the Jenkins master again so as to continue to run the current construction task.
Referring to fig. 5, a block diagram of a software engineering configuration apparatus based on Jenkins tool according to another embodiment of the present application is shown, where the apparatus further includes, on the basis of the embodiment shown in fig. 3: a configuration file generating unit 510.
A configuration file generating unit 510 for converting the created build task into a corresponding initial build task configuration file.
The initial construction task configuration file comprises task definitions corresponding to the created tasks, and system resources and software resources in the current system environment.
The configuration file generating unit can obtain corresponding task definitions according to the established construction tasks; and acquiring all software installed in the current system environment and all Jenkins plug-ins installed in the Jenkins tool. The user can write and obtain the final construction task configuration file corresponding to the established construction task on the basis of the initial construction task configuration file, so that the burden of software developers is reduced.
Corresponding to the embodiment of the software engineering configuration method based on the Jenkins tool, the application also provides computer equipment.
Referring to fig. 6, a block diagram of a computer device, which may be a server or a computer terminal, installed with Jenkins tool software according to an embodiment of the present invention is shown, as shown in fig. 6, the device includes a processor 610 and a memory 620;
the memory 620 has program instructions stored therein, and the processor 610 implements the following functional steps by executing the stored instructions in the memory 620:
when the code change of a code warehouse of a target software project is monitored, acquiring a target construction task configuration file corresponding to the target software project;
analyzing the target construction task configuration file to obtain target system resources, dependency relationships and task definitions required by the construction task, wherein the target system resources comprise: the machine type, the machine specification and the operating system are depended on by the construction task, and the machine type comprises a virtual machine, a container, a bare metal or a physical machine; the dependency relationship is used for explaining software and Jenkins plug-ins on which the construction tasks depend; the task defines a build step and a trigger time for defining the build task;
configuring a system resource matched with the target system resource;
according to the dependency relationship, configuring target software and a target Jenkins plug-in which the construction task depends in the current system environment;
and generating a construction task according to the task definition.
In a possible implementation manner of the present application, the configuring the system resource matched with the target system resource includes:
searching whether the target system resource exists in the current system environment;
if the target system resource exists in the current system environment, executing a step of configuring software and Jenkins plug-ins on which the construction task depends in the current system environment according to the dependency relationship;
and if the target system resource does not exist in the current system environment, creating the target system resource, and then executing the step of configuring the software and the Jenkins plug-in which the construction task depends in the current system environment according to the dependency relationship.
In another possible implementation manner of the present application, the configuring, according to the dependency relationship, software and Jenkins plug-ins, on which the construction task depends, in a current system environment includes:
searching whether the target software is installed in the current operating system;
if the target software is not installed in the current operating system, acquiring the target software according to a download address of the target software contained in the target construction task configuration file, and installing the target software;
if the target software is installed in the current operating system, continuously searching whether the Jenkins tool is provided with the target Jenkins plug-in or not;
if the target Jenkins plug-in is not installed in the Jenkins tool, acquiring the target Jenkins plug-in according to a download address of the target Jenkins plug-in contained in the target construction task configuration file, and installing the target Jenkins plug-in;
and if the target Jenkins plug-in is installed in the Jenkins tool, determining that the target software and the target Jenkins plug-in are installed in the current system environment.
In another possible implementation manner of the present application, the generating a build task according to the task definition includes:
creating or updating the construction task according to the task definition;
and mounting the target system resource to a Jenkins host to run the construction task.
In yet another possible implementation manner of the present application, the method further includes:
monitoring the running state of the Jenkins tool and monitoring the running state of the current operating system;
when the running state of the current operating system is abnormal, generating alarm information;
and when the operation state of the Jenkins tool is that the target system resource is disconnected, re-mounting the target system resource to the Jenkins host.
In another possible implementation manner of the present application, the method further includes:
and converting the created construction task into an initial construction task configuration file corresponding to the created construction task, wherein the initial construction task configuration file comprises a task definition corresponding to the created task, and system resources and software resources in the current system environment.
According to the computer device provided by the embodiment, the system resources (namely, the system environment) required by the construction task are automatically configured according to the construction task configuration file of the software project written by the software developer, and the system resources are automatically mounted on the Jenkins host. And automatically configuring software and Jenkins plug-ins depended by the construction tasks according to the dependency relationship in the construction task configuration file, and finally automatically creating the Jenkins construction tasks according to task definitions in the construction task configuration file. The user only needs to maintain the configuration file of the construction task, and the other processes automatically perform configuration and creation of the construction task by automatically analyzing the configuration file of the construction task by the system without the operation of the user on a graphical interface, so that the operation is simple and the efficiency is high; moreover, the user only needs to maintain and construct the task configuration file, and the maintenance cost is low.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the device-like embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Claims (12)
1. A software engineering configuration method based on Jenkins tool is characterized by comprising the following steps:
when the code change of a code warehouse of a target software project is monitored, acquiring a target construction task configuration file corresponding to the target software project;
analyzing the target construction task configuration file to obtain target system resources, dependency relationships and task definitions required by the construction task, wherein the target system resources comprise: the machine type, the machine specification and the operating system are depended on by the construction task, and the machine type comprises a virtual machine, a container, a bare metal or a physical machine; the dependency relationship is used for explaining software and Jenkins plug-ins on which the construction tasks depend; the task defines a build step and a trigger time for defining the build task;
configuring a system resource matched with the target system resource;
according to the dependency relationship, configuring target software and a target Jenkins plug-in which the construction task depends in the current system environment;
and generating a construction task according to the task definition.
2. The method of claim 1, wherein configuring the system resource that matches the target system resource comprises:
searching whether the target system resource exists in the current system environment;
if the target system resource exists in the current system environment, executing a step of configuring software and Jenkins plug-ins on which the construction task depends in the current system environment according to the dependency relationship;
and if the target system resource does not exist in the current system environment, creating the target system resource, and then executing the step of configuring the software and the Jenkins plug-in which the construction task depends in the current system environment according to the dependency relationship.
3. The method according to claim 1, wherein configuring the software and Jenkins plug-ins on which the build task depends in the current system environment according to the dependency relationship comprises:
searching whether the target software is installed in the current operating system;
if the target software is not installed in the current operating system, acquiring the target software according to a download address of the target software contained in the target construction task configuration file, and installing the target software;
if the target software is installed in the current operating system, continuously searching whether the Jenkins tool is provided with the target Jenkins plug-in or not;
if the target Jenkins plug-in is not installed in the Jenkins tool, acquiring the target Jenkins plug-in according to a download address of the target Jenkins plug-in contained in the target construction task configuration file, and installing the target Jenkins plug-in;
and if the target Jenkins plug-in is installed in the Jenkins tool, determining that the target software and the target Jenkins plug-in are installed in the current system environment.
4. The method of any of claims 1-3, wherein generating a build task from the task definition comprises:
creating or updating the construction task according to the task definition;
and mounting the target system resource to a Jenkins host to run the construction task.
5. The method of claim 1, further comprising:
monitoring the running state of the Jenkins tool and monitoring the running state of the current operating system;
when the running state of the current operating system is abnormal, generating alarm information;
and when the operation state of the Jenkins tool is that the target system resource is disconnected, re-mounting the target system resource to the Jenkins host.
6. The method of claim 1, further comprising:
and converting the created construction task into an initial construction task configuration file corresponding to the created construction task, wherein the initial construction task configuration file comprises a task definition corresponding to the created construction task, and system resources and software resources in the current system environment.
7. A software engineering configuration device based on Jenkins tool, comprising:
the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring a target construction task configuration file corresponding to a target software project when the code change of a code warehouse of the target software project is monitored;
the analysis unit is used for analyzing the target construction task configuration file to obtain target system resources, dependency relationships and task definitions required by the construction task, wherein the target system resources comprise: the machine type, the machine specification and the operating system are depended on by the construction task, and the machine type comprises a virtual machine, a container, a bare metal or a physical machine; the dependency relationship is used for explaining software and Jenkins plug-ins on which the construction tasks depend; the task defines a build step and a trigger time for defining the build task;
the first configuration unit is used for configuring the system resource matched with the target system resource;
the second configuration unit is used for configuring the target software and the target Jenkins plug-in which the construction task depends in the current system environment according to the dependency relationship;
and the task generating unit is used for generating a construction task according to the task definition.
8. The apparatus of claim 7, wherein the first configuration unit comprises:
the first searching subunit is used for searching whether the target system resource exists in the current system environment; when the target system resource exists in the current system environment, the second configuration unit executes software and Jenkins plug-ins which depend on the construction task and are configured in the current system environment according to the dependency relationship;
a creating subunit, configured to create the target system resource when the target system resource does not exist in the current system environment.
9. The apparatus of claim 7, wherein the second configuration unit comprises:
the second searching subunit is used for searching whether the target software depended by the construction task is installed in the current operating system;
a first obtaining subunit, configured to, when the target software is not installed in the current operating system, obtain the target software according to a download address of the target software included in the target construction task configuration file, and install the target software;
a third searching subunit, configured to, when the target software is installed in the current operating system, continue to search whether the Jenkins tool is installed with the target Jenkins plug-in;
the second obtaining subunit is used for obtaining the target Jenkins plug-in according to the download address of the target Jenkins plug-in contained in the target construction task configuration file when the target Jenkins plug-in is not installed in the Jenkins tool, and installing the target Jenkins plug-in;
and the first determining subunit is used for determining that the target software and the target Jenkins plug-in are installed in the current system environment when the target Jenkins plug-in is installed in the Jenkins tool.
10. The apparatus according to any one of claims 7-9, wherein the task generating unit comprises:
the task generation subunit is used for creating or updating the construction task according to the task definition;
and the mounting subunit is used for mounting the target system resource to a Jenkins host so as to run the construction task.
11. The apparatus of claim 7, further comprising:
the monitoring unit is used for monitoring the running state of the Jenkins tool and the running state of the current operating system;
the alarm unit is used for generating alarm information when the running state of the current operating system is abnormal;
and the re-mounting unit is used for re-mounting the target system resource to the Jenkins host when the operation state of the Jenkins tool is that the target system resource is disconnected.
12. The apparatus of claim 7, further comprising:
the configuration file generating unit is used for converting the created construction task into an initial construction task configuration file corresponding to the created construction task, wherein the initial construction task configuration file comprises a task definition corresponding to the created construction task, and system resources and software resources in the current system environment.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710773700.8A CN107608710B (en) | 2017-08-31 | 2017-08-31 | Software project construction task configuration method and device based on Jenkins tool |
| PCT/CN2018/102918 WO2019042311A1 (en) | 2017-08-31 | 2018-08-29 | Software project setup task configuration method and device using jenkins |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710773700.8A CN107608710B (en) | 2017-08-31 | 2017-08-31 | Software project construction task configuration method and device based on Jenkins tool |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107608710A CN107608710A (en) | 2018-01-19 |
| CN107608710B true CN107608710B (en) | 2021-08-31 |
Family
ID=61056757
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710773700.8A Active CN107608710B (en) | 2017-08-31 | 2017-08-31 | Software project construction task configuration method and device based on Jenkins tool |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107608710B (en) |
| WO (1) | WO2019042311A1 (en) |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107608710B (en) * | 2017-08-31 | 2021-08-31 | 华为技术有限公司 | Software project construction task configuration method and device based on Jenkins tool |
| CN108647010B (en) * | 2018-04-27 | 2021-11-26 | 武汉斗鱼网络科技有限公司 | Project engineering initialization method, terminal equipment and storage medium |
| CN108958843A (en) * | 2018-07-12 | 2018-12-07 | 成都数字天空科技有限公司 | Plug-in unit construction method, system, equipment and medium based on lightweight script |
| CN110895460A (en) * | 2018-09-13 | 2020-03-20 | 深圳市优必选科技有限公司 | Jenkins-based robot system integration method and device and terminal equipment |
| CN111414226A (en) * | 2019-01-07 | 2020-07-14 | 北京智融网络科技有限公司 | Method and system for establishing task sandbox |
| CN109871258A (en) * | 2019-01-17 | 2019-06-11 | 珠海金山网络游戏科技有限公司 | The method and device of modification host configuration based on distributed container |
| CN110096304A (en) * | 2019-03-16 | 2019-08-06 | 平安城市建设科技(深圳)有限公司 | Task construction method, device, equipment and storage medium based on Jenkins |
| CN110286880B (en) * | 2019-06-17 | 2020-12-01 | 中国科学院软件研究所 | GitHub and Travis CI oriented complete continuous integrated data collection method |
| CN110515625A (en) * | 2019-08-02 | 2019-11-29 | 苏州浪潮智能科技有限公司 | Task construction method, device, equipment and computer readable storage medium |
| CN110888652B (en) * | 2019-10-24 | 2023-07-07 | 福建天泉教育科技有限公司 | Multi-version construction method and terminal based on jenkins plug-in |
| CN110955415B (en) * | 2019-12-03 | 2024-03-08 | 杭州当贝网络科技有限公司 | Method for projecting multi-platform service adaptation |
| CN111144839B (en) * | 2019-12-17 | 2024-02-02 | 深圳市优必选科技股份有限公司 | Project construction method, continuous integration system and terminal equipment |
| CN111274041A (en) * | 2020-02-24 | 2020-06-12 | 北京达佳互联信息技术有限公司 | Graphics processor mounting method and device, electronic equipment and storage medium |
| CN112148462B (en) * | 2020-10-20 | 2023-03-28 | 上海新炬网络信息技术股份有限公司 | Jenkins-based CICD process processing method |
| CN114650213A (en) * | 2020-12-18 | 2022-06-21 | 航天信息股份有限公司 | Method, device and storage medium for configuring Jenkins server cluster |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105786691A (en) * | 2014-12-25 | 2016-07-20 | 重庆重邮信科通信技术有限公司 | Automatic integration testing device, method and system of mobile terminal |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE10121790B4 (en) * | 2000-06-03 | 2006-11-23 | International Business Machines Corp. | Software configuration method for use in a computer system |
| US7549148B2 (en) * | 2003-12-16 | 2009-06-16 | Microsoft Corporation | Self-describing software image update components |
| CN101515232A (en) * | 2008-02-21 | 2009-08-26 | 卓望数码技术（深圳）有限公司 | Software continuous integration system and method |
| CN103207802B (en) * | 2012-01-12 | 2018-10-19 | 上海盛大网络发展有限公司 | Operation system of software and method |
| CN105739966A (en) * | 2016-01-19 | 2016-07-06 | 浪潮软件集团有限公司 | Continuous integration method and device |
| CN106095408B (en) * | 2016-05-31 | 2019-05-14 | 浙江网新恒天软件有限公司 | A kind of system and method for data monitoring and Code automatic build and deployment |
| CN106815052A (en) * | 2017-01-10 | 2017-06-09 | 南威软件股份有限公司 | A kind of method of the rapid deployment system for being adapted to multi-environment configuration |
| CN107608710B (en) * | 2017-08-31 | 2021-08-31 | 华为技术有限公司 | Software project construction task configuration method and device based on Jenkins tool |
-
2017
- 2017-08-31 CN CN201710773700.8A patent/CN107608710B/en active Active
-
2018
- 2018-08-29 WO PCT/CN2018/102918 patent/WO2019042311A1/en active Application Filing
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105786691A (en) * | 2014-12-25 | 2016-07-20 | 重庆重邮信科通信技术有限公司 | Automatic integration testing device, method and system of mobile terminal |
Non-Patent Citations (1)
| Title |
|---|
| "jenkinsci/system-config-dsl-plugin;Cyrille;《https://github.com/jenkinsci/system-config-dsl-plugin》;20160831;第1-2页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107608710A (en) | 2018-01-19 |
| WO2019042311A1 (en) | 2019-03-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107608710B (en) | Software project construction task configuration method and device based on Jenkins tool | |
| CN109358858B (en) | Automatic deployment method, device, medium and electronic equipment | |
| US20230244465A1 (en) | Systems and methods for automated retrofitting of customized code objects | |
| US10769250B1 (en) | Targeted security monitoring using semantic behavioral change analysis | |
| US8732693B2 (en) | Managing continuous software deployment | |
| EP2972821B1 (en) | Application compatibility checking in a distributed computing environment | |
| US20230161694A1 (en) | Orchestration for automated performance testing | |
| WO2012088173A1 (en) | Code clone notification and architectural change visualization | |
| CN107193607B (en) | Method and apparatus for updating code file, storage medium, processor, and terminal | |
| CN106980565B (en) | Upgrading process monitoring method and device | |
| CN104679500B (en) | Method and device for realizing automatic generation of entity class | |
| CN111831567B (en) | Application test environment configuration method, device, system and medium | |
| CN116069341A (en) | Automatic deployment method, equipment and storage medium for application program | |
| CN105677394A (en) | Method and apparatus for upgrading application on terminal device | |
| KR101599471B1 (en) | Apparatus, system, method and readable recording medium of managing a project file | |
| US20230061121A1 (en) | Methods concerning ongoing treatment for cancer | |
| CN109032641B (en) | Application version updating method and device | |
| CN115291935A (en) | Component updating method, component updating device, equipment and storage medium | |
| CN113986237A (en) | Method and device for creating Jenkins compiling task | |
| CN115729590A (en) | Service deployment method, device, equipment and computer readable storage medium | |
| CN116820526B (en) | Operating system upgrading method, device, equipment and storage medium | |
| CN111651189A (en) | Product delivery method and device of continuous integration system and electronic equipment | |
| CN114240265B (en) | Product deployment method and device based on mixed environment | |
| US11159358B2 (en) | Sentry for information technology system blueprints | |
| CN115668133A (en) | Industrial application package management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220209 Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province Patentee after: Huawei Cloud Computing Technology Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| TR01 | Transfer of patent right |