CN112835572B - Method and equipment for self-defining reference flow by means of project management tool - Google Patents
Method and equipment for self-defining reference flow by means of project management tool Download PDFInfo
- Publication number
- CN112835572B CN112835572B CN202110128400.0A CN202110128400A CN112835572B CN 112835572 B CN112835572 B CN 112835572B CN 202110128400 A CN202110128400 A CN 202110128400A CN 112835572 B CN112835572 B CN 112835572B
- Authority
- CN
- China
- Prior art keywords
- package
- model
- code engineering
- information
- dependency
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Marketing (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the specification discloses a method and equipment for self-defining a reference flow by a project management tool. To solve the problem that the reference package must be manually copied and cannot be fused with the general infrastructure. The method comprises the following steps: developing a model to generate a model package and a code engineering package, wherein the model package corresponds to the code engineering package; carrying out model dependency description on the model package in a model description file to obtain model dependency information; carrying out code engineering dependency description on the code engineering package in a code engineering description file to obtain code engineering dependency information; packaging and deploying the model package and the code engineering package, adding the model package into a project management tool, and pushing the model package and the code engineering package at the same time; and adding the model package reference according to the model dependency information, and adding the code engineering package reference corresponding to the model package.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for self-defining a reference flow by a project management tool.
Background
At present, in a scene of multi-module development, reference among the multi-modules is lacking, public reference source management is lacking, in the existing reference process, a reference party and a user are tightly coupled, and a developer cannot complete the reference process in a self-service mode. The models are dependent without tool support, the reference package must be copied manually, the manual copying is easy to make mistakes, the transfer of products is not facilitated, and the limitation is large.
In addition, there are situations where a developer builds rules and systems to provide content references, but cannot be fused with a generic infrastructure.
Disclosure of Invention
One or more embodiments of the present specification provide a method and apparatus for customizing a referencing flow by a project management tool. The method is used for solving the following technical problems: the problem of the referencing package having to be manually copied and not fused with the generic infrastructure.
To solve the above technical problems, one or more embodiments of the present specification are implemented as follows:
in a first aspect, the present specification provides a method for customizing a referencing flow by a project management tool, comprising:
developing a model to generate a model package and a code engineering package, wherein the model package corresponds to the code engineering package;
carrying out model dependency description on the model package in a model description file to obtain model dependency information;
carrying out code engineering dependency description on the code engineering package in a code engineering description file to obtain code engineering dependency information;
packaging and deploying the model package and the code engineering package, adding the model package into a project management tool, and pushing the model package and the code engineering package at the same time;
and adding the model package reference according to the model dependency information, and adding the code engineering package reference corresponding to the model package.
The method comprises the steps of carrying out dependency description on a model package and a code engineering package, packaging the model package and the code engineering package, defining a reference package, adding the model package into a project management tool, pushing the model package, carrying out model package reference according to dependency information, and defining a reference flow. Such that the party providing the reference extrapolates the package and the party using can obtain the package from a common location according to a common rule.
Optionally, removing the model package reference, and removing the code engineering package reference corresponding to the model package.
Optionally, acquiring the model dependency information, and judging whether the model package exists or not;
and if the information exists, removing the model dependent information, and removing the code engineering dependent information of the jar packet corresponding to the model packet.
The model dependency information comprises a model package belonging group, a model package unique identifier and a model package version number;
the model package belongs to a group, the model package unique identifier and the model package version number determine the uniqueness of the model.
Optionally, the code engineering dependent information includes: a group to which the code engineering package belongs, a code engineering package unique identifier, and a code engineering package version number;
and the code engineering package version number corresponds to the model package version number by using a preset rule.
Optionally, the group to which the model package belongs is the same as the group to which the code engineering package belongs, and the unique identifier of the model package is the same as the unique identifier of the code engineering package.
The unique identifier of the model package is the same as the unique identifier of the code engineering package, so that the uniqueness is determined, and the code engineering package and the model package can be ensured to correspond through preset rules.
Optionally, the packaging and deploying the model package and the code engineering package specifically includes:
judging whether the model package and the code engineering package exist or not;
if the model description file exists, reading the model description file, and acquiring the model dependent information;
creating a specific file, and adding the model dependent information and packaging related configuration information in the specific file;
and executing a packaging process according to the model dependency information and the packaging related configuration information.
Optionally, the package related configuration information includes package type information and configuration information of a plug-in;
and the plug-in expands the packing mechanism of the project management tool and executes the packing process of the project management tool.
Optionally, the executing a packaging process according to the model dependency information and the packaging related configuration information specifically includes:
acquiring configuration information of the plug-in;
acquiring a file to be packaged, wherein the file to be packaged comprises the model package and the code engineering package;
and acquiring the packing type information, and compressing and packing the file to be packed by using the plug-in.
In a second aspect, one or more embodiments of the present disclosure provide an apparatus for custom referencing a flow in dependence upon an item management tool, comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform:
developing a model to generate a model package and a code engineering package, wherein the model package corresponds to the code engineering package;
carrying out model dependency description on the model package in a model description file to obtain model dependency information;
carrying out code engineering dependency description on the code engineering package in a code engineering description file to obtain code engineering dependency information;
packaging and deploying the model package and the code engineering package, adding the model package into a project management tool, and pushing the model package and the code engineering package at the same time;
and adding the model package reference according to the model dependency information, and then adding the code engineering package reference corresponding to the model package.
One or more embodiments of the present specification provide a method and apparatus that rely on a project management tool to customize the referencing flow, by which the problem of referencing packages that must be manually copied and that cannot be fused with a common infrastructure is solved. The reference mechanism of the project management tool is used for reference, the packing mode of the project management tool is expanded, the model in the modeling process is packed into a packet which can be managed and identified by the project management tool, and the product is delivered to the project management tool for management, so that the packet management efficiency is improved, and the convenience is improved.
Drawings
In order to more clearly illustrate the embodiments of the present description or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some of the embodiments described in the present description, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow diagram of a method for relying on a project management tool to customize a referencing flow provided in one or more embodiments of the present disclosure;
FIG. 2 is a diagram of model package versus code engineering package provided in one or more embodiments of the present disclosure;
FIG. 3 is a flow diagram of a package deployment model package and code engineering package provided in accordance with one or more embodiments of the present disclosure;
FIG. 4 is a schematic diagram illustrating an implementation of a package deployment model package and code engineering package according to one or more embodiments of the present disclosure;
FIG. 5 is a flow diagram of removing model package references and code engineering package references provided by one or more embodiments of the present disclosure;
FIG. 6 is a schematic structural diagram of an apparatus for customizing a referencing flow by a project management tool according to one or more embodiments of the present disclosure.
Detailed Description
The embodiment of the specification provides a method and equipment for self-defining a reference flow by a project management tool.
In order to make the technical solutions in the present specification better understood by those skilled in the art, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
The following describes in detail the technical solutions provided by the embodiments of the present specification with reference to the accompanying drawings.
In the embodiments of the present specification, the project management tool is exemplified by maven, and the code engineering package is exemplified by jar package.
FIG. 1 is a flow chart of a method for customizing a referencing flow by a project management tool according to one or more embodiments of the present disclosure, which specifically includes the following steps:
s101: the method comprises the steps of developing a model to generate a model package and a code engineering package, wherein the model package corresponds to the code engineering package.
In one or more embodiments of the present disclosure, the tools used by the developer to develop the model are not limited. The developer develops a model, and a model product is formed after the model development is completed, wherein the model product comprises a model package and a code engineering package. The model package is abbreviated as mdppg, and the code engineering package mainly comprises produced codes, and takes jar packages as an example, and for the same model, the model package mdppg and the jar packages have the same unique identifier, and the model package mdppg and the jar packages correspond.
S102: and carrying out model dependency description on the model package in a model description file to obtain model dependency information.
In one or more embodiments of the present specification, the model dependency information includes a model package group, a model package unique identifier, and a model package version number, where the model package group, the model package unique identifier, and the model package version number determine a model uniqueness.
The model package is used as a product of the model and needs to be fused into a maven system, model dependency description can be carried out on the model package in a model description file, the model description file can be named mdprj, and it is understood that the name of the model description file can be customized and is not limited herein. The dependency description information in the model description file mdproj includes groupId, artifactId, version.
Wherein groupId defines the group to which the model package belongs, artifactId defines the unique flag of the model package, and version defines the version number of the model package. The group groupId uniquely identifies the artifactId and version as the basic coordinates on which it depends, and it should be noted that the basic coordinates are unique. For any dependency, the basic coordinates are most important, and maven can find the required dependency based on the coordinates. In the maven management system, there are a plurality of models, the basic coordinates of which are different from each other, and the uniqueness of the model in the maven management system is confirmed by the basic coordinates of the dependency composed of the belonging group groupId, the unique identification artifactId and version number version.
S103: and carrying out code engineering dependency description on the code engineering package in a code engineering description file to obtain code engineering dependency information.
In one or more embodiments of the present disclosure, the code engineering dependency information includes a group to which the code engineering package belongs, a code engineering package unique identifier, and a code engineering package version number, where the code engineering package version number corresponds to the model package version number using a preset rule.
The maven default product type is jar, the jar package is subjected to code engineering dependency description in the code engineering description file, and the code engineering dependency description information comprises a jar package belonging group, a jar package unique identifier and a jar package version number, and the explanation is that the jar package belonging group, the jar package unique identifier and the jar package version number can also uniquely determine one jar package. The jar packet version number corresponds to the model packet version number by using a preset rule, and the preset rule may be that letters are added at the back or the front of the model packet version number, for example, the model packet version number is 0.1.1, the jar packet version number may be M0.1.1 or 0.1.1M according to the rule, it is understood that the added letters may be arbitrary, and if the model packet version number is 0.1.1, the jar packet version number may also be J0.1.1 or 0.1.1J. The model package version number is not limited to the above embodiment, and may be 1.1 or the like. Similarly, the preset rule is not limited to the above embodiment, and the preset rule may be an underline added below the version number of the model package or a specific character added in front of or behind the version number of the model package, which is not specifically limited herein.
In one or more embodiments of the present disclosure, the group to which the model package belongs is the same as the group to which the code engineering package belongs, and the model package unique identifier is the same as the code engineering package unique identifier.
FIG. 2 is a diagram of model package versus code engineering package for one or more embodiments of the present disclosure, wherein the model package mdppg is juxtaposed with the jar package, having the same artifactld, wherein the artifactld defines a unique flag. The model package mdppg and jar package also have the same groupid, which defines the group to which they belong. The model packet mdkg and the jar packet have the same belonging group and unique identifier, the jar packet version number corresponds to the model packet version number by using a preset rule, and in the subsequent pushing process, the jar packet and the model packet mdkg are conveniently pushed simultaneously, so that the correspondence of the jar packet and the model packet is ensured, and the situation that the jar packet does not correspond to the model packet and the reference error occurs is avoided.
S104: packaging and deploying the model package and the code engineering package, adding the model package into a project management tool, and pushing the model package and the code engineering package at the same time.
After the model package dependency information and the jar package dependency information are described, a maven reference mechanism needs to be consulted, a maven packaging mechanism is expanded, the model package is added into a maven management mechanism for maven management and identification, and meanwhile, the model package and the jar package are pushed, so that the management efficiency of the model package is improved, and convenience is improved.
Fig. 3 is a flow diagram of a package deployment model package and a code engineering package according to one or more embodiments of the present disclosure.
In one or more embodiments of the present description, determining whether a model package and a code engineering package are present; if the model exists, reading a model description file to acquire model dependent information; creating a specific file, and adding model dependent information and packaging related configuration information in the specific file; and executing the packing process according to the model dependent information and the packing related configuration information.
Specifically, taking a particular file as a pore. Judging whether the model package and the code engineering package exist or not, if not, throwing out the abnormality, and ending the packaging process. If the model dependency information exists, reading the model dependency information in the model description file mdprj, creating a pon.xml file, and adding the model dependency information and the packaging related configuration information in the pon.xml file.
The model dependency information of the model package is added to the poc.xml file, and the group, the unique identifier and the version number defined during the description of the model package dependency are added to the poc.xml file, which should be noted that the poc.xml file may include more than one group, the unique identifier and the version number, may include a plurality of different groups, unique identifiers and version numbers, and of course, the poc.xml file may also include other information, such as information about a dependency range, a dependency type, or whether the dependency is optional.
In one or more embodiments of the present specification, the package-related configuration information includes package type information, plug-in configuration information, and a package mechanism of a plug-in expansion project management tool, and performs a project management tool package process.
And the packaging related configuration information is also required to be added in the pon.xml file, and the packaging related configuration information comprises packaging type information and plug-in configuration information. And adding the packaging related configuration information, namely adding a definition attribute in the pon.xml file, wherein the attribute name is packaging type and plug-in configuration. The package type information designates a package type, and as in the example of the pom.xml file, metadata-pack is package type information, metadata-pack designates a package type, and the type is mdppg, and the suffix is mdppg. The plug-in configuration information describes plug-in configuration, and the businessmodel-maven-plug in is a packaging plug-in, and expands a packaging mechanism, blends a model package type, rewrites a package process, namely rewrites a packaging process, and packages a mdppg type. If the packaging deployment model package and the code engineering are successful, the packaging process is finished, the reference package is customized, the model package and the jar package are successfully integrated into a maven system, then the dependent version can be searched and managed by fully utilizing the infrastructure, the dependent package is not required to be manually copied and can be integrated with the universal infrastructure, and the model is determined to be unique because the basic coordinates of the dependent description are not required to repeatedly develop the same model, and the reference is directly carried out in the maven system through the basic coordinates when the model is required to be referred. If the packaging deployment model package and the code engineering fail, the exception is thrown out, and the packaging process is ended. The developer can re-describe the dependency information in mdprj and re-perform the packaging process until the packaging and deployment model package and code engineering are successful.
FIG. 4 is a schematic diagram illustrating an implementation of a package deployment model package and code engineering package according to one or more embodiments of the present disclosure.
In one or more embodiments of the present description, configuration information for a plug-in is obtained; acquiring a file to be packaged, wherein the file to be packaged comprises a model package and a code engineering package; and obtaining packing type information, and compressing and packing the file to be packed by using the plug-in.
Specifically, after packaging is executed, firstly obtaining plug-in configuration, obtaining plug-in configuration information in a pore.xml file, and if the plug-in configuration is failed, throwing out an exception and ending packaging execution. It should be noted that, the developer does not configure the plug-in information in the pon.xml file, or the developer may obtain the plug-in configuration failure when configuring the plug-in information in the pon.xml file, and throw out the exception, which is not limited herein specifically.
If the plug-in configuration is successfully acquired, acquiring a file list, and acquiring files in the project from a maven context, wherein the files in the project comprise all files in the whole project, and all files comprise files of a model package and files of a jar package. The method comprises the steps of obtaining package type information, namely obtaining a file type and a path, wherein the file type comprises a model package type, a model package type is integrated by using a businessmodel-maven-plug-in extension maven package mechanism, files in a file list are compressed and packaged, and the file list comprises model packages.
After the model package and the jar package are compressed and packaged, the model package and the jar package are pushed, and in the pushing process, the model package and the jar package can be pushed at the same time, so that the jar package and the model package are guaranteed to correspond.
S105: and adding the model package reference according to the model dependency information, and adding the code engineering package reference corresponding to the model package.
The model dependency information determines the uniqueness of the model and the basic coordinates of the model, the maven finds the model package to be referred according to the basic coordinates, the model dependency information contains a version number, the version number of the jar package corresponds to the version number of the domain model package, the corresponding jar package reference can be found according to the added model package reference, and then the jar package reference corresponding to the model package is added.
By relying on the maven infrastructure for model reference, developers can complete the referencing process in a self-service manner. The model package which is pushed outwards in a direction for providing the reference is obtained from the public position according to the public rule, so that the manual copying of the model package is avoided, the product transmission is facilitated, and the application range is wide. And the model package pushed outwards in a direction providing the reference is obtained from the public position according to the public rule, so that a developer does not need to build rules and a system, and the reference content is provided.
In one or more embodiments of the present description, the model package reference is removed, and the code engineering package reference corresponding to the model package is removed.
Furthermore, one or more embodiments of the present description may not only model package references, but also remove model package references. A developer can create various models in the development process, various different model packages can be introduced, and unnecessary model packages can be inevitably introduced in the process of introducing the model packages, and at the moment, the unnecessary model packages can be removed by removing model package references.
FIG. 5 is a flow diagram of removing model package references and code engineering package references provided by one or more embodiments of the present disclosure.
In one or more embodiments of the present description, model dependency information is obtained, whether a model package exists is determined, and if so, the model dependency information is removed, and code engineering dependency information of a jar package corresponding to the model package is removed.
Specifically, removing model dependency information, unloading model reference, firstly obtaining model dependency information, judging whether a model package exists or not, if not, throwing out an abnormality, and stopping unloading the model reference flow. If the model package is judged to exist, removing the model dependency information in the model description file mddproj, and simultaneously removing jar package code engineering dependency information corresponding to the model package, so that the unloading model is successfully referenced, and ending the unloading model referencing flow.
It should be noted that, in the above embodiments, the mode of throwing the exception includes, but is not limited to, popup dialog, dividing the page into two pages, i.e., left and right pages or upper and lower pages, wherein one page throws the exception, the exception information is included when throwing the exception, and the exception information can locate the exception position, so that the developer can determine the exception information, quickly solve the exception, and accelerate the development process.
At least one of the above-described aspects employed by one or more embodiments of the present description addresses the problem of a reference package that must be manually copied and not be integrated with a common infrastructure. The method has the advantages that a maven quotation mechanism is used for reference, a maven packaging mode is expanded, a model in a modeling process is packaged into a package which can be managed and identified by the maven, a product is delivered to the maven for management, package management efficiency is improved, convenience is improved, a general maven infrastructure is used, and an existing development flow and an existing tool system are fused.
FIG. 6 is a schematic structural diagram of an apparatus for customizing a referencing procedure by a project management tool according to one or more embodiments of the present disclosure, where the apparatus includes:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform:
developing a model to generate a model package and a code engineering package, wherein the model package corresponds to the code engineering package;
carrying out model dependency description on the model package in a model description file to obtain model dependency information;
carrying out code engineering dependency description on the code engineering package in a code engineering description file to obtain code engineering dependency information;
packaging and deploying the model package and the code engineering package, adding the model package into a project management tool, and pushing the model package and the code engineering package at the same time;
and adding the model package reference according to the model dependency information, and adding the code engineering package reference corresponding to the model package.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The foregoing is merely one or more embodiments of the present description and is not intended to limit the present description. Various modifications and alterations to one or more embodiments of this description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of one or more embodiments of the present description, is intended to be included within the scope of the claims of the present description.
Claims (4)
1. A method of customizing a referencing flow in dependence upon a project management tool, comprising:
developing a model to generate a model package and a code engineering package, wherein the model package corresponds to the code engineering package;
carrying out model dependency description on the model package in a model description file to obtain model dependency information;
carrying out code engineering dependency description on the code engineering package in a code engineering description file to obtain code engineering dependency information;
packaging and deploying the model package and the code engineering package, adding the model package into a project management tool, and pushing the model package and the code engineering package;
adding the model package reference according to the model dependency information, and adding a code engineering package reference corresponding to the model package;
the model dependency information comprises a model package belonging group, a model package unique identifier and a model package version number;
the model package belongs to a group, the model package unique identifier and the model package version number determine the uniqueness of the model;
the code engineering dependency information includes: a group to which the code engineering package belongs, a code engineering package unique identifier, and a code engineering package version number;
the code engineering package version number corresponds to the model package version number by using a preset rule;
the group to which the model package belongs is the same as the group to which the code engineering package belongs, and the unique identifier of the model package is the same as the unique identifier of the code engineering package;
the packaging and deploying the model package and the code engineering package specifically comprises the following steps:
judging whether the model package and the code engineering package exist or not;
if the model description file exists, reading the model description file, and acquiring the model dependent information;
creating a specific file, and adding the model dependent information and packaging related configuration information in the specific file;
executing a packaging process according to the model dependent information and the packaging related configuration information;
the packing related configuration information comprises packing type information and plug-in configuration information;
the plug-in expands a packing mechanism of the project management tool and executes a packing process of the project management tool;
the step of executing the packaging process according to the model dependent information and the packaging related configuration information specifically comprises the following steps:
acquiring configuration information of the plug-in;
acquiring a file to be packaged, wherein the file to be packaged comprises the model package and the code engineering package;
and acquiring the packing type information, and compressing and packing the file to be packed by using the plug-in.
2. The method according to claim 1, wherein the method further comprises:
removing the model package reference;
and removing the code engineering package references corresponding to the model packages.
3. The method according to claim 2, characterized by comprising:
acquiring the model dependency information and judging whether the model package exists or not;
and if the code engineering package exists, removing the model dependency information, and removing the code engineering dependency information of the code engineering package corresponding to the model package.
4. An apparatus for customizing a referencing flow in dependence upon a project management tool, comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform:
developing a model to generate a model package and a code engineering package, wherein the model package corresponds to the code engineering package;
carrying out model dependency description on the model package in a model description file to obtain model dependency information;
carrying out code engineering dependency description on the code engineering package in a code engineering description file to obtain code engineering dependency information;
packaging and deploying the model package and the code engineering package, adding the model package into a project management tool, and pushing the model package and the code engineering package at the same time;
adding the model package reference according to the model dependency information, and then adding a code engineering package reference corresponding to the model package;
the model dependency information comprises a model package belonging group, a model package unique identifier and a model package version number;
the model package belongs to a group, the model package unique identifier and the model package version number determine the uniqueness of the model;
the code engineering dependency information includes: a group to which the code engineering package belongs, a code engineering package unique identifier, and a code engineering package version number;
the code engineering package version number corresponds to the model package version number by using a preset rule;
the group to which the model package belongs is the same as the group to which the code engineering package belongs, and the unique identifier of the model package is the same as the unique identifier of the code engineering package;
the packaging and deploying the model package and the code engineering package specifically comprises the following steps:
judging whether the model package and the code engineering package exist or not;
if the model description file exists, reading the model description file, and acquiring the model dependent information;
creating a specific file, and adding the model dependent information and packaging related configuration information in the specific file;
executing a packaging process according to the model dependent information and the packaging related configuration information;
the packing related configuration information comprises packing type information and plug-in configuration information;
the plug-in expands a packing mechanism of the project management tool and executes a packing process of the project management tool;
the step of executing the packaging process according to the model dependent information and the packaging related configuration information specifically comprises the following steps:
acquiring configuration information of the plug-in;
acquiring a file to be packaged, wherein the file to be packaged comprises the model package and the code engineering package;
and acquiring the packing type information, and compressing and packing the file to be packed by using the plug-in.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110128400.0A CN112835572B (en) | 2021-01-29 | 2021-01-29 | Method and equipment for self-defining reference flow by means of project management tool |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110128400.0A CN112835572B (en) | 2021-01-29 | 2021-01-29 | Method and equipment for self-defining reference flow by means of project management tool |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112835572A CN112835572A (en) | 2021-05-25 |
| CN112835572B true CN112835572B (en) | 2024-03-29 |
Family
ID=75932409
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110128400.0A Active CN112835572B (en) | 2021-01-29 | 2021-01-29 | Method and equipment for self-defining reference flow by means of project management tool |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112835572B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116578281B (en) * | 2023-07-13 | 2023-11-24 | 江西金发金融信息服务有限公司 | Web page development method, system, electronic device and storage medium based on code package |
| CN118295691B (en) * | 2024-03-07 | 2025-05-16 | 深圳市道旅旅游科技股份有限公司 | Quotation package packaging method and related device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106104467A (en) * | 2014-06-30 | 2016-11-09 | 北京新媒传信科技有限公司 | A kind of Automation arranging method and terminal |
| CN106990960A (en) * | 2017-03-28 | 2017-07-28 | 阿里巴巴集团控股有限公司 | Code dispositions method and device |
| CN108519874A (en) * | 2017-02-27 | 2018-09-11 | 腾讯科技（深圳）有限公司 | The generation method and device of Python project packets |
| CN109725909A (en) * | 2018-05-07 | 2019-05-07 | 中国平安人寿保险股份有限公司 | Code file is packaged dispositions method, continuous integrating server and system |
| CN110442376A (en) * | 2019-07-19 | 2019-11-12 | 精硕科技（北京）股份有限公司 | A kind of method and device for realizing Software package |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8949788B2 (en) * | 2008-12-17 | 2015-02-03 | Red Hat, Inc. | Building and packaging software |
| US8516437B2 (en) * | 2010-01-22 | 2013-08-20 | Ebay Inc. | System and method for creating, managing, and reusing schema type definitions in services oriented architecture services, grouped in the form of libraries |
| US10095499B2 (en) * | 2016-09-16 | 2018-10-09 | Microsoft Technology Licensing, Llc | Optimization for multi-project package manager |
-
2021
- 2021-01-29 CN CN202110128400.0A patent/CN112835572B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106104467A (en) * | 2014-06-30 | 2016-11-09 | 北京新媒传信科技有限公司 | A kind of Automation arranging method and terminal |
| CN108519874A (en) * | 2017-02-27 | 2018-09-11 | 腾讯科技（深圳）有限公司 | The generation method and device of Python project packets |
| CN106990960A (en) * | 2017-03-28 | 2017-07-28 | 阿里巴巴集团控股有限公司 | Code dispositions method and device |
| CN109725909A (en) * | 2018-05-07 | 2019-05-07 | 中国平安人寿保险股份有限公司 | Code file is packaged dispositions method, continuous integrating server and system |
| CN110442376A (en) * | 2019-07-19 | 2019-11-12 | 精硕科技（北京）股份有限公司 | A kind of method and device for realizing Software package |
Non-Patent Citations (2)
| Title |
|---|
| Maven在Java项目中的引入及应用;江日念;林霞;乔德新;;电脑知识与技术(第21期);全文 * |
| 基于源代码分析的逆向建模;彭四伟;朱群雄;;计算机应用研究(第07期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112835572A (en) | 2021-05-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA3155732A1 (en) | Business process configuring method, business request processing method, and devices | |
| CN112835587B (en) | Compiling integration method and device | |
| CN112764753B (en) | Project deployment method and device, electronic equipment and storage medium | |
| CN111400119B (en) | Multi-project and multi-platform self-adaptive chip design FPGA prototype verification method and system | |
| KR100871563B1 (en) | Apparatus and method for component based software development | |
| CN112835572B (en) | Method and equipment for self-defining reference flow by means of project management tool | |
| CN105630557B (en) | Hot patch method and apparatus | |
| CN109814873B (en) | Code publishing method and device | |
| CN111158655A (en) | Software operating environment deployment method and device | |
| CN106815049B (en) | Method and device for upgrading feature library | |
| CN107402765A (en) | A kind of code inspection dissemination method and system | |
| CN106528170A (en) | Software package release method and system based on multi-language environment | |
| CN114385504A (en) | Microservice application development and debugging method and device | |
| CN115904933A (en) | Code warehouse management method and device, electronic equipment and storage medium | |
| CN107193582B (en) | Publishing method and system | |
| CN108108169A (en) | Multi-branch construction method and system based on Jenkins | |
| CN111459535A (en) | Branch merging method, device, equipment and computer storage medium | |
| CN108268266A (en) | A kind of upgrade method and device | |
| CN114185555A (en) | Server deployment method and device and electronic equipment | |
| CN111142877B (en) | Automatic extracting method, system and storage medium for interface function and parameter type of ROM chip patch | |
| CN111522591A (en) | Method for realizing quick start software of VxWorks cert and computer program product | |
| CN116301908B (en) | Buildroot local compiling method and system based on Shenwei architecture | |
| CN117389660A (en) | Method and system for detecting jar packet homonymy | |
| CN106933763A (en) | Data processing method and device | |
| CN116185484A (en) | Method and device for realizing consistency of version library and version product data |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20240227 Address after: 250101 Inspur science and Technology Park, 1036 Inspur Road, hi tech Zone, Jinan City, Shandong Province Applicant after: Inspur Genersoft Co.,Ltd. Country or region after: China 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. Country or region before: China |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |