A design method and system for publishing components based on pipeline mode

By using the assembly line method during the release of the component, pull the remote code warehouse and build branches, solve the problem of not being submitted to the version library before the component release, and realize the stability and consistency of the component publishing.

CN114237561BActive Publication Date: 2025-01-24CHINA CITIC BANK CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202111500324.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-09
Publication Date
2025-01-24
Estimated Expiration
2041-12-09

AI Technical Summary

Technical Problem

In the prior art, components have been published but the code has not been submitted to the repository, which affects the stability and consistency of components during the release process.

Method used

Publish components based on a pipeline -based method, create and upload component assembly lines by constructing a server, pull the remote code warehouse in the assembly line, switch the branch to be constructed, and then compile, pack, and upload to ensure that the uploaded components are consistent with the remote code.

Benefits of technology

Publish components through the assembly line to ensure that the published components are built with remote branches, thereby ensuring the stability and consistency of the publishing component.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114237561B_ABST
    Figure CN114237561B_ABST
Patent Text Reader

Abstract

The present invention discloses a design method and system for publishing components based on an assembly line, and relates to the field of automatic program design. The method comprises: pushing developed code information to a remote code repository, and performing version control management on the developed code information based on a version management tool; based on a build server, a production-side development terminal creates an assembly line; based on the assembly line, the code after version control management is written, pulled, compiled, and packaged to generate code component information of the developed code information; the code component information is pushed to a product warehouse for storage, and a first pull instruction is generated; according to the first pull instruction, the consumer-side development terminal pulls the code component information from the product warehouse for use. The method solves the technical problem that the components in the prior art have been released, but the codes have not been submitted to the version library for version control management, which greatly affects the stability and consistency of the components during the release process.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of automatic program design, and in particular to a design method and system for publishing components in an assembly line manner. Background Art

[0002] During the software development process, components are published on the development terminal by using project management tool commands. Currently, components are published based on project types. For example, Maven type projects are published on the development terminal using the mvn deploy command, and npm type projects are published on the development terminal using the npm publish command.

[0003] However, the inventors of this application found that the above technology has at least the following technical problems in the process of implementing the technical solution of the invention in the embodiment of this application:

[0004] The existing technology has the problem that the component has been released, but the code has not been submitted to the version library for version control management, which greatly affects the stability and consistency of the component during the release process. Summary of the invention

[0005] The embodiment of the present application provides a design method and system for publishing components in a pipeline-based manner, which solves the technical problem in the prior art that components have been published but the codes have not been submitted to the version library for version control management, which greatly affects the stability and consistency of the components during the publishing process. The embodiment of the present application achieves the technical effect of using a build server to create and upload a component pipeline, pull a remote code repository in the pipeline, switch the branch to be built, and then compile, package, and upload it to ensure that the uploaded component is consistent with the remote code, and ensure that the published component is built using a remote branch, thereby ensuring the stability and consistency of the published component.

[0006] In view of the above problems, the present invention is proposed to provide a method to overcome the above problems or at least partially solve the above problems.

[0007] In the first aspect, an embodiment of the present application provides a design method for publishing components based on a pipeline, the method comprising: obtaining developed code information of a production development terminal; pushing the developed code information to a remote code repository, and performing version control management on the developed code information based on a version management tool; based on a build server, the production development terminal creates a pipeline; based on the pipeline, writing, pulling, compiling, and packaging the code after the version control management to generate code component information of the developed code information; pushing the code component information to a product warehouse for storage, and generating a first pull instruction; according to the first pull instruction, the consumer development terminal pulls the code component information from the product warehouse for use.

[0008] On the other hand, the present application also provides a design system for publishing components based on a pipeline method, and the system includes: a first acquisition unit, the first acquisition unit is used to obtain the developed code information of the producer development terminal; a first management unit, the first management unit is used to push the developed code information to a remote code repository, and perform version control management on the developed code information based on a version management tool; a first creation unit, the first creation unit is used to create a pipeline by the producer development terminal based on a build server; a first generation unit, the first generation unit is used to write, pull, compile, and package the code after the version control management based on the pipeline, and generate code component information of the developed code information; a second generation unit, the second generation unit is used to push the code component information to a product warehouse for storage, and generate a first pull instruction; a first pull unit, the first pull unit is used for the consumer development terminal to pull the code component information from the product warehouse for use according to the first pull instruction.

[0009] In a third aspect, an embodiment of the present invention provides an electronic device, comprising a bus, a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the transceiver, the memory, and the processor are connected via the bus, and the computer program, when executed by the processor, implements the steps in any one of the above-described methods for controlling output data.

[0010] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps in any one of the above-mentioned methods for controlling output data.

[0011] One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

[0012] The method adopts the following steps: obtaining the developed code information of the production party's development terminal; pushing the developed code information to a remote code repository, and performing version control management on the developed code information based on a version management tool; based on a build server, the production party's development terminal creates a pipeline; based on the pipeline, the code after the version control management is written, pulled, compiled, and packaged to generate code component information of the developed code information; pushing the code component information to a product warehouse for storage, and generating a first pull instruction; according to the first pull instruction, the consumer party's development terminal pulls the code component information from the product warehouse for use. Thus, the technical effect of using a build server to create and upload a component pipeline, pulling a remote code repository in the pipeline, switching the branch to be built, and then compiling, packaging, and uploading is achieved to ensure that the uploaded component is consistent with the remote code, and that the released component is built using a remote branch, thereby ensuring the stability and consistency of the released component.

[0013] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 A schematic diagram of a flow chart of a design method for publishing components in an assembly line manner according to an embodiment of the present application;

[0015] Figure 2 A schematic diagram of a process of creating a pipeline by a production development terminal in a design method for publishing components in a pipeline-based manner according to an embodiment of the present application;

[0016] Figure 3 A schematic diagram of a process of uploading encrypted values ​​and code component information to a product warehouse in a design method for publishing components in a pipeline manner according to an embodiment of the present application;

[0017] Figure 4 This is a schematic diagram of the structure of a design system for publishing components in an assembly line manner according to an embodiment of the present application;

[0018] Figure 5 A schematic diagram of the structure of an electronic device for executing a method for controlling output data provided in an embodiment of the present application.

[0019] Explanation of the figure marks: first obtaining unit 11, first management unit 12, first creating unit 13, first generating unit 14, second generating unit 15, first pulling unit 16, bus 1110, processor 1120, transceiver 1130, bus interface 1140, memory 1150, operating system 1151, application 1152 and user interface 1160. DETAILED DESCRIPTION

[0020] In the description of the embodiments of the present invention, those skilled in the art should know that the embodiments of the present invention can be implemented as methods, devices, electronic devices and computer-readable storage media. Therefore, the embodiments of the present invention can be specifically implemented in the following forms: complete hardware, complete software (including firmware, resident software, microcode, etc.), a combination of hardware and software. In addition, in some embodiments, the embodiments of the present invention can also be implemented in the form of a computer program product in one or more computer-readable storage media, and the computer-readable storage medium contains computer program code.

[0021] The above-mentioned computer-readable storage medium may adopt any combination of one or more computer-readable storage media. Computer-readable storage media include: electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or devices, or any combination of the above. More specific examples of computer-readable storage media include: portable computer disks, hard disks, random access memories, read-only memories, erasable programmable read-only memories, flash memories, optical fibers, optical disc read-only memories, optical storage devices, magnetic storage devices or any combination of the above. In an embodiment of the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, device, or device.

[0022] Application Overview

[0023] The embodiments of the present invention describe the provided methods, devices, and electronic devices through flowcharts and / or block diagrams.

[0024] It should be understood that each box in the flowchart and / or block diagram and the combination of boxes in the flowchart and / or block diagram can be implemented by computer-readable program instructions. These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, and these computer-readable program instructions are executed by a computer or other programmable data processing device to produce a device that implements the functions / operations specified by the boxes in the flowchart and / or block diagram.

[0025] These computer-readable program instructions may also be stored in a computer-readable storage medium that enables a computer or other programmable data processing device to work in a specific manner. In this way, the instructions stored in the computer-readable storage medium produce an instruction device product including functions / operations specified in the blocks in the flowchart and / or block diagram.

[0026] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby enabling the instructions executed on the computer or other programmable data processing apparatus to provide a process for implementing the functions / operations specified in the blocks in the flowchart and / or block diagram.

[0027] The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0028] Embodiment 1

[0029] like Figure 1 As shown, an embodiment of the present application provides a design method for publishing components based on a pipeline manner, wherein the method includes:

[0030] Step S100: obtaining the developed code information of the production side development terminal;

[0031] Step S200: Pushing the developed code information to a remote code repository, and performing version control management on the developed code information based on a version management tool;

[0032] Specifically, during the software development process, the producer completes the development work at the terminal, submits the completed developed code information and pushes the code to the remote code repository, which is the code repository on the server. Based on the version management tool, the developed code information is version controlled and managed. If the code before modification cannot be viewed, it is very difficult to find code problems. If there is a software that can record all modifications and all versions of the document, this type of software is generally called a version control tool. The version management tool generally has the following characteristics: it can record historical versions and roll back historical versions; it can be used for team development and facilitate code merging.

[0033] Step S300: Based on the construction server, the production party develops a terminal to create a pipeline;

[0034] like Figure 2 As shown, further, based on the construction server, the production party develops the terminal to create the pipeline, and step S300 of the embodiment of the present application also includes:

[0035] Step S310: Setting pipeline parameter information and pipeline environment variable information;

[0036] Step S320: Based on the version management tool, the developed code information in the remote code repository is cloned to the workspace of the build server to generate cloned code information.

[0037] Specifically, based on the build server, the production party development terminal creates a pipeline. The build server is a dedicated machine used to build applications. Every time the developer adds new code, the added content will be notified to the build server. The server will correspondingly pull the new code from the code repository, build it from scratch, and run all unit tests. The final result is a clean build containing all the latest codes. The production party creates a pipeline on the build server. The pipeline technology is to decompose a repetitive process into several sub-processes. Each sub-process is implemented by a special functional component. Multiple processing processes are staggered in time and passed through each functional segment in turn. In this way, each sub-process can be carried out in parallel with other sub-processes. Set pipeline parameter information, such as branch name, warehouse information, configuration listening port, container specifications, expansion and contraction conditions, version environment variables, pipeline operation parameters, pipeline environment variable information, such as JDK version, Maven version, Npm version, etc. Based on the version management tool, the developed code information in the remote code repository is cloned to the workspace of the build server to generate clone code information, that is, a copy of the remote code repository is copied to the local, and the developed code information is cloned to achieve a one-to-one correspondence between subsequent component versions and code branches, ensuring that the released components are built using remote branches.

[0038] Step S400: Based on the pipeline, the code after the version control management is written, pulled, compiled, and packaged to generate code component information of the developed code information;

[0039] Specifically, based on the pipeline, the code after the version control management is written, pulled, compiled, and packaged to generate code component information of the developed code information. The code component information is to enable the code to be reused in different applications, reduce the development cycle, and improve utilization. Some frequently used functions are made into a small set, and various organizational methods are specified. This is the code component. An assembly, a link library, or even a class in the code can be called a code component.

[0040] Step S500: pushing the code component information to the product warehouse for storage, and generating a first pull instruction;

[0041] Step S600: According to the first pull instruction, the consumer development terminal pulls the code component information from the product warehouse for use.

[0042] Specifically, the code component information is pushed to the product warehouse for storage. The product warehouse is the output of the build process, including software packages, test reports, application configuration files, etc., which can be directly run on the server or viewable in binary form, usually referred to as binary software products. The acquisition, use, and sharing methods of products generated by different development languages ​​are different. Different product warehouses can manage binary products of their respective development language types. All product packages and dependent components can be included in a unified product library for unified management. The product warehouse should be the only trusted source of products for testing and production deployment. According to the first pull instruction, the consumer development terminal pulls the code component information from the product warehouse for use. A one-to-one correspondence between component versions and code branches is achieved to ensure that the released components are built using remote branches, thereby ensuring the technical effect of stability and consistency of the released components.

[0043] like Figure 3 As shown, further, the embodiment S320 of the present application also includes:

[0044] Step S321: Based on the project management tool, compile, build, and package the cloned code information to generate a component to be released;

[0045] Step S322: Generate an encrypted value for the component to be released based on an encryption algorithm;

[0046] Step S323: Upload the encrypted value and the component to be released to the product warehouse.

[0047] Specifically, based on the project management tool, the cloned code information is compiled, built, and packaged to generate the components to be released. The project management tool is a collection of continuous automation programs, such as installation, upgrade, configuration, and deletion of programs. The use of project management tools can solve many problems for front-end development and improve development efficiency. The project management tools include Maven, Npm, etc. Maven is a cross-platform project management and construction automation tool that covers compilation, testing, packaging, and deployment, and mainly serves the project construction, dependency management, and project information management of the Java platform; Npm is a package manager tool for Node.js, which is a code module shared and packaged by js developers, and a public collection of open source packages for front-end web applications, etc. Npm is also a tool used by command line client developers to install and publish these software packages. Based on the encryption algorithm, an encrypted value is generated for the components to be released. The basic process of data encryption is to process the original plaintext file or data according to a certain algorithm to make it an unreadable section of code as "ciphertext". The encrypted value and the components to be released are uploaded to the product warehouse to achieve the technical effect of protecting the data from being illegally stolen or read by others, thereby ensuring the security of the code data.

[0048] Furthermore, step S330 of the embodiment of the present application further includes:

[0049] Step S334: the version management tool includes but is not limited to GIT / SVN / CVS;

[0050] Step S335: Based on the version management tool, clone the remote code repository and check out the branch.

[0051] Specifically, the version management tools include but are not limited to GIT / SVN / CVS. GIT is a version control tool for Linux kernel development. It adopts a distributed version library approach and does not require server-side software support, making the release and communication of source code extremely convenient. SVN is an open source version control system that adopts a branch management system. Documents, projects, and codes can be placed in the central warehouse of SVN. CVS is a concurrent version system, a mainstream open source network-transparent version control system, used for source code maintenance in a multi-person development environment. Based on the version management tool, the remote code repository is cloned to generate a cloned code repository, that is, a copy of the remote code repository is copied to the local, and a new local repository will be created after cloning. In the warehouse cloning and checkout branch link, the version management tool is used to perform cloning and checkout operations to achieve a one-to-one correspondence between subsequent component versions and code branches, ensuring the technical effect that the released components are built using remote branches.

[0052] Furthermore, based on the encryption algorithm, step S332 of the embodiment of the present application further includes:

[0053] Step S3321: The encryption algorithm includes but is not limited to MD5 / SHA1 / SHA256;

[0054] Step S3322: Generate the encrypted value for the code component information based on the standard hash algorithm of the encryption algorithm.

[0055] Specifically, based on the encryption algorithm, an encrypted value is generated for the code component information, and the encryption algorithm includes but is not limited to MD5 / SHA1 / SHA256. The MD5 encryption algorithm is a secure hash algorithm. Inputting two different plaintexts will not result in the same output value. Based on the output value, the original plaintext cannot be obtained, that is, the process is irreversible. The SHA1 encryption algorithm is a data encryption algorithm. The idea of ​​the algorithm is to accept a piece of plaintext and then convert it into a piece of (generally smaller) ciphertext in an irreversible way. It can also be simply understood as taking a string of input codes (called pre-mapping or information) and converting them into a shorter length, fixed-bit output sequence, namely a hash value (also called a message digest or information authentication code). The SHA256 encryption algorithm is a 256-bit encryption algorithm that encrypts the intermediate hash value by using the message block as a key. It is an algorithm that converts arbitrarily long messages into shorter, fixed-length message digests. Based on the standard hash algorithm of the encryption algorithm, the encrypted value is generated for the code component information, that is, in the component generation stage, an encrypted value is generated for the component using the standard hash algorithm, so as to achieve the technical effect of protecting data from being illegally stolen or read, thereby ensuring the security of code data.

[0056] Furthermore, after the production party develops the terminal to create the pipeline, step S300 of the embodiment of the present application further includes:

[0057] Step S310: obtaining a first trigger mode, wherein the first trigger mode includes: timing trigger, submission trigger, branch merge trigger and manual trigger;

[0058] Step S320: triggering and executing the pipeline according to the first triggering mode.

[0059] Specifically, after the production party develops the terminal to create a pipeline, a first trigger method is obtained to trigger the execution of the pipeline. The first trigger method includes: timed trigger, submission trigger, branch merge trigger and manual trigger. The timed trigger can automatically trigger the execution of the function at a specified time point. The submission trigger uses "submit" to trigger the event and execute the code in the event. The branch merge trigger is the branch merge code operation that triggers the program execution, and the manual trigger is the manual execution of the trigger program. According to the first trigger method, the pipeline is triggered and executed, and the pipeline process is executed to achieve the technical effect of supporting different types of trigger strategies, and the appropriate trigger method can be selected according to the usage scenario to trigger the pipeline operation.

[0060] In summary, the design method and system for publishing components in a pipeline manner provided by the embodiments of the present application have the following technical effects:

[0061] The method adopts the following steps: obtaining the developed code information of the production party's development terminal; pushing the developed code information to a remote code repository, and performing version control management on the developed code information based on a version management tool; based on a build server, the production party's development terminal creates a pipeline; based on the pipeline, the code after the version control management is written, pulled, compiled, and packaged to generate code component information of the developed code information; pushing the code component information to a product warehouse for storage, and generating a first pull instruction; according to the first pull instruction, the consumer party's development terminal pulls the code component information from the product warehouse for use. Thus, the technical effect of using a build server to create and upload a component pipeline, pulling a remote code repository in the pipeline, switching the branch to be built, and then compiling, packaging, and uploading is achieved to ensure that the uploaded component is consistent with the remote code, and that the released component is built using a remote branch, thereby ensuring the stability and consistency of the released component.

[0062] Embodiment 2

[0063] Based on the same inventive concept as the design method for publishing components in an assembly line manner in the aforementioned embodiment, the present invention also provides a design system for publishing components in an assembly line manner, such as Figure 4 As shown, the system comprises:

[0064] A first obtaining unit 11, wherein the first obtaining unit 11 is used to obtain the developed code information of the production side development terminal;

[0065] A first management unit 12, the first management unit 12 is used to push the developed code information to a remote code repository, and perform version control management on the developed code information based on a version management tool;

[0066] A first creation unit 13, the first creation unit 13 is used to create a pipeline based on the construction server and the production party development terminal;

[0067] A first generating unit 14, the first generating unit 14 is used to write, pull, compile, and package the code after the version control management based on the pipeline to generate code component information of the developed code information;

[0068] A second generating unit 15, the second generating unit 15 is used to push the code component information to the product warehouse for storage, and generate a first pull instruction;

[0069] The first pulling unit 16 is used for, according to the first pulling instruction, the consumer development terminal to pull the code component information from the product warehouse for use.

[0070] Furthermore, the system also includes:

[0071] A first setting unit, the first setting unit is used to set pipeline parameter information and pipeline environment variable information;

[0072] The third generating unit is used to clone the developed code information in the remote code repository to the workspace of the build server based on the version management tool to generate cloned code information.

[0073] Furthermore, the system also includes:

[0074] A fourth generating unit, the fourth generating unit is used to compile, build, and package the cloned code information based on a project management tool to generate a component to be released;

[0075] A fifth generating unit, the fifth generating unit being used to generate an encrypted value for the component to be released based on an encryption algorithm;

[0076] A first uploading unit is used to upload the encrypted value and the code component information to the product warehouse.

[0077] Furthermore, the system also includes:

[0078] A second management unit, wherein the second management unit is used for the version management tool including but not limited to GIT / SVN / CVS;

[0079] The first operating unit is used to perform a clone operation and a branch checkout operation on the remote code repository based on the version management tool.

[0080] Furthermore, the system also includes:

[0081] A first encryption unit, wherein the encryption algorithm used by the first encryption unit includes but is not limited to MD5 / SHA1 / SHA256;

[0082] The sixth generation unit is used to generate the encrypted value for the code component information based on a standard hash algorithm of the encryption algorithm.

[0083] Furthermore, the system also includes:

[0084] A second obtaining unit, the second obtaining unit is used to obtain a first trigger mode, the first trigger mode includes: timing trigger, submission trigger, branch merge trigger and manual trigger;

[0085] A first execution unit, wherein the first execution unit is used to trigger and execute the pipeline according to the first trigger mode.

[0086] The foregoing Figure 1 The various variations and specific examples of a design method for publishing components in an assembly line manner in Example 1 are also applicable to a design system for publishing components in an assembly line manner in this embodiment. Through the above detailed description of a design method for publishing components in an assembly line manner, those skilled in the art can clearly know the implementation method of a design system for publishing components in an assembly line manner in this embodiment, so for the sake of brevity of the specification, it will not be described in detail here.

[0087] In addition, an embodiment of the present invention further provides an electronic device, including a bus, a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor. The transceiver, the memory, and the processor are respectively connected via a bus. When the computer program is executed by the processor, each process of the above-mentioned method embodiment for controlling output data is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0088] Exemplary Electronic Devices

[0089] For details, see Figure 5 As shown, an embodiment of the present invention further provides an electronic device, which includes a bus 1110 , a processor 1120 , a transceiver 1130 , a bus interface 1140 , a memory 1150 and a user interface 1160 .

[0090] In the embodiment of the present invention, the electronic device further includes: a computer program stored in the memory 1150 and executable on the processor 1120, and when the computer program is executed by the processor 1120, each process of the above-mentioned method embodiment for controlling output data is implemented.

[0091] The transceiver 1130 is configured to receive and send data under the control of the processor 1120 .

[0092] In an embodiment of the present invention, the bus architecture (represented by bus 1110), bus 1110 may include any number of interconnected buses and bridges, and bus 1110 connects various circuits including one or more processors represented by processor 1120 and a memory represented by memory 1150.

[0093] Bus 1110 represents one or more of any of several types of bus structures, including a memory bus and memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. Such architectures include, by way of example and not limitation, an Industry Standard Architecture bus, a Micro Channel Architecture bus, an expansion bus, a Video Electronics Standards Association, a Peripheral Component Interconnect bus.

[0094] The processor 1120 may be an integrated circuit chip having signal processing capabilities. In the implementation process, each step of the above method embodiment may be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The above processors include: a general-purpose processor, a central processing unit, a network processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, a complex programmable logic device, a programmable logic array, a microcontroller unit or other programmable logic device, a discrete gate, a transistor logic device, and a discrete hardware component. The methods, steps, and logic block diagrams disclosed in the embodiments of the present invention may be implemented or executed. For example, the processor may be a single-core processor or a multi-core processor, and the processor may be integrated into a single chip or located on multiple different chips.

[0095] Processor 1120 may be a microprocessor or any conventional processor. The method steps disclosed in conjunction with the embodiments of the present invention may be directly executed by a hardware decoding processor, or may be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a readable storage medium known in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, a register, etc. The readable storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware.

[0096] The bus 1110 may also connect various other circuits such as peripheral devices, voltage regulators or power management circuits, and the bus interface 1140 provides an interface between the bus 1110 and the transceiver 1130, which are well known in the art. Therefore, the embodiments of the present invention will not be further described.

[0097] The transceiver 1130 may be one element or multiple elements, such as multiple receivers and transmitters, and provides a unit for communicating with various other devices on a transmission medium. For example, the transceiver 1130 receives external data from other devices, and the transceiver 1130 is used to send data processed by the processor 1120 to other devices. Depending on the nature of the computer device, a user interface 1160 may also be provided, such as a touch screen, a physical keyboard, a display, a mouse, a speaker, a microphone, a trackball, a joystick, or a stylus.

[0098] It should be understood that in an embodiment of the present invention, the memory 1150 may further include a memory remotely arranged relative to the processor 1120, and these remotely arranged memories may be connected to the server through a network. One or more parts of the above network may be a self-organizing network, an intranet, an extranet, a virtual private network, a local area network, a wireless local area network, a wide area network, a wireless wide area network, a metropolitan area network, the Internet, a public switched telephone network, a plain old telephone service network, a cellular telephone network, a wireless network, a wireless fidelity network, and a combination of two or more of the above networks. For example, the cellular telephone network and the wireless network may be a global mobile communication device, a code division multiple access device, a global microwave interconnection access device, a general packet radio service device, a wideband code division multiple access device, a long term evolution device, an LTE frequency division duplex device, an LTE time division duplex device, an advanced long term evolution device, a universal mobile communication device, an enhanced mobile broadband device, a massive machine type communication device, an ultra-reliable low latency communication device, etc.

[0099] It should be understood that the memory 1150 in the embodiment of the present invention may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. Among them, the non-volatile memory includes: a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, or a flash memory.

[0100] Volatile memory includes random access memory, which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronously linked dynamic random access memory, and direct memory bus random access memory. The memory 1150 of the electronic device described in the embodiments of the present invention includes but is not limited to the above and any other suitable types of memory.

[0101] In the embodiment of the present invention, the memory 1150 stores the following elements of the operating system 1151 and the application program 1152: executable modules, data structures, or subsets thereof, or extended sets thereof.

[0102] Specifically, the operating system 1151 includes various device programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application 1152 includes various application programs, such as a media player and a browser, which are used to implement various application services. The program for implementing the method of the embodiment of the present invention may be included in the application 1152. The application 1152 includes applets, objects, components, logic, data structures, and other computer device executable instructions that perform specific tasks or implement specific abstract data types.

[0103] In addition, an embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the various processes of the above-mentioned method embodiment for controlling output data are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0104] The above is only a specific implementation of the embodiment of the present invention, but the protection scope of the embodiment of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the embodiment of the present invention, which should be included in the protection scope of the embodiment of the present invention. Therefore, the protection scope of the embodiment of the present invention should be based on the protection scope of the claims.

Claims

1. A design method for publishing components based on a pipeline approach, wherein: The method comprises: Obtain the developed code information of the production side development terminal; Pushing the developed code information to a remote code repository, and performing version control management on the developed code information based on a version management tool; Based on the construction server, the production side development terminal creates a pipeline, wherein based on the construction server, the production side development terminal creates a pipeline, including: Set pipeline parameter information and pipeline environment variable information; Based on the version management tool, the developed code information in the remote code repository is cloned to the workspace of the build server to generate cloned code information; Based on the pipeline, the code after the version control management is written, pulled, compiled, and packaged to generate code component information of the developed code information; Pushing the code component information to a product warehouse for storage, and generating a first pull instruction; According to the first pull instruction, the consumer development terminal pulls the code component information from the product warehouse for use; The method further comprises: Based on the project management tool, compile, build, and package the cloned code information to generate components to be released; Based on the encryption algorithm, an encrypted value is generated for the component to be released; The encrypted value and the component to be released are uploaded to the product warehouse.

2. The method of claim 1, wherein: The method further comprises: The version management tools include but are not limited to GIT / SVN / CVS; Based on the version management tool, clone operations and check-out branch operations are performed on the remote code repository.

3. The method of claim 1, wherein: The encryption-based algorithm includes: The encryption algorithm includes but is not limited to MD5 / SHA1 / SHA256; The encrypted value is generated for the code component information based on a standard hash algorithm of the encryption algorithm.

4. The method of claim 1, wherein: After the production side develops the terminal to create the pipeline, it includes: Obtaining a first trigger mode, wherein the first trigger mode includes: timing trigger, submission trigger, branch merge trigger and manual trigger; According to the first triggering mode, the pipeline is triggered and executed.

5. A design system for publishing components based on a pipeline approach, wherein: The system comprises: A first obtaining unit, the first obtaining unit is used to obtain the developed code information of the production side development terminal; A first management unit, the first management unit is used to push the developed code information to a remote code repository, and perform version control management on the developed code information based on a version management tool; The first creation unit is used to create a pipeline based on the construction server and the production development terminal, wherein the creation of the pipeline based on the construction server and the production development terminal includes: Set pipeline parameter information and pipeline environment variable information; Based on the version management tool, the developed code information in the remote code repository is cloned to the workspace of the build server to generate cloned code information; A first generating unit, the first generating unit is used to write, pull, compile, and package the code after the version control management based on the pipeline, and generate code component information of the developed code information; A second generation unit, the second generation unit is used to push the code component information to a product warehouse for storage, and generate a first pull instruction; A first pulling unit, wherein the first pulling unit is used for the consumer development terminal to pull the code component information from the product warehouse for use according to the first pulling instruction; The system further comprises: Based on the project management tool, compile, build, and package the cloned code information to generate components to be released; Based on the encryption algorithm, an encrypted value is generated for the component to be released; The encrypted value and the component to be released are uploaded to the product warehouse.

6. A design electronic device for releasing components based on a pipeline method, comprising a bus, a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the transceiver, the memory, and the processor are connected via the bus, characterized in that: When the computer program is executed by the processor, the steps in the method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the steps in the method according to any one of claims 1 to 4 are implemented.

Citation Information

Patent Citations

  • Rapid automatic compiling and deploying method based on cloud life cycle management

    CN112035352A