CN109739539A - Application dissemination method, device, equipment and the storage medium of Cross-environment - Google Patents
Application dissemination method, device, equipment and the storage medium of Cross-environment Download PDFInfo
- Publication number
- CN109739539A CN109739539A CN201811617268.4A CN201811617268A CN109739539A CN 109739539 A CN109739539 A CN 109739539A CN 201811617268 A CN201811617268 A CN 201811617268A CN 109739539 A CN109739539 A CN 109739539A
- Authority
- CN
- China
- Prior art keywords
- environment
- application
- publication
- subsystem
- version
- 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
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
Dissemination method is applied the invention discloses a kind of Cross-environment, this method comprises: when issuing in a certain subsystem of source environment in application, judging whether the subsystem meets preset Cross-environment issue rules；If so, obtaining the application version and preset release model corresponding with the subsystem of publication；Application publication packet to be synchronized is obtained according to the application version of the publication and the release model；Publication template instances corresponding with the application to be synchronized publication packet are obtained, the application publication packet to be synchronized and the publication template instances are submitted into preset target environment, so that the corresponding application publication operation of target environment generation.The invention also discloses application distributing device, equipment and a kind of storage mediums of a kind of Cross-environment.The application automatic synchronization that the present invention realizes Cross-environment is issued, while being avoided and being expended more computing resource.
Description
Technical field
The present invention relates to application dissemination method, device, equipment and the storages of field of computer technology more particularly to Cross-environment
Medium.
Background technique
With the continuous development of computer software technology, there is more powerful function to allow apply, better performance, often
It needs constantly to be updated the version of application.In the prior art, using more generally increment file-based is issued
Method by calculating the delta file between application publication packet, and generates increment according to delta file and upgrades list, then issues
Increment upgrading is carried out to client.Such as: publication packet V1 includes file f 1, f2, and publication packet V2 includes file f 1, f2, f3, publication
Wrapping V3 includes file f 1, f3, f4；Δ V1 is the delta file packet of V1 to V2, includes f3, and Δ V2 is the delta file of V2 to V3
Packet includes-f2 and f4；Machine H1 needs to be upgraded to V2 from V1, it is only necessary to update Δ V1, machine H2 needs are upgraded to from V2
V3, it is only necessary to update Δ V2.
The defect of aforesaid way is: 1) can not carry out the automatic deployment of Cross-environment；2) fine size is calculated to file-level
Delta file between publication packet needs to expend more computing resource.
Summary of the invention
It is a primary object of the present invention to propose application dissemination method, device, equipment and the storage medium of a kind of Cross-environment,
The application automatic synchronization for aiming at Cross-environment is issued, while avoiding expending more computing resource.
To achieve the above object, the present invention provides a kind of application dissemination method of Cross-environment, the application hair of the Cross-environment
Cloth method includes the following steps:
When in a certain subsystem in source environment publication in application, judging whether the subsystem meets preset Cross-environment
Issue rules；
If so, obtaining the application version and preset release model corresponding with the subsystem of publication；
Application publication packet to be synchronized is obtained according to the application version of the publication and the release model；
Publication template instances corresponding with the application to be synchronized publication packet are obtained, by the application publication to be synchronized
Packet and the publication template instances submit to preset target environment, so that the target environment generates corresponding application publication and makees
Industry.
Preferably, described that application publication packet to be synchronized is obtained according to the application version of the publication and the release model
The step of include:
When the release model is general mode, application publication packet corresponding with the application version of the publication is obtained,
It issues and wraps as application to be synchronized；
When the release model is incremental mode, it is real to obtain each application of the subsystem in the target environment
Example；
According to preset rules, calculate corresponding to be released with each application example of the subsystem in the target environment
Version path；
Application publication packet corresponding with the application version for including in the version path to be released is obtained, as to be synchronized
It is wrapped using publication.
Preferably, described according to preset rules, it calculates and each application example of the subsystem in the target environment
The step of corresponding version path to be released includes:
Obtain the history released version path of each application example of the subsystem in the source environment；
Duplicate removal is carried out to the history released version path of each application example of the subsystem in the source environment, is merged
Processing, obtains a longest common path；
Obtain the current version of each application example of the subsystem in the target environment；
In the longest common path, using the current version as starting point, by the history release after the starting point
This path is as the corresponding version path to be released of each application example of the subsystem in the target environment.
Preferably, described to issue in a certain subsystem of source environment in application, judging whether the subsystem meets
The step of preset Cross-environment issue rules includes:
When publication in a certain subsystem in source environment in application, detecting the subsystem owning in the source environment
Whether the version of application example is consistent, if unanimously, determining that the subsystem meets preset Cross-environment issue rules；
Alternatively, when issuing in a certain subsystem of source environment in application, detecting the subsystem in the source environment
The version of application example whether changed, if the version of any application example of the subsystem in the source environment
It is changed, then determines that the subsystem meets preset Cross-environment issue rules.
Preferably, the application dissemination method of the Cross-environment further include:
The execution state for obtaining the application publication operation in the target environment, the execution state is written to pre-
If issue record table in；
Issue record table described in poll judges in the issue record table with the presence or absence of in the note for being not carried out completion status
Record；
If it exists, then periodically to target environment request with it is described be in be not carried out completion status record corresponding answer
With the current execution state of publication operation, and the current execution state is written back in the issue record table, until described
There is no in the record for being not carried out completion status in issue record table.
Preferably, described that the current execution state is written back in the issue record table, until the issue record
After the step of in table there is no in the record for being not carried out completion status, further includes:
All release informations that the issue record table records in preset duration are summarized, to generate publication report
Table；
The front end that the publication report is sent to the source environment is shown.
Preferably, described that the application publication packet to be synchronized and the publication template instances are submitted into preset target
The step of environment includes:
It is added after the application publication packet to be synchronized is associated with the publication template instances to preset publishing queue；
The application programming interface for periodically calling the target environment, will be described to be synchronized in the publishing queue
Application publication packet and the publication template instances submit to preset target environment.
Preferably, described to issue in a certain subsystem of source environment in application, judging whether the subsystem meets
Before the step of preset Cross-environment issue rules, further includes:
The automatic synchronization publication switch of the subsystem is set in the configuration management database of the source environment；
When receiving the open command based on automatic synchronization publication switch triggering, display one comprising general mode and
The selective listing of incremental mode；
The selection instruction triggered based on the selective listing is received, according to selection instruction setting and the subsystem pair
The release model answered.
In addition, to achieve the above object, applying distributing device the present invention also provides a kind of Cross-environment, which is characterized in that
The Cross-environment includes: using distributing device
Judgment module, for working as the publication in a certain subsystem of source environment in application, judging whether the subsystem is full
The preset Cross-environment issue rules of foot；
First acquisition module obtains answering for publication if meeting preset Cross-environment issue rules for the subsystem
With version and preset release model corresponding with the subsystem；
Second obtains module, for obtaining application to be synchronized according to the application version of the publication and the release model
Publication packet；
Submit module, for obtaining publication template instances corresponding with the application to be synchronized publication packet, by described in
Synchronous application publication packet and the publication template instances submit to preset target environment, so that target environment generation pair
The application publication operation answered.
Preferably, described second module is obtained further include:
First acquisition unit, for obtaining the application version with the publication when the release model is general mode
Corresponding application publication packet, issues as application to be synchronized and wraps；
Second acquisition unit, for obtaining the subsystem in the target when the release model is incremental mode
Each application example in environment；According to preset rules, calculate and each application example of the subsystem in the target environment
Corresponding version path to be released；Obtain application publication corresponding with the application version for including in the version path to be released
Packet is issued as application to be synchronized and is wrapped.
Preferably, the second acquisition unit is also used to:
Obtain the history released version path of each application example of the subsystem in the source environment；
Duplicate removal is carried out to the history released version path of each application example of the subsystem in the source environment, is merged
Processing, obtains a longest common path；
Obtain the current version of each application example of the subsystem in the target environment；
In the longest common path, using the current version as starting point, by the history release after the starting point
This path is as the corresponding version path to be released of each application example of the subsystem in the target environment.
In addition, to achieve the above object, distribution apparatus is applied the present invention also provides a kind of Cross-environment, the Cross-environment
Using distribution apparatus include: memory, processor and be stored on the memory and can run on the processor across
Environment apply release process, the Cross-environment using release process is executed by the processor when realization as described above across
The step of application dissemination method of environment.
In addition, to achieve the above object, the present invention also provides a kind of storage medium, being stored with transannular on the storage medium
Release process is applied in border, and the Cross-environment realizes Cross-environment as described above when being executed by processor using release process
The step of using dissemination method.
The present invention when in a certain subsystem of source environment publication in application, to judge whether the subsystem meets preset
Cross-environment issue rules；If so, obtaining the application version and preset release model corresponding with the subsystem of publication；Root
Application publication packet to be synchronized is obtained according to the application version of the publication and the release model；It obtains and to be synchronized is answered with described
Corresponding publication template instances are wrapped with publication, the application publication packet to be synchronized and the publication template instances are submitted to pre-
If target environment so that the target environment generates corresponding application and issues operation.Source environment of the present invention by obtaining automatically
Application publication packet to be synchronized and corresponding publication template instances, and submit to target environment automatically and issued, whole process
It is operated without manpower intervention, without the delta file calculated between publication packet, so that the present invention realizes the application of Cross-environment
Automatic synchronization publication, while avoiding and expending more computing resource.
Detailed description of the invention
Fig. 1 is the device structure schematic diagram for the hardware running environment that the embodiment of the present invention is related to；
Fig. 2 is the flow diagram using dissemination method first embodiment of Cross-environment of the present invention；
Fig. 3 is the system architecture schematic diagram of source environment in the embodiment of the present invention.
The embodiments will be further described with reference to the accompanying drawings for the realization, the function and the advantages of the object of the present invention.
Specific embodiment
It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, it is not intended to limit the present invention.
As shown in Figure 1, Fig. 1 is the device structure schematic diagram for the hardware running environment that the embodiment of the present invention is related to.
Cross-environment of the embodiment of the present invention can be PC machine or server apparatus using distribution apparatus.
As shown in Figure 1, the equipment may include: processor 1001, such as CPU, network interface 1004, user interface
1003, memory 1005, communication bus 1002.Wherein, communication bus 1002 is for realizing the connection communication between these components.
User interface 1003 may include display screen (Display), input unit such as keyboard (Keyboard), optional user interface
1003 can also include standard wireline interface and wireless interface.Network interface 1004 optionally may include that the wired of standard connects
Mouth, wireless interface (such as WI-FI interface).Memory 1005 can be high speed RAM memory, be also possible to stable memory
(non-volatile memory), such as magnetic disk storage.Memory 1005 optionally can also be independently of aforementioned processor
1001 storage device.
It will be understood by those skilled in the art that device structure shown in Fig. 1 does not constitute the restriction to equipment, can wrap
It includes than illustrating more or fewer components, perhaps combines certain components or different component layouts.
As shown in Figure 1, as may include that operating system, network are logical in a kind of memory 1005 of computer storage medium
That believes module, Subscriber Interface Module SIM and Cross-environment applies release process.
In terminal shown in Fig. 1, network interface 1004 is mainly used for connecting background server, carries out with background server
Data communication；User interface 1003 is mainly used for connecting client (user terminal), carries out data communication with client；And processor
1001 can be used for calling the application release process of the Cross-environment stored in memory 1005, and execute the application of following Cross-environments
Operation in each embodiment of dissemination method.
Based on above-mentioned hardware configuration, propose Cross-environment of the present invention applies dissemination method embodiment.
It is the flow diagram using dissemination method first embodiment of Cross-environment of the present invention, the side referring to Fig. 2, Fig. 2
Method includes:
Step S10, when in a certain subsystem in source environment publication in application, to judge whether the subsystem meets default
Cross-environment issue rules；
In the present embodiment, environment refers to that can be used for an independent network rings disposing application architecture, being isolated on network
Border, including but not limited to exploitation environment, integration testing environment, user acceptance test environment, production environment, disaster tolerance environment etc..This
Embodiment can be application for realizing the Cross-environment application automatic synchronization publication from source environment to target environment, such as source environment
Test environment, target environment can be the production environment of application, and source environment and target environment include identical subsystem.
It is the system architecture schematic diagram of source environment in the embodiment of the present invention referring to Fig. 3, Fig. 3, includes one automatic in the environment of source
Change operation platform AOMP (Automation Operations Management Platform), a configuration management database
CMDB (Configuration Management Database) and several subsystems S1 ..., Sn.Wherein, AOMP can be real
Now automate the various functions of O&M, including but not limited to: the automatic publication of application, server or the network equipment (one or
More of person) end execute order (or command set), operating database, run timing task dispatching；CMDB is used to store in IT architecture
Various assets of equipments, application architecture configuration item；Subsystem refers in IT architecture, can be used for the most granule of Stand-alone distribution
Degree, usually an independent module；It can be published to when a usual subsystem actual deployment on more machines, then every portion
Deployment is all an application example.
In the present embodiment, when user triggers the application publication instruction based on a certain version, source environment is existed by AOMP
The application of the version is issued in the subsystem that one or more users specify.It is applied when being issued in a certain subsystem in source environment
When, first determine whether the subsystem meets preset Cross-environment application issue rules, which can be by
The preparatory flexible setting of user.
In one embodiment, above-mentioned steps S10 may further include: issue when in a certain subsystem in source environment
In application, whether the version for detecting all application examples of the subsystem in the source environment is consistent, if unanimously, determining
The subsystem meets preset Cross-environment issue rules；Alternatively, when the publication in a certain subsystem of source environment is in application, inspection
Whether the version for surveying application example of the subsystem in the source environment is changed, if the subsystem is in the source
The version of any application example in environment is changed, then determines that the subsystem meets preset Cross-environment publication rule
Then.
For example, when in the subsystem S1 of source environment released version for V's in application, if detecting the institute of subsystem S1
The version for having application example is V, then can be determined that subsystem S1 meets preset Cross-environment issue rules；Alternatively, when in source
Released version is V's in application, if detecting the version hair of any application example in subsystem S1 in the subsystem S1 of environment
Change has been given birth to, then can be determined that subsystem S1 meets preset Cross-environment issue rules.Whether this automatic detection subsystem is full
The mode of the preset Cross-environment issue rules of foot can detect the application publication situation in the environment of source very well, be it is subsequent carry out across
The premise of the synchronous publication of the application of environment.
If the subsystem meets preset Cross-environment issue rules, S20 is thened follow the steps, obtains the application version of publication
With preset release model corresponding with the subsystem；
By taking above-mentioned subsystem S1 as an example, when subsystem S1 meets preset Cross-environment issue rules, the available son
The application version that system is currently issued, i.e. version V, while obtaining preset release model corresponding with subsystem S1.With subsystem
Corresponding release model of uniting may include general mode and incremental mode, and user can be different son in advance according to actual needs
Its corresponding release model is arranged in system.If setting release model is general mode, only need subsystem S1 in target ring
Application version on border directly upgrades to current version of the subsystem S1 in the environment of source, if setting release model is to increase
Amount mode, then needed that environmentally all versions of the S1 since the current version of S1 in target environment are issued all in target ring source
It is played back in border primary.
Step S30 obtains application publication packet to be synchronized according to the application version of the publication and the release model；
In the step, according to the above-mentioned application version issued in subsystem got and hair corresponding with the subsystem
Cloth pattern acquiring application publication packet to be synchronized.
Specifically, step S30 may further include: when the release model be general mode when, obtain with it is described
The corresponding application publication packet of the application version of publication, issues as application to be synchronized and wraps；When the release model is difference module
When formula, each application example of the subsystem in the target environment is obtained；According to preset rules, calculate and the subsystem
The corresponding version path to be released of each application example in the target environment；It obtains and the version path Zhong Bao to be released
The corresponding application publication packet of the application version contained, issues as application to be synchronized and wraps.
Still it is illustrated by taking above-mentioned subsystem S1 as an example, it, can be with if the release model of subsystem S1 is general mode
Packet V directly is issued into application corresponding with the application version V currently issued and (refers to the version of application publication packet using publication packet V
This is V) as application to be synchronized publication packet；If the release model of subsystem S1 is incremental mode, the son is obtained first
Each application example of the system S1 in target environment is calculated with subsystem S1 in target environment then according to preset rules
The corresponding version path to be released of each application example, later, obtain with the version path to be released in include each application
The corresponding application publication packet of version, issues as application to be synchronized and wraps.
Further, as an implementation, described according to preset rules, it calculates with the subsystem in the target
The step of each application example in environment corresponding version path to be released may include: to obtain the subsystem in the source ring
The history released version path of each application example in border；To going through for each application example of the subsystem in the source environment
History released version path carries out duplicate removal, merging treatment, obtains a longest common path；The subsystem is obtained in the target
The current version of each application example in environment；It, will be described using the current version as starting point in the longest common path
History released version path after starting point as each application example of the subsystem in the target environment it is corresponding to
Released version path.
With subsystem S1 as an example it is assumed that source environment S1 is there are two application example J and K, the wherein history released version of J
Path are as follows: the history released version path of V1- > V2- > Vm- > Vn- > V, K are as follows: V1- > V2- > V1- > Vm- > Vn- > V (wherein V1 weight
Recur cloth), then the history released version path of J and K is subjected to duplicate removal, merged, the longest common path of available J and K are as follows:
V1->V2->Vm->Vn->V；Assuming that target environment S1, there are two application example M and N, version is respectively Vm, Vn, then in longest public affairs
Altogether in path, using Vm as starting point, take history released version path Vn- > V after Vm as corresponding with application example M pending
Cloth version path, similarly using Vn as starting point, take history released version path V after Vn as it is corresponding with application example N to
Released version path.Later, application publication packet Vn corresponding with the application version for including in the version path to be released is obtained
And V, it issues and wraps as application to be synchronized.
It is this take longest common path by way of, both ensure that succeeding target environment to application publication packet history send out
The complete playback of cloth version in turn ensures the application publication packet that will not repeat playback identical version, to improve Cross-environment
Using publication synchronous efficiency.
Certainly, as another embodiment, when getting each application example of the subsystem in the source environment
History released version path after, the history released version path of each application example that can not also be will acquire carry out duplicate removal,
Merging treatment, but after the current version for getting each application example of the subsystem in the target environment, directly
In the history released version path of each application example got, using the current version as starting point, after the starting point
History released version path as the corresponding version to be released of each application example of the subsystem in the target environment
Path.
For example, the history released version path of the application example J of above-mentioned source environment S1 are as follows: V1- > V2- > Vm- > Vn- > V is answered
With the history released version path of example K are as follows: V1- > V2- > V1- > Vm- > Vn- > V (wherein V1 repeats to issue), it is assumed that target ring
There are two application example M and N by border S1, and version is respectively Vm, Vn, then directly in the history released version path of application example J
Using Vm as starting point, take history released version path Vn- > V after Vm as version road to be released corresponding with application example M
Diameter similarly takes the history released version road after Vn using Vn as starting point directly in the history released version path of application example K
Diameter V is as version path to be released corresponding with application example N.
Thought of the above two mode based on increment synchronization is that the increment of succeeding target environment subsystem application example upgrades
(i.e. source, environmentally all versions publication of the S1 since the current version of S1 in target environment all plays back one in target environment
It is secondary with realize increment upgrade) provide premise.
It should be noted that compared to incremental mode, the application under general mode synchronizes publication, due to being that a direct step will
Each application example of the subsystem in target environment upgrades to the current version of source environment, therefore speed is faster, required network
Flow is less；But it for the application that certain versions in source environment and target environment have big difference, generally requires by them
Between the version that differs carry out increment upgrading, can guarantee using smoothly latest edition is upgraded to, therefore, with incremental mode into
The synchronous publication of row application can guarantee that the application in target environment can accurately and smoothly be upgraded to latest edition.Specific implementation
When, user can flexible choice release model be according to actual needs general mode or incremental mode.
Step S40 is obtained and is issued the corresponding publication template instances of packet with the application to be synchronized, will be described to be synchronized
Preset target environment is submitted to using publication packet and the publication template instances, so that the target environment generates corresponding answer
With publication operation.
So-called issue mould plate refers to needing a series of operating procedure, for example divide when being carried out on AOMP using publication
Give out a contract for a project, execute deployment script, include version etc., these steps form a cured template, can be in multiple publication repeatedly
It uses；And issue mould plate example, it refers to issuing the example that can all clone issue mould plate every time.Example and template are repaired
Changing will not interact.
In the step, obtains and issue the corresponding publication template instances of packet with above-mentioned application to be synchronized, it then will be to be synchronized
Application publication wrap corresponding with its publication template instances and submit to preset target environment together so that target environment generation pair
The application publication operation answered.
Specifically, described that the application publication packet to be synchronized and the publication template instances are submitted into preset target
The step of environment may include: to be added after being associated with the application publication packet to be synchronized with the publication template instances to default
Publishing queue；The application programming interface for periodically calling the target environment, by described in the publishing queue to
Synchronous application publication packet and the publication template instances submit to preset target environment.
By taking above-mentioned application to be synchronized publication packet Vn and V as an example, due to the version path to be released of above application example M
For Vn- > V, the version path to be released of application example N is V, it is assumed that getting corresponding publication template instances is Tvn and Tv, then
S1-M-Vn (Tvn) -> V (Tv), S1-N-V (Tv) are obtained after the two is associated with, by S1-M-Vn (Tvn) -> V (Tv), S1-N-V
(Tv) publishing queue of AOMP is added, then the application programming interface of regular invocation target environment, by the publishing queue
In application to be synchronized publication packet and publication template instances submit to preset target environment.It should be noted that when publication
While publishing queue is added in template instances, it can also be synchronized to target environment by template instances are issued with automatic trigger, it is specific real
Shi Shike is with flexible setting.
Target environment is automatically generated according to the publication template instances received and application to be synchronized publication packet using hair
Cloth operation, the operation are the complete playback that source environment corresponds to operation, and in addition to executing machine and environmental variance, remaining is matched
Set, data it is almost the same.If it is general mode, only one step of the operation of generation, i.e. S1-V-Tv is (to S1 subsystem
All machines issue packet using the application of this publication template instances publication V version of Tv)；If it is incremental mode, the work of generation
Each version of each machine of industry has a step, such as above-mentioned Incremental Route, to be released due to above application example M
Version path is Vn- > V, and the version path to be released of application example N is V, therefore the operation that target environment generates has following 3
A step:
1) S1-M-Vn-Tvn is (to M machine the answering using this publication template instances publication Vn version of Tvn of S1 subsystem
It is wrapped with publication)；
2) S1-M-V-Tv (uses the application of this publication template instances publication V version of Tv to send out in the M machine of S1 subsystem
Cloth bag)；
3) S1-N-V-Tv (uses the application of this publication template instances publication V version of Tv to send out in the N machine of S1 subsystem
Cloth bag).
Above-mentioned application publication operation executes in target environment automatically according to corresponding publication template instances, until all
It is completed using publication job execution.
In the present embodiment, source environment is real by obtaining application publication packet to be synchronized and corresponding publication template automatically
Example, and submit to target environment automatically and issued, whole process is operated without manpower intervention, is issued between packet without calculating
Delta file, so that the application automatic synchronization that the present embodiment realizes Cross-environment is issued, while avoiding and expending more meter
Calculate resource.
Further, it is based on above-mentioned first embodiment, proposes the application publication second embodiment of the method for the present invention Cross-environment.
It in the present embodiment, can also include: that the application publication obtained in the target environment is made after above-mentioned steps S40
The execution state is written into preset issue record table the execution state of industry；Issue record table described in poll judges institute
It states in issue record table with the presence or absence of in the record for being not carried out completion status；If it exists, then it is periodically asked to the target environment
It asks with described in the current execution state for recording corresponding application publication operation for being not carried out completion status, and will be described current
Execution state is written back in the issue record table, until there is no be in be not carried out completion status in the issue record table
Record.
In the present embodiment, the execution state of the application publication operation in the available target environment of source environment, and will hold
Row state is written into preset issue record table, later, can judge the issue record table with the periodic polling issue record table
In with the presence or absence of in being not carried out the record of completion status, and if it exists, then periodically request to be in described to the target environment
Be not carried out completion status records the current execution state of corresponding application publication operation, and the current execution state is written back to
In issue record table, until there is no in the record for being not carried out completion status in issue record table.Finally, in each Cross-environment
Application publication after the completion of, will record this publication subsystem, machine, used publication template instances, issue packet version
Information is stored to issue record table to database.
Further, described that the current execution state is written back in the issue record table, until the publication is remembered
After the step of in record table there is no in the record for being not carried out completion status, can also include:
All release informations that the issue record table records in preset duration are summarized, to generate publication report
Table；The front end that the publication report is sent to the source environment is shown.
It, can (such as in the past 1 day, past 1 week etc.) owns in preset duration by issue record table in the present embodiment
Release information is summarized, and to generate publication report, is then shown the front end that the publication report is sent to source environment, such as
This issues situation convenient for the application of front end operation maintenance personnel timely learning Cross-environment.
Further, the above embodiments are based on, propose the application publication 3rd embodiment of the method for the present invention Cross-environment.
In the present embodiment, described to issue in a certain subsystem of source environment in application, judging that the subsystem is
It can also include: the configuration management database in the source environment before no the step of meeting preset Cross-environment issue rules
The automatic synchronization of the middle setting subsystem issues switch；When receive based on the automatic synchronization publication switch triggering unlatching
When instruction, display one includes the selective listing of general mode and incremental mode；Receive the selection triggered based on the selective listing
Release model corresponding with the subsystem is arranged according to the selection instruction in instruction.
By taking subsystem S1 as an example, the present embodiment is provided with one based on subsystem in the configuration management database CMDB of source environment
The automatic synchronization of system S1 issues switch, when receiving the open command based on automatic synchronization publication switch triggering, display one
Selective listing comprising general mode and incremental mode, when the selection instruction for receiving user and being triggered based on the selective listing
When, i.e., release model corresponding with subsystem S1 is arranged according to the selection instruction is general mode or incremental mode.Certainly, except son
Outside system S1, the automatic synchronization publication switch of other subsystems is additionally provided in configuration management database CMDB, user can root
The automatic synchronization publication switch of different sub-systems is opened or closed according to actual needs, and difference is selected based on different subsystems
Release model.In this way, the flexibility of release model selection is improved.
It should be noted that Environmental Support two kinds of Cross-environments in source apply release model, one is real-time modes, i.e., only right
The subsystem that single user specifies executes the application publication of Cross-environment, for example only executes Cross-environment to above-mentioned subsystem S1 and answer
With publication；Another is full dose mode, it can all subsystems in a key trigger source environment execute Cross-environment automatically
Using publication, such case apply in general to the generally existing difference in version of the subsystem for including in source environment and target environment compared with
Big situation.Still support the general mode and incremental mode of subsystem, such as a part of subsystem using general under full dose mode
Logical mode, a part of subsystem use incremental mode, and for each subsystem, the application issue logic of Cross-environment is with real-time mould
Formula is consistent；In addition, when judging whether subsystem meets preset Cross-environment issue rules under full dose mode, it can be using serial
Mode, for example first judge whether subsystem S1 meets preset Cross-environment issue rules, then judge whether subsystem S2 meets
Preset Cross-environment issue rules ..., and so on, it can so reduce the pressure of target environment.When it is implemented, source environment
The selection function using release model of Cross-environment can be provided, so that user is according to actual needs in real-time mode and full dose mould
Flexible choice is carried out between formula.
Distributing device is applied the present invention also provides a kind of Cross-environment.Cross-environment of the present invention includes: using distributing device
Judgment module, for working as the publication in a certain subsystem of source environment in application, judging whether the subsystem is full
The preset Cross-environment issue rules of foot；
First acquisition module obtains answering for publication if meeting preset Cross-environment issue rules for the subsystem
With version and preset release model corresponding with the subsystem；
Second obtains module, for obtaining application to be synchronized according to the application version of the publication and the release model
Publication packet；
Submit module, for obtaining publication template instances corresponding with the application to be synchronized publication packet, by described in
Synchronous application publication packet and the publication template instances submit to preset target environment, so that target environment generation pair
The application publication operation answered.
Further, described second module is obtained further include:
First acquisition unit, for obtaining the application version with the publication when the release model is general mode
Corresponding application publication packet, issues as application to be synchronized and wraps；
Second acquisition unit, for obtaining the subsystem in the target when the release model is incremental mode
Each application example in environment；According to preset rules, calculate and each application example of the subsystem in the target environment
Corresponding version path to be released；Obtain application publication corresponding with the application version for including in the version path to be released
Packet is issued as application to be synchronized and is wrapped.
Further, the second acquisition unit is also used to:
Obtain the history released version path of each application example of the subsystem in the source environment；
Duplicate removal is carried out to the history released version path of each application example of the subsystem in the source environment, is merged
Processing, obtains a longest common path；
Obtain the current version of each application example of the subsystem in the target environment；
In the longest common path, using the current version as starting point, by the history release after the starting point
This path is as the corresponding version path to be released of each application example of the subsystem in the target environment.
Further, the judgment module is also used to:
When publication in a certain subsystem in source environment in application, detecting the subsystem owning in the source environment
Whether the version of application example is consistent, if unanimously, determining that the subsystem meets preset Cross-environment issue rules；
Alternatively, when issuing in a certain subsystem of source environment in application, detecting the subsystem in the source environment
The version of application example whether changed, if the version of any application example of the subsystem in the source environment
It is changed, then determines that the subsystem meets preset Cross-environment issue rules.
Further, the application distributing device of the Cross-environment further include:
Execution state writing module, for obtaining the execution state of the publication operation of the application in the target environment,
The execution state is written into preset issue record table；
Poller module, for issue record table described in poll, judging, which whether there is to be in the issue record table, is not held
The record of row completion status；
Execution state write-back module, if for existing in the issue record table in the record for being not carried out completion status,
It then periodically requests to issue working as operation in the corresponding application that records for being not carried out completion status with described to the target environment
Preceding execution state, and the current execution state is written back in the issue record table, until in the issue record table not
In the presence of in the record for being not carried out completion status.
Further, the application distributing device of the Cross-environment further include:
Issue report generation module, for by the issue record table recorded in preset duration it is all release news into
Row summarizes, to generate publication report；
Sending module, the front end for the publication report to be sent to the source environment are shown.
Further, the submission module is also used to:
It is added after the application publication packet to be synchronized is associated with the publication template instances to preset publishing queue；
The application programming interface for periodically calling the target environment, will be described to be synchronized in the publishing queue
Application publication packet and the publication template instances submit to preset target environment.
Further, the application distributing device of the Cross-environment further include:
Setup module, the automatic synchronization for the subsystem to be arranged in the configuration management database of the source environment are sent out
Cloth switch；
Display module, for showing one when receiving the open command based on automatic synchronization publication switch triggering
Selective listing comprising general mode and incremental mode；
Receiving module is arranged for receiving the selection instruction based on selective listing triggering according to the selection instruction
Release model corresponding with the subsystem.
Concrete operations performed by above-mentioned each program module can refer to the application dissemination method embodiment of Cross-environment of the present invention,
Details are not described herein again.
The present invention also provides a kind of storage mediums.
The release process of applying of Cross-environment is stored on storage medium of the present invention, the Cross-environment applies release process quilt
Processor realizes the step of application dissemination method of Cross-environment as described above when executing.
Wherein, the Cross-environment run on the processor is performed realized method using release process and can join
The each embodiment of dissemination method is applied according to Cross-environment of the present invention, details are not described herein again.
It should be noted that, in this document, the terms "include", "comprise" or its any other variant are intended to non-row
His property includes, so that the process, method, article or the system that include a series of elements not only include those elements, and
And further include other elements that are not explicitly listed, or further include for this process, method, article or system institute it is intrinsic
Element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that including being somebody's turn to do
There is also other identical elements in the process, method of element, article or system.
The serial number of the above embodiments of the invention is only for description, does not represent the advantages or disadvantages of the embodiments.
Through the above description of the embodiments, those skilled in the art can be understood that above-described embodiment side
Method can be realized by means of software and necessary general hardware platform, naturally it is also possible to by hardware, but in many cases
The former is more preferably embodiment.Based on this understanding, technical solution of the present invention substantially in other words does the prior art
The part contributed out can be embodied in the form of software products, which is stored in one as described above
In storage medium (such as ROM/RAM, magnetic disk, CD), including some instructions are used so that terminal device (it can be mobile phone,
Computer, server, air conditioner or network equipment etc.) execute method described in each embodiment of the present invention.
The above is only a preferred embodiment of the present invention, is not intended to limit the scope of the invention, all to utilize this hair
Equivalent structure or equivalent flow shift made by bright specification and accompanying drawing content is applied directly or indirectly in other relevant skills
Art field, is included within the scope of the present invention.
Claims (13)
1. a kind of Cross-environment applies dissemination method, which is characterized in that the application dissemination method of the Cross-environment includes following step
It is rapid:
When publication in a certain subsystem in source environment in application, judging whether the subsystem meets preset Cross-environment publication
Rule；
If so, obtaining the application version and preset release model corresponding with the subsystem of publication；
Application publication packet to be synchronized is obtained according to the application version of the publication and the release model；
Obtain publication template instances corresponding with the application to be synchronized publication packet, the application to be synchronized is issued wrap with
The publication template instances submit to preset target environment, so that the target environment generates corresponding application and issues operation.
2. Cross-environment as described in claim 1 applies dissemination method, which is characterized in that the application according to the publication
Version and the release model obtain the step of packet is issued in application to be synchronized
When the release model is general mode, application publication packet corresponding with the application version of the publication is obtained, as
Application publication packet to be synchronized；
When the release model is incremental mode, each application example of the subsystem in the target environment is obtained；
According to preset rules, version to be released corresponding with each application example of the subsystem in the target environment is calculated
Path；
Application publication packet corresponding with the application version for including in the version path to be released is obtained, as application to be synchronized
Publication packet.
3. Cross-environment as claimed in claim 2 applies dissemination method, which is characterized in that it is described according to preset rules, it calculates
The step of version path to be released corresponding with each application example of the subsystem in the target environment includes:
Obtain the history released version path of each application example of the subsystem in the source environment；
To the subsystem at the history released version path of each application example in source environment progress duplicate removal, merging
Reason, obtains a longest common path；
Obtain the current version of each application example of the subsystem in the target environment；
In the longest common path, using the current version as starting point, by the history released version road after the starting point
Diameter is as the corresponding version path to be released of each application example of the subsystem in the target environment.
4. Cross-environment as claimed any one in claims 1 to 3 applies dissemination method, which is characterized in that described when in source
Publication is in application, the step of whether subsystem meets preset Cross-environment issue rules judged in a certain subsystem of environment
Include:
When in a certain subsystem in source environment publication in application, detecting all applications of the subsystem in the source environment
Whether the version of example is consistent, if unanimously, determining that the subsystem meets preset Cross-environment issue rules；
Alternatively, when issuing in a certain subsystem of source environment in application, detecting the subsystem answering in the source environment
Whether changed with the version of example, if the version of any application example of the subsystem in the source environment occurs
Change, then determine that the subsystem meets preset Cross-environment issue rules.
5. Cross-environment as claimed any one in claims 1 to 3 applies dissemination method, which is characterized in that the Cross-environment
Apply dissemination method further include:
The execution state for obtaining the application publication operation in the target environment, the execution state is written to preset
In issue record table；
Issue record table described in poll judges in the issue record table with the presence or absence of in the record for being not carried out completion status；
If it exists, then it periodically requests to send out with described in the corresponding application that records for being not carried out completion status to the target environment
The current execution state of cloth operation, and the current execution state is written back in the issue record table, until the publication
There is no in the record for being not carried out completion status in record sheet.
6. Cross-environment as claimed in claim 5 applies dissemination method, which is characterized in that described by the current execution state
It is written back in the issue record table, until there is no the steps in the record for being not carried out completion status in the issue record table
After rapid, further includes:
All release informations that the issue record table records in preset duration are summarized, to generate publication report；
The front end that the publication report is sent to the source environment is shown.
7. Cross-environment as claimed any one in claims 1 to 3 applies dissemination method, which is characterized in that it is described will be described
Application publication to be synchronized wraps the step of submitting to preset target environment with the publication template instances and includes:
It is added after the application publication packet to be synchronized is associated with the publication template instances to preset publishing queue；
The application programming interface for periodically calling the target environment to be synchronized answers described in the publishing queue
Preset target environment is submitted to publication packet and the publication template instances.
8. Cross-environment as claimed any one in claims 1 to 3 applies dissemination method, which is characterized in that described when in source
Publication is in application, the step of whether subsystem meets preset Cross-environment issue rules judged in a certain subsystem of environment
Before, further includes:
The automatic synchronization publication switch of the subsystem is set in the configuration management database of the source environment；
When receiving the open command based on automatic synchronization publication switch triggering, display one includes general mode and increment
The selective listing of mode；
The selection instruction triggered based on the selective listing is received, is arranged according to the selection instruction corresponding with the subsystem
Release model.
9. a kind of Cross-environment applies distributing device, which is characterized in that the Cross-environment includes: using distributing device
Judgment module, for when in a certain subsystem of source environment publication in application, to judge whether the subsystem meets pre-
If Cross-environment issue rules；
First acquisition module obtains the application version of publication if meeting preset Cross-environment issue rules for the subsystem
Sheet and preset release model corresponding with the subsystem；
Second obtains module, issues for obtaining application to be synchronized according to the application version of the publication and the release model
Packet；
Module is submitted, issues the corresponding publication template instances of packet with the application to be synchronized for obtaining, it will be described to be synchronized
Application publication packet and the publication template instances submit to preset target environment so that the target environment generation it is corresponding
Using publication operation.
10. Cross-environment as claimed in claim 9 applies distributing device, which is characterized in that the second acquisition module is also wrapped
It includes:
First acquisition unit, for obtaining corresponding with the application version of the publication when the release model is general mode
Application publication packet, as application to be synchronized issue wrap；
Second acquisition unit, for obtaining the subsystem in the target environment when the release model is incremental mode
In each application example；According to preset rules, calculate corresponding with each application example of the subsystem in the target environment
Version path to be released；Application publication packet corresponding with the application version for including in the version path to be released is obtained, is made
It issues and wraps for application to be synchronized.
11. Cross-environment as claimed in claim 10 applies distributing device, which is characterized in that the second acquisition unit is also used
In:
Obtain the history released version path of each application example of the subsystem in the source environment；
To the subsystem at the history released version path of each application example in source environment progress duplicate removal, merging
Reason, obtains a longest common path；
Obtain the current version of each application example of the subsystem in the target environment；
In the longest common path, using the current version as starting point, by the history released version road after the starting point
Diameter is as the corresponding version path to be released of each application example of the subsystem in the target environment.
12. a kind of Cross-environment applies distribution apparatus, which is characterized in that the Cross-environment includes: storage using distribution apparatus
Device, processor and the application release process for being stored in the Cross-environment that can be run on the memory and on the processor, institute
That states Cross-environment realizes such as transannular described in any item of the claim 1 to 8 when being executed using release process by the processor
The step of application dissemination method in border.
13. a kind of storage medium, which is characterized in that the release process of applying of Cross-environment is stored on the storage medium, it is described
Cross-environment realizes answering such as Cross-environment described in any item of the claim 1 to 8 when being executed by processor using release process
The step of with dissemination method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811617268.4A CN109739539B (en) | 2018-12-27 | 2018-12-27 | Cross-environment application release method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811617268.4A CN109739539B (en) | 2018-12-27 | 2018-12-27 | Cross-environment application release method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109739539A true CN109739539A (en) | 2019-05-10 |
| CN109739539B CN109739539B (en) | 2021-10-19 |
Family
ID=66361622
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811617268.4A Active CN109739539B (en) | 2018-12-27 | 2018-12-27 | Cross-environment application release method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109739539B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110941446A (en) * | 2019-11-06 | 2020-03-31 | 苏宁云计算有限公司 | Version release method and device based on multi-environment offline task |
| CN111796863A (en) * | 2020-07-10 | 2020-10-20 | 四川中电启明星信息技术有限公司 | Cross-environment project version management method |
| CN112650815A (en) * | 2021-01-19 | 2021-04-13 | 青岛海尔科技有限公司 | Method and device for synchronizing environmental data, storage medium and electronic device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100325622A1 (en) * | 2007-12-13 | 2010-12-23 | Derek Morton | Updating Firmware of an Electronic Device |
| CN104991791A (en) * | 2015-06-09 | 2015-10-21 | 北京奇虎科技有限公司 | Incremental quantity upgrade release method and apparatus of file |
| CN104991790A (en) * | 2015-06-09 | 2015-10-21 | 北京奇虎科技有限公司 | Upgrade release method and apparatus of file |
| CN105867941A (en) * | 2016-04-18 | 2016-08-17 | 深圳市永兴元科技有限公司 | Software upgrading system and realization method thereof |
| CN107463362A (en) * | 2016-06-03 | 2017-12-12 | 北京京东尚科信息技术有限公司 | The method and system of lasting deployment based on multiple Jenkins |
| CN107870772A (en) * | 2017-10-09 | 2018-04-03 | 深圳前海微众银行股份有限公司 | Application dispositions method, platform, system and the readable storage medium storing program for executing of Cross-environment |
-
2018
- 2018-12-27 CN CN201811617268.4A patent/CN109739539B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100325622A1 (en) * | 2007-12-13 | 2010-12-23 | Derek Morton | Updating Firmware of an Electronic Device |
| CN104991791A (en) * | 2015-06-09 | 2015-10-21 | 北京奇虎科技有限公司 | Incremental quantity upgrade release method and apparatus of file |
| CN104991790A (en) * | 2015-06-09 | 2015-10-21 | 北京奇虎科技有限公司 | Upgrade release method and apparatus of file |
| CN105867941A (en) * | 2016-04-18 | 2016-08-17 | 深圳市永兴元科技有限公司 | Software upgrading system and realization method thereof |
| CN107463362A (en) * | 2016-06-03 | 2017-12-12 | 北京京东尚科信息技术有限公司 | The method and system of lasting deployment based on multiple Jenkins |
| CN107870772A (en) * | 2017-10-09 | 2018-04-03 | 深圳前海微众银行股份有限公司 | Application dispositions method, platform, system and the readable storage medium storing program for executing of Cross-environment |
Non-Patent Citations (2)
| Title |
|---|
| TIJS VAN DER STORM: "Lightweight incremental application upgrade", 《SOFTWARE ENGINEERING SEN》 * |
| 张宇杰: "基于Android平台的智能手机多包连续升级技术改进与实现", 《中国优秀博硕学位论文全文数据库(硕士) 信息科技辑》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110941446A (en) * | 2019-11-06 | 2020-03-31 | 苏宁云计算有限公司 | Version release method and device based on multi-environment offline task |
| CN111796863A (en) * | 2020-07-10 | 2020-10-20 | 四川中电启明星信息技术有限公司 | Cross-environment project version management method |
| CN111796863B (en) * | 2020-07-10 | 2024-04-05 | 四川中电启明星信息技术有限公司 | Cross-environment project version management method |
| CN112650815A (en) * | 2021-01-19 | 2021-04-13 | 青岛海尔科技有限公司 | Method and device for synchronizing environmental data, storage medium and electronic device |
| CN112650815B (en) * | 2021-01-19 | 2023-06-16 | 青岛海尔科技有限公司 | Method and device for synchronizing environment data, storage medium and electronic device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109739539B (en) | 2021-10-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105164644B (en) | Hook frame | |
| CN110222036B (en) | Method and system for automated database migration | |
| EP3387528B1 (en) | Updating dependent services | |
| CN107193607B (en) | Method and apparatus for updating code file, storage medium, processor, and terminal | |
| US9658846B2 (en) | Software configuration control wherein containers are associated with physical storage of software application versions in a software production landscape | |
| CN109739539A (en) | Application dissemination method, device, equipment and the storage medium of Cross-environment | |
| CN109240716B (en) | Big data platform version management and rapid iterative deployment method and system | |
| CN110727575B (en) | Information processing method, system, device and storage medium | |
| CN110007946B (en) | Method, device, equipment and medium for updating algorithm model | |
| CN113505520A (en) | Method, device and system for supporting heterogeneous federated learning | |
| CN115454869A (en) | Interface automation test method, device, equipment and storage medium | |
| CN110968331A (en) | Method and device for running application program | |
| CN112379963A (en) | Remote application window control method and device and computer equipment | |
| CN116257438A (en) | Updating method of interface test case and related equipment | |
| EP2196901A1 (en) | Systems and methods for tracking software stands in a software production landscape | |
| Uyeno et al. | PASSIM: a discrete-event simulation package for PASCAL | |
| US20070185929A1 (en) | Method and apparatus for processing monitoring | |
| CN112559124A (en) | Model management system and target operation instruction processing method and device | |
| CN110752964A (en) | Network equipment testing method and device | |
| CN115454870A (en) | Method, device, equipment and storage medium for intelligently debugging flutter application program | |
| CN114895916A (en) | Code deployment method, device, storage medium and electronic equipment | |
| CN114153480A (en) | Code synchronization method, component publishing method, device thereof and computer storage medium | |
| CN113535558A (en) | Software version transmission method and device | |
| CN113326052A (en) | Method and device for upgrading service component, computer equipment and storage medium | |
| WO2020138386A1 (en) | Cooperative simulation repeater employing previous trace data |
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 |