CN107404520A - A kind of management method and system based on cloud management platform - Google Patents
A kind of management method and system based on cloud management platform Download PDFInfo
- Publication number
- CN107404520A CN107404520A CN201710597106.8A CN201710597106A CN107404520A CN 107404520 A CN107404520 A CN 107404520A CN 201710597106 A CN201710597106 A CN 201710597106A CN 107404520 A CN107404520 A CN 107404520A
- Authority
- CN
- China
- Prior art keywords
- file
- git
- engineering
- version
- engineerings
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/103—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for protecting copy right
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a kind of management method and system based on cloud management platform, multiple-limb management system is provided with the cloud management platform, the multiple-limb management system uses client-side/server-side architecture；This method includes：Service end receives the fileinfo for multiple files that client is sent, and the fileinfo includes file content and branch's version；The service end is the corresponding Git engineerings of each document creation one and branch's version of the Git engineerings, there was only a corresponding file, branch's version using branch's version of file corresponding to each Git engineering as the Git engineerings in each Git engineering；The service end record and preservation file and Git engineering mapping tables.Technical solution of the present invention ensures that branch's version of file and branch's version of the engineering created are consistent, realizes branch's Version Control to single file by being automated as each document creation Git engineerings.
Description
Technical field
The present invention relates to cloud computing technology, espespecially a kind of management method and system based on cloud management platform.
Background technology
In cloud computing era, cloud management platform project is relatively more, and main line project shows with the project concurrent development of customization
As happening occasionally.In order to be compared rational code control, typically a branch is drawn to enter line code control using each project
System.The method can suffer a problem that, be not that All Files in module is required for being customized and melts hair, and develop
The situation that developer develops multiple modules can be run into, it is possible to which it is bigger to run into module, but simply changes some mould
The situation of several files of block, now It is not necessary to all codes of download module, it is only necessary to download the several texts for needing to change
Part, can of modifying complete customized development, but if each project draws a branch to enter the mode that line code controls,
All codes can only be pulled, code of then modifying, the control dynamics of the code of this mode are too coarse, and waste and grind
The unnecessary memory space of hair personnel and time.
The content of the invention
In order to solve the above-mentioned technical problem, the invention provides a kind of management method and system of cloud management platform, pass through
Each document creation Git engineerings are automated as, ensure that branch's version of file and branch's version of the engineering created are consistent,
Realize branch's version management to single file.
In order to reach the object of the invention, the invention provides a kind of management method based on cloud management platform, the cloud pipe
Multiple-limb management system is provided with platform, the multiple-limb management system uses client-side/server-side architecture；This method bag
Include：
Service end receives the fileinfo for multiple files that client is sent, and the fileinfo includes file content and divided
Branch version；
The service end is branch's version of the corresponding Git engineerings of each document creation one and the Git engineerings, each
There was only a corresponding file in individual Git engineerings, using branch's version of file corresponding to each Git engineering as the Git
Branch's version of engineering；
The service end record and preservation file and Git engineering mapping tables, the file and Git engineering corresponding relations
Table includes the engineering name of each Git engineering and the one-to-one relationship of the mark of corresponding file.
Further, the mark of the file includes engineering name, folder hierarchy and the file name of file.
Further, the character of entitled 32 from increasing column-generation by mysql of the engineering of each Git engineering
String.
Further, this method also includes：
The service end receive client transmission on contain filename and branch's version pull order after, will
File in Git engineerings corresponding to the filename and branch's version is transferred to the client.
Further, this method also includes：
The client shows branch's version corresponding to All Files and each file, when detecting any one file
And after branch's version of this document is chosen, order is pulled described in the client to service end transmission.
Further, the file by Git engineerings corresponding to the filename and branch's version is transferred to the visitor
Family end, including：
The mark of the file included in order is pulled described in automatic identification, according to the file and Git engineering corresponding relations
Table and the mark of the file identified find corresponding to Git engineerings, will respective branches version in the corresponding Git engineerings
File encryption after be transferred to the client.
Further, this method also includes：
When the client locally preserves the file of same file title, the client calculates Git engineerings automatically
In the md5 values of file that locally preserve of file and client, if the md5 values of two files of the same name are identical, not from service
Download the file in the Git engineerings in device end；If the md5 values of two files of the same name differ, the text locally preserved is changed
The filename of part, then download the file in the Git engineerings.
Further, this method also includes：
The client sends the amended file after file content is changed to the service end；
The mark for the file that the service end automatic identification receives, if after service end does not locally find the modification
File corresponding to Git engineerings, then be Git engineerings corresponding to the amended document creation；If locally looked in service end
To Git engineerings corresponding to the amended file, then the amended file is submitted in corresponding Git engineerings.
Further, this method also includes：The service end periodically searches file corresponding to all Git engineerings, if looked for
Less than file corresponding to certain Git engineering, then certain described Git engineering is deleted.
In order to reach the object of the invention, present invention also offers a kind of management system based on cloud management platform, the cloud
Multiple-limb management system is provided with management platform, the multiple-limb management system uses client-side/server-side architecture；The multiple-limb
Management system includes：
Service end, the fileinfo of multiple files for receiving client transmission, the fileinfo are included in file
Hold and branch's version；
The service end, it is additionally operable to branch's version for one corresponding Git engineering of each document creation and the Git engineerings
This, an only corresponding file in each Git engineering, using branch's version of file corresponding to each Git engineering as
Branch's version of the Git engineerings；
The service end, record and preservation file and Git engineering mapping tables, the file is corresponding with Git engineerings to close
It is the one-to-one relationship that table includes the engineering name of each Git engineering and the mark of respective file.
Technical solution of the present invention provides a kind of management method and system based on cloud management platform, the cloud management platform
In be provided with multiple-limb management system, the multiple-limb management system uses client-side/server-side architecture；This method includes：Service
End receives the fileinfo for multiple files that client is sent, and the fileinfo includes file content and branch's version；It is described
Service end is branch's version of the corresponding Git engineerings of each document creation one and the Git engineerings, in each Git engineering
An only corresponding file, branch's version using branch's version of file corresponding to each Git engineering as the Git engineerings
This；The service end record and preservation file and Git engineering mapping tables, the file and Git engineering mapping table bags
Include the one-to-one relationship of the engineering name of each Git engineering and the mark of respective file.Technical solution of the present invention passes through automatic
Each document creation Git engineerings are turned to, ensures that branch's version of file and branch's version of the engineering created are consistent, realizes
To the branch Version Control of single file.Further, when client needs to change the code of file, it is only necessary under
The file for needing to change is carried, reduces unnecessary file transmission, improves the efficiency of code administration, and shorten research and development of products week
Phase, improve product competitiveness.
Other features and advantages of the present invention will be illustrated in the following description, also, partly becomes from specification
Obtain it is clear that or being understood by implementing the present invention.The purpose of the present invention and other advantages can be by specification, rights
Specifically noted structure is realized and obtained in claim and accompanying drawing.
Brief description of the drawings
Accompanying drawing is used for providing further understanding technical solution of the present invention, and a part for constitution instruction, with this
The embodiment of application is used to explain technical scheme together, does not form the limitation to technical solution of the present invention.
Fig. 1 is the management method schematic flow sheet provided in an embodiment of the present invention based on cloud management platform；
Fig. 2 is the management system structural representation provided in an embodiment of the present invention based on cloud management platform.
Embodiment
Technical scheme is described in detail below in conjunction with drawings and Examples.
It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, it is not intended to limit the present invention.
In follow-up description, the suffix using such as " module ", " part " or " unit " for representing element is only
Be advantageous to the explanation of the present invention, itself there is no a specific meaning.Therefore, " module ", " part " or " unit " can mix
Ground uses.
For the object, technical solutions and advantages of the present invention are more clearly understood, below in conjunction with accompanying drawing to the present invention
Embodiment be described in detail.It should be noted that in the case where not conflicting, in the embodiment and embodiment in the application
Feature can mutually be combined.
Can be in the computer system of such as one group computer executable instructions the flow of accompanying drawing illustrates the step of
Perform.Also, although logical order is shown in flow charts, in some cases, can be with suitable different from herein
Sequence performs shown or described step.
The huge project of size of code is when it come to arrived, generally requiring could by many person cooperative work several weeks or even several months
Complete.In development process, the work such as the modification, additions and deletions, recovery of code can be faced with, developer can not possibly clearly remember often
Secondary change, at this time just need to track the change course of code by Version.Version assigns each
One version number of file, every time after modification, even only having changed a letter, Version all can be recorded accurately
Come, and change the version number of this document.So, each version number just correspond to the one-shot change of file, can enter style of writing according to this
The operation such as the contrast of part, recovery.
Git is a Version, with traditional Version CVS (Concurrent Versions
System) or SVN (Subversion) is different, and whether the entirety that Git record vncsion histories are only concerned file data becomes
Change, Git does not preserve the variance data of the front and rear change of file content.In fact, Git is more like makees snapshot the file of change
Afterwards, it is recorded in a miniature file system.When submitting renewal every time, it can scan the finger print information of an All Files simultaneously
One snapshot is made to file, then preserves an index for pointing to current snapshot.To improve performance, if file does not change, Git is not
It can again preserve, and one only is made to the snapshot that last time preserves and is connected in distributed version control system, client not only carries
The File Snapshot of latest edition is taken, but intactly mirror image gets off original code storage.In such event, any one is cooperateed with
The server fail of work, the ware-house here that can be come out afterwards with any one mirror image recover.This kind of system is all
It can specify and be interacted with some different distal end code storages.Whereby, it is possible to respectively and different in same project
The people of work group cooperates.Different collaboration process can be set as needed.In addition, because Git is on local disk
In store all history renewals about current project, and most operations in Git all only need to access local file
And resource, without networking, so it is very fast to deal with speed.And Git version number is globally unique.It is being saved in Git
Before, all data will carry out the verification of content and (checksum) is calculated, and the unique mark using this result as data
And index.In other words, it is not possible to after you have modified file or catalogue, Git knows nothing.This characteristic is as Git's
Design philosophy, it build the bottom of overall architecture in.So if file becomes imperfect in transmission, or disk failures cause
File data lacks, and Git can discover immediately.
Before the embodiment of the present invention is elaborated, the inventive concept of the present invention is first explained.Skill provided by the invention
In art scheme, using Git technologies, each file in multiple-limb management by synchronization system automatic identification upload code, it is automatically
Each document creation git engineerings, when changing code, can change some file in multiple-limb management by synchronization system, and
All codes need not be downloaded, reduces unnecessary code and downloads, reduce ineffective time, improve code revision efficiency, contracting
The short sawn timber R＆D cycle.
Fig. 1 is the management method schematic flow sheet provided in an embodiment of the present invention based on cloud management platform, as shown in figure 1,
Multiple-limb management system is provided with cloud management platform, the multiple-limb management system uses client-side/server-side architecture；This method
Including：
Step 101, service end receives the fileinfo for multiple files that client is sent, and the fileinfo includes file
Content and branch's version；
Step 102, the service end is the corresponding Git engineerings of each document creation one and the branch of the Git engineerings
Version, an only corresponding file in each Git engineering, branch's version of file corresponding to each Git engineering is made
For branch's version of the Git engineerings；
Step 103, the service end record and preservation file and Git engineering mapping tables, the file and Git engineerings
Mapping table includes the one-to-one relationship of the engineering name of each Git engineering and the mark of respective file.
Further, the mark of the corresponding file includes engineering name, folder hierarchy and the filename of file
Claim.
Further, the engineering of each Git engineering it is entitled by mysql from increasing sequence come the character of 32 that generates
String.
Further, this method also includes：
The service end receive client transmission on contain filename and branch's version pull order after, will
File in Git engineerings corresponding to the filename and branch's version is transferred to the client.
Further, this method also includes：
The client shows branch's version corresponding to All Files and each file, when detecting any one file
And after branch's version of this document is chosen, order is pulled described in the client to service end transmission.
Further, the file by Git engineerings corresponding to the filename and branch's version is transferred to the visitor
Family end, including：
The mark of the file included in order is pulled described in automatic identification, according to the file and Git engineering corresponding relations
Table and the mark of the file identified find corresponding to Git engineerings, will respective branches version in the corresponding Git engineerings
File encryption after be transferred to the client.
Further, this method also includes：
When the client locally preserves the file of same file title, the client calculates Git engineerings automatically
In the md5 values of file that locally preserve of file and client, if the md5 values of two files of the same name are identical, not from service
Download the file in the Git engineerings in device end；If the md5 values of two files of the same name differ, the text locally preserved is changed
The filename of part, then download the file in the Git engineerings.
Further, this method also includes：
The client sends the amended file after file content is changed to the service end；
The mark for the file that the service end automatic identification receives, if after service end does not locally find the modification
File corresponding to Git engineerings, then be Git engineerings corresponding to the amended document creation；If locally looked in service end
To Git engineerings corresponding to the amended file, then the amended file is submitted in corresponding Git engineerings.
Further, the service end periodically searches file corresponding to all Git engineerings, if can not find certain Git engineering
Corresponding file, then delete certain described Git engineering.
Embodiment one
The embodiment of the present invention is applied to cloud management platform, and multiple-limb management system is provided with cloud management platform.
First, multiple-limb management system uses cs frameworks, that is, provides a client and a service end, and service end provides
User's registration function, the rear end of service end carry out file management using git modes., it is necessary to configure text after service end installation
Part way to manage, input svn addresses, username and password or git addresses, username and password.
Again, user installs client in an operating system first, then, by client establishment file, and in file
Branch's version of middle addition code and file, is then submitted to service end.Client and service end are developed using java,
The data transfer of client and service end and communication are encrypted using ssl cipher modes.Client passes through ip, port numbers and use
Data are simultaneously transmitted in name in an account book password Connection Service end, branch's version comprising file content and each file in data.Client
Support to carry out branch's version setting to file, file or multiple files.
Again, after data upload to service end, service end automatic identification All Files and branch's version, and in file pipe
Engineering establishment is carried out in reason, i.e., engineering is created in git, the engineering name of establishment has uniqueness, and being set when creating engineering should
Branch's version of engineering, branch's version information are branch's version information of this document of client transmissions.Engineering name passes through
Mysql's generates the character string of 32 from increasing sequence, ensures the uniqueness of engineering name.An only text in each engineering
The one-to-one relationship of part, service end log file and the engineering created and ensure point in the branch's version and engineering of file
Branch version is identical, and the corresponding relation of maintenance is the unique name of engineering and the engineering name-folder hierarchy-of file that create
File name.Engineering name where being exemplified below file is projectA, and the file level where file is file
DirectoryB/ file DirectoryC file names are FileD, then file is identified as projectA-DirectoryB-
DirectoryC-FileD。
Again, when changing file, client pulls file.Client can browse through All Files and file is corresponding
Branch's version.After branch's version that client selects some file and this document, execution pulls order, communicates a command to
Service end, service end are automatically recognized as engineering name-folder hierarchy-file name of file, looked for according to the title of identification
To corresponding engineering, the file encryption of respective branches version in engineering is transferred to client.If client does not have locally
File, then file is directly downloaded, if there is a file of the same name the local of client, the md5 values of the automatic calculation document of client, if
The md5 values of two files of the same name are identical, then do not operate；If md5 values are different, modification local file is filename .bak,
Then file is downloaded, Piece file mergence function is not provided.
Again, file modification is completed, and client is presented a paper.Client encrypted transmission file is to service end, and service end is certainly
Engineering name-folder hierarchy-file name of dynamic identification file identification, i.e. file, if not finding corresponding engineering, i.e.,
File is newly-built file, then automatically creates engineering, and each one file of engineering carries out storage management, if corresponding work
Journey, then new file is submitted into corresponding engineering.
Finally, service end is regular, for example per weekend, performs timed task automatically, search file corresponding to all engineerings, such as
Fruit can not find corresponding file in multiple-limb management by synchronization system, then it represents that file corresponding to the engineering is deleted, then deletes
Except the engineering.Invalid storage is reduced, reduces storage pressure.
Fig. 2 is the management system structural representation provided in an embodiment of the present invention based on cloud management platform, such as Fig. 2 institutes
Show, multiple-limb management system is provided with cloud management platform, the multiple-limb management system uses client-side/server-side architecture；Should
Multiple-limb management system includes：
Service end, the fileinfo of multiple files for receiving client transmission, the fileinfo are included in file
Hold and branch's version；
The service end, it is additionally operable to branch's version for one corresponding Git engineering of each document creation and the Git engineerings
This, an only corresponding file in each Git engineering, using branch's version of file corresponding to each Git engineering as
Branch's version of the Git engineerings；
The service end, record and preservation file and Git engineering mapping tables, the file is corresponding with Git engineerings to close
It is that table includes the engineering name of each Git engineering and the mark one-to-one relationship of corresponding file.
Further, service end provides user's registration function, and the rear end of service end carries out file management using git modes.
, it is necessary to which configuration file management mode, input svn addresses, username and password or git addresses, is used after service end installation
Name in an account book and password.
Further, management code and branch's dynamics of code are to file-level.File is uploaded to service by client
Behind end, service end automatic identification All Files and branch's version, and engineering establishment is carried out in file management, i.e., in git
Engineering is created, the engineering name of establishment has uniqueness, branch's version of the engineering, branch's version information are set when creating engineering
For branch's version information of this document of client transmissions.Engineering name generates the word of 32 by mysql from increasing sequence
Symbol string, ensure the uniqueness of engineering name.The engineering of an only file in each engineering, service end log file and establishment
One-to-one relationship and ensure that branch's version of file is identical with branch's version in engineering, the corresponding relation of maintenance is creates
The unique name of engineering and engineering name-folder hierarchy-file name of file.Engineering name where being exemplified below file
Referred to as projectA, the file level where file are file DirectoryB/ file DirectoryC file names
For FileD, then file is identified as projectA-DirectoryB-DirectoryC-FileD.
Further, single file can only be pulled by changing code and branch.Client can browse through All Files with
And branch's version corresponding to file.After branch's version that client selects some file and this document, execution pulls order,
Service end is communicated a command to, service end is automatically recognized as engineering name-folder hierarchy-file name of file, according to knowledge
Other title finds corresponding engineering, and the file encryption of respective branches version in engineering is transferred to client.
Further, service end can automatically remove invalid data.Service end is regular, for example per weekend, automatic perform is determined
When task, file corresponding to all engineerings is searched, if can not find corresponding file in multiple-limb management by synchronization system, then it represents that
File corresponding to the engineering is deleted, then deletes the engineering.Invalid storage is reduced, reduces storage pressure.
Technical solution of the present invention, pass through the multiple-limb management system of upload code to cloud management platform, multiple-limb lock-in tube
Each file in reason system automatic identification upload code, be automatically each document creation git engineerings, change code when
Wait, some file in more management systems can be changed, without downloading all codes, reduce under unnecessary code
Carry, reduce the invalid development time, improve code revision efficiency, shorten the research and development of products cycle.
Although disclosed herein embodiment as above, described content be only readily appreciate the present invention and use
Embodiment, it is not limited to the present invention.Technical staff in any art of the present invention, taken off not departing from the present invention
On the premise of the spirit and scope of dew, any modification and change, but the present invention can be carried out in the form and details of implementation
Scope of patent protection, still should be subject to the scope of the claims as defined in the appended claims.
Claims (10)
1. a kind of management method based on cloud management platform, it is characterised in that be provided with multi-limbed tube in the cloud management platform
Reason system, the multiple-limb management system use client-side/server-side architecture；This method includes：
Service end receives the fileinfo for multiple files that client is sent, and the fileinfo includes file content and branch's version
This；
The service end is branch's version of the corresponding Git engineerings of each document creation one and the Git engineerings, each
There was only a corresponding file in Git engineerings, using branch's version of file corresponding to each Git engineering as the Git works
Branch's version of journey；
The service end record and preservation file and Git engineering mapping tables, the file and Git engineering mapping table bags
Include the engineering name of each Git engineering and the one-to-one relationship of the mark of corresponding file.
2. management method as claimed in claim 1, it is characterised in that the mark of the file includes the engineering name of file, text
Part interlayer level structure and file name.
3. management method as claimed in claim 1, it is characterised in that the engineering of each Git engineering is entitled to pass through mysql's
From the character string of 32 of increasing column-generation.
4. management method as claimed in claim 2, it is characterised in that this method also includes：The service end receives client
End send on contain filename and branch's version pull order after, by corresponding to the filename and branch's version
File in Git engineerings is transferred to the client.
5. management method as claimed in claim 4, it is characterised in that this method also includes：The client shows all texts
Branch's version corresponding to part and each file, when the branch's version for detecting any one file and this document is chosen
Afterwards, order is pulled described in the client to service end transmission.
6. management method as claimed in claim 4, it is characterised in that described by corresponding to the filename and branch's version
File in Git engineerings is transferred to the client, including：
The mark of the file included in order is pulled described in automatic identification, according to the file and Git engineerings mapping table and
The mark of the file identified finds corresponding Git engineerings, by the text of respective branches version in the corresponding Git engineerings
The client is transferred to after part encryption.
7. management method as claimed in claim 4, it is characterised in that this method also includes：
When the client locally preserves the file of same file title, the client calculates in Git engineerings automatically
The md5 values for the file that file and client locally preserve, if the md5 values of two files of the same name are identical, not from server end
Download the file in the Git engineerings；If the md5 values of two files of the same name differ, the file that locally preserves is changed
Filename, then download the file in the Git engineerings.
8. management method as claimed in claim 1, it is characterised in that this method also includes：
The client sends the amended file after file content is changed to the service end；
The mark for the file that the service end automatic identification receives, if locally not finding the amended text in service end
Git engineerings corresponding to part, then it is Git engineerings corresponding to the amended document creation；If locally find institute in service end
Git engineerings corresponding to amended file are stated, then the amended file are submitted in corresponding Git engineerings.
9. management method as claimed in claim 1, it is characterised in that this method also includes：The service end periodically searches institute
There is file corresponding to Git engineerings, if can not find file corresponding to certain Git engineering, delete certain described Git engineering.
10. a kind of management system based on cloud management platform, it is characterised in that be provided with multi-limbed tube in the cloud management platform
Reason system, the multiple-limb management system use client-side/server-side architecture；The multiple-limb management system includes：
Service end, for receive client transmission multiple files fileinfo, the fileinfo include file content and
Branch's version；
The service end, branch's version for one corresponding Git engineering of each document creation and the Git engineerings is additionally operable to,
There was only a corresponding file in each Git engineering, using branch's version of file corresponding to each Git engineering as described in
Branch's version of Git engineerings；
The service end, record and preservation file and Git engineering mapping tables, the file and Git engineering mapping tables
The one-to-one relationship of the mark of engineering name and respective file including each Git engineering.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710597106.8A CN107404520A (en) | 2017-07-20 | 2017-07-20 | A kind of management method and system based on cloud management platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710597106.8A CN107404520A (en) | 2017-07-20 | 2017-07-20 | A kind of management method and system based on cloud management platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107404520A true CN107404520A (en) | 2017-11-28 |
Family
ID=60402363
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710597106.8A Pending CN107404520A (en) | 2017-07-20 | 2017-07-20 | A kind of management method and system based on cloud management platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107404520A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110018857A (en) * | 2018-01-05 | 2019-07-16 | 武汉斗鱼网络科技有限公司 | Application component Hua Zhong branch automatic management method, storage medium, device and method |
| CN110750259A (en) * | 2018-07-23 | 2020-02-04 | 北京奇虎科技有限公司 | Method and device for treating a component |
| CN110750502A (en) * | 2018-07-23 | 2020-02-04 | 北京奇虎科技有限公司 | Component processing method and device |
| CN111143315A (en) * | 2019-12-27 | 2020-05-12 | 贵州电网有限责任公司 | Version management method of transformer substation secondary circuit information model based on Git |
| CN111666081A (en) * | 2020-04-30 | 2020-09-15 | 平安科技（深圳）有限公司 | Project version release method, device, equipment and medium based on Git |
| CN117270943A (en) * | 2023-09-15 | 2023-12-22 | 上海子虔科技有限公司 | Cloud application file version management system and method based on metadata |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103248674A (en) * | 2013-04-22 | 2013-08-14 | 浙江大学 | Shared file management method for cross-domain cloud platform |
-
2017
- 2017-07-20 CN CN201710597106.8A patent/CN107404520A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103248674A (en) * | 2013-04-22 | 2013-08-14 | 浙江大学 | Shared file management method for cross-domain cloud platform |
Non-Patent Citations (1)
| Title |
|---|
| 邓亮: ""基于分布式版本控制工具的个性化文件同步系统设计与实现"", 《万方学位论文》 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110018857A (en) * | 2018-01-05 | 2019-07-16 | 武汉斗鱼网络科技有限公司 | Application component Hua Zhong branch automatic management method, storage medium, device and method |
| CN110018857B (en) * | 2018-01-05 | 2022-08-16 | 武汉斗鱼网络科技有限公司 | Method, storage medium, device and method for automatically managing branches in application modularization |
| CN110750259A (en) * | 2018-07-23 | 2020-02-04 | 北京奇虎科技有限公司 | Method and device for treating a component |
| CN110750502A (en) * | 2018-07-23 | 2020-02-04 | 北京奇虎科技有限公司 | Component processing method and device |
| CN110750259B (en) * | 2018-07-23 | 2024-04-05 | 三六零科技集团有限公司 | Method and device for processing component |
| CN111143315A (en) * | 2019-12-27 | 2020-05-12 | 贵州电网有限责任公司 | Version management method of transformer substation secondary circuit information model based on Git |
| CN111666081A (en) * | 2020-04-30 | 2020-09-15 | 平安科技（深圳）有限公司 | Project version release method, device, equipment and medium based on Git |
| CN111666081B (en) * | 2020-04-30 | 2024-04-05 | 平安科技（深圳）有限公司 | Git-based project version release method, device, equipment and medium |
| CN117270943A (en) * | 2023-09-15 | 2023-12-22 | 上海子虔科技有限公司 | Cloud application file version management system and method based on metadata |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107404520A (en) | A kind of management method and system based on cloud management platform | |
| CN110019215B (en) | Key pattern management in a multi-tenancy database system | |
| CN110147369B (en) | Data splitting and write redirection in a multi-leased database system | |
| CN109947767B (en) | System sharing type in multi-leasing database system | |
| US10019441B2 (en) | Systems and methods for managing document repositories | |
| US20130226876A1 (en) | Synchronizing local clients with a cloud-based data storage system | |
| US10255286B2 (en) | File metadata handler for storage and parallel processing of files in a distributed file system, and associated systems and methods | |
| CN109564529A (en) | Placeholder based on Symbolic Links | |
| CA2509008A1 (en) | System and method for transport of objects utilizing ldap directory structure | |
| US9600300B2 (en) | Method to generate dynamic customized context-sensitive help | |
| CN112947992B (en) | Code version management method and device | |
| CN103443782A (en) | Retrieval, parsing and application of a configuration for a client having a windows-based embedded image | |
| JP2001306372A (en) | Method for managing document and storage medium storing program for executing the method | |
| CN114047938B (en) | Method, device, equipment and readable storage medium for constructing mirror image | |
| US20200409669A1 (en) | Technique for transforming a standard messaging component to a customized component | |
| US10152265B1 (en) | Efficient repository migration and storage | |
| US20170140009A1 (en) | Caching linked queries for optimized compliance management | |
| US11288003B2 (en) | Cross-platform replication of logical units | |
| US8667034B1 (en) | System and method for preserving symbolic links by a storage virtualization system | |
| CN110958293B (en) | File transmission method, system, server and storage medium based on cloud server | |
| CN108628632A (en) | A kind of packaging method and device | |
| US11741045B2 (en) | Format agnostic database migration | |
| US20070067449A1 (en) | Redundant appliance configuration repository in standard hierarchical format | |
| CN114047939A (en) | Data processing method and middleware | |
| JP2009265902A (en) | Document management device, document management method, information processing program, and recording medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20171128 |