CN105094851A - Method for momentarily issuing codes based on Git - Google Patents
Method for momentarily issuing codes based on Git Download PDFInfo
- Publication number
- CN105094851A CN105094851A CN201510561172.0A CN201510561172A CN105094851A CN 105094851 A CN105094851 A CN 105094851A CN 201510561172 A CN201510561172 A CN 201510561172A CN 105094851 A CN105094851 A CN 105094851A
- Authority
- CN
- China
- Prior art keywords
- git
- file
- code
- submitted
- developer
- 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
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a method for momentarily issuing codes based on Git. The specific achievement process is as follows: at first, a manager defines a central library and fixed branches of Git, namely, the manager defines a certain Git resource library as the central library and defines main branches of a specified project as the fixed branches; obtaining latest versions submitted by codes on the fixed branches of the central library of the Git through a hook script; converting the versions in the Git into self-increasing serial numbers for storage; correlating a developed source code with a task package; and momentarily creating and obtaining a correct file version. Compared with the prior art, the method for momentarily issuing codes based on Git can be used for momentarily creating an issue package necessary for a client without manually picking up files for creation on the condition that multiple people cooperate to develop the same project, so that the working efficiency and the quality of the issue package are improved, the practicability is strong, the application range is wide, and the method is easy to popularize.
Description
Technical field
The present invention relates to field of computer technology, specifically a kind of practical, based on the implementation method of Git release code at any time.
Background technology
Git as distributed version control system, because it is convenient, high efficiency, use by increasing open source projects, and some traditional non-open source projects, also start progressively to consider to use Git to carry out the version of management project file.But do not have a kind of effective mode to carry out issuing at any time, fast based on Git at present, for the more urgent problem that client proposes, cannot construct in time and issue bag, timely response can not be accomplished.
Based on this, the invention provides a kind of implementation method based on Git release code at any time, the method is by definition Git central library, by the submission of the fixing branch in Git hook script monitoring central library, by submit to version conversion become can calculate from addendum number, and the source file using task agent and developer to submit to associates, the AKU for customer demand or bug can be constructed flexibly, effectively overcome the above problems.
Summary of the invention
Technical assignment of the present invention is for above weak point, provide a kind of practical, based on the implementation method of Git release code at any time.
Based on an implementation method for Git release code at any time, its specific implementation process is:
One, first keeper defines Git central library and fixes branch, and namely keeper defines certain Git resources bank is central library, and the trunk branch of technical routine is as fixing branch;
Two, obtain Git central library by hook script and fix the latest edition that in branch, code is submitted to;
Three, the version conversion in Git is become from addendum number storage;
Four, the source code of exploitation is associated with task agent;
Five, build at any time and can correct FileVersion be obtained.
In described step one, keeper defines Git central library and fixes branch, developer's creation task bag, developer is exploitation code in local Git development library, after having developed, fix the code synchronisation of branch with central library, after managing conflict, code is submitted in central library.
The detailed process of described step 2 is: in central library, add hook script, each submission of monitoring developer, by comparing the difference between this submission of developer and the version fixing submission last time in branch in hook script, get and comprise the file path of submission, the information of file operation, again in conjunction with the version number that this is submitted to, the information such as submitter, time of adding stores in a database, namely thinks that the content obtaining that this is submitted to completes.
The detailed process of described step 3 is: Git storehouse uses Hash codes as version number, and when stored data base, can be each Hash codes definition numbering automatically, numbering, from increasing, be numbered as comparing foundation using this during structure.
During stored data base, be submitted to the detailed process that Hash codes that central library fixes branch renumbers to each be: numbering adopts natural number from the mode increased, once numbering is often submitted to add 1, numbering and the Hash codes submitted to, file path, file operation information correspondence, namely once submit to and comprise multiple file, store in a database.
The detailed process of described step 4 is: when developer submits source code to, task agent is defined by developer, the effect of this bag is described in the essential information of task agent, after developer has developed, when central library receives the code that developer submits to from local library, the code release submitted to, start context, file path, file operation type, submitter, submission time information are associated with task agent, when building, this task agent of independent structure, has accurately taken out demand or has solved the concrete file of bug needs and be built into AKU.
The detailed process of described step 5 is: adopt task agent by for the file association solving customer issue, build task agent at any time; When collaborative development, file has multiple version and start context exists in multiple task agent, when building, first the start context that in this task agent, identical file is maximum is compared, then the start context using the maximum start context of this file and this file to build compares, if the start context built is larger, then issue in bag and use the maximum start context built, otherwise the maximum start context of the file in use task agent, this ensure that the FileVersion issued in bag can not cover the FileVersion in production environment.
A kind of implementation method based on Git release code at any time of the present invention, has the following advantages:
A kind of implementation method based on Git release code at any time of this invention, can build, timely customer in response at any time; By the version process of tool, compare hand picking file detection higher, error rate is lower; Task agent associates with sound code file, divides demand or sound code file corresponding to bug in logic; Support the collaborative development of many developers, the project development cycle can be shortened; Have recorded Git central library and submit record to, and version conversion is become the numbering of independent increment, be easy to edition comparison, and the history information of readability can be provided; When multiple person cooperational develops same project, can not need manually to pick file and build, build the issue bag that client needs at any time, increase work efficiency and issue bag quality, practical, applied widely, be easy to promote.
Embodiment
Below in conjunction with specific embodiment, the invention will be further described.
The invention provides a kind of implementation method based on Git release code at any time, solving when using Git management document version, correctly can build FileVersion, and issue bag can be built at any time, can build and accurately solve customer issue, improve client response speed and satisfaction.
Based on this, the implementation procedure of the method is:
Keeper defines Git central library and fixes branch, developer's creation task bag, and developer is exploitation code in local Git development library, after having developed, fixes the code synchronisation of branch, be submitted in central library by code after managing conflict with central library.
Hook script is added in central library, each submission of monitoring developer, by comparing the difference between this submission of developer and the version fixing submission last time in branch in hook script, get the information such as the file path of submission, file operation, again in conjunction with the version number that this is submitted to, the information such as submitter, time of adding stores in a database, namely thinks that the content obtaining that this is submitted to completes.
The version number of Git is Hash codes, and FileVersion when conveniently building compares, and when stored data base, can be each Hash codes definition numbering automatically, numbering, from increasing, be numbered as comparing foundation using this during structure.
The content submitted to associates with the task agent that developer creates, and function can repeatedly be submitted to, and submission information is all recorded in task agent.
Because be multiple developer's collaborative developments, so the different editions of identical file may be there is, in different task agent, at this moment building process needs to compare FileVersion, obtain the numbering that the latest edition of numbering corresponding to the FileVersion that built and task agent file to be built is corresponding, when avoiding upgrading, version covers, and the FileVersion content calculated is structured in and issues in bag, is supplied to client and uses.
More specifically, technic relization scheme of the present invention is as follows:
One, keeper defines the fixing branch of Git central library,
Git is distributed version control system, and each resources bank is complete clone, so in theory, the Git resources bank of same project is equal rank.In the present invention, it is central library that keeper needs to define certain Git resources bank, and the trunk branch of technical routine is as fixing branch, developer is exploitation code in local Git development library, after having developed, fix the code synchronisation of branch with central library, after managing conflict, code is submitted in central library.
Two, obtain Git central library by hook script and fix the latest edition that in branch, code is submitted to.
Hook script pre-receive in amendment central library, when user performs " git-push " namely toward central library submission code commands at local library, central library will call pre-receive script, by performing code in script, the difference between this submission of developer and the version fixing submission last time in branch can be compared, get the information such as the file path of submission, file operation, again in conjunction with the version number that this is submitted to, the information such as submitter, time of adding stores in a database, namely thinks that the content obtaining that this is submitted to completes.
Three, the version conversion in Git is become from addendum number storage.
Because Git storehouse uses the unique Hash codes in the whole world as version number, Hash codes itself cannot do the comparison of size, so the size conveniently doing version when building compares, be submitted to the Hash codes that central library fixes branch renumber each, the mode that numbering adopts natural number certainly to increase, often submits to once numbering to add 1, numbering meeting and the information such as Hash codes, file path, the file operation correspondence submitted to, namely may comprise multiple file in once submitting to, store in a database.
Four, the source code of exploitation associates with task agent.
In order to accurately construct the file that can meet certain demand or solve needed for certain bug, what need to distinguish each demand or bug completes the source file related to, the present invention is when developer submits to, task agent is defined by developer, the effect of this bag is described in the essential information of task agent, after developer has developed, when central library receives the code that developer submits to from local library, by the code release submitted to, start context, file path, file operation type, submitter, the information such as submission time associate with task agent, when building, this task agent can be built separately, accurate taking-up completes demand or solves the concrete file of bug needs and be built into AKU, can to upgrade all files for project, and involved file of only upgrading, minimize on the impact of project construction environment.
Five, build at any time and can correct FileVersion be obtained.
After going wrong in the production environment of client, generally wish that developer solves immediately and issues and guarantee the repair free of charge direct problem, but in common integrated structure, solve the problem of client, need the whole item object program building certain time period, the program construction of whole project is become to issue bag, in this process, in order to ensure that the correctness of constructing environment needs to wait for that relevant developer could build after being submitted to by code, may can not accomplish timely customer in response demand; And the correction of the problem to other may be comprised, if not full test, after upgrading, serious harmful effect may be caused to client's production system.Shoot the arrow at the target to reach, the present invention adopts task agent by for the file association solving customer issue, can build task agent at any time.When collaborative development, file may have multiple version and start context exists in multiple task agent, when building, first the start context that in this task agent, identical file is maximum is compared, then the start context using the maximum start context of this file and this file to build compares, if the start context built is larger, then issue in bag and use the maximum start context built, otherwise the maximum start context of the file in use task agent, this ensure that the FileVersion issued in bag can not cover the FileVersion in production environment.
Above-mentioned embodiment is only concrete case of the present invention; scope of patent protection of the present invention includes but not limited to above-mentioned embodiment; any according to the invention a kind of based on Git at any time the implementation method of release code claims and any person of an ordinary skill in the technical field to its suitable change done or replacement, all should fall into scope of patent protection of the present invention.
Claims (7)
1., based on an implementation method for Git release code at any time, it is characterized in that, its specific implementation process is:
One, first keeper defines Git central library and fixes branch, and namely keeper defines certain Git resources bank is central library, and the trunk branch of technical routine is as fixing branch;
Two, obtain Git central library by hook script and fix the latest edition that in branch, code is submitted to;
Three, the version conversion in Git is become from addendum number storage;
Four, the source code of exploitation is associated with task agent;
Five, build at any time and can correct FileVersion be obtained.
2. a kind of implementation method based on Git release code at any time according to claim 1, it is characterized in that, in described step one, keeper defines Git central library and fixes branch, developer's creation task bag, developer is exploitation code in local Git development library, after having developed, fix the code synchronisation of branch with central library, after managing conflict, code is submitted in central library.
3. a kind of implementation method based on Git release code at any time according to claim 1, it is characterized in that, the detailed process of described step 2 is: in central library, add hook script, each submission of monitoring developer, by comparing the difference between this submission of developer and the version fixing submission last time in branch in hook script, get the file path comprising submission, the information of file operation, again in conjunction with the version number that this is submitted to, add submitter, the information such as time store in a database, namely think that the content obtaining that this is submitted to completes.
4. a kind of implementation method based on Git release code at any time according to claim 1, it is characterized in that, the detailed process of described step 3 is: Git storehouse uses Hash codes as version number, when stored data base, can be each Hash codes definition numbering automatically, numbering, from increasing, is numbered as comparing foundation using this during structure.
5. a kind of implementation method based on Git release code at any time according to claim 4, it is characterized in that, during stored data base, be submitted to the detailed process that Hash codes that central library fixes branch renumbers to each be: numbering adopts natural number from the mode increased, once numbering is often submitted to add 1, numbering and the Hash codes submitted to, file path, file operation information correspondence, namely once submit to and comprise multiple file, store in a database.
6. a kind of implementation method based on Git release code at any time according to claim 1, it is characterized in that, the detailed process of described step 4 is: when developer submits source code to, task agent is defined by developer, the effect of this bag is described in the essential information of task agent, after developer has developed, when central library receives the code that developer submits to from local library, by the code release submitted to, start context, file path, file operation type, submitter, submission time information associates with task agent, when building, this task agent of independent structure, accurate taking-up completes demand or solves the concrete file of bug needs and be built into AKU.
7. a kind of implementation method based on Git release code at any time according to claim 1, it is characterized in that, the detailed process of described step 5 is: adopt task agent by for the file association solving customer issue, build task agent at any time; When collaborative development, file has multiple version and start context exists in multiple task agent, when building, first the start context that in this task agent, identical file is maximum is compared, then the start context using the maximum start context of this file and this file to build compares, if the start context built is larger, then issue in bag and use the maximum start context built, otherwise the maximum start context of the file in use task agent, this ensure that the FileVersion issued in bag can not cover the FileVersion in production environment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510561172.0A CN105094851A (en) | 2015-09-06 | 2015-09-06 | Method for momentarily issuing codes based on Git |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510561172.0A CN105094851A (en) | 2015-09-06 | 2015-09-06 | Method for momentarily issuing codes based on Git |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105094851A true CN105094851A (en) | 2015-11-25 |
Family
ID=54575379
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510561172.0A Pending CN105094851A (en) | 2015-09-06 | 2015-09-06 | Method for momentarily issuing codes based on Git |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105094851A (en) |
Cited By (33)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105373388A (en) * | 2015-11-30 | 2016-03-02 | 西安闻泰电子科技有限公司 | Code management method for automatically uploading PATCH modifications |
| CN105487912A (en) * | 2015-11-30 | 2016-04-13 | 西安闻泰电子科技有限公司 | Public problem modification multi-branch maintenance system and method |
| CN106201784A (en) * | 2016-07-18 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | A kind of data back up method based on git and system |
| CN106886420A (en) * | 2017-03-30 | 2017-06-23 | 努比亚技术有限公司 | A kind of program code managing device, method and program code manager |
| CN107203724A (en) * | 2017-05-18 | 2017-09-26 | 北京京东尚科信息技术有限公司 | File submits method and apparatus |
| CN107247601A (en) * | 2017-07-04 | 2017-10-13 | 武汉斗鱼网络科技有限公司 | Development process optimization method, device and storage medium |
| CN107341150A (en) * | 2016-04-28 | 2017-11-10 | 泰康保险集团股份有限公司 | Automate dissemination method and device |
| CN107451172A (en) * | 2016-03-31 | 2017-12-08 | 阿里巴巴集团控股有限公司 | Method of data synchronization and equipment for edition management system |
| CN107797927A (en) * | 2017-10-18 | 2018-03-13 | 中国平安人寿保险股份有限公司 | Using automated testing method, device, equipment and readable storage medium storing program for executing |
| CN107908421A (en) * | 2017-09-29 | 2018-04-13 | 北京创鑫旅程网络技术有限公司 | The method and device of software code versions management and issue |
| CN107918541A (en) * | 2017-11-28 | 2018-04-17 | 武汉斗鱼网络科技有限公司 | Information processing method, device, electronic equipment and storage medium |
| CN108345467A (en) * | 2017-03-14 | 2018-07-31 | 平安科技（深圳）有限公司 | The update method and device of edition tree file |
| CN108829437A (en) * | 2018-06-29 | 2018-11-16 | 北京金山安全软件有限公司 | Product development method, system, device, computer equipment and storage medium |
| CN108984413A (en) * | 2018-07-24 | 2018-12-11 | 浙江数链科技有限公司 | Branch code management method and device |
| CN109144562A (en) * | 2018-04-19 | 2019-01-04 | 南京新贝金服科技有限公司 | A kind of smart code publication alarm method based on zookeeper |
| CN109213516A (en) * | 2017-07-01 | 2019-01-15 | 武汉斗鱼网络科技有限公司 | The method of code synchronisation and notice, storage medium, equipment and system in SVN |
| CN109213518A (en) * | 2018-08-16 | 2019-01-15 | 安徽云才信息技术有限公司 | A method of the system automation based on git persistently constructs |
| CN109240734A (en) * | 2018-07-17 | 2019-01-18 | 北京奇虎科技有限公司 | Code submits method and device |
| CN109240738A (en) * | 2018-08-30 | 2019-01-18 | 广州虎牙信息科技有限公司 | Data base authority management method, device and computer equipment |
| CN109522025A (en) * | 2018-10-30 | 2019-03-26 | 深圳市小赢信息技术有限责任公司 | A kind of code delivery system based on git |
| CN109542769A (en) * | 2018-10-25 | 2019-03-29 | 武汉精立电子技术有限公司 | A kind of automated testing method of continuous integrating |
| CN109783105A (en) * | 2018-12-14 | 2019-05-21 | 平安普惠企业管理有限公司 | Encoding statistics method, equipment, storage medium and the device of enterprises service platform |
| CN109918412A (en) * | 2019-01-22 | 2019-06-21 | 新智云数据服务有限公司 | Data processing method, device, equipment and storage medium |
| CN110083587A (en) * | 2019-04-16 | 2019-08-02 | 会找房(北京)网络技术有限公司 | A kind of databases comparison measures and procedures for the examination and approval based on Git |
| CN110119393A (en) * | 2016-04-29 | 2019-08-13 | 清华大学 | Code release management system and method |
| CN110187914A (en) * | 2019-05-23 | 2019-08-30 | 杭州火小二科技有限公司 | Application and development method, system and device |
| CN110502273A (en) * | 2019-08-27 | 2019-11-26 | 浪潮云信息技术有限公司 | A kind of method, terminal and computer readable storage medium constructing local project |
| CN111190637A (en) * | 2019-07-24 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Version file release management method, device and system |
| CN111666081A (en) * | 2020-04-30 | 2020-09-15 | 平安科技（深圳）有限公司 | Project version release method, device, equipment and medium based on Git |
| CN111708747A (en) * | 2020-06-15 | 2020-09-25 | 中国航空工业集团公司西安飞行自动控制研究所 | Method for generating version tree of distributed version management document |
| CN112000334A (en) * | 2020-07-20 | 2020-11-27 | 北京达佳互联信息技术有限公司 | Page development method, device, server and storage medium |
| CN112134948A (en) * | 2020-09-21 | 2020-12-25 | 苏州科达科技股份有限公司 | Component publishing synchronization method, system, device and storage medium |
| US11175912B2 (en) | 2019-11-12 | 2021-11-16 | Wistron Corp. | Version management system, version management method and non-transitory computer-readable medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103473076A (en) * | 2013-09-25 | 2013-12-25 | 中国联合网络通信集团有限公司 | Issuing method and issuing system for code version |
| CN103729195A (en) * | 2014-01-15 | 2014-04-16 | 北京奇虎科技有限公司 | Control method and system for software version |
| CN104360845A (en) * | 2014-10-27 | 2015-02-18 | 浪潮软件股份有限公司 | Collaborative development construction method based on SVN (switching virtual networking) |
| CN104536744A (en) * | 2014-12-19 | 2015-04-22 | 微梦创科网络科技（中国）有限公司 | Method and server for automatically building and deploying codes |
| CN104793946A (en) * | 2015-04-27 | 2015-07-22 | 广州杰赛科技股份有限公司 | Application deployment method and system based on cloud computing platform |
-
2015
- 2015-09-06 CN CN201510561172.0A patent/CN105094851A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103473076A (en) * | 2013-09-25 | 2013-12-25 | 中国联合网络通信集团有限公司 | Issuing method and issuing system for code version |
| CN103729195A (en) * | 2014-01-15 | 2014-04-16 | 北京奇虎科技有限公司 | Control method and system for software version |
| CN104360845A (en) * | 2014-10-27 | 2015-02-18 | 浪潮软件股份有限公司 | Collaborative development construction method based on SVN (switching virtual networking) |
| CN104536744A (en) * | 2014-12-19 | 2015-04-22 | 微梦创科网络科技（中国）有限公司 | Method and server for automatically building and deploying codes |
| CN104793946A (en) * | 2015-04-27 | 2015-07-22 | 广州杰赛科技股份有限公司 | Application deployment method and system based on cloud computing platform |
Non-Patent Citations (2)
| Title |
|---|
| SJ: "Git Hook 整合 Redmine API 自動提交版本變更記錄至 Issue", 《HTTPS://BLOG.TORIGHT.COM/POSTS/4096/GIT-HOOK-整合-REDMINE-API-自動提交版本變更記錄至-ISSUE.HTML》 * |
| 恒-IVAN: "git快速使用（本地仓库同步到远程仓库）", 《HTTP://WWW.CNBLOGS.COM/IVANGEL/P/4208437.HTML 》 * |
Cited By (44)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105487912A (en) * | 2015-11-30 | 2016-04-13 | 西安闻泰电子科技有限公司 | Public problem modification multi-branch maintenance system and method |
| CN105373388A (en) * | 2015-11-30 | 2016-03-02 | 西安闻泰电子科技有限公司 | Code management method for automatically uploading PATCH modifications |
| CN107451172A (en) * | 2016-03-31 | 2017-12-08 | 阿里巴巴集团控股有限公司 | Method of data synchronization and equipment for edition management system |
| CN107341150A (en) * | 2016-04-28 | 2017-11-10 | 泰康保险集团股份有限公司 | Automate dissemination method and device |
| CN110119393A (en) * | 2016-04-29 | 2019-08-13 | 清华大学 | Code release management system and method |
| CN106201784A (en) * | 2016-07-18 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | A kind of data back up method based on git and system |
| CN106201784B (en) * | 2016-07-18 | 2019-01-29 | 浪潮(北京)电子信息产业有限公司 | A kind of data back up method and system based on git |
| CN108345467A (en) * | 2017-03-14 | 2018-07-31 | 平安科技（深圳）有限公司 | The update method and device of edition tree file |
| CN108345467B (en) * | 2017-03-14 | 2021-04-16 | 平安科技（深圳）有限公司 | Version tree file updating method and device |
| CN106886420A (en) * | 2017-03-30 | 2017-06-23 | 努比亚技术有限公司 | A kind of program code managing device, method and program code manager |
| CN106886420B (en) * | 2017-03-30 | 2020-10-09 | 广州柔视智能科技有限公司 | Program code management device and method and program code manager |
| CN107203724A (en) * | 2017-05-18 | 2017-09-26 | 北京京东尚科信息技术有限公司 | File submits method and apparatus |
| CN107203724B (en) * | 2017-05-18 | 2020-06-30 | 北京京东尚科信息技术有限公司 | File submission method and device |
| CN109213516A (en) * | 2017-07-01 | 2019-01-15 | 武汉斗鱼网络科技有限公司 | The method of code synchronisation and notice, storage medium, equipment and system in SVN |
| CN107247601A (en) * | 2017-07-04 | 2017-10-13 | 武汉斗鱼网络科技有限公司 | Development process optimization method, device and storage medium |
| CN107908421A (en) * | 2017-09-29 | 2018-04-13 | 北京创鑫旅程网络技术有限公司 | The method and device of software code versions management and issue |
| CN107908421B (en) * | 2017-09-29 | 2022-06-24 | 北京创鑫旅程网络技术有限公司 | Software code version management and release method and device |
| CN107797927A (en) * | 2017-10-18 | 2018-03-13 | 中国平安人寿保险股份有限公司 | Using automated testing method, device, equipment and readable storage medium storing program for executing |
| CN107918541A (en) * | 2017-11-28 | 2018-04-17 | 武汉斗鱼网络科技有限公司 | Information processing method, device, electronic equipment and storage medium |
| CN109144562A (en) * | 2018-04-19 | 2019-01-04 | 南京新贝金服科技有限公司 | A kind of smart code publication alarm method based on zookeeper |
| CN108829437A (en) * | 2018-06-29 | 2018-11-16 | 北京金山安全软件有限公司 | Product development method, system, device, computer equipment and storage medium |
| CN109240734A (en) * | 2018-07-17 | 2019-01-18 | 北京奇虎科技有限公司 | Code submits method and device |
| CN108984413A (en) * | 2018-07-24 | 2018-12-11 | 浙江数链科技有限公司 | Branch code management method and device |
| CN109213518A (en) * | 2018-08-16 | 2019-01-15 | 安徽云才信息技术有限公司 | A method of the system automation based on git persistently constructs |
| CN109240738A (en) * | 2018-08-30 | 2019-01-18 | 广州虎牙信息科技有限公司 | Data base authority management method, device and computer equipment |
| CN109240738B (en) * | 2018-08-30 | 2022-03-01 | 广州虎牙信息科技有限公司 | Database authority management method and device and computer equipment |
| CN109542769A (en) * | 2018-10-25 | 2019-03-29 | 武汉精立电子技术有限公司 | A kind of automated testing method of continuous integrating |
| CN109522025A (en) * | 2018-10-30 | 2019-03-26 | 深圳市小赢信息技术有限责任公司 | A kind of code delivery system based on git |
| CN109522025B (en) * | 2018-10-30 | 2021-07-20 | 深圳市小赢信息技术有限责任公司 | Code issuing system based on git |
| CN109783105A (en) * | 2018-12-14 | 2019-05-21 | 平安普惠企业管理有限公司 | Encoding statistics method, equipment, storage medium and the device of enterprises service platform |
| CN109783105B (en) * | 2018-12-14 | 2024-04-09 | 北京中发展智源人工智能科技发展有限公司 | Coding statistical method, equipment, storage medium and device of enterprise service platform |
| CN109918412A (en) * | 2019-01-22 | 2019-06-21 | 新智云数据服务有限公司 | Data processing method, device, equipment and storage medium |
| CN110083587A (en) * | 2019-04-16 | 2019-08-02 | 会找房(北京)网络技术有限公司 | A kind of databases comparison measures and procedures for the examination and approval based on Git |
| CN110187914A (en) * | 2019-05-23 | 2019-08-30 | 杭州火小二科技有限公司 | Application and development method, system and device |
| CN111190637A (en) * | 2019-07-24 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Version file release management method, device and system |
| CN111190637B (en) * | 2019-07-24 | 2024-06-07 | 腾讯科技（深圳）有限公司 | Version file release management method, device and system |
| CN110502273A (en) * | 2019-08-27 | 2019-11-26 | 浪潮云信息技术有限公司 | A kind of method, terminal and computer readable storage medium constructing local project |
| US11175912B2 (en) | 2019-11-12 | 2021-11-16 | Wistron Corp. | Version management system, version management method and non-transitory computer-readable medium |
| 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 |
| CN111708747B (en) * | 2020-06-15 | 2023-02-10 | 中国航空工业集团公司西安飞行自动控制研究所 | Method for generating distributed version management document version tree |
| CN111708747A (en) * | 2020-06-15 | 2020-09-25 | 中国航空工业集团公司西安飞行自动控制研究所 | Method for generating version tree of distributed version management document |
| CN112000334A (en) * | 2020-07-20 | 2020-11-27 | 北京达佳互联信息技术有限公司 | Page development method, device, server and storage medium |
| CN112134948A (en) * | 2020-09-21 | 2020-12-25 | 苏州科达科技股份有限公司 | Component publishing synchronization method, system, device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105094851A (en) | Method for momentarily issuing codes based on Git | |
| CN102236672B (en) | A kind of data lead-in method and device | |
| CN101847228B (en) | Workflow static planning method based on process mode | |
| CN109086071A (en) | A kind of method and server of management software version information | |
| US8898635B2 (en) | System and method for automatic impact variable analysis and field expansion in mainframe systems | |
| CN106156186A (en) | A kind of data model managing device, server and data processing method | |
| CN105719126B (en) | system and method for scheduling Internet big data tasks based on life cycle model | |
| CN103971223A (en) | Automatic calibrating method of make-to-order production materials by server | |
| CN108920436A (en) | A kind of file data comparison method, tool and equipment | |
| CN102968298A (en) | Software product construction method | |
| CN103473342A (en) | Report data generating method and system | |
| CN103019726A (en) | Management method and device of software system service rules | |
| CN106648587A (en) | Annotation-based Web application code generation method | |
| CN106528070A (en) | Data table generation method and equipment | |
| US9495132B2 (en) | Release management systems and methods | |
| CN105224332A (en) | A kind of application program generates method and apparatus | |
| CN106445529A (en) | Backup method and system for configuration information of continuous integration server | |
| CN104881361A (en) | Software development process monitoring and managing method and system | |
| CN103150386B (en) | A kind of C4ISR system meta-model construction method | |
| CN109947459A (en) | A kind of software product construction method | |
| US20130110730A1 (en) | Integration of computerized project planning and project diagramming | |
| CN103995699A (en) | Electric power enterprise information system development method based on MDA | |
| US20230393825A1 (en) | Automated software deployment techniques | |
| CN105320562B (en) | A kind of distributed job Accelerating running method and system based on operational feature fingerprint | |
| CN108132802B (en) | Application method of configuration model in system development |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20151125 |
|
| WD01 | Invention patent application deemed withdrawn after publication |