CN110247964A - The method and device of code publication - Google Patents

The method and device of code publication Download PDF

Info

Publication number
CN110247964A
CN110247964A CN201910488699.3A CN201910488699A CN110247964A CN 110247964 A CN110247964 A CN 110247964A CN 201910488699 A CN201910488699 A CN 201910488699A CN 110247964 A CN110247964 A CN 110247964A
Authority
CN
China
Prior art keywords
server
release module
publication
automatic
synchronization
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
Application number
CN201910488699.3A
Other languages
Chinese (zh)
Inventor
段乾
吴峰
郭伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Yidianshikong Network Co Ltd
Original Assignee
Shanghai Yidianshikong Network Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Yidianshikong Network Co Ltd filed Critical Shanghai Yidianshikong Network Co Ltd
Priority to CN201910488699.3A priority Critical patent/CN110247964A/en
Publication of CN110247964A publication Critical patent/CN110247964A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

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)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)

Abstract

This application discloses a kind of devices and methods therefors of code publication, including release module, automatic release module again, manual release module and server again;The release module, automatic release module again and manual release module again are connect with the server;The release module will provide service on the code that developer writes, resource supplying to server, and not carry out same cloth to not synchronous machine identification, not complete to not fully synchronized machine identification with cloth;The automatic release module again is directed to not fully synchronized server, issues corresponding code, resource again automatically to the server;It is described that release module issues publication again and reminds, developer is reminded to be retransmitted manually for not synchronous server again manually.The technical issues of not having retransmission mechanism and not fully synchronized code server, resource missing present application addresses the server that existing delivery system does not synchronize.

Description

The method and device of code publication
Technical field
This application involves the communications fields, in particular to a kind of method and device of code publication.
Background technique
Delivery system is that company is used to provide code that developer writes, resource supplying to service to network server is showed System.By delivery system, the function that developer can have been developed is pushed on existing network server and provides clothes for user Business.For issuing every time, needs developer to carry out publication application, submit corresponding server list and corresponding version. But the bandwidth for being constrained to delivery system server itself, network packet transmission such as lose at the various problems, and user is in same primary publication When applying carrying out code, source synchronous to multiple servers, it is understood that there may be part machine code, resource are synchronous or incomplete Synchronous situation.For this code, source synchronous, if having part machine same in the more machines of mark to be synchronized It walks successfully, then mark is this time issued successfully.It successfully or is only synchronized the machine of partial code, resource for not synchronizing, then needs It wants developer to resubmit publication application to synchronize.Existing delivery system will do it mark not for not synchronous machine It is issued, the version before corresponding code, resource version still do not synchronize on machine;Not fully synchronized machine then identifies hair Cloth does not complete, and machine version is current announced version.
But existing delivery system has the disadvantage in that
1. for having selected to issue, but the server of non-synchronizing code, resource, retransmission mechanism is not carried out, then It is subsynchronous to need that corresponding publication is submitted to apply.
2. for having selected to issue, not fully synchronized machine has identified machine version then as application publication Version, actually may synchronizing code, resource it is incomplete or synchronizing code, resource missing cause function unavailable.
Summary of the invention
The main purpose of the application is to provide a kind of method and device of code publication, to solve existing delivery system not Synchronous server does not have the problem of retransmission mechanism and not fully synchronized code server, resource missing.
To achieve the goals above, according to the one aspect of the application, the device of code publication is provided.
Device according to the publication of the code of the application includes: release module, automatic release module again, issues again manually Module and server;The release module, automatic release module again and manually again release module with the server Connection;
The release module will provide service on the code that developer writes, resource supplying to server, and to not same The machine identification of step does not carry out same cloth, does not complete to not fully synchronized machine identification with cloth;
The automatic release module again is directed to not fully synchronized server, and to the server, publication is corresponding again automatically Code, resource;It is described that release module issues publication again and reminds, remind exploitation for not synchronous server again manually Personnel are retransmitted manually.
It further, further include configuration module, the configuration module is connect with the server;Developer passes through described Configuration module configures each code, the publication maximum time of resource, automatic sending times and manual sending times;The publication Maximum time is the maximum time interval for stopping publication to the end since developer clicks publication;If certain server is same Code, resource time are walked more than the publication maximum time, then release module disconnects the connection of corresponding server automatically;It is described from Dynamic sending times are the automatic release module again in not fully synchronized server sync failure, described to send out again automatically The progress of cloth module issues maximum number automatically again, is more than after the number, and the automatic repeating transmission of the server terminates, described automatic Again release module generation error log, while notifying current publisher and the administrator of release module there are timing error, Manpower intervention is needed to inquire.The manual sending times are that not synchronous server is described in the case where not needing manually to examine The maximum times that release module is issued again again manually, if it exceeds the number, then the publication of the server terminates, institute Manual release module generation error log again is stated, while it is same to notify that current publisher and the release module administrator exist Mistake is walked, manpower intervention is needed to inquire.
Further, the publication maximum time passes through administrator setting.
Further, publication maximum time default setting when administrator is not set is 600 seconds.
Further, the automatic sending times are configured by administrator.
Further, the automatic sending times are defaulted as 0 when administrator is not set, i.e., are not retransmitted automatically.
Further, the manual sending times are configured by administrator.
Further, the manual sending times are defaulted as 0 when administrator is not set, i.e., not can be carried out after publication failure It retransmits manually.
To achieve the goals above, according to the another aspect of the application, a kind of method of code publication is provided.
According to the code of the application publication method comprising steps of
Step 1, administrator are by the configuration module to publication maximum time, automatic sending times, manual sending times It is configured;
Step 2, developer apply issuing and issuing by the release module;
Step 3, in synchronizing process, for having synchronized successful server, the release module is from publisher server list It removes;For not synchronous machine, the release module is included to the server list for needing manual re-synchronization;For Not fully synchronized machine, the release module are included to the server list of automatic re-synchronization;
Step 4, for the server of manual re-synchronization, the developer by it is described manually again release module into Row re-synchronization, and corresponding synchronization times are recorded, and the termination when reaching maximum synchronization times, it is described to send out again manually Cloth module generation error log, while notifying current publisher and the release module administrator that there are timing errors, it needs Manpower intervention inquiry;
Step 5, for the server of automatic re-synchronization, automatic re-synchronization is carried out by automatic re-synchronization module, and Record current synchronization times, and the termination when reaching maximum synchronization times, the automatic release module generation error again Log, while notifying current publisher and the release module administrator that there are timing errors, need manpower intervention to inquire.
Further, for the server of manual re-synchronization, the manual sending times are when administrator is not configured, institute It states release module and terminates the synchronization of respective server, and prompt respective server publication failure, while showing corresponding error service Device list;For the server of automatic re-synchronization, the automatic sending times are when administrator is not configured, the release module The synchronization of respective server is terminated, and the publication of respective server is prompted to fail, while showing corresponding error server list.
The utility model has the advantages that through the invention, for not synchronizing the server of code, resource, reaching and matching in this publication When the publication maximum time set, this publication terminates.Subsequent corresponding developer can be taken separated from such clothes that do not issue Business device, is issued again, and developer does not need to apply for corresponding publication process again at this time, while only needing to issue corresponding Not synchronous server, maximum re-synchronization number is by administrator configurations.For publication has been carried out, but not completely Synchronous server is more than display publication error after specified time, while being automatically resumed publication, by existing part generation Code, resource carry out discard processing.Re-start the secondary publication process of the server, the basis of the secondary publication process of server On, if terminating the synchronization process of the machine after synchronizing code, the resource frequency of failure are more than specified number, generating simultaneously Alarm reminds respective operations personnel and delivery system administrator to pay close attention to.And automatic publication again and manually in the present invention Again publication separately carries out, and mutual logic is not interfered.
Detailed description of the invention
The attached drawing constituted part of this application is used to provide further understanding of the present application, so that the application's is other Feature, objects and advantages become more apparent upon.The illustrative examples attached drawing and its explanation of the application is for explaining the application, not Constitute the improper restriction to the application.In the accompanying drawings:
Fig. 1 is the flow chart according to the method for the code of the embodiment of the present application publication.
Specific embodiment
In order to make those skilled in the art more fully understand application scheme, below in conjunction in the embodiment of the present application Attached drawing, the technical scheme in the embodiment of the application is clearly and completely described, it is clear that described embodiment is only The embodiment of the application a part, instead of all the embodiments.Based on the embodiment in the application, ordinary skill people Member's every other embodiment obtained without making creative work, all should belong to the model of the application protection It encloses.
It should be noted that term " includes " and " tool in the description and claims of this application and above-mentioned attached drawing Have " and their any deformation, it is intended that cover it is non-exclusive include, for example, containing a series of steps or units Process, method, system, product or equipment those of are not necessarily limited to be clearly listed step or unit, but may include without clear Other step or units listing to Chu or intrinsic for these process, methods, product or equipment.
The present invention provides a kind of multiserver code, source synchronous system, including it is release module, configuration module, automatic Again release module, manual release module and server again.The release module, issues mould at configuration module again automatically Block and manual release module again are respectively mounted on the terminal device, and are connect with the server.
The release module will provide service on the code that developer writes, resource supplying to server, and to not same The machine identification of step does not carry out same cloth, does not complete to not fully synchronized machine identification with cloth;
The automatic release module again is directed to not fully synchronized server, and to the server, publication is corresponding again automatically Code, resource;It is described that release module issues publication again and reminds, remind exploitation for not synchronous server again manually Personnel are retransmitted manually;
Developer configures each code, the publication maximum time of resource, automatic sending times by the configuration module And manual sending times;The publication maximum time is to stop the maximum of publication to the end since developer clicks publication Time interval;If certain server sync code, resource time are more than the publication maximum time, release module is from dynamic circuit breaker Open the connection of corresponding server;In the present invention, the publication maximum time is by administrator setting, if administrator does not set It sets, then defaulting the publication maximum time is 600 seconds;The automatic sending times are the automatic release module again not complete When all synchro server sync fails, the automatic progress of release module again issues maximum number automatically again, is more than After the number, the automatic repeating transmission of the server is terminated, the automatic release module generation error log again, while being notified current There are timing errors by publisher and the administrator of release module, and manpower intervention is needed to inquire.The automatic sending times are by pipe Reason person is configured, default data 0 is not retransmitted automatically.The manual sending times are that not synchronous server exists The maximum times that release module is issued again again manually in the case where manually examining are not needed, if it exceeds this time Number, then the server publication terminate, it is described manually release module generation error log again, while notify current publisher with And there are timing errors by the release module administrator, and manpower intervention is needed to inquire.The manual sending times by administrator into Row configuration, default data 0 not can be carried out manual repeating transmission after publication failure.
As shown in Figure 1, the method that code of the invention is issued includes the following steps:
Step 1, administrator are by the configuration module to publication maximum time, automatic sending times, manual sending times It is configured;
Step 2, developer apply issuing and issuing by the release module;
Step 3, in synchronizing process, for having synchronized successful server, the release module is from publisher server list It removes;For not synchronous machine, the release module is included to the server list for needing manual re-synchronization;For Not fully synchronized machine, the release module are included to the server list of automatic re-synchronization;
Step 4, for the server of manual re-synchronization, the developer by it is described manually again release module into Row re-synchronization, and corresponding synchronization times are recorded, and the termination when reaching maximum synchronization times, it is described to send out again manually Cloth module generation error log, while notifying current publisher and the release module administrator that there are timing errors, it needs Manpower intervention inquiry;If manual sending times are not configured in administrator, it is subsynchronous that the release module terminates this, and prompts this Secondary publication failure, while showing corresponding error server list;
Step 5, for the server of automatic re-synchronization, automatic re-synchronization is carried out by automatic re-synchronization module, and Record current synchronization times, and the termination when reaching maximum synchronization times, the automatic release module generation error again Log, while notifying current publisher and the release module administrator that there are timing errors, need manpower intervention to inquire;Such as The automatic sending times are not configured in fruit administrator, then it is subsynchronous to terminate this for the release module, and prompt this publication failure, Corresponding error server list is shown simultaneously.
Multiserver code according to the present invention, source synchronous system and method, the present invention provides specific embodiments It is as follows:
The longest issuing time of administrator setting is 1500 seconds, and the automatic maximum number of retransmissions for retransmitting module is 3 times, manually The maximum number of retransmissions for retransmitting module is 3 times, when developer has applied by carrying out the same of indicated release V to server A-C Step operation, server A, B are issued successfully, and server C has issued part resource, code, after the completion of publication because of network jitter It not can be carried out fully synchronized, C is divided into not fully synchronized server at this time, and progress is issued again automatically, on server C together Part resource, the source code of step are deleted.Then the first time for carrying out C is issued automatically to be retried, if the network of C is asked at this time Topic, in specified maximum issue duration, delivery system is not attached to server C, and C is divided into non-sync server column again at this time Table.If issued successfully, this TV station machine this time issues completion.If continuous automatic publication again weight more than 3 times or manually New publication is more than 3 times, and publication terminates at this time.
As shown in this embodiment, in the issuing process, certain machine has and only following three kinds of situations:
1. synchronizing success.
2. retransmitting 3 failures of module synchronization automatically.
3. retransmitting 3 failures of module synchronization manually.
The foregoing is merely preferred embodiment of the present application, are not intended to limit this application, for the skill of this field For art personnel, various changes and changes are possible in this application.Within the spirit and principles of this application, made any to repair Change, equivalent replacement, improvement etc., should be included within the scope of protection of this application.

Claims (10)

1. the device of code publication, which is characterized in that including release module, automatic release module again, issue mould again manually Block and server;The release module, automatic release module again and manual release module again connect with the server It connects;
The release module will provide service on the code that developer writes, resource supplying to server, and to not synchronization Machine identification does not carry out same cloth, does not complete to not fully synchronized machine identification with cloth;
The automatic release module again according to the mark of the release module determine server be do not issue completely it is synchronous or Synchronize it is unfinished, for not fully synchronized server, by the automatic release module again to the server automatically again Issue corresponding code, resource;It is described that release module issues publication again and reminds for not synchronous server again manually, Developer is reminded to be retransmitted manually.
2. the device of code publication according to claim 1, which is characterized in that it further include configuration module, the configuration mould Block is connect with the server;Developer by the configuration module configure each code, resource publication maximum time, from Dynamic sending times and manual sending times;The publication maximum time is to stop to the end since developer clicks publication The maximum time interval of publication;If certain server sync code, resource time are more than the publication maximum time, issue Module disconnects the connection of corresponding server automatically;The automatic sending times are the automatic release module again completely not same When the server sync failure of step, it is more than this time that the automatic progress of release module again issues maximum number automatically again After number, the automatic repeating transmission of the server is terminated, the automatic release module generation error log again, while notifying current publication There are timing errors by person and the administrator of release module, and manpower intervention is needed to inquire.The manual sending times are not synchronize Server in the case where not needing manually to examine release module is issued again again the maximum times manually, such as Fruit is more than the number, then the publication of the server terminates, the release module generation error log again manually, while notice is worked as There are timing errors by preceding publisher and the release module administrator, and manpower intervention is needed to inquire.
3. the device of code publication according to claim 2, which is characterized in that the publication maximum time passes through administrator Setting.
4. the device of code according to claim 3 publication, which is characterized in that the publication maximum time administrator not Default setting is 600 seconds when setting.
5. the device of code according to claim 2 publication, which is characterized in that the automatic sending times by administrator into Row configuration.
6. the device of code according to claim 5 publication, which is characterized in that the automatic sending times administrator not It is defaulted as 0 when setting, i.e., is not retransmitted automatically.
7. the device of code according to claim 2 publication, which is characterized in that the manual sending times by administrator into Row configuration.
8. the device of code according to claim 7 publication, which is characterized in that the manual sending times administrator not It is defaulted as 0 when setting, i.e., not can be carried out manual repeating transmission after publication failure.
9. a kind of method issued using code described in claim 2 to 8 any claim, which is characterized in that including step It is rapid:
Step 1, administrator carry out publication maximum time, automatic sending times, manual sending times by the configuration module Configuration;
Step 2, developer apply issuing and issuing by the release module;
Step 3, in synchronizing process, for having synchronized successful server, the release module is removed from publisher server list; For not synchronous machine, the release module is included to the server list for needing manual re-synchronization;For not complete All synchro machine, the release module are included to the server list of automatic re-synchronization;
Step 4, for the server of manual re-synchronization, release module carries out weight to the developer again by described manually It is new synchronous, and corresponding synchronization times are recorded, and the termination when reaching maximum synchronization times, it is described to issue mould again manually Block generation error log, while notifying current publisher and the release module administrator there are timing error, it needs artificial Intervention inquiry;
Step 5, for the server of automatic re-synchronization, automatic re-synchronization is carried out by automatic re-synchronization module, and record Current synchronization times, and the termination when reaching maximum synchronization times, the automatic release module generation error log again, It notifies current publisher and the release module administrator that there are timing errors simultaneously, manpower intervention is needed to inquire.
10. the method for code according to claim 9 publication, which is characterized in that for the server of manual re-synchronization, For the manual sending times when administrator is not configured, the release module terminates the synchronization of respective server, and prompts corresponding Server publication failure, while showing corresponding error server list;For the server of automatic re-synchronization, the automatic weight Number is sent out when administrator is not configured, the release module terminates the synchronization of respective server, and prompts the hair of respective server Cloth failure, while showing corresponding error server list.
CN201910488699.3A 2019-06-05 2019-06-05 The method and device of code publication Pending CN110247964A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910488699.3A CN110247964A (en) 2019-06-05 2019-06-05 The method and device of code publication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910488699.3A CN110247964A (en) 2019-06-05 2019-06-05 The method and device of code publication

Publications (1)

Publication Number Publication Date
CN110247964A true CN110247964A (en) 2019-09-17

Family

ID=67886347

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910488699.3A Pending CN110247964A (en) 2019-06-05 2019-06-05 The method and device of code publication

Country Status (1)

Country Link
CN (1) CN110247964A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113094066A (en) * 2021-03-16 2021-07-09 北京优奥创思科技发展有限公司 Multi-server code publishing method and system

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030037029A1 (en) * 2001-08-15 2003-02-20 Iti, Inc. Synchronization of plural databases in a database replication system
CN1815959A (en) * 2005-02-04 2006-08-09 联想(北京)有限公司 Method for issuing application software to network computer by server
CN104090763A (en) * 2014-07-11 2014-10-08 携程计算机技术(上海)有限公司 Compiling and publishing method and publishing server
CN105549992A (en) * 2015-12-08 2016-05-04 北京奇虎科技有限公司 Code publishing method, device and system
CN105930182A (en) * 2016-04-13 2016-09-07 北京思特奇信息技术股份有限公司 Distributed code version release system and method
CN109814873A (en) * 2019-02-14 2019-05-28 北京顺丰同城科技有限公司 A kind of code dissemination method and device

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030037029A1 (en) * 2001-08-15 2003-02-20 Iti, Inc. Synchronization of plural databases in a database replication system
CN1815959A (en) * 2005-02-04 2006-08-09 联想(北京)有限公司 Method for issuing application software to network computer by server
CN104090763A (en) * 2014-07-11 2014-10-08 携程计算机技术(上海)有限公司 Compiling and publishing method and publishing server
CN105549992A (en) * 2015-12-08 2016-05-04 北京奇虎科技有限公司 Code publishing method, device and system
CN105930182A (en) * 2016-04-13 2016-09-07 北京思特奇信息技术股份有限公司 Distributed code version release system and method
CN109814873A (en) * 2019-02-14 2019-05-28 北京顺丰同城科技有限公司 A kind of code dissemination method and device

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113094066A (en) * 2021-03-16 2021-07-09 北京优奥创思科技发展有限公司 Multi-server code publishing method and system
CN113094066B (en) * 2021-03-16 2024-03-26 北京优奥创思科技发展有限公司 Multi-server code release method and system

Similar Documents

Publication Publication Date Title
EP3190775A1 (en) Cloud data backup and recovery method
CN102769626B (en) A kind of session information synchronous method, device and system
CN103544303B (en) A kind of method of data synchronization, system and equipment
CN105554175A (en) ARP backup method in PW (Pseudo-wires) redundancy scene
CN105791307B (en) Network Time Protocol message safety certifying method and device
CN103354560B (en) Method and system for data decomposition and synchronization
CN110677282B (en) Hot backup method of distributed system and distributed system
WO2016065875A1 (en) Switching-on method, base station, base station controller, switching-on system and storage medium
CN107124305A (en) node device operation method and node device
WO2016065853A1 (en) Self-recovery method and device after disconnection of base station
CN102055605B (en) Disaster tolerance system and method applied to AAA (authentication, authorization and accounting) server
CN110247964A (en) The method and device of code publication
CN105812492B (en) A kind of method of data synchronization and system
WO2017016196A1 (en) Data synchronization method, apparatus, and system
CN106850153B (en) Data retransmission method and system
CN109088830A (en) A kind of port status synchronous method and device
CN101083566A (en) Method and apparatus for performing data performance monitor in transmission network management
CN104022515B (en) Reactive compensation cabinet and the control method of reactive compensation unit
CN108600004B (en) Video server configuration management method and system
CN105721395A (en) Data synchronization configuration method, apparatus and system
CN109165199A (en) A kind of file synchronisation method, device, equipment and computer readable storage medium
CN107273272A (en) The monitoring method and device of a kind of hot-plug equipment
CN109639850A (en) A kind of method and system for realizing active and standby DHCP SERVER based on VRRP
CN112702427A (en) Industrial internet data synchronization system
CN102739316B (en) Method and device for implementing transmission mode

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

Application publication date: 20190917

RJ01 Rejection of invention patent application after publication