CN112134948A - Component publishing synchronization method, system, device and storage medium - Google Patents
Component publishing synchronization method, system, device and storage medium Download PDFInfo
- Publication number
- CN112134948A CN112134948A CN202010997707.XA CN202010997707A CN112134948A CN 112134948 A CN112134948 A CN 112134948A CN 202010997707 A CN202010997707 A CN 202010997707A CN 112134948 A CN112134948 A CN 112134948A
- Authority
- CN
- China
- Prior art keywords
- component
- synchronization
- issuing
- party
- fetching
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a method, a system, equipment and a storage medium for synchronizing component release, wherein the method comprises the following steps: acquiring a component issuing request submitted by an issuing party, wherein the component issuing request comprises a fetching party list; issuing the component to a sharing server according to the component issuing request; sending the component issuing information to the fetching party in the fetching party list; acquiring a component synchronization request submitted by a fetching party, wherein the component synchronization request comprises synchronization branch information; and synchronizing the components in the shared server to the corresponding synchronization branches. By adopting the invention, the automatic issuing synchronization of the components can be realized only by acquiring the component issuing request and the component synchronization request, so that the management of the components is more automatic and reasonable, the project can be more controllable while the time is saved, thereby solving the problem of component use in the project management process in the prior art and meeting the requirements of different projects on universal or customized components.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a method, a system, a device, and a storage medium for synchronizing component distribution.
Background
With the development of science and technology, the diversity of projects and the complexity of software systems, a complex system is divided into a plurality of components, and the boundaries and responsibilities of the components are separated. The separated components are more convenient to upgrade and maintain independently, but the problem brought by the separated components is the matching problem between component issuing and component taking.
The components tend to be both generic and custom for different practical needs. The general component needs to inform all project teams using the component every time the component is changed, but whether the team is taken at the present stage or not needs to be determined according to specific situations; each time a customized component is changed, it need only notify the relevant team using the component. And the efficiency of manual release access of components has apparently failed to meet the needs of current project management. The existing automatic synchronization mode of the distributed components and the like have certain risks in the controllability of projects, and are not suitable for most development modes.
Disclosure of Invention
The present invention provides a method, a system, a device and a storage medium for synchronizing component issuance, which can realize automatic issuance synchronization of components only by acquiring a component issuance request and a component synchronization request.
The embodiment of the invention provides a component publishing synchronization method, which comprises the following steps:
acquiring a component issuing request submitted by an issuing party, wherein the component issuing request comprises a fetching party list;
issuing the component to a sharing server according to the component issuing request;
sending the component issuing information to the fetching party in the fetching party list;
acquiring a component synchronization request submitted by a fetching party, wherein the component synchronization request comprises synchronization branch information;
and synchronizing the components in the shared server to the corresponding synchronization branches.
Optionally, the publishing the component to the shared server according to the component publishing request includes:
determining the position of a code warehouse where the component code is located and compiling platform information according to the component issuing request;
and triggering an automatic construction task of the component, wherein the automatic construction task is configured to acquire the component code from the corresponding code warehouse position, automatically construct the component to be issued on the compiling platform, and store the file of the component and the compiling log file to the sharing server.
Optionally, the publishing the component to the shared server according to the component publishing request further includes:
acquiring component release information of the component after the component is constructed and released, and generating a component release file, wherein the component release file comprises released component information and a component release path;
and submitting the component release file to a svn file repository.
Optionally, the sending the component issuing information to each fetching party in the fetching party list includes the following steps:
sending a component synchronization request link to each fetching party in the fetching party list, wherein the synchronization request link is configured to jump to a component synchronization application form after clicking, the component synchronization application form displays component release information, and the component release information comprises released component information and optional synchronization branch information.
Optionally, the obtaining of the component synchronization request submitted by the fetching party includes the following steps:
acquiring components and synchronous branches needing to be synchronized, which are selected by a taking party in a component synchronous application form;
determining an approver of the synchronous branch according to the synchronous branch;
sending a synchronous component approval notice to a terminal of an approval staff to obtain an approval result of the approval staff;
and if the approval result is that the approval is passed, synchronizing the components in the shared server to the synchronization branch selected by the fetching party.
Optionally, synchronizing the component in the shared server to the synchronization branch includes:
storing a component synchronization file in an svn file warehouse, and acquiring the version number of the component synchronization file, wherein the component synchronization file comprises component information selected by a fetching party in a component synchronization application form, and the selected component information comprises specific file information contained in the component;
and transmitting the version number of the component synchronization file into a component synchronization task and triggering the component synchronization task, wherein the component synchronization task is configured to search the component synchronization file in an svn file warehouse and synchronize the file of the component in the shared server to the synchronization branch according to the component synchronization file.
Optionally, the component synchronization task is configured to synchronize the component in the shared server to the synchronization branch by:
obtaining the latest code of the synchronous directory of the synchronous branch from a code warehouse;
synchronizing files of components in the shared server into the synchronization branch;
uploading the synchronized code of the synchronized directory of the synchronized branch to the code repository.
Optionally, the component synchronization task is configured to synchronize the component in the shared server to the synchronization branch by:
when receiving a component synchronization requirement corresponding to a new synchronization branch, judging whether the number of synchronization branches bound under a current component synchronization task is greater than a preset threshold value;
if so, the component synchronization requirements of the new synchronization branch are switched to another component synchronization task execution.
By adopting the component issuing synchronization method, the automatic issuing synchronization of the components can be realized only by acquiring the component issuing request and the component synchronization request, so that the management of the components is more automatic and reasonable, the project can be more controllable while the time is saved, the problem of component use in the project management process in the prior art is solved, and the requirements of different projects on universal or customized components can be met.
The embodiment of the invention also provides a component release synchronization system, which is applied to the component release synchronization method, and the system comprises:
the device comprises a first receiving module, a second receiving module and a sending module, wherein the first receiving module is used for acquiring a component issuing request submitted by an issuing party, and the component issuing request comprises a fetching party list;
the component issuing module is used for issuing the components to the sharing server according to the component issuing request;
the issuing notification module is used for sending the component issuing information to the fetching party in the fetching party list;
the second receiving module is used for acquiring a component synchronization request submitted by a fetching party, wherein the component synchronization request comprises synchronization branch information;
and the component synchronization module is used for synchronizing the components in the shared server to the corresponding synchronization branches.
By adopting the component issuing synchronization system, the automatic issuing synchronization of the components can be realized only by acquiring the component issuing request and the component synchronization request, so that the management of the components is more automatic and reasonable, the project can be more controllable while the time is saved, the problem of component use in the project management process in the prior art is solved, and the requirements of different projects on universal or customized components can be met.
An embodiment of the present invention further provides a device for synchronizing component distribution, including:
a processor;
a memory having stored therein executable instructions of the processor;
wherein the processor is configured to perform the steps of the component issue synchronization method via execution of the executable instructions.
By adopting the component issuing synchronization device provided by the invention, the processor executes the component issuing synchronization method when executing the executable instruction, thereby obtaining the beneficial effect of the component issuing synchronization method.
The embodiment of the invention also provides a computer-readable storage medium for storing a program, and the program realizes the steps of the component release synchronization method when being executed.
By adopting the computer-readable storage medium provided by the invention, the stored program realizes the steps of the component publishing synchronization method when being executed, thereby the beneficial effects of the component publishing synchronization method can be obtained.
Drawings
Other features, objects and advantages of the present invention will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, with reference to the accompanying drawings.
FIG. 1 is a flow diagram of a component publication synchronization method according to one embodiment of the invention;
FIG. 2 is a schematic diagram of a component publication synchronization system in accordance with an embodiment of the invention;
FIG. 3 is a flow diagram for automatically building components and component publishing in accordance with an embodiment of the present invention;
FIG. 4 is a flow diagram of component synchronization approval in accordance with an embodiment of the present invention;
FIG. 5 is a block diagram of a component publication synchronization apparatus according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a computer storage medium according to an embodiment of the present invention.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar structures, and thus their repetitive description will be omitted.
As shown in fig. 1, in an embodiment, the component publishing synchronization method includes the following steps:
s100: acquiring a component publishing request submitted by a publisher;
the component publishing request comprises a fetching party list, wherein the fetching party list comprises fetching party information, and a component publishing object can be determined through the fetching party list;
s200: issuing the component to a sharing server according to the component issuing request;
s300: sending the component issuing information to the fetching party in the fetching party list;
s400: acquiring a component synchronization request submitted by a fetching party, wherein the component synchronization request comprises synchronization branch information;
s500: and synchronizing the components in the shared server to the corresponding synchronization branches.
By adopting the component issuing synchronization method, firstly, the automatic issuing of the component based on the component issuing request of the issuing party is realized through the steps S100-S300, and then the automatic synchronization of the component based on the component synchronization request of the taking party can be realized through the steps S400 and S500, so that the automatic issuing synchronization of the component can be realized only by acquiring the component issuing request and the component synchronization request, the management of the component is more automatic and reasonable, the project can be more controllable while the time is saved, the problem of component use in the project management process in the prior art is solved, and the requirements of different projects on universal or customized components can be met.
As shown in fig. 2, an embodiment of the present invention further provides a component publishing synchronization system, which is applied to the component publishing synchronization method, and the system includes:
a first receiving module M100, configured to obtain a component issuing request submitted by an issuer, where the component issuing request includes a fetching party list;
the component publishing module M200 is configured to publish the component to the shared server according to the component publishing request;
the issuing notification module M300 is used for sending the component issuing information to the fetching party in the fetching party list;
a second receiving module M400, configured to obtain a component synchronization request submitted by a fetching party, where the component synchronization request includes synchronization branch information;
a component synchronization module M500, configured to synchronize the components in the shared server to the corresponding synchronization branches.
By adopting the component issuing synchronization method of the invention, the automatic issuing of the component based on the component issuing request of the issuing party is realized through the first receiving module M100, the component issuing module M200 and the issuing notification module M300, and the automatic synchronization of the component based on the component synchronization request of the taking party can be realized through the second receiving module M400 and the component synchronization module M500, so that the automatic issuing synchronization of the component can be realized only by acquiring the component issuing request and the component synchronization request, the management of the component is more automatic and reasonable, the project can be more controllable while the time is saved, the problem of component use in the project management process in the prior art is solved, and the requirements of different projects on universal or customized components can be met.
In this embodiment, the publisher is typically a component development and maintenance person, who can submit the component publishing request after completing the component development and submitting the component code into the code repository according to the actual requirements, such as the customized requirements of the component, bug resolution, etc. The component publishing request may further include a warehouse location where the component code is located, corresponding compiling platform information, component information, a reason for applying for publishing, and the like.
Specifically, in step S100, when the publisher initiates the component publishing request, the repository-branch-compiling platform where the component is located may be selected in the form of filling the component publishing request form in the platform interface of the component publishing synchronization system, so as to locate the component name that actually needs to be constructed and published; the reason for the component release is written and the person list of the fetching party is chosen to be filled out. It should be noted that some components need to be tested and verified again before being released, and selection can be performed on the interface, in this case, after the component is constructed, only the person who applies for the release is notified, and after the developer tests and verifies, the developer can apply for the component release alone.
As shown in fig. 3, in this embodiment, the step S200 includes the following steps:
s210: determining the position of a code warehouse where the component code is located and compiling platform information according to the component issuing request;
s220: triggering an automatic construction task of the component, automatically constructing the component to be issued, and storing a file of the component and a compiling log file to a shared server;
specifically, the automatic construction task is configured to obtain the latest component code from the corresponding code warehouse location, and automatically construct the component to be released on the compiling platform.
Here, triggering the automatic construction task may be triggering jenkins jobs. The component information, the code warehouse position, the compiling platform information and the like in the component issuing request can be automatically acquired from the configuration of jenkins jobthrough the script at regular time based on jenkins interface functions. And automatically matching the corresponding jenkins jobs in the background according to the information in the component issuing request, transmitting parameters required by component construction to the jenkins jobs through a jenkins jobtrigger command, and automatically triggering construction of the corresponding components. After the component is built, if the building is successful, the file of the component and the compiling log file are stored in the sharing server, if the building is failed, the compiling log file is stored in the sharing server, the subsequent step of automatic release is not continued, and a release party can be informed to solve the building problem as soon as possible through a mode such as an email.
Therefore, the invention obtains the components through the automatic construction of the component codes, does not need manual operation construction of the publisher, improves the efficiency of component publishing, and can be better suitable for the rapid publishing of the components in batches.
As shown in fig. 3, in this embodiment, the step S200: publishing the component to the shared server according to the component publishing request, further comprising:
s230: and acquiring the component release information of the component after the component is constructed and released, and generating a component release file.
The component release file comprises released component information and a component release path, and specifically, the component release file also comprises a component release application form number and a construction result;
specifically, deploying a script on a slave client (i.e., a compiler) connected to a jenkins joba, and collecting relevant information after the publishing component is built, including: the method comprises the following steps of issuing an application form number by a component, the name of the component, the branch name of a warehouse, the version number of a branch, a construction result, a component issuing path and the like. And after the information is collected, the format of the installation protocol is written to the component release file.
S240: and submitting the component release file to a svn file repository.
Specifically, the file is submitted to the svn file repository through the svn tool. The svn is an abbreviation of subversion, is an open source code version control system, can be used for multiple persons to jointly develop the same project by adopting efficient management of a branch management system, realizes resource sharing and realizes final centralized management. The svn file repository is a data repository which can realize version control management of the component release files.
And simultaneously, detecting the state of the svn file warehouse at one end of the platform server of the component publishing and synchronizing system at regular time, analyzing and splitting the obtained new component publishing file once the file warehouse is detected to have new file submission, and storing the component information into a database of the platform server of the component publishing and synchronizing system.
In the embodiment, the data transmission between the client and the component publishing synchronization system platform server uses an svn tool, and the svn is used as a code management tool, so that the security of code management can be improved.
In this embodiment, the step S300: sending component publishing information to each fetching party in the fetching party list, comprising the steps of:
sending a component synchronization request link to each fetching party in the fetching party list, wherein the synchronization request link is configured to jump to a component synchronization application form after clicking, the component synchronization application form displays component release information, and the component release information comprises component information and optional synchronization branch information.
The invention is convenient for the user to quickly trigger and fill in the synchronous application form of the component by a link mode. In other alternative embodiments, besides entering the synchronous application page through the link, the synchronous application page may also be entered directly through the component publishing synchronous system platform, at this time, only the publishing path of the publishing component needs to be input, and the subsequent operation is consistent with the entering through the link. In order to ensure information security, the link needs to display specific component information after logging in, that is, only members in the access party list have permission to apply for related component synchronization.
In this embodiment, the component publishing information may further include: applying for a publisher, a publishing reason, a publishing path, a publishing component platform and a component name. The triggering of the component issuing the information to the accessing party can be realized, for example, by a mailbox server, according to a predefined mail template, or in other ways.
Since the publishing and fetching of components is more often a many-to-many relationship, i.e., one component may be used by multiple branches/items, and one branch/item may use multiple components. Therefore, after receiving the component synchronization request link corresponding to the component release information, the fetching party clicks the link to enter a component synchronization application interface, and a component application form is displayed in the component application interface, wherein a component release path, a release component name, a branch with synchronization requirements, a reason for applying synchronization, files specifically contained in the component, paths of the files and the like are displayed. The access party can select the required components and synchronization object branches on the synchronization application sheet according to the actual conditions of the project. The interface of the synchronous application form is dynamically generated according to the condition of the publishing component. And screening is carried out according to the component information used by the synchronous branch, and only the component information used by the branch is displayed.
After the synchronization branch is selected, detailed information of the publishing component used by the selected synchronization branch can be filtered, such as a header file and a library file contained in each component, a specific taking path of the component, a relative path of synchronization and the like; in addition, a mail notifier can be filled in, namely, the related personnel are notified about the synchronous message of the time.
In this embodiment, after the synchronous application form of the fetching party is submitted, the final approval confirmation is required to be performed by the approver of the branch/project, so as to ensure the accuracy of the fetching component. As shown in fig. 4, in this embodiment, the step S400: the method for acquiring the component synchronization request submitted by the accessing party comprises the following steps:
s410: acquiring components and synchronous branches needing to be synchronized, which are selected by a taking party in a component synchronous application form;
s420: determining an approver of the synchronous branch according to the synchronous branch;
s430: sending a synchronous component approval notice to a terminal of an approval staff to obtain an approval result of the approval staff;
specifically, the approver receives the reminding message of synchronous approval of the components and the approval agency page at the page of the component publishing and synchronizing system and the mail side at the same time, and selects the 'approve' or 'reject' button to approve.
S440: if the approval result is approval pass, the step S500 is continued: synchronizing components in the shared server to a synchronization branch selected by the fetching party;
s450: and if the approval result is that the approval is not passed, ending the current process.
Therefore, the automatic approval process is added in the component taking synchronization, so that the controllability of the project is further improved, and the development process of the project is better controlled.
In this embodiment, the step S500: synchronizing components in the shared server to the synchronization branch, comprising the steps of:
and storing the component synchronization file in an svn file warehouse, and acquiring the version number of the component synchronization file, wherein the component synchronization file comprises component information selected by a fetching party in a component synchronization application form, and the selected component information comprises specific file information contained in the component.
Specifically, the component information of the publishing component used by the synchronization branch has been previously collated and stored in the component publishing synchronization system platform server database. After the synchronous application form is successfully submitted, the component synchronization information of the components in the application form is written into a component synchronization file and is submitted to a svn file warehouse, wherein the component synchronization file comprises an id number for identifying each component (the id number of the component is used for distinguishing each component from other components), component information, namely file information contained in each component, a relative release path corresponding to each file, a relative synchronization path and the like.
And transmitting the release branch information, the release path, the synchronization branch information, the component synchronization file name and the version number of the component synchronization file into a component synchronization task and triggering the component synchronization task, wherein the component synchronization task is configured to search the component synchronization file in an svn file warehouse, and acquire and synchronize files in the components in the shared server one by one below the path corresponding to the synchronization branch according to the analysis of the component synchronization file.
After the synchronization is completed, a submission log is automatically generated, and the source of the component and the reason of the synchronization are written in the log. And then submitting the codes of the synchronous directory of the synchronous branch after local synchronization to a code warehouse, and notifying related mail notifiers by mails. Therefore, corresponding log information can be provided for each time of issuing and taking of the component, and the component information can be traced clearly.
In this embodiment, the component synchronization task may also be referred to the configured synchronization job through a trigger command of the jenkins job, and is implemented through the construction of the jenkins job. Therefore, automatic execution of the component synchronization task can be realized, manual operation of workers is not needed, the component synchronization efficiency can be improved, and the component synchronization accuracy is ensured.
In this embodiment, the component synchronization task is configured to synchronize the component in the shared server to the synchronization branch by:
obtaining the latest code of the synchronous directory of the synchronous branch from a code warehouse;
specifically, whether a synchronization path of the synchronization branch exists locally is judged, if not, the latest code of the synchronization directory of the synchronization branch is downloaded from a code warehouse (only the directory with the synchronization requirement is downloaded here), and if so, the synchronization directory of the local synchronization branch is directly updated;
synchronizing files of components in the shared server into the synchronization branch;
and uploading the codes of the synchronous directories of the synchronized branches to the code warehouse so as to update the codes of the synchronous directories of the corresponding synchronized branches in the code warehouse.
In this embodiment, the component synchronization task further adopts processing logic of load balancing, that is, when synchronizing the component in the shared server to the synchronization branch, the following steps are further performed:
when the component issuing synchronization system platform receives a component synchronization demand corresponding to a new synchronization branch, judging whether the number of synchronization branches bound under a current component synchronization task is greater than a preset threshold value, wherein each component synchronization demand refers to an operation demand for synchronizing one component to one synchronization branch;
if so, switching the component synchronization requirement of the new synchronization branch to another component synchronization task for execution, namely binding the new synchronization branch with another component synchronization task, and executing the subsequently received component synchronization requirement of the synchronization branch by the corresponding bound component synchronization task;
if not, the component synchronization requirement corresponding to the new synchronization branch can still be executed by the current component synchronization task.
The embodiment of the invention also provides a device for synchronizing the component release, which comprises a processor; a memory having stored therein executable instructions of the processor; wherein the processor is configured to perform the steps of the component issue synchronization method via execution of the executable instructions.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 600 according to this embodiment of the invention is described below with reference to fig. 5. The electronic device 600 shown in fig. 5 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 5, the electronic device 600 is embodied in the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 that connects the various system components (including the storage unit 620 and the processing unit 610), a display unit 640, and the like.
Wherein the storage unit stores program code executable by the processing unit 610 to cause the processing unit 610 to perform steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription flow processing method section of the present specification. For example, the processing unit 610 may perform the steps as shown in fig. 1.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)6201 and/or a cache memory unit 6202, and may further include a read-only memory unit (ROM) 6203.
The memory unit 620 may also include a program/utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 600 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 via the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
By adopting the component issuing synchronization device provided by the invention, the processor executes the component issuing synchronization method when executing the executable instruction, thereby obtaining the beneficial effect of the component issuing synchronization method.
The embodiment of the invention also provides a computer-readable storage medium for storing a program, and the program realizes the steps of the component release synchronization method when being executed. In some possible embodiments, aspects of the present invention may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the steps according to various exemplary embodiments of the present invention described in the above-mentioned electronic prescription flow processing method section of this specification, when the program product is run on the terminal device.
Referring to fig. 6, a program product 800 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or cluster. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
By adopting the computer-readable storage medium provided by the invention, the stored program realizes the steps of the component publishing synchronization method when being executed, thereby the beneficial effects of the component publishing synchronization method can be obtained.
The foregoing is a more detailed description of the invention in connection with specific preferred embodiments and it is not intended that the invention be limited to these specific details. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (11)
1. A component publishing synchronization method, comprising the steps of:
acquiring a component issuing request submitted by an issuing party, wherein the component issuing request comprises a fetching party list;
issuing the component to a sharing server according to the component issuing request;
sending the component issuing information to the fetching party in the fetching party list;
acquiring a component synchronization request submitted by a fetching party, wherein the component synchronization request comprises synchronization branch information;
and synchronizing the components in the shared server to the corresponding synchronization branches.
2. The component publishing synchronization method according to claim 1, wherein the component is published to a shared server according to the component publishing request, comprising the steps of:
determining the position of a code warehouse where the component code is located and compiling platform information according to the component issuing request;
and triggering an automatic construction task of the component, wherein the automatic construction task is configured to acquire the component code from the corresponding code warehouse position, automatically construct the component to be issued on the compiling platform, and store the file of the component and the compiling log file to the sharing server.
3. The component publication synchronization method according to claim 2, wherein the publishing of the component to the shared server according to the component publication request further comprises the steps of:
acquiring component release information of the component after the component is constructed and released, and generating a component release file, wherein the component release file comprises released component information and a component release path;
and submitting the component release file to a svn file repository.
4. The component publication synchronization method according to claim 1, wherein the sending of component publication information to each of the fetching parties in the list of fetching parties comprises the steps of:
sending a component synchronization request link to each fetching party in the fetching party list, wherein the synchronization request link is configured to jump to a component synchronization application form after clicking, the component synchronization application form displays component release information, and the component release information comprises component information and optional synchronization branch information.
5. The component publishing synchronization method according to claim 4, wherein the step of obtaining the component synchronization request submitted by the accessing party comprises the steps of:
acquiring components and synchronous branches needing to be synchronized, which are selected by a taking party in a component synchronous application form;
determining an approver of the synchronous branch according to the synchronous branch;
sending a synchronous component approval notice to a terminal of an approval staff to obtain an approval result of the approval staff;
and if the approval result is that the approval is passed, synchronizing the components in the shared server to the synchronization branch selected by the fetching party.
6. The component publication synchronization method according to claim 1, wherein synchronizing the components in the shared server to the synchronization branch comprises the steps of:
storing a component synchronization file in an svn file warehouse, and acquiring the version number of the component synchronization file, wherein the component synchronization file comprises component information selected by a fetching party in a component synchronization application form, and the selected component information comprises specific file information contained in the component;
and transmitting the version number of the component synchronization file into a component synchronization task and triggering the component synchronization task, wherein the component synchronization task is configured to search the component synchronization file in an svn file warehouse and synchronize the components in the shared server to the synchronization branch according to the component synchronization file.
7. The component publication synchronization method of claim 6, wherein the component synchronization task is configured to synchronize the component in the shared server to the synchronization branch by:
obtaining the latest code of the synchronous directory of the synchronous branch from a code warehouse;
synchronizing files of components in the shared server into the synchronization branch;
uploading the synchronized code of the synchronized directory of the synchronized branch to the code repository.
8. The component publication synchronization method of claim 6, wherein the component synchronization task is configured to synchronize the component in the shared server to the synchronization branch by:
when receiving a component synchronization requirement corresponding to a new synchronization branch, judging whether the number of synchronization branches bound under a current component synchronization task is greater than a preset threshold value;
if so, the component synchronization requirements of the new synchronization branch are switched to another component synchronization task execution.
9. A component release synchronization system applied to the component release synchronization method according to any one of claims 1 to 8, the system comprising:
the device comprises a first receiving module, a second receiving module and a sending module, wherein the first receiving module is used for acquiring a component issuing request submitted by an issuing party, and the component issuing request comprises a fetching party list;
the component issuing module is used for issuing the components to the sharing server according to the component issuing request;
the issuing notification module is used for sending the component issuing information to the fetching party in the fetching party list;
the second receiving module is used for acquiring a component synchronization request submitted by a fetching party, wherein the component synchronization request comprises synchronization branch information;
and the component synchronization module is used for synchronizing the components in the shared server to the corresponding synchronization branches.
10. A component publication synchronization apparatus, comprising:
a processor;
a memory having stored therein executable instructions of the processor;
wherein the processor is configured to perform the steps of the component publication synchronization method of any of claims 1 to 8 via execution of the executable instructions.
11. A computer readable storage medium storing a program, wherein the program when executed implements the steps of the component publication synchronization method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010997707.XA CN112134948B (en) | 2020-09-21 | 2020-09-21 | Component release synchronization method, system, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010997707.XA CN112134948B (en) | 2020-09-21 | 2020-09-21 | Component release synchronization method, system, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112134948A true CN112134948A (en) | 2020-12-25 |
| CN112134948B CN112134948B (en) | 2023-05-02 |
Family
ID=73841926
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010997707.XA Active CN112134948B (en) | 2020-09-21 | 2020-09-21 | Component release synchronization method, system, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112134948B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112817623A (en) * | 2021-01-26 | 2021-05-18 | 北京自如信息科技有限公司 | Method and device for publishing application program, mobile terminal and readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105094851A (en) * | 2015-09-06 | 2015-11-25 | 浪潮软件股份有限公司 | Method for momentarily issuing codes based on Git |
| CN105302533A (en) * | 2014-07-25 | 2016-02-03 | 腾讯科技（深圳）有限公司 | Code synchronizing method and apparatus |
| CN107193607A (en) * | 2017-05-26 | 2017-09-22 | 网易（杭州）网络有限公司 | Method and apparatus, storage medium, processor and terminal for updating code file |
| CN110018857A (en) * | 2018-01-05 | 2019-07-16 | 武汉斗鱼网络科技有限公司 | Application component Hua Zhong branch automatic management method, storage medium, device and method |
| CN110855735A (en) * | 2019-09-20 | 2020-02-28 | 广州亚美信息科技有限公司 | Project publishing method, device and system and computer equipment |
-
2020
- 2020-09-21 CN CN202010997707.XA patent/CN112134948B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302533A (en) * | 2014-07-25 | 2016-02-03 | 腾讯科技（深圳）有限公司 | Code synchronizing method and apparatus |
| CN105094851A (en) * | 2015-09-06 | 2015-11-25 | 浪潮软件股份有限公司 | Method for momentarily issuing codes based on Git |
| CN107193607A (en) * | 2017-05-26 | 2017-09-22 | 网易（杭州）网络有限公司 | Method and apparatus, storage medium, processor and terminal for updating code file |
| CN110018857A (en) * | 2018-01-05 | 2019-07-16 | 武汉斗鱼网络科技有限公司 | Application component Hua Zhong branch automatic management method, storage medium, device and method |
| CN110855735A (en) * | 2019-09-20 | 2020-02-28 | 广州亚美信息科技有限公司 | Project publishing method, device and system and computer equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112817623A (en) * | 2021-01-26 | 2021-05-18 | 北京自如信息科技有限公司 | Method and device for publishing application program, mobile terminal and readable storage medium |
| CN112817623B (en) * | 2021-01-26 | 2021-10-08 | 北京自如信息科技有限公司 | Method and device for publishing application program, mobile terminal and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112134948B (en) | 2023-05-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210240604A1 (en) | Api driven continuous testing systems for testing disparate software | |
| CN109358858B (en) | Automatic deployment method, device, medium and electronic equipment | |
| US9311064B1 (en) | Systems and methods for automated centralized build/merge management | |
| US8984489B2 (en) | Quality on submit process | |
| US8924935B1 (en) | Predictive model of automated fix handling | |
| CN106815031B (en) | Kernel module loading method and device | |
| US8234660B2 (en) | Method and apparatus for a support platform | |
| US8713554B1 (en) | Automated hotfix handling model | |
| KR20070120095A (en) | Method and apparatus for providing process guidance | |
| US9971573B2 (en) | Computing platform and method thereof for searching, executing, and evaluating computational algorithms | |
| CN114461269A (en) | Software development release management method, device, equipment and storage medium | |
| CN111679851A (en) | Demand code management method, apparatus, system and computer readable storage medium | |
| CN111367531A (en) | Code processing method and device | |
| CN112134948B (en) | Component release synchronization method, system, equipment and storage medium | |
| US8245182B2 (en) | Class selectable design sharing | |
| US11893383B2 (en) | Configuration properties management for software | |
| US20180285085A1 (en) | Customer Information Control System (CICS) Services Deployment System | |
| US11113105B1 (en) | Computer implemented system and method for generating platform agnostic digital worker | |
| CN113918525A (en) | Data exchange scheduling method, system, electronic device, medium, and program product | |
| US11048479B2 (en) | Software conversion simulation mode | |
| Harper et al. | Deploying healthcare simulation models using containerization and continuous integration | |
| CN114610327B (en) | Automatic publishing and deploying method, device, medium and computer equipment | |
| US10977210B2 (en) | Methods for implementing an administration and testing tool | |
| CN115022317B (en) | Cloud platform-based application management method and device, electronic equipment and storage medium | |
| CN107818048B (en) | Computer code branch integrated quality inspection method and related equipment |
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 |