CN111930415A - Construction deployment method and device for large-scale software product - Google Patents

Construction deployment method and device for large-scale software product Download PDF

Info

Publication number
CN111930415A
CN111930415A CN202010575762.XA CN202010575762A CN111930415A CN 111930415 A CN111930415 A CN 111930415A CN 202010575762 A CN202010575762 A CN 202010575762A CN 111930415 A CN111930415 A CN 111930415A
Authority
CN
China
Prior art keywords
interface
construction
deployment
business object
strategy
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.)
Granted
Application number
CN202010575762.XA
Other languages
Chinese (zh)
Other versions
CN111930415B (en
Inventor
解其亮
焦学瑞
舒鹏飞
魏忠法
刘建涛
徐同明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur General Software Co Ltd
Original Assignee
Shandong Inspur Genersoft Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shandong Inspur Genersoft Information Technology Co Ltd filed Critical Shandong Inspur Genersoft Information Technology Co Ltd
Priority to CN202010575762.XA priority Critical patent/CN111930415B/en
Publication of CN111930415A publication Critical patent/CN111930415A/en
Application granted granted Critical
Publication of CN111930415B publication Critical patent/CN111930415B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Abstract

The application discloses a construction and deployment method and device for a large-scale software product, which are used for solving the problems of huge engineering quantity, complex operation, high possibility of errors and the like of the conventional construction and deployment method. The method comprises the steps of determining a preset unit interface, a construction strategy interface and a deployment strategy interface corresponding to a service object unit to be constructed; determining a construction context and a construction strategy configuration corresponding to the business object unit according to the unit interface and the construction strategy interface, and constructing the business object unit; and determining a deployment context and a deployment strategy configuration corresponding to the business object unit according to the unit interface and the deployment strategy interface, and deploying the business object unit.

Description

Construction deployment method and device for large-scale software product
Technical Field
The present application relates to the field of software configuration and deployment technologies, and in particular, to a configuration and deployment method and apparatus for a large software product.
Background
In a software system, a large software product typically includes multiple business domains, each business domain including multiple modules, each module including multiple business object units. Thus, a software product may include thousands of business object units in total.
In a software product, if the source code repository is defined according to the granularity of the business object units, and each business object unit corresponds to one source code repository, one software product may include thousands of source code repositories.
Therefore, when a constructor constructs and deploys a software product, each business object unit needs to be manually defined according to the source code repository of each business object unit. Moreover, when modifying the related configuration information and the deployment information, the constructor also needs to sequentially modify the business object units that need to be modified.
The construction and deployment method of the software product needs constructors to repeat similar operations for thousands of times, the workload is huge, and the problems of omission, errors and the like easily occur in manual definition, so that the normal operation of the software product is influenced.
Disclosure of Invention
The embodiment of the application provides a construction and deployment method and device for a large-scale software product, and aims to solve the problems of huge engineering quantity, complex operation, high possibility of errors and the like of the conventional construction and deployment method.
The construction and deployment method for the large-scale software product provided by the embodiment of the application comprises the following steps:
determining a preset unit interface, a construction strategy interface and a deployment strategy interface corresponding to a service object unit to be constructed;
determining a construction context and a construction strategy configuration corresponding to the business object unit according to the unit interface and the construction strategy interface, and constructing the business object unit;
and determining a deployment context and a deployment strategy configuration corresponding to the business object unit according to the unit interface and the deployment strategy interface, and deploying the business object unit.
In one example, determining a construction context and a construction policy configuration corresponding to the business object unit according to the unit interface and the construction policy interface, and constructing the business object unit includes: acquiring a construction strategy identifier corresponding to the service object unit according to the unit interface; determining construction strategy configuration information corresponding to the business object unit according to the construction strategy identification; loading a corresponding construction policy program for constructing a policy interface according to the construction policy configuration information to call the unit interface and obtain a construction context corresponding to the business object unit; and constructing the business object unit according to the construction policy interface and the construction context.
In one example, determining a deployment context and a deployment policy configuration corresponding to the business object unit according to the unit interface and the deployment policy interface, and deploying the business object unit includes: acquiring a deployment strategy identifier corresponding to the service object unit according to the unit interface; determining deployment strategy configuration information corresponding to the service object unit according to the deployment strategy identification; loading a deployment strategy program of a corresponding deployment strategy interface according to the deployment strategy configuration information so as to call the unit interface and obtain a deployment context corresponding to the service object unit; and deploying the business object unit according to the deployment strategy interface and the deployment context.
In one example, before constructing the business object unit, the method further comprises: if the starting structure in the unit interface is yes, continuing to execute the structure operation of the business object unit; and if the starting or the construction of the unit interface is not, terminating the construction operation of the service object unit.
In one example, according to the configuration information of the construction policy, loading a corresponding construction policy program for constructing a policy interface, including: and determining to adopt a default construction strategy or adopt a pre-specified construction strategy according to whether default information in the construction strategy configuration information exists or not, and loading a construction strategy program of a corresponding construction strategy interface.
In one example, before determining a preset unit interface corresponding to a business object unit, constructing a policy interface, and deploying the policy interface, the method further includes: determining an interface standard of the preset business object unit in the code engineering construction and deployment processes; the interface standard comprises a unit interface, a construction policy interface, a deployment policy interface, an engineering type configuration, a basic context, a construction context, a deployment context, a construction policy configuration and a deployment policy configuration.
In one example, constructing the business object unit according to the construction policy interface and the construction context includes: and according to the construction context, assigning the construction context parameters in the construction policy interface, and executing the construction operation of the service object unit.
In one example, the method further comprises: and expanding the construction policy in the construction policy interface by specifying whether default information in the construction policy configuration exists.
In one example, the unit interface is used for defining a standard interface which needs to be realized when the business object unit constructs and deploys a source code project; the unit interface comprises a unit identifier, a product identifier, a key application identifier, a service unit identifier, a business object identifier, whether to start construction, construct a strategy identifier, whether to start deployment, deploy a strategy identifier and a source code position.
The device for constructing and deploying the large-scale software product provided by the embodiment of the application comprises:
the determining module is used for determining a preset unit interface, a construction strategy interface and a deployment strategy interface corresponding to a service object unit to be constructed;
the construction module is used for determining construction context and construction strategy configuration corresponding to the business object unit according to the unit interface and the construction strategy interface, and constructing the business object unit;
and the deployment module is used for determining the deployment context and the deployment strategy configuration corresponding to the business object unit according to the unit interface and the deployment strategy interface and deploying the business object unit.
The construction and deployment method and device for the large-scale software product provided by the embodiment of the application at least have the following beneficial effects:
the method can directly call the corresponding interface and method in the process of constructing and deploying the business object units by predefining the interface standards of the business object units without manually defining each business object unit, thereby saving a large amount of redundant workload of constructors.
Moreover, the error conditions such as omission and the like are easy to occur in the manual definition process, and the problems of errors and the like which may occur in the manual definition process are reduced by directly calling the interface.
A large number of similar business object units exist in the software product, and by the method, the similar business object units can share the same interface, so that the uniform control of the large number of similar business object units is realized.
In addition, if the relevant information of the business object units needs to be modified, a large number of business object units can be modified together by modifying the content in the interface standard, and the same modification operation does not need to be repeated for many times, so that the unified management of similar business object units is facilitated, and the additional operation time is saved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a method for constructing and deploying a large-scale software product according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a configuration deployment apparatus of a large-scale software product according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a flowchart of a method for constructing and deploying a large-scale software product according to an embodiment of the present application, which specifically includes the following steps:
s101: and determining a preset unit interface, a construction strategy interface and a deployment strategy interface corresponding to the service object unit to be constructed.
In the embodiment of the application, in the construction process and the deployment process of the business object unit, the server may determine an interface standard preset by the business object unit to be constructed, and construct and deploy the business object unit according to the interface standard. The interface standard is an interface standard which is predefined for each business object unit and is required to be followed in the code engineering construction and deployment process of the business object unit.
Specifically, the interface standard includes a unit interface of the service object unit, an engineering type configuration, a base context, a construction policy interface, a construction context, a construction policy configuration, a deployment policy interface, a deployment context, and a deployment policy configuration.
The unit interface is used for defining a standard interface which needs to be realized when the business object unit constructs and deploys a source code project; the engineering type configuration is used for defining the engineering type of the source code engineering of the business object unit, and the construction strategy and the deployment strategy corresponding to different engineering types are different; the base context is used to represent the underlying information that is common to the various business object units in the software product.
The cell interface includes 11 attributes: unit identification, product identification, key application identification, service unit identification, business object identification, engineering type identification, whether construction is started, construction strategy identification, whether deployment is started, deployment strategy identification and source code position.
The unit identification is used for uniquely identifying a business object unit; the product identification is used for identifying a large software product, and when a multi-product line exists, the product identification can be used for distinguishing software products to which different business object units belong; the key application identification is used for determining the application field of the business object unit in the large-scale software product; the service unit identification is used for determining a module to which the business object unit belongs in the corresponding application field of the large-scale software product; the 'business object identification' is used for determining the business object corresponding to the business object unit, and is the minimum business logic unit; the engineering type identifier is used for determining the engineering type of the software product corresponding to the business object unit; whether construction is started or not is used for indicating whether the business object unit needs to be constructed or not, and the starting construction is a precondition for constructing the business object unit; the 'construction policy identifier' is used for indicating the identifier of the construction policy adopted by the business object unit; whether deployment is started or not is used for indicating whether the business object unit needs to be deployed or not, and the starting deployment is a precondition for deploying the business object unit; the "deployment policy identifier" is used to indicate an identifier of a deployment policy adopted by the service object unit; the "source code location" is used to determine the location of the source code repository corresponding to the business object unit.
And the 6 attributes included in the basic context are 6 attributes including unit identifier, product identifier, key application identifier, service unit identifier, service object identifier and engineering type identifier included in the unit interface.
The engineering type configuration includes 4 attributes: project type identification, project type coding, project type name and description. The engineering type identifier is used for uniquely identifying one engineering type; "engineering type code" is used to indicate the code of the corresponding engineering type; "project type name" is used to denote the name of the corresponding project type; "description" is used for simplicity to describe the purpose, features, etc. of the corresponding type of engineering.
In this embodiment, before constructing and deploying the service object unit, the server may first determine a preset unit interface, a construction policy interface, and a deployment policy interface corresponding to the service object unit, so as to construct and deploy the service object unit according to the preset unit interface, the construction policy interface, and the deployment policy interface.
S102: and determining a construction context and construction strategy configuration corresponding to the business object unit according to the unit interface and the construction strategy interface, and constructing the business object unit.
In this embodiment of the present application, in the process of constructing a business object unit, a server may determine a corresponding construction context and construction policy configuration according to a unit interface and a construction policy interface of the business object unit, so as to construct the business object unit according to the construction context according to the corresponding construction policy.
Specifically, the construction process of the business object unit comprises the following steps:
first, the server can obtain a construction policy identifier in the unit interface attribute according to the unit interface of the service object unit.
Secondly, the server can determine the construction policy configuration information corresponding to the service object unit according to the obtained construction policy identifier.
The configuration policy configuration is also one of the predefined interface standards, and is used to determine the configuration policy adopted by the service object unit in the configuration process, and record the relevant information of the configuration policy of the service object unit, including 4 attributes: constructing a strategy identifier, an engineering type identifier, constructing a strategy implementation class and judging whether the strategy is default or not.
The "construction policy identifier" is used to indicate an identifier of a construction policy adopted by the service object unit; the engineering type identifier is used for determining the engineering type of the software product corresponding to the business object unit; the "construct policy implementation class" is used to describe relevant information for constructing the policy implementation class, such as a name describing the implementation class; "Default or not" is used to mark a default build policy implementation class or otherwise specify a build policy implementation class for a particular project type.
Thirdly, the server can determine the construction strategy adopted by the business object unit in the construction process according to the content in the column of 'default' in the obtained construction strategy configuration information.
In one embodiment, if the column "default" is empty, it indicates that the business object unit adopts the default construction policy under the corresponding project type, and if the column "default" is not empty, the server may determine the construction policy under the specific project type previously specified for the business object unit according to the content of the column.
The server may then extend the build policy for the business object unit by specifying the build policy under the particular project type in the "Default or not" column.
Fourthly, the server can load a corresponding construction policy program for constructing the policy interface according to the corresponding construction policy so as to call an 'acquiring construction context' method in the unit interface and acquire the construction context corresponding to the business object unit.
Fifth, the server can construct the business object units by constructing the policy interface and the obtained construction context.
The construction context is used for recording construction information of a business object unit, and comprises 3 attributes: source code position, source code warehouse authentication credential, and construction policy identification. The source code position determines the position of a source code warehouse corresponding to the business object unit; the source code warehouse authentication credential is used for specifying the authentication credential which needs to be provided when the source code is acquired; the "build policy identification" is used to indicate an identification of the build policy employed by the business object unit.
The construction strategy interface is used for executing the construction process of the business object unit according to the construction context and the construction strategy.
In one embodiment, parameters of the build context are included in the build policy interface. After the server acquires the content of the construction context from the unit interface, the server can assign values to the parameters in the construction policy interface so that the construction policy interface executes construction operation according to the corresponding parameter values.
In one embodiment, the server may determine whether to construct the business object unit based on the contents of the "if construct enabled" column in the unit interface before constructing the business object unit.
If the content of the column of 'whether to enable construction' is yes, the construction operation of the business object unit is continuously executed. If the content of the column of 'whether to start construction or not' in the unit interface is negative, the construction operation of the business object unit is terminated.
S103: and determining a deployment context and a deployment strategy configuration corresponding to the business object unit according to the unit interface and the deployment strategy interface, and deploying the business object unit.
In this embodiment of the present application, in the process of deploying the service object unit, the server may determine, according to the unit interface and the deployment policy interface of the service object unit, a corresponding deployment context and deployment policy configuration, so as to deploy the service object unit according to the deployment context and the corresponding deployment policy.
Specifically, the deployment process of the business object unit includes the following steps:
first, the server may obtain a deployment policy identifier in a unit interface attribute according to a unit interface of the service object unit.
Secondly, the server can determine deployment strategy configuration information corresponding to the service object unit according to the obtained deployment strategy identifier.
The deployment policy configuration is also one of predefined interface standards, and is used to determine a deployment policy adopted by the business object unit in the deployment process, record relevant information of the deployment policy of the business object unit, and include 4 attributes: deployment strategy identification, project type identification, deployment strategy implementation class and default.
The "deployment policy identifier" is used to indicate an identifier of a deployment policy adopted by the service object unit; the "deployment policy implementation class" is used to describe relevant information of the deployment policy implementation class, such as a name describing the implementation class; "Default or not" is used to mark a default deployment policy implementation class or otherwise specify a deployment policy implementation class for a particular engineering type.
Thirdly, the server can determine the deployment strategy adopted by the service object unit in the deployment process according to the content in the column of 'default' in the acquired deployment strategy configuration information.
Fourthly, the server can load the deployment strategy program of the corresponding deployment strategy interface according to the corresponding deployment strategy so as to call the method for acquiring the deployment context in the unit interface and acquire the deployment context corresponding to the service object unit.
Fifthly, the server can deploy the business object unit through the deployment strategy interface and the obtained deployment context.
The deployment context is used for recording the deployment information of the business object unit, and comprises 3 attributes: source code location, source code repository authentication credentials, deployment policy identification.
The deployment strategy interface is used for executing the deployment process of the business object unit according to the deployment context and the deployment strategy.
In one embodiment, parameters of the deployment context are included in the deployment policy interface. After acquiring the content of the deployment context from the unit interface, the server can assign values to the parameters in the deployment policy interface, so that the deployment policy interface executes deployment operation according to the corresponding parameter values.
In one embodiment, the construction and deployment operations of the service object unit by the server are performed sequentially, the service object unit is constructed first, and then the constructed service object unit is deployed.
Then, after the service object unit is constructed and completed, the server can determine whether to deploy the service object unit according to the content of the column "whether to enable deployment" in the unit interface. If the content of the column of 'whether to enable deployment' is yes, the deployment operation of the business object unit is continuously executed. If the content of the column of 'whether to start deployment' in the unit interface is negative, the deployment operation of the business object unit is terminated.
It should be noted that the principle of constructing and deploying the business object unit is substantially the same, and therefore, in the present application, a part not described in detail about the deployment operation of the business object unit may be performed with reference to a corresponding construction operation.
In the embodiment of the application, by predefining the interface standard of the business object unit, the corresponding interface and method can be directly called in the process of constructing and deploying the business object unit without manually defining each business object unit.
And a large number of similar business object units exist in the software product, and the similar business object units can share the same interface by the method, so that the unified control of the large number of similar business object units is realized.
In addition, if the relevant information of the business object unit needs to be modified, the content in the interface standard can be modified, so that a large number of business object units can be modified together, and the same modification operation does not need to be repeated for many times.
The method saves a large amount of redundant workload of constructors, simplifies the operation of constructing and deploying the software product, saves a large amount of operation time, and is favorable for reducing the problems of errors and the like which may occur during manual definition.
For ease of understanding, the present application illustrates the construction and deployment of a sales order business object unit of a metadata type.
In the process of constructing and deploying the sales order, the process is divided into a development phase of a predefined interface standard and a running phase of executing construction and deployment operations.
During the development phase, the server may determine that the unit interface of the sales order business object unit is as shown in Table 1:
TABLE 1
Figure BDA0002551305600000101
Figure BDA0002551305600000111
The engineering type configuration of the sales order business object units is shown in table 2:
TABLE 2
Attribute name Value of
Engineering type identification MetaDataType
Engineering type coding MetaDataType
Project type name Metadata-like engineering
Description of the invention Project built using metadata
The configuration strategy of the sales order business object unit is shown in table 3:
TABLE 3
Attribute name Value of
Constructing policy identification MetaDataDeployStrategy
Type of engineering MetaDataType
Constructing policy implementation classes com.company.erp.MetaDataDeployStrategy
Whether or not to default Is that
Therefore, in the running stage, the server can construct and deploy the sales order business object unit according to the data in the interface standard.
In the construction process, the server firstly determines the configuration information of the corresponding unit interface according to the business object identifier of the sales order. In this example, the "enable or not enable construction" attribute is "yes," and the execution of the construction process begins.
First, according to the information of the unit interface of the sales order, it is determined that the corresponding construction policy is identified as MetaDataBuildStrategy. Secondly, according to the default attribute of the configuration strategy, determining to adopt the default configuration strategy, loading the program, calling the method for acquiring the configuration context in the unit interface, and acquiring the corresponding configuration context. And finally, transmitting the obtained construction context to a corresponding construction strategy program for construction.
It should be noted that, because the principle of the construction process of the sales order and the principle of the deployment process are essentially consistent, the description of the deployment process may refer to the corresponding construction process, and this application is not repeated herein.
Based on the same inventive concept, the above method for constructing and deploying a large software product provided in the embodiment of the present application further provides a corresponding device for constructing and deploying a large software product, as shown in fig. 2.
Fig. 2 is a schematic structural diagram of a configuration and deployment apparatus of a large-scale software product provided in an embodiment of the present application, which specifically includes:
the determining module 201 determines a preset unit interface, a configuration policy interface and a deployment policy interface corresponding to a service object unit to be configured;
a construction module 202, configured to determine a construction context and a construction policy configuration corresponding to the business object unit according to the unit interface and the construction policy interface, and construct the business object unit;
the deployment module 203 determines a deployment context and a deployment policy configuration corresponding to the business object unit according to the unit interface and the deployment policy interface, and deploys the business object unit.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (10)

1. A method for constructing and deploying a large-scale software product is characterized by comprising the following steps:
determining a preset unit interface, a construction strategy interface and a deployment strategy interface corresponding to a service object unit to be constructed;
determining a construction context and a construction strategy configuration corresponding to the business object unit according to the unit interface and the construction strategy interface, and constructing the business object unit;
and determining a deployment context and a deployment strategy configuration corresponding to the business object unit according to the unit interface and the deployment strategy interface, and deploying the business object unit.
2. The method according to claim 1, wherein determining a construction context and a construction policy configuration corresponding to the business object unit according to the unit interface and the construction policy interface, and constructing the business object unit comprises:
acquiring a construction strategy identifier corresponding to the service object unit according to the unit interface;
determining construction strategy configuration information corresponding to the business object unit according to the construction strategy identification;
loading a corresponding construction policy program for constructing a policy interface according to the construction policy configuration information to call the unit interface and obtain a construction context corresponding to the business object unit;
and constructing the business object unit according to the construction policy interface and the construction context.
3. The method according to claim 1, wherein determining a deployment context and a deployment policy configuration corresponding to the business object unit according to the unit interface and the deployment policy interface, and deploying the business object unit comprises:
acquiring a deployment strategy identifier corresponding to the service object unit according to the unit interface;
determining deployment strategy configuration information corresponding to the service object unit according to the deployment strategy identification;
loading a deployment strategy program of a corresponding deployment strategy interface according to the deployment strategy configuration information so as to call the unit interface and obtain a deployment context corresponding to the service object unit;
and deploying the business object unit according to the deployment strategy interface and the deployment context.
4. The method of claim 1, wherein prior to constructing the business object units, the method further comprises:
if the starting structure in the unit interface is yes, continuing to execute the structure operation of the business object unit;
and if the starting or the construction of the unit interface is not, terminating the construction operation of the service object unit.
5. The method according to claim 1, wherein loading a corresponding construction policy program for constructing a policy interface according to the construction policy configuration information comprises:
and determining to adopt a default construction strategy or adopt a pre-specified construction strategy according to whether default information in the construction strategy configuration information exists or not, and loading a construction strategy program of a corresponding construction strategy interface.
6. The method according to claim 1, wherein before determining the preset unit interface corresponding to the business object unit, constructing the policy interface, and deploying the policy interface, the method further comprises:
determining an interface standard of the preset business object unit in the code engineering construction and deployment processes;
the interface standard comprises a unit interface, a construction policy interface, a deployment policy interface, an engineering type configuration, a basic context, a construction context, a deployment context, a construction policy configuration and a deployment policy configuration.
7. The method of claim 2, wherein constructing the business object unit according to the build policy interface and the build context comprises:
and according to the construction context, assigning the construction context parameters in the construction policy interface, and executing the construction operation of the service object unit.
8. The method of claim 5, further comprising:
and expanding the construction policy in the construction policy interface by specifying whether default information in the construction policy configuration exists.
9. The method according to claim 1, wherein the unit interface is used to define a standard interface that the business object unit needs to implement when constructing and deploying source code engineering;
the unit interface comprises a unit identifier, a product identifier, a key application identifier, a service unit identifier, a business object identifier, whether to start construction, construct a strategy identifier, whether to start deployment, deploy a strategy identifier and a source code position.
10. A device for deploying a large-scale software product, comprising:
the determining module is used for determining a preset unit interface, a construction strategy interface and a deployment strategy interface corresponding to a service object unit to be constructed;
the construction module is used for determining construction context and construction strategy configuration corresponding to the business object unit according to the unit interface and the construction strategy interface, and constructing the business object unit;
and the deployment module is used for determining the deployment context and the deployment strategy configuration corresponding to the business object unit according to the unit interface and the deployment strategy interface and deploying the business object unit.
CN202010575762.XA 2020-06-22 2020-06-22 Construction deployment method and device for large-scale software product Active CN111930415B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010575762.XA CN111930415B (en) 2020-06-22 2020-06-22 Construction deployment method and device for large-scale software product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010575762.XA CN111930415B (en) 2020-06-22 2020-06-22 Construction deployment method and device for large-scale software product

Publications (2)

Publication Number Publication Date
CN111930415A true CN111930415A (en) 2020-11-13
CN111930415B CN111930415B (en) 2022-07-12

Family

ID=73316652

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010575762.XA Active CN111930415B (en) 2020-06-22 2020-06-22 Construction deployment method and device for large-scale software product

Country Status (1)

Country Link
CN (1) CN111930415B (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101291252A (en) * 2008-05-31 2008-10-22 华为技术有限公司 Method, device and system for application deployment
CN105511906A (en) * 2015-11-25 2016-04-20 苏州科达科技股份有限公司 Automatic deploy method, device and system of video platform
CN108052333A (en) * 2017-12-11 2018-05-18 北京紫优能源科技有限公司 A kind of power scheduling centralized control system standardization Automation arranging method and framework
CN108881390A (en) * 2018-05-18 2018-11-23 深圳壹账通智能科技有限公司 the cloud platform deployment method, device and equipment of electronic account service
CN110377294A (en) * 2019-07-23 2019-10-25 上海金融期货信息技术有限公司 A kind of multi-environment configuration system and method based on DevOps
CN110647316A (en) * 2019-09-23 2020-01-03 苏州达家迎信息技术有限公司 Method and device for generating universal business object, computer equipment and storage medium
CN110753088A (en) * 2019-09-18 2020-02-04 平安科技(深圳)有限公司 System deployment method and device
CN111142878A (en) * 2018-11-06 2020-05-12 中兴通讯股份有限公司 SDN operation and maintenance method, device, equipment and readable storage medium
CN111176697A (en) * 2020-01-02 2020-05-19 广州虎牙科技有限公司 Service instance deployment method, data processing method and cluster federation
CN111176662A (en) * 2020-01-20 2020-05-19 厦门靠谱云股份有限公司 Architecture implementation method capable of being freely assembled and deployed in distributed and single environment and deployment method

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101291252A (en) * 2008-05-31 2008-10-22 华为技术有限公司 Method, device and system for application deployment
CN105511906A (en) * 2015-11-25 2016-04-20 苏州科达科技股份有限公司 Automatic deploy method, device and system of video platform
CN108052333A (en) * 2017-12-11 2018-05-18 北京紫优能源科技有限公司 A kind of power scheduling centralized control system standardization Automation arranging method and framework
CN108881390A (en) * 2018-05-18 2018-11-23 深圳壹账通智能科技有限公司 the cloud platform deployment method, device and equipment of electronic account service
CN111142878A (en) * 2018-11-06 2020-05-12 中兴通讯股份有限公司 SDN operation and maintenance method, device, equipment and readable storage medium
CN110377294A (en) * 2019-07-23 2019-10-25 上海金融期货信息技术有限公司 A kind of multi-environment configuration system and method based on DevOps
CN110753088A (en) * 2019-09-18 2020-02-04 平安科技(深圳)有限公司 System deployment method and device
CN110647316A (en) * 2019-09-23 2020-01-03 苏州达家迎信息技术有限公司 Method and device for generating universal business object, computer equipment and storage medium
CN111176697A (en) * 2020-01-02 2020-05-19 广州虎牙科技有限公司 Service instance deployment method, data processing method and cluster federation
CN111176662A (en) * 2020-01-20 2020-05-19 厦门靠谱云股份有限公司 Architecture implementation method capable of being freely assembled and deployed in distributed and single environment and deployment method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
KIRA2WILL: "DRY原则和设计模式", 《HTTPS://WWW.CNBLOGS.COM/KIRA2WILL/P/4015315.HTML》 *
WUHUACONG(伍华聪): "Winform开发框架的业务对象统一调用方式", 《HTTPS://WWW.CNBLOGS.COM/WUHUACONG/P/3409326.HTML》 *

Also Published As

Publication number Publication date
CN111930415B (en) 2022-07-12

Similar Documents

Publication Publication Date Title
CN109840429B (en) Intelligent contract deployment and calling method and device
US7908349B2 (en) Resource management with rule based consistency check
US20050262501A1 (en) Software distribution method and system supporting configuration management
CN110705237B (en) Automatic document generation method, data processing device and storage medium
CN111399828B (en) Model-driven logic device modeling method and terminal
CN106557307B (en) Service data processing method and system
CN111784108B (en) Modeling method and device of main data management platform
CN111460232A (en) Functional module searching method, device, terminal and computer readable storage medium
CN112506505A (en) Method for producing program code by code template engine
CN111176665B (en) High-capacity emmc mirror image manufacturing method and device
CN113448862A (en) Software version testing method and device and computer equipment
CN103500099A (en) Method for achieving quick software secondary development through expansion points and expansion
CN111930415B (en) Construction deployment method and device for large-scale software product
CN105677427A (en) Module upgrading method and device
CN102857817A (en) Set-top box production system and method capable of realizing dynamical loading
CN115982043A (en) Vehicle interface testing method, device, equipment and storage medium
CN115757172A (en) Test execution method and device, storage medium and computer equipment
CN112256978B (en) Data processing method, device and medium based on data model
CN114819631A (en) Multitask visualization method and device, computer equipment and storage medium
CN107844639B (en) Project standard structure automatic generation method and system
CN110674119A (en) Data processing method, system and computer readable storage medium
CN112817931A (en) Method and device for generating incremental version file
CN117725896A (en) Form filling method and device, electronic equipment and storage medium
CN117008890B (en) Extended application development system and method
CN111930718B (en) Node adjustment method and device for configuration management database

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
TA01 Transfer of patent application right

Effective date of registration: 20220614

Address after: 250101 Inspur science and Technology Park, 1036 Inspur Road, hi tech Zone, Jinan City, Shandong Province

Applicant after: Inspur Genersoft Co.,Ltd.

Address before: 250101 Inspur science and Technology Park, 1036 Inspur Road, hi tech Zone, Jinan City, Shandong Province

Applicant before: SHANDONG INSPUR GENESOFT INFORMATION TECHNOLOGY Co.,Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant