CN113254426B - CAD data distributed version control system based on branches and base lines - Google Patents
CAD data distributed version control system based on branches and base lines Download PDFInfo
- Publication number
- CN113254426B CN113254426B CN202110787934.4A CN202110787934A CN113254426B CN 113254426 B CN113254426 B CN 113254426B CN 202110787934 A CN202110787934 A CN 202110787934A CN 113254426 B CN113254426 B CN 113254426B
- Authority
- CN
- China
- Prior art keywords
- branch
- data
- development
- cad data
- baseline
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F30/00—Computer-aided design [CAD]
- G06F30/10—Geometric CAD
- G06F30/12—Geometric CAD characterised by design entry means specially adapted for CAD, e.g. graphical user interfaces [GUI] specially adapted for CAD
Abstract
The invention relates to a CAD data distributed version control system based on branches and baselines, a remote central data warehouse and a plurality of local data warehouses, which solves the independence of the work of engineers, ensures the sharing and the transmission of product data, achieves the effect of parallel design, and can reduce the redundancy of the remote central data warehouse, a data management branch is built in the remote central data warehouse, the data management branch comprises a development branch, a trial-production branch, a release branch and a change branch, ensures the traceability of the CAD data in the whole product life cycle management, ensures the independence of the development and the change problem repair of new characteristics, is convenient to adjust the customer requirements, meets the differentiated requirements of customers, and can completely recover the product data and the process data from the clone copy of the local data warehouse when the remote central data warehouse fails to recover due to disaster, the distributed storage management effect is achieved, and the data safety of the CAD is improved.
Description
Technical Field
The invention relates to the technical field of data management, in particular to a CAD data distributed version control system based on branches and baselines.
Background
The central centralized version control is a mainstream mode of a PDM/PLM (product data management/product life cycle management) management structure and an electronic engineering file history change record in the industry at present, namely, an engineering file is stored in a central server, when an engineer starts to work, the engineering file is directly copied from a server check-out (detected) product/project engineering file, after the modification is completed, the work done by the engineer is directly submitted to the central server, and the whole process is an exclusive behavior, namely, after the engineering file is detected by one engineer, other engineers cannot perform any operation on the engineering file.
In the future complex and changeable product development environment and enterprise digital transformation process, the central centralized version control faces many challenges, for example, under the condition of parallel, multi-scheme and customer-designed main melody, the following typical problems are brought about by centralized version control management of product CAD data: 1. the support of parallel design is lacked, the centralized version control is a free exclusive data control mode, and the design team can not be effectively oriented to carry out parallel research and development based on product characteristics, namely, each time of iterative update of the version can be continued after the previous engineer releases resources; 2. a great deal of unnecessary version redundancy is caused, as engineers hope to keep the change in the design process, a great deal of CAD data copies of the intermediate process are submitted to the service, but most of the intermediate process versions do not have any guiding and reference function for a product design team, so that a great deal of redundancy occurs in a central CAD data warehouse, the complexity of version tracing is brought, and system resources are seriously wasted; 3. product CAD data version dependence and tracking capacity are lacked, product research and development need to be subjected to detailed design, verification, trial production, volume production and after-sale, engineering change spans multiple stages of product research and development, derived product versions can appear in different client processes to meet client differentiation requirements, actually, product data in the processes often have dependence and relevance, centralized version control cannot distinguish research and development stages where schematic data are located, and client requirements corresponding to the data cannot be expressed; 4. the analysis is influenced by missing changes, and the centralized version control cannot distinguish the research and development stage where the schematic data is located and the specific client version, so that the analysis and execution of change management have no technical support, and the changes cannot be effectively transmitted; 5. data security has hidden dangers, some unexpected factors cause that the central version image cannot be recovered due to disasters, and the security of product development data of enterprise core competitiveness also brings great challenges.
Disclosure of Invention
To overcome the deficiencies of the prior art, it is an object of the present invention to provide a branch and baseline based CAD data distributed version control system.
The technical scheme adopted by the invention is as follows:
a CAD data distributed version control system based on branch and base line comprises:
the system comprises a plurality of local data warehouses, a plurality of data warehouse management units and a plurality of data warehouse management units, wherein the local data warehouses are used for managing CAD data of each engineer independently, and each local data warehouse is interacted with work area data of the corresponding engineer respectively;
the remote central data warehouse is used for data sharing, and the plurality of local data warehouses are in communication connection with the remote central data warehouse;
the local data warehouse is internally provided with a clone copy of the remote central data warehouse, a data management branch is built in the remote central data warehouse and comprises:
and the development branch is used for uploading when an engineer finishes design work in the local data warehouse or needs to inform the whole team of the intermediate result of the design, and comprises a plurality of development nodes, and each development node is in communication connection with the corresponding local data warehouse.
And the trial-manufacturing branch is used for trial-manufacturing the digital prototype of the product, the CAD data of the development branch needs to be copied to the trial-manufacturing branch when the trial-manufacturing is submitted, and the repair of the CAD data needs to be switched to the trial-manufacturing branch.
And the release branch is used for archiving the CAD data, copying the data repaired by the trial-manufacture branch to the release branch, and establishing a release baseline for the release branch at the current time point, wherein the release baseline represents the release version of the product.
And the change branch is used for improving the change initiated by the problem, pulling the CAD data from the corresponding publishing base line to the change branch, finishing the modification of the CAD data on the change branch in the change process, and merging the CAD data modified in the change process into the publishing branch to form a new publishing base line of an optimized version after the problem is repaired.
Preferably, an engineer independent work branch is built in the local data warehouse and used for the engineer to independently complete the design work of the corresponding product CAD data in the development branch, and the engineer independent work is in communication connection with the corresponding development node of the development branch.
Preferably, a new scheme branch is established in the independent work branch of the engineer and used for developing or correcting a new function, a development base line is established on the development branch, the new scheme branch pulls CAD data from the development base line, and the CAD data is merged into the development branch after being modified.
Preferably, the engineer independent work branch and the development branch are both frozen when the trial branch is executed, and the CAD data repaired on the trial branch is merged into the development branch after the trial branch.
Preferably, the data management branch further comprises a client branch, and the client branch is in communication connection with the release baseline and is used for performing customized modification on the current release version of the release baseline and performing design and verification work on the client branch.
Preferably, the number of the data management branches is several, and the development nodes in the data management branches are connected with another data management branch through iterative communication.
Preferably, the local data warehouse is in communication connection with the working area through a local cache area, and the local cache area is used for temporarily storing the CAD data.
Preferably, the CAD data modified on the change branch is merged to the development node corresponding to the development branch in a merging manner, and then is subjected to trial production through the trial production branch and then is sent to the release branch to form a new release baseline of the formal version.
Preferably, a general-purpose component standard library is built in the remote central data warehouse and is issued and filed through a data management branch.
Preferably, the general-purpose component standard library records the components, the component lists and the corresponding versions reused by the product in an XML mode, analyzes the change influence of the general-purpose components and the standard components in the general-purpose component standard library, and timely informs a product responsible person of the changed content in an event mode.
The invention has the beneficial effects that:
in the CAD data distributed version control system based on the branches and the base line, independent work of each engineer is not interfered with each other, so that the independence of the work of the engineers is solved, the sharing and transmission of product data are ensured, and the effect of parallel design is achieved;
the local data warehouse is fully utilized, and the redundancy of a remote central data warehouse is reduced;
the traceability of the CAD data in the whole product life cycle management is ensured through the evolution of the product in the data management branch;
accurate and flexible change control is realized, an independent change branch control change process is established for the change of the CAD data independently, and the independence of development of new characteristics and repair of change problems is ensured; the client requirements can be adjusted conveniently, and the client differentiation requirements can be met;
almost all engineer desktops participating in product design clone version images of a remote central data warehouse, and when the remote central data warehouse cannot recover due to disasters, the cloned copies of the local data warehouse can completely recover product data and process data, so that distributed storage is achieved, and the safety of CAD data is improved;
the method is characterized in that the derived customized products are managed based on customized customer branches, and the change influence is analyzed accordingly, so that the changed content and influence can be conveniently and timely informed to a product principal in an event manner during change;
the universal part library of the standard parts is established in the remote central data warehouse and published and filed through the data management branch, so that the problems of evolution and reuse of the standard parts and the universal parts are solved, and the construction and reuse capacity of the standard parts and the universal parts is provided in the local data warehouse so as to submit the reused component drawings.
Drawings
FIG. 1 is a block diagram of a CAD data distributed version control baseline.
Fig. 2 is a block diagram of a CAD data distributed version control branch.
Fig. 3 is a block diagram of a new scenario branch.
Fig. 4 is a schematic diagram of the communication link between the local data warehouse and the remote central data warehouse.
Fig. 5 is a schematic diagram of archiving CAD data in a local data repository.
FIG. 6 is a block diagram of a customer branch.
Fig. 7 is a schematic diagram of a building call of a universal standard component library.
FIG. 8 is a block diagram of a multi-scheme parallelization.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
Referring to fig. 1 to 8, the present invention provides a technical solution: a CAD data distributed version control system based on branch and base line comprises:
the system comprises a plurality of local data warehouses, a plurality of data warehouse management units and a plurality of data warehouse management units, wherein the local data warehouses are used for managing CAD data of each engineer independently, and each local data warehouse is interacted with work area data of the corresponding engineer respectively;
the remote central data warehouse is used for data sharing, and the plurality of local data warehouses are in communication connection with the remote central data warehouse;
the local data warehouse is internally provided with a clone copy of the remote central data warehouse, and a data management branch is built in the remote central data warehouse, so that CAD data at different stages can be managed and tracked conveniently, as shown in FIG. 2, the data management branch comprises:
the development branch is used for uploading the engineering workers to the local data warehouse to complete the design work or need to inform the whole team of the intermediate result of the design, and comprises a plurality of development nodes, and each development node is in communication connection with the corresponding local data warehouse; the development branch acts on a product development stage, an engineer is not allowed to directly modify and submit, the engineer takes the development branch as a starting point and develops or modifies a new function in an independent work branch of the engineer, when the engineer considers that the engineer completes the design work or needs to inform the middle result of the design to the whole team, a merging request is sent to the development branch, the development branch is actually maintained with the latest CAD data in the product development process, so that the team leader and the product leader can check the whole product data condition, the engineer newly joining the team can be ensured to obtain the latest product data, and the independent work branch of the engineer independently working on the basis of the latest design result is established.
And the trial-manufacturing branch is used for copying the CAD data of the development branch to the trial-manufacturing branch when the digital prototype of the product is basically determined and trial manufacturing is submitted, the product enters a trial-manufacturing stage at the moment, the repair of the CAD data needs to be switched to the trial-manufacturing branch, the independent work branch and the development branch of an engineer are frozen and are not allowed to be modified, the repaired CAD data on the trial-manufacturing branch can be merged to the development branch after trial manufacturing, the CAD data can be conveniently developed and reused, and the latest CAD data in the research and development process can be conveniently maintained so that a team leader and a product leader can check the integral product data condition.
And after the product trial production verification passes, the product responsible person initiates a product release process, namely, the CAD data is filed, the data repaired by the trial production branch is copied to the release branch, a release base line is established for the release branch at the current time point, and the release base line represents the release version of the product.
The change branch is used for the change initiated by the problems of after-sale of the product, engineering quality, process improvement and the like, at this time, the product possibly iterates in the next version, the CAD data needs to be pulled from the specific publishing base line needing to be changed to the change branch, the modification of the CAD data in the change process is completed on the change branch, after the problems are repaired, the CAD data modified in the change process is merged to the publishing branch to form a new publishing base line of an optimized version (the publishing base line is not trial-manufactured, so the CAD data can be quickly generated and can be temporarily used, but is not a formal version), and the CAD data modified on the change branch is merged to the development node corresponding to the development branch in a merging mode, and then the CAD data is trial-manufactured through the trial-manufacturing branch and then sent to the publishing branch to form a new publishing base line of the formal version.
The client branch is in communication connection with the release base line and is used for performing customized modification on the current release version of the release base line, when one release version based on the standard product needs to be subjected to customized modification, the client branch can be pulled from the corresponding release base line to face a specific client, and all design and verification work is finished on the client branch, so that the independence of client-oriented design is ensured, and the traceability of the customized product and the standard product is established; as shown in fig. 6, the problem of influence of product change on customized products and versions of standard products is solved, customized products are often developed on the basis of one version of the standard products in a customized manner, a customer branch can be pulled on the basis of a release baseline, when a product initiates change, a change influence report is automatically formed according to the branch relation and the relation between the baseline and the branch, influence analysis caused by the change is informed, and decision and execution of the change are accelerated.
In order to ensure that respective works of engineers are not interfered with each other, in this embodiment, preferably, an engineer independent work branch is built in the local data warehouse and is used for the engineers to independently complete corresponding product CAD data design works in the development branches, and the engineer independent work is in communication connection with corresponding development nodes of the development branches; acting on the development stage of the product, each engineer has an independent engineer independent work branch, and when the engineers acquire design tasks, the respective CAD design work of the product is completed, and the respective work is guaranteed not to interfere with each other.
In order to facilitate development of new features or new functions, in this embodiment, preferably, a new scheme branch is set up in the engineer independent work branch for development or modification of the new functions, a development baseline is set up on the development branch, CAD data is pulled from the development baseline by the new scheme branch, and the CAD data is merged into the development branch after being modified by the new scheme branch; if a new structural design scheme needs to be verified in the product development process, and it is desirable to reuse the current design without affecting the product development progress, as shown in fig. 3, a design branch of the new scheme (i.e., a new scheme branch) is pulled from a certain baseline of the development branch to perform new design verification, which not only satisfies the requirement of reusing the design, but also ensures that the CAD data of the main development is not affected, ensures the product development progress, and after the new design verification passes, a request for merging to the development branch can be initiated.
In order to facilitate parallel verification of multiple schemes, in this embodiment, preferably, the data management branch is provided with a plurality of development nodes, and the development nodes in the data management branch are connected with another data management branch through iterative communication; as shown in fig. 8, the product design involves multi-scheme parallel verification, a policy of independently working scheme branches (i.e., data management branches) can be established for each scheme, the respective scheme design is completed on different scheme branches, if trial production and proofing are required to be submitted, the data of the scheme branches are merged into the development nodes of the main development branch in the main scheme branches to submit trial production until the verification is finished, and if the scheme of the scheme (# 3) branch is finally selected, the entire product has actually completed iterative release of multiple versions.
In order to facilitate temporary storage of the CAD data, in this embodiment, preferably, the local data warehouse is in communication connection with the working area through a local cache area, and the local cache area is used for temporarily storing the CAD data.
In order to facilitate the reuse of the common parts/standard parts and improve the working efficiency, in the embodiment, preferably, a common part standard part library is built in a remote central data warehouse, the common part standard part library is developed, trial-manufactured, issued and changed through a data management branch, and finally, the issuing and filing are realized, as shown in fig. 7, the common part/standard part data in the remote central data warehouse is cloned through a plug-in calling API, an engineer detects the common part/standard part data from a local data warehouse to a working area, the common part/standard part data is conveniently reused, the common part standard part library records the components, the device list and the corresponding version for product reuse through an XML mode, the change influence of the common parts and the standard parts in the common part standard part library is analyzed, and the changed content is timely informed to a product responsible person in an event mode, whether to make a synchronized change to the affected product.
As shown in fig. 1, an enterprise-level distributed CAD data management and control environment is established for a product development team, engineers can well manage procedural versions of individual designs by using the technology, and simultaneously, when individual design results need to be shared and submitted, a merge application is initiated and merged into development branches of a remote central data warehouse, so that the parallel design problem of the CAD design team is solved, the number of central versions is reduced, the working independence of the engineers is solved, and the sharing and the transmission of product data are guaranteed. The method is characterized in that the connection of a remote central data warehouse and a plurality of local data warehouses is taken as a base line, the distributed version control of the CAD data is realized by combining a plurality of branches (namely, an engineer independent work branch, a development branch, a trial production branch, a release branch, a change branch and a customer branch), the mature process of CAD design and the change and change history of the CAD data are completely recorded, so that the CAD data has traceability in the whole product life cycle management, the CAD data management at different stages is solved, the CAD data can be circulated along with the maturity of products, the product development, trial production repair, product release and change management can be better completed, and the product research and development process of enterprises can be standardized.
Accurate and flexible change control is realized, independent new scheme branches and change branches are independently established for the change of the CAD data, the change process is controlled, and the development of new characteristics and the independence of repairing the change problems are guaranteed.
The release base line represents the release version of the product, the product data of the archived release version is frozen to express the manufacturable data of the product, the correctness of the data is ensured, and the preparation work and the management cost of the product manufacture are reduced.
Take the communication connection between the local data warehouse and the remote central data warehouse as an example:
the local data warehouse development API supports CAD design tool integration, as shown in fig. 4, by calling the API through a plug-in to clone the product CAD data of the remote central data warehouse, submit new models to the local data warehouse in real time, and merge the data of the local data warehouse to the remote central data warehouse.
The work flow of an engineer: the engineer clones the CAD data of the remote central data warehouse in the CAD design tool, and the CAD data is synchronized to the local data warehouse at the moment; an engineer detects CAD data from a local data warehouse to a working area and opens a CAD drawing of the working area; the engineer modifies the CAD model or the newly added model in the CAD design tool; saving the CAD model, and automatically adding the newly added model and the modified model to a local cache region by the plug-in; the engineer submits the current modification to the local data warehouse, and the result is shown in fig. 5; if the CAD data needs to be merged into the remote central data warehouse, the remote central data warehouse submits a merging application, and the remote central data warehouse merges the CAD data of an engineer in the local data warehouse.
Finally, it should be noted that: although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that changes may be made in the embodiments and/or equivalents thereof without departing from the spirit and scope of the invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A CAD data distributed version control system based on branch and base line is characterized by comprising:
the system comprises a plurality of local data warehouses, a plurality of data warehouse management units and a plurality of data warehouse management units, wherein the local data warehouses are used for managing CAD data of each engineer independently, and each local data warehouse is interacted with work area data of the corresponding engineer;
the remote central data warehouse is used for data sharing, and the local data warehouses are in communication connection with the remote central data warehouse;
a clone copy of a remote central data warehouse is arranged in the local data warehouse, a data management branch is built in the remote central data warehouse, and the data management branch comprises:
the development branch is used for uploading the engineering work in a local data warehouse or when the engineering work needs to be informed to the whole team, and comprises a plurality of development nodes, and each development node is in communication connection with the corresponding local data warehouse;
the trial-manufacturing branch is used for trial-manufacturing a digital prototype of a product, the CAD data of the development branch needs to be copied to the trial-manufacturing branch when the trial-manufacturing is submitted, and the repair of the CAD data needs to be switched to the trial-manufacturing branch;
the release branch is used for archiving CAD data, copying the data repaired by the trial-manufacture branch to the release branch, and establishing a release baseline for the release branch at the current time point, wherein the release baseline represents a release version of a product;
and the change branch is used for improving the change initiated by the problem, pulling the CAD data from the corresponding issue baseline to the change branch, finishing the modification of the CAD data in the change process on the change branch, and merging the CAD data modified in the change process into the issue branch to form a new issue baseline of an optimized version after the problem is repaired.
2. The distributed branch and baseline-based CAD data version control system of claim 1, wherein: an engineer independent work branch is built in the local data warehouse and used for the engineer to independently complete the design work of the corresponding product CAD data in the development branch, and the engineer independent work is in communication connection with the corresponding development node of the development branch.
3. The distributed branch and baseline-based CAD data version control system of claim 2, wherein: the engineering independent work branch is built with a new scheme branch for developing or correcting new functions, a development base line is built on the development branch, CAD data are pulled from the development base line by the new scheme branch, and the CAD data are merged into the development branch after being modified.
4. The distributed branch and baseline-based CAD data version control system of claim 2, wherein: and when the trial-manufacture branch is executed, the independent work branch and the development branch of the engineer are both frozen, and the CAD data repaired on the trial-manufacture branch is merged to the development branch after trial-manufacture.
5. The distributed branch and baseline-based CAD data version control system of claim 1, wherein: the data management branch also comprises a client branch which is in communication connection with the release base line and is used for performing customized modification on the current release version of the release base line and performing design and verification work on the client branch.
6. The distributed branch and baseline-based CAD data version control system of claim 1, wherein: the data management branch is provided with a plurality of development nodes, and the development nodes in the data management branch are connected with another data management branch through iterative communication.
7. The distributed branch and baseline-based CAD data version control system of claim 1, wherein: the local data warehouse is in communication connection with the working area through a local cache area, and the local cache area is used for temporarily storing CAD data.
8. The distributed branch and baseline-based CAD data version control system of claim 1, wherein: and the CAD data modified on the change branch is merged to the development nodes corresponding to the development branches in a merging mode, and then is subjected to trial production through the trial production branches and then is sent to the release branches to form a new release baseline of the formal version.
9. The distributed branch and baseline-based CAD data version control system of claim 1, wherein: and a universal part standard component library is built in the remote central data warehouse and is issued and filed through a data management branch.
10. The distributed branch and baseline-based CAD data version control system of claim 9, wherein: the general component standard component library records the components, the component lists and the corresponding versions reused by the products in an XML mode, analyzes the change influence of the general components and the standard components in the general component standard component library, and timely informs a product responsible person of the changed content in an event mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110787934.4A CN113254426B (en) | 2021-07-13 | 2021-07-13 | CAD data distributed version control system based on branches and base lines |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110787934.4A CN113254426B (en) | 2021-07-13 | 2021-07-13 | CAD data distributed version control system based on branches and base lines |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113254426A CN113254426A (en) | 2021-08-13 |
| CN113254426B true CN113254426B (en) | 2021-10-29 |
Family
ID=77191130
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110787934.4A Active CN113254426B (en) | 2021-07-13 | 2021-07-13 | CAD data distributed version control system based on branches and base lines |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113254426B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114579545A (en) * | 2022-01-19 | 2022-06-03 | 广州新科佳都科技有限公司 | Method and device for querying data of multiple bins based on subway station system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302533A (en) * | 2014-07-25 | 2016-02-03 | 腾讯科技（深圳）有限公司 | Code synchronizing method and apparatus |
| CN110866492A (en) * | 2019-11-13 | 2020-03-06 | 广州品唯软件有限公司 | Baseline branch identification method and device and computer system |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5729744A (en) * | 1996-06-10 | 1998-03-17 | International Business Machine Corp. | Method and system of enhanced versioning control of objects in a data processing system using change control information which includes reasons for changes |
| US8510659B2 (en) * | 2009-08-14 | 2013-08-13 | Oracle International Corporation | Analytical previewing of multi-dimensional sales territory proposals |
| US10467202B2 (en) * | 2017-07-21 | 2019-11-05 | Bank Of America Corporation | System for multi-release and parallel development of a database |
| CN109426604A (en) * | 2017-08-22 | 2019-03-05 | 阿里巴巴集团控股有限公司 | The monitoring method and equipment of code development |
| CN109725926B (en) * | 2017-10-31 | 2022-05-31 | 阿里巴巴集团控股有限公司 | Method and device for managing baseline and data processing method |
| US11222091B2 (en) * | 2018-12-27 | 2022-01-11 | Citrix Systems, Inc. | Systems and methods for development of web products |
| CN111382049B (en) * | 2018-12-28 | 2023-05-02 | 阿里云计算有限公司 | Code submitting method and device and electronic equipment |
| CN110489347A (en) * | 2019-08-20 | 2019-11-22 | 深圳市钱海网络技术有限公司 | Method for edition management, device, equipment and readable storage medium storing program for executing based on GIT |
| CN111309629A (en) * | 2020-03-12 | 2020-06-19 | 南京创联智软信息科技有限公司 | Processing and analyzing system for testing multiple items |
-
2021
- 2021-07-13 CN CN202110787934.4A patent/CN113254426B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302533A (en) * | 2014-07-25 | 2016-02-03 | 腾讯科技（深圳）有限公司 | Code synchronizing method and apparatus |
| CN110866492A (en) * | 2019-11-13 | 2020-03-06 | 广州品唯软件有限公司 | Baseline branch identification method and device and computer system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113254426A (en) | 2021-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105893050B (en) | Method for carrying out full-life-cycle management on software project based on PLMS, SVN and Jenkins | |
| CN107291565B (en) | Operation and maintenance visual automatic operation platform and implementation method | |
| US11620277B2 (en) | Transaction processing at non-relational databases | |
| US20180189690A1 (en) | Product development management system and method | |
| CN104281906A (en) | Process engine achieving method and system in service process | |
| CN107844961A (en) | Over contract Construction stage intelligent management system and method based on BIM | |
| EP2610762A1 (en) | Database version management system | |
| CN111651431A (en) | Database service oriented management flow standardization method | |
| US20080301010A1 (en) | Component Inventory Management | |
| CN113254426B (en) | CAD data distributed version control system based on branches and base lines | |
| CN110019138A (en) | A kind of transmission table space Autonomic Migration Framework method and system based on Zabbix | |
| CN112700219A (en) | ACTIVITI-based process management platform | |
| CN110413309A (en) | A kind of item code branch management method and system based on gitlab | |
| CN112036825A (en) | Automatic operation and maintenance management system based on work order | |
| Liu et al. | Automating handover in dynamic workflow environments | |
| CN111241675B (en) | Complex product collaborative design management method and system based on data driving | |
| Liu et al. | APS, ERP and MES systems integration for semiconductor backend assembly | |
| CN109615554B (en) | Synchronous data system based on intelligent manufacturing and operation method and synchronization method thereof | |
| CN110852623A (en) | BPMN-based command control process design method | |
| CN103197927B (en) | A kind of method that realizes of Workflow and system thereof | |
| CN102750610A (en) | Transaction control method in product lifecycle phase management-enterprise resource planning (PLM-ERP) integration process | |
| CN109271199A (en) | A kind of method and system for database continuous integrating and script file management | |
| CN113535684B (en) | Autonomous command control method based on Activiti | |
| Xin et al. | A framework of software reusing engineering management | |
| CN113434264B (en) | Intelligent processing method, device, equipment and storage medium for task components |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |