CN113190265A - Configuration generation method based on Git - Google Patents
Configuration generation method based on Git Download PDFInfo
- Publication number
- CN113190265A CN113190265A CN202110533840.4A CN202110533840A CN113190265A CN 113190265 A CN113190265 A CN 113190265A CN 202110533840 A CN202110533840 A CN 202110533840A CN 113190265 A CN113190265 A CN 113190265A
- Authority
- CN
- China
- Prior art keywords
- configuration
- key
- line
- node
- content
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000008859 change Effects 0.000 claims abstract description 24
- 238000012360 testing method Methods 0.000 claims abstract description 9
- 238000012986 modification Methods 0.000 claims abstract description 4
- 230000004048 modification Effects 0.000 claims abstract description 4
- 239000010979 ruby Substances 0.000 claims description 14
- 229910001750 ruby Inorganic materials 0.000 claims description 14
- 238000012545 processing Methods 0.000 claims description 6
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000003672 processing method Methods 0.000 claims description 3
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000011161 development Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 239000003550 marker Substances 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 244000061520 Angelica archangelica Species 0.000 description 1
- 235000001287 Guettarda speciosa Nutrition 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000007373 indentation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- 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
-
- 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/73—Program documentation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a configuration generation method based on Git, which comprises the following steps: the Latest content of the Repo1 is pulled to the item list; pulling the content of the Last edition sending to a Last directory; difference comparison, namely comparing the difference between dev configuration under late and dev configuration under Last; applying the changed content to the site configuration file under the 'late' directory; for items related to the environment, manual modification can be carried out according to actual conditions; and saving the change, and submitting the Latest to a warehouse, namely finishing the configuration update of the site test environment. The tool method does not change the original configuration structure, and can effectively synchronize and reserve the annotation line; the yaml can be beautified, and the line head can be filled with the specific empty lattice number when the yaml is generated for the condition that the annotations and the empty lattice number of the line head of the data line in the original yaml are disordered; the operation is simple, convenient and quick.
Description
Technical Field
The invention relates to a configuration generation method based on Git, which is suitable for generation and release of yaml configuration of software micro-service related application from a development environment to a test or production environment.
Background
The current popular micro-service divides the service in the single application into sub-services, and the granularity of each service is relatively small, so a large number of services appear in the system. Since each service requires the necessary configuration information to operate, on the other hand, as the product functions are iterated, the configuration required by the service is increased. A centralized configuration management facility is therefore necessary, which is the configuration center.
In the project research and development stage, multiple environments such as dev, site, prod and the like are involved from development, testing and online release, and when the test or online release stage is started, configuration change of the corresponding environment cannot be avoided.
By means of the configuration, the most applied angelica yaml is a plain text, readability is good, transplanting is easy, and use is common. However, because the hierarchical relationship uses a blank character indentation mode, handwriting is easy to make mistakes (one more blank and one less blank can cause configuration failure); in addition, incremental changes in configuration are unavoidable in the project iteration, and configuration updates for test and production environments are extremely inconvenient.
In the traditional mode, developers arrange configuration changes of a development environment and inform testers of the arrangement changes, and the configuration accuracy of the test and production environment is guaranteed through testing. Project flow is relatively normal, but problems caused by configuration errors in actual operation frequently occur. We have found that:
1. because of more developers, the configuration change descriptions organized by the development side are often omitted;
2. the configuration compiled by the tester according to the information provided by development occasionally has writing errors;
3. the problem caused by the configuration error is uncertain, which often wastes much time and energy to research, and even may cause the failure of the product on line.
Disclosure of Invention
The invention aims to solve the problems and provides a configuration generation method based on Git, which reduces the error probability of configuration generation and greatly improves the development efficiency while keeping the purity of a configuration center.
To achieve the above object, the present invention provides a configuration generation method based on Git, comprising the following steps: and using git to perform version management on the configuration files, wherein each environment configuration file is stored in the same git warehouse, and the working principle is as follows, assuming that Repo 1: 1. the Latest content of the Repo1 is pulled to the item list;
2. pulling the content of the Last edition sending to a Last directory;
3. difference comparison, namely comparing the difference between dev configuration under late and dev configuration under Last;
4. applying the changed content to the site configuration file under the 'late' directory;
5, the items related to the environment can be manually modified according to actual conditions;
6. and saving the change, and submitting the Latest to a warehouse, namely finishing the configuration update of the site test environment.
Preferably, in order to obtain the corresponding node relationship of each configuration item, a fast yaml parsing method is autonomously implemented, and the specific method is as follows: 1-1, reading the yaml file line by line, wherein the number of blank spaces at the beginning of the next line is equal to that of the previous line, and the nodes at the same level are obtained;
1-2, when the number of the spaces at the beginning is larger than that of the previous line, configuring child nodes of the items for the previous line;
1-3, when the number of blank spaces at the beginning is assumed to be n and is smaller than that of the previous line, searching the line with the number of blank spaces smaller than n forward, wherein the line configuration item is the father node of the current line;
1-4, when encountering a comment line, searching a next non-comment line, and if the beginning of the next non-comment line has n spaces, resetting the number of the spaces at the beginning of the comment line to n, namely, the parent node of the comment line is the same as the parent node of the next data line, and the processing method is the same when a plurality of comment lines appear continuously.
To reduce the time complexity, the forward lookup can be replaced by another algorithm:
11-1, firstly, performing dictionary processing on the traversed number of each row of empty spaces, and if the head of a row has n empty spaces, updating fact [ n ] < the row number of the current row, and processing all rows in the same way;
11-2, traversing to a node10 in a line 10, wherein the head of the line has 8 blank spaces, searching a father node, only obtaining the value (data is a line number) of the fact [8], and removing the last-stage name of the key according to a key (node name) generation method mentioned in the following difference comparison, wherein the line pointed by the value is the same-stage node of the node10, so as to obtain the father node of the key;
preferably, the specific steps of the difference comparison in the step 3 are as follows:
2-1, respectively resolving two files to be compared into a list based on the method, wherein each node is used as an item and is inserted into the tail of the list, and the item uses a KeyValuePair type;
2-2.key generation method is string splicing: < Node1> < Interval Mark > < Node2> … < Interval Mark > < NodeN >, wherein NodeN can be end Node key or comment;
NodeN-1 is a father node of NodeN, NodeN-2 is a father node of NodeN-1, and recursion is carried out in sequence;
value, i.e. the original content of the original configuration item, retrieve the first ": "as a basis for value, when": "before" # ", when there is no value treatment;
wherein, < space mark > "is special content, the content in the avoiding configuration is enough, and yaml can be accurately and reversely generated on the basis;
2-4, comparing the keyValuePair in the two lists one by one, if the keys are the same, the nodes are the same name, otherwise, the nodes can not be matched, and the comparison result is:
a. the nodes with the same name are the same in value; the two sides are configured identically, i.e. without change;
b. the nodes with the same name are different in value; -specifying a change in a configuration item;
finding no current key of the sit in a Dev dictionary; -this configuration entry of the Dev is deleted;
finding no Dev's current key in Sit's dictionary; this configuration item of the Dev is newly added;
preferably, the method for generating the yaml configuration is used, because the element in the list is keyValuePair, and key is the containing node relation;
3-1, taking the node name of the current item from the key, taking the key 'langugues < interval identification > -Ruby' as an example, and taking the node name as '-Ruby';
3-2, counting the number n of the interval marks in the key;
3-3. writing yaml method is:
a. generating a new row, wherein the row head space lattice number is n x 2; reference is made to the "change application" method for calculating the generation of blank spaces in yaml;
yaml's true key is < NodeN >, taking "key" (key of keyValuePair) "languages < interval identification > -Ruby" as an example, and its true key is "-Ruby"
C. When Value is not null, "+ space + < Value >;
preferably, the specific steps of step 4 are as follows:
4-1, retrieving the node position of dev configuration of the configuration item changeItem in latest;
4-2. when changeItem change type is "New", then create this content in the sit configuration file of latest (find changeItem at dev and sit's common front neighbor nearbyItem1, insert changeItem after sit's nearbyItem 1);
4-3, when the changeItem change type is 'delete', deleting the content in the site configuration file of the latest; if the content does not exist in the site of the latest, the deletion is not needed;
4-4, when the changeItem change type is 'update', updating corresponding content in the site configuration file of the latest; if the content does not exist in the site configuration file of the latest, updating is not needed;
compared with the prior art, the invention has the beneficial effects that: 1. the tool method does not change the original configuration structure, and can effectively synchronize and reserve the annotation line;
2. the yaml can be beautified, and the line head can be filled with the specific empty lattice number when the yaml is generated for the condition that the annotations and the empty lattice number of the line head of the data line in the original yaml are disordered;
3. the operation is simple, convenient and quick.
Drawings
FIG. 1 is a view of a configuration management interface of software in the present embodiment;
fig. 2 is a flowchart of a configuration generation method according to the present embodiment.
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 embodiments, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts based on the embodiments of the present invention belong to the protection scope of the present invention.
The embodiment provides a technical scheme: referring to fig. 1-2, a Git-based configuration generation method comprises the steps of:
1. automatically acquiring the version number (tag/commit list, tag number is recommended for convenient retrieval) of the git library when the software is opened;
2. the "publishing environment" -SIT is selected,
3. select "Dev contrast version";
4. clicking 'generating configuration', namely generating a configuration file of the SIT environment to the local;
5. the configuration files with changes are viewed one by one. If necessary, carrying out manual correction; configuration entries that are confirmed to be error-free are checked in the "confirmed" column. When all the configuration items are marked as 'confirmed', the file in the file list is displayed as green, which aims to force each change item to be checked, and prevent the condition of overlooking and generating overlooking.
6. Clicking 'release configuration', and releasing the configuration of the sit environment.
Wherein, a fast yaml analysis method is automatically realized to obtain the corresponding node relation of each configuration item.
1-1, reading the yaml file line by line, wherein the number of blank spaces at the beginning of the next line is equal to that of the previous line, and the nodes at the same level are obtained;
1-2, when the number of the spaces at the beginning is larger than that of the previous line, configuring child nodes of the items for the previous line;
1-3, when the number of blank spaces at the beginning is assumed to be n and is smaller than that of the previous line, searching the line with the number of blank spaces smaller than n forward, wherein the line configuration item is the father node of the current line;
1-4, when encountering a comment line, searching a next non-comment line, and if the beginning of the next non-comment line has n spaces, resetting the number of the spaces at the beginning of the comment line to n, namely, the parent node of the comment line is the same as the parent node of the next data line, and the processing method is the same when a plurality of comment lines appear continuously.
To reduce the time complexity, the forward lookup can be replaced by another algorithm:
11-1, firstly, performing dictionary processing on the traversed number of each row of empty spaces, and if the head of a row has n empty spaces, updating fact [ n ] < the row number of the current row, and processing all rows in the same way;
11-2, traversing to the node10 in the 10 th row, wherein the head of the row has 8 spaces, searching for a parent node, only obtaining the value (data is row number) of dit [8], the row pointed by the value is the same node of the node10, and removing the last-stage name of the key according to a key (node name) generation method mentioned in the following difference comparison to obtain the parent node.
Wherein, the difference comparison in the step 3 comprises the following specific steps:
2-1, respectively resolving two files to be compared into a list based on the method, wherein each node is used as an item and is inserted into the tail of the list, and the item uses a KeyValuePair type;
2-2.key generation method is string splicing: < Node1> < Interval flag > < Node2> … < Interval flag > < NodeN >, where NodeN can be the end Node key, also noted;
NodeN-1 is a father node of NodeN, NodeN-2 is a father node of NodeN-1, and recursion is carried out in sequence;
value, i.e. the original content of the original configuration item, retrieve the first ": "as a basis for value, when": "before" # ", when there is no value treatment;
taking the following segments as an example,
the key-value is obtained as follows:
1.key:languages
value:<empty>
key: langugages < Interval > # this is a line of comments/descriptions, "-" denotes the array value: < null > "
Key: languges < Interval marker > -Ruby
value:<null>
Key: languges < space marker > -Perl
value:<null>
Key: languages < Interval Mark > -Python
value:<null>
Wherein, < space mark > "is special content, the content in the avoiding configuration is enough, and yaml can be accurately and reversely generated on the basis;
"Ruby" in the example is one of the array type values, but here we do not care about the definition of yaml itself, but let it be key with no effect-it is still possible to write back in reverse.
Wherein < null > is distinguished from < empty >, which means no Value, and < empty > which means a Value but a blank string.
2-4, comparing the keyValuePair in the two lists one by one, if the keys are the same, the nodes are the same name, otherwise, the nodes can not be matched, and the comparison result is:
a. the nodes with the same name are the same in value; the two sides are configured identically, i.e. without change;
b. the nodes with the same name are different in value; -specifying a change in a configuration item;
finding no current key of the sit in a Dev dictionary; -this configuration entry of the Dev is deleted;
finding no Dev's current key in Sit's dictionary; this configuration item of the Dev is newly added;
wherein, the method for generating the yaml configuration is that the element in the list is the key value, and the key is the containing node relation;
3-1, taking the node name of the current item from the key, taking the key 'langugues < interval identification > -Ruby' as an example, and taking the node name as '-Ruby';
3-2, counting the number of interval marks in the key (assumed as n);
3-3. writing yaml method is:
a. generating a new row, wherein the row head space lattice number is n x 2;
yaml's true key is < NodeN >, taking "key" (key of keyValuePair) "languages < interval identification > -Ruby" as an example, and its true key is "-Ruby"
C. When Value is not null, "+ space + < Value >",
wherein, the specific steps of the step 4 are as follows:
4-1, retrieving the node position of dev configuration of the configuration item changeItem in latest;
4-2. when changeItem change type is "New", then create this content in the sit configuration file of latest (find changeItem at dev and sit's common front neighbor nearbyItem1, insert changeItem after sit's nearbyItem 1);
4-3, when the changeItem change type is 'delete', deleting the content in the site configuration file of the latest; if the content does not exist in the site of the latest, the deletion is not needed;
4-4, when the changeItem change type is 'update', updating corresponding content in the site configuration file of the latest; if the content does not exist in the site configuration file of the latest, updating is not needed;
description of the drawings: the common front adjacent node nearbyItem1 indicates that a and b (current elements of two lists) respectively find tempitems forward in the respective lists, and the key coincidence of the tempitems is the target. The node may be a peer node of a (or b) or a parent node thereof.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It should be noted that in the description of the present specification, reference to the description of the term "one embodiment", "some embodiments", "an example", "a specific example", or "some examples", etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples, which are described in this specification in connection with system embodiments that are relatively simple to describe as they are substantially similar to method embodiments, as may be described in connection with part of this specification. The above-described system embodiments are merely illustrative, and the units described as separate components may or may not be physically separate, and the components suggested as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (6)
1. A configuration generation method based on Git, using Git to make version management for configuration files, each environment configuration file is stored in the same Git warehouse, supposing Repo1, characterized in that: the method comprises the following steps:
(1) pull the Latest content of Repo1 under the "late" directory;
(2) pull the Last edition sending content to the Last list directory;
(3) comparing the dev configuration under the Last with the dev configuration under the Last;
(4) applying the changed content to the site configuration file under the 'last' directory;
(5) for items related to the environment, manual modification can be performed according to actual conditions;
(6) and saving the change, and submitting the Latest to a warehouse, namely finishing the configuration update of the site test environment.
2. A Git-based configuration generation method according to claim 1, wherein: in order to obtain the corresponding node relation of each configuration item, a fast yaml analysis method is autonomously realized, and the specific method is as follows:
(1-1) reading the yaml file line by line, wherein the number of blank spaces at the beginning of the next line is equal to that of the previous line, and the nodes at the same level are obtained;
(1-2) when the number of the spaces at the beginning is larger than that of the previous line, configuring child nodes of the item for the previous line;
(1-3) when the number of the spaces at the beginning is n, which is assumed to be smaller than that of the previous line, searching the line with the number of the spaces smaller than n forward, wherein the line configuration item is the father node of the current line;
(1-4) when encountering a comment line, searching a next non-comment line, and if the beginning of the next non-comment line has n spaces, resetting the number of the spaces at the beginning of the comment line to n, namely, the parent node of the comment line is the same as the parent node of the next data line, and the processing method is the same when a plurality of comment lines appear continuously.
3. A Git-based configuration generation method according to claim 1, wherein: to reduce the time complexity, the forward lookup can be replaced by another algorithm:
(11-1) performing dictionary processing on the traversed number of each row of empty spaces, updating fact [ n ] < the row number of the current row if the head of the row has n empty spaces, and processing all rows in the same way;
(11-2) traversing to advance to the node10 in the 10 th row, wherein the head of the row has 8 spaces, searching for a parent node, only obtaining the value of dit [8] (the data is the row number), the row pointed by the value is the same node of the node10, and removing the last-stage name of the key according to a key node name generation method mentioned in the following difference comparison to obtain the parent node of the key.
4. A Git-based configuration generation method according to claim 1, wherein: the difference comparison in the step 3 comprises the following specific steps:
(2-1) respectively analyzing two files to be compared into a list based on the method, taking each node as an item, inserting the item into the tail of the list, and using a KeyValuePair type by the item;
(2-2) the key generation method is character string splicing: < Node1> < Interval Mark > < Node2> … < Interval Mark > < NodeN >, wherein NodeN can be end Node key or comment;
NodeN-1 is a father node of NodeN, NodeN-2 is a father node of NodeN-1, and recursion is carried out in sequence;
(2-3) value, original content of original configuration item, retrieve first of current line ": "as a basis for value, when": "before" # ", when there is no value treatment;
wherein, < space mark > "is special content, the content in the avoiding configuration is enough, and yaml can be accurately and reversely generated on the basis;
(2-4) comparing the key value objects in the two lists one by one, if the keys are the same, the nodes are the same name, otherwise, the nodes can not be matched, and the comparison result is divided into:
(a) the same-name nodes, value is the same; the two sides are configured identically, i.e. without change;
(b) the nodes with the same name are different in value; -specifying a change in a configuration item;
(c) current key of sit can not be found in Dev's dictionary; -this configuration entry of the Dev is deleted;
(d) current key of Dev can not be found in dictionary of Sit; this configuration item of the Dev is newly added.
5. A Git-based configuration generation method according to claim 1, wherein: generating a yaml configuration, wherein the element in the list is keyValuePair, and key is the containing node relation; the specific method comprises the following steps:
(3-1) taking the node name of the current item from the key, taking the key 'langugues < interval identification > -Ruby' as an example, and taking the node name of the key as '-Ruby';
(3-2) counting the number of interval marks in the key (assumed to be n);
(3-3). write yaml method:
(a) generating a new row, with a row head space number of n x 2;
(b) yaml's true key is < NodeN >, exemplified by "key" "languages < Interval identification > -Ruby", whose true key is "-Ruby"
(c) When Value is not null, "+ space + < Value > is written.
6. A Git-based configuration generation method according to claim 1, wherein: the specific steps of the step (4) are as follows:
(4-1) retrieving a node position of dev configuration of the configuration item changeItem in latest;
(4-2) when the changeItem change type is 'newly added', creating the content in the sit configuration file of latest, searching for the nearbyItem1 of the changeItem at the common front adjacent node of dev and sit, and inserting the changeItem after the nearbyItem1 of sit;
(4-3) when the changeItem change type is 'delete', deleting the content in the sit configuration file of the latest; if the content does not exist in the site of the latest, the deletion is not needed;
(4-4) when the changeItem change type is 'update', updating corresponding content in the sit configuration file of latest; if this content is not present in the sit configuration file of latest, no update is required.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110533840.4A CN113190265B (en) | 2021-05-17 | 2021-05-17 | Git-based configuration generation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110533840.4A CN113190265B (en) | 2021-05-17 | 2021-05-17 | Git-based configuration generation method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113190265A true CN113190265A (en) | 2021-07-30 |
| CN113190265B CN113190265B (en) | 2023-12-15 |
Family
ID=76982016
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110533840.4A Active CN113190265B (en) | 2021-05-17 | 2021-05-17 | Git-based configuration generation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113190265B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180081786A1 (en) * | 2016-09-19 | 2018-03-22 | Grand Rounds, Inc. | Methods and systems for content management and testing |
| CN107967159A (en) * | 2017-11-22 | 2018-04-27 | 腾讯科技（深圳）有限公司 | The method and server of a kind of profileapplied |
| CN108228231A (en) * | 2018-01-08 | 2018-06-29 | 南京邮电大学 | A kind of visualization shift algorithm of Git warehouses file annotation system |
| CN111142903A (en) * | 2019-12-23 | 2020-05-12 | 杭州安恒信息技术股份有限公司 | Configuration file interactive updating method and device based on file comparison |
| CN111694612A (en) * | 2020-05-28 | 2020-09-22 | 平安普惠企业管理有限公司 | Configuration checking method, device, computer system and storage medium |
| CN112486589A (en) * | 2020-11-26 | 2021-03-12 | 中国人寿保险股份有限公司 | System configuration item management method and device, electronic equipment and storage medium |
| CN112486532A (en) * | 2020-11-25 | 2021-03-12 | 中移（杭州）信息技术有限公司 | Method and device for managing configuration file, electronic equipment and storage medium |
-
2021
- 2021-05-17 CN CN202110533840.4A patent/CN113190265B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180081786A1 (en) * | 2016-09-19 | 2018-03-22 | Grand Rounds, Inc. | Methods and systems for content management and testing |
| CN107967159A (en) * | 2017-11-22 | 2018-04-27 | 腾讯科技（深圳）有限公司 | The method and server of a kind of profileapplied |
| CN108228231A (en) * | 2018-01-08 | 2018-06-29 | 南京邮电大学 | A kind of visualization shift algorithm of Git warehouses file annotation system |
| CN111142903A (en) * | 2019-12-23 | 2020-05-12 | 杭州安恒信息技术股份有限公司 | Configuration file interactive updating method and device based on file comparison |
| CN111694612A (en) * | 2020-05-28 | 2020-09-22 | 平安普惠企业管理有限公司 | Configuration checking method, device, computer system and storage medium |
| CN112486532A (en) * | 2020-11-25 | 2021-03-12 | 中移（杭州）信息技术有限公司 | Method and device for managing configuration file, electronic equipment and storage medium |
| CN112486589A (en) * | 2020-11-26 | 2021-03-12 | 中国人寿保险股份有限公司 | System configuration item management method and device, electronic equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| DMITRII A. ZUBOK 等: "A multi-agent approach to the monitoring of cloud computing system with dynamically changing configuration", 《2016 18TH CONFERENCE OF OPEN INNOVATIONS ASSOCIATION AND SEMINAR ON INFORMATION SECURITY AND PROTECTION OF INFORMATION TECHNOLOGY (FRUCT-ISPIT)》, pages 410 - 416 * |
| 常荣 等: "基于虚拟化技术的信息系统测试环境搭建与应用研究", 《信息技术与信息化》, no. 207, pages 96 - 99 * |
| 董龙成: "基于ZooKeeper的配置中心系统设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》, pages 138 - 673 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113190265B (en) | 2023-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6470347B1 (en) | Method, system, program, and data structure for a dense array storing character strings | |
| Agichtein et al. | Mining reference tables for automatic text segmentation | |
| US7158975B2 (en) | System and method for storing and accessing data in an interlocking trees datastore | |
| EP2731032B1 (en) | Labeling versioned hierarchical data | |
| CN108228231B (en) | Visualization drifting method of Git warehouse file annotation system | |
| US7809764B2 (en) | Method and apparatus for preserving dependancies during data transfer and replication | |
| Agarwal et al. | Approximate incremental big-data harmonization | |
| US9087091B2 (en) | Determination of differences in hierarchical data | |
| CN110969517B (en) | Bidding life cycle association method, system, storage medium and computer equipment | |
| CN112463774B (en) | Text data duplication eliminating method, equipment and storage medium | |
| CN110795526B (en) | Mathematical formula index creating method and system for retrieval system | |
| Ujwal et al. | Classification-based adaptive web scraper | |
| CN111143513B (en) | Sensitive word recognition method and device and electronic equipment | |
| US7340471B2 (en) | Saving and restoring an interlocking trees datastore | |
| CN104899337A (en) | File index building method and system | |
| CN113190265A (en) | Configuration generation method based on Git | |
| US8204887B2 (en) | System and method for subsequence matching | |
| CN111460000A (en) | Backtracking data query method and system based on relational database | |
| CN113407538B (en) | Incremental acquisition method for data of multi-source heterogeneous relational database | |
| Chukhray et al. | Proximate objects probabilistic searching method | |
| Altın et al. | Analyzing the Encountered Problems and Possible Solutions of Converting Relational Databases to Graph Databases | |
| CN113420192B (en) | UI element searching method based on fuzzy matching | |
| Anam et al. | Schema mapping using hybrid ripple-down rules | |
| CN110019987B (en) | Log matching method and device based on decision tree | |
| CN116702720A (en) | File processing method and device, electronic equipment and storage 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |