Project delivery method and device, equipment and storage medium

Abstract

The invention provides a project delivery method, device and equipment and a storage medium, which can be applied to the technical fields of proprietary cloud, application software and the like, and comprises the following steps: a management device obtains project information of a target project to be delivered, and downloads a software source component package of the target project from a delivery storage module based on the project information of the target project; based on the N description files of the software source component package, determining a storage address of each software source material in N software source materials corresponding to the target project in a research and development storage module; on the basis of the storage addresses of the N software source materials in the research and development storage module and the project information of the target project, downloading addresses of the N software source materials are generated; and the delivery package of the target project is generated based on the downloading addresses of the software source component and the N software source materials, and the delivery package is stored in the delivery storage module, so that the delivery device downloads the delivery package from the delivery storage module, and the delivery quality of the project is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a project delivery method, apparatus, device, and storage medium. Background Technology

[0002] In the delivery of projects such as private cloud or applications, it is necessary to deliver the projects developed by the R&D team to the customer. Current project delivery methods typically involve R&D personnel storing the software source materials of the project to be delivered in a development storage module. Delivery personnel then copy the software source materials of the project to be delivered from the development storage module and bring them to the delivery site for deployment.

[0003] However, some projects have a large amount of software source material data. When using the current project delivery methods, it is easy to cause data omissions or errors, resulting in low project delivery efficiency and quality. Summary of the Invention

[0004] This application provides a project delivery method, apparatus, equipment, and storage medium that can improve the quality and efficiency of project delivery.

[0005] In a first aspect, this application provides a project delivery method applied to equipment management, the method comprising:

[0006] Obtain the project information of the target project to be delivered, and based on the project information of the target project, download the software source component package of the target project from the delivery storage module. The software source component package includes at least the software source components of the target project and N description files. The description files are used to describe the storage address of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer.

[0007] Based on the N description files, determine the storage address of each software source material in the R&D storage module among the N software source materials corresponding to the target project;

[0008] Based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project, the download addresses of the N software source materials are generated.

[0009] Based on the download addresses of the software source components and the N software source materials, a delivery package for the target project is generated and stored in the delivery storage module, so that the delivery device can download the delivery package from the delivery storage module.

[0010] Secondly, this application provides a project delivery method applied to the delivery of equipment, the method comprising:

[0011] Obtain the project information of the target project to be delivered, and based on the project information, download the delivery package of the target project from the delivery storage module;

[0012] Parse the delivery package to obtain the download addresses of the software source components and N software source materials of the target project;

[0013] Based on the download addresses of the N software source materials, download the N software source materials from the R&D storage module;

[0014] Based on the software source components and the N software source materials, the target project is delivered.

[0015] The delivery package is generated based on the download addresses of the software source components and N software source materials of the target project. The download addresses of the N software source materials are generated based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project. The storage addresses of the N software source materials in the R&D storage module are determined based on the N description files corresponding to the target project. The software source components and the N description files are obtained by parsing the software source component package of the target project. The description files are used to describe the storage addresses of the software source materials corresponding to the target project in the R&D storage module. The software source component package is stored in the delivery storage module.

[0016] Thirdly, this application provides a project delivery device for use in managing equipment, the device comprising:

[0017] An acquisition unit is used to acquire project information of a target project to be delivered, and based on the project information of the target project, download the software source component package of the target project from the delivery storage module. The software source component package includes at least the software source components of the target project and N description files. The description files are used to describe the storage address of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer.

[0018] The address determination unit is used to determine the storage address of each software source material in the R&D storage module based on the N description files.

[0019] The address generation unit is used to generate download addresses for the N software source materials based on their respective storage addresses in the R&D storage module and the project information of the target project.

[0020] The delivery unit is configured to generate a delivery package for the target project based on the download addresses of the software source components and the N software source materials, and store the delivery package in the delivery storage module so that the delivery device can download the delivery package from the delivery storage module.

[0021] In some embodiments, the project information includes the project identifier, delivery time, and authorization token of the target project. The acquisition unit is specifically used to download the software source component package from the delivery storage module based on the project identifier of the target project. The address generation unit is specifically used to generate a download address for the i-th software source material among the N software source materials, based on the storage address of the i-th software source material in the R&D storage module, and the project identifier, delivery time, and authorization token of the target project, where i is a positive integer less than or equal to N.

[0022] In some embodiments, the delivery unit is specifically configured to generate a download script based on the download address of each of the N software source components; generate a delivery package for the target project based on the software source components and the download script; and mark the status of the delivery package as pending delivery.

[0023] In some embodiments, the acquisition unit is further configured to acquire the software source components and N description files of the target project; compile and package the software source components and the N description files to generate the software source component package; set a tag for the software source component package and mark the status of the software source component package as a release status; and store the software source component package with the release status in the delivery storage module.

[0024] In some embodiments, the acquisition unit is specifically configured to: if M new addresses are detected in the first address list corresponding to the target project, acquire the M new addresses, wherein the first address list includes the storage address of the description file corresponding to the target project in the R&D storage module, and M is a positive integer; download M new description files corresponding to the target project from the R&D storage module based on the M addresses; and acquire the software source component from the software source component code library based on the M new description files, and acquire the N description files, wherein the N description files include the M new description files.

[0025] In some embodiments, the acquisition unit is specifically used to write the M new description files into the software source component code library; and to acquire the software source component and the N description files from the software source component code library.

[0026] In some embodiments, the acquisition unit is specifically used to acquire the software source component and NM description files from the software source component code library; and to combine the M new description files and the NM description files to form the N description files.

[0027] In some embodiments, the acquisition unit is further configured to write the M new description files into the software source component code library.

[0028] In some embodiments, the acquisition unit is further configured to: download M new software source materials corresponding to the target project; store the M new software source materials in the R&D storage module to obtain the storage addresses of the M new software source materials in the R&D storage module; generate M new description files based on the storage addresses of the M new software source materials in the R&D storage module; store the M new description files in the R&D storage module to obtain the storage addresses of the M new description files in the R&D storage module; and add the storage addresses of the M new description files in the R&D storage module to the first address list.

[0029] Fourthly, this application provides a project delivery device for use with delivery equipment, the device comprising:

[0030] The acquisition unit is used to acquire project information of the target project to be delivered, and download the delivery package of the target project from the delivery storage module based on the project information;

[0031] The parsing unit is used to parse the delivery package to obtain the download addresses of the software source components and N software source materials of the target project;

[0032] The download unit is used to download N software source materials from the R&D storage module based on the download addresses of the N software source materials;

[0033] The delivery unit is used to complete the delivery of the target project based on the software source components and the N software source materials;

[0034] The delivery package is generated based on the download addresses of the software source components and N software source materials of the target project. The download addresses of the N software source materials are generated based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project. The storage addresses of the N software source materials in the R&D storage module are determined based on the N description files corresponding to the target project. The software source components and the N description files are obtained by parsing the software source component package of the target project. The description files are used to describe the storage addresses of the software source materials corresponding to the target project in the R&D storage module. The software source component package is stored in the delivery storage module.

[0035] In some embodiments, the project information includes the project identifier, delivery time, and authorization token of the target project. The download unit is specifically used to perform address authentication based on the project identifier, delivery time, and authorization token of the target project. After the address authentication is successful, the download unit downloads N software source materials from the R&D storage module based on the download addresses of the N software source materials.

[0036] Fifthly, an electronic device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory to perform the methods described in the first or second aspect and their respective implementations.

[0037] Sixthly, a chip is provided for implementing the methods of either the first or second aspect and their respective implementations. Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the methods of either the first or second aspect and their respective implementations.

[0038] In a seventh aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the methods described in the first or second aspect and their respective implementations.

[0039] Eighthly, a computer program product is provided, including computer program instructions that cause a computer to perform the methods described in the first or second aspect and their respective implementations.

[0040] Ninthly, a computer program is provided that, when run on a computer, causes the computer to perform the methods of the first or second aspect and their respective implementations described above.

[0041] In summary, the management device of this application acquires the project information of the target project to be delivered, and downloads the software source component package of the target project from the delivery storage module based on the project information. The software source component package includes at least the software source components of the target project and N description files. The description files describe the storage addresses of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer. Based on the N description files, the storage address of each of the N software source materials corresponding to the target project in the R&D storage module is determined. Based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project, download addresses of the N software source materials are generated. Based on the software source components and the download addresses of the N software source materials, a delivery package of the target project is generated and stored in the delivery storage module, so that the delivery device can download the delivery package from the delivery storage module. Correspondingly, the delivery device obtains the project information of the target project to be delivered, and based on the project information, downloads the corresponding delivery package of the target project from the delivery storage module; parses the delivery package to obtain the download addresses of the software source components and N software source materials of the target project; based on the download addresses of the N software source materials, downloads the N software source materials from the R&D storage module; and based on the software source components and N software source materials, completes the delivery of the target project. Therefore, this embodiment of the application packages the software source components and software source materials of the target project together, solving the problem of chaotic management of software source materials, preventing omissions or errors of software source materials, and thus improving the project delivery quality. At the same time, this embodiment of the application generates download addresses for software source materials and packages these download addresses with the software source components in the delivery package, allowing different delivery devices to simultaneously download the software source materials from the R&D storage module through these download addresses, eliminating the need for multiple copies, reducing project delivery costs, and improving project delivery efficiency. In other words, this embodiment of the application uses a standard automated process, reducing manual operations, improving delivery efficiency, and ensuring the synchronization and consistency of software source components, delivery projects, and software source materials, reducing the likelihood of errors and omissions, and improving project delivery quality. Attached Figure Description

[0042] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 A schematic diagram of an implementation environment for the project delivery method provided in this application embodiment;

[0044] Figure 2A flowchart illustrating a project delivery method provided in an embodiment of this application;

[0045] Figure 3 A flowchart illustrating a project delivery method provided in an embodiment of this application;

[0046] Figure 4 A schematic diagram illustrating the framework of the project delivery method provided in the embodiments of this application;

[0047] Figure 5 This is a schematic diagram illustrating the software source material transfer process involved in an embodiment of this application;

[0048] Figure 6 This is a schematic diagram of the software source material merging process involved in an embodiment of this application;

[0049] Figure 7 This is a schematic diagram illustrating the software source material packaging process involved in an embodiment of this application;

[0050] Figure 8 This is a schematic block diagram of a project delivery device provided in one embodiment of this application;

[0051] Figure 9 This is a schematic block diagram of a project delivery device provided in one embodiment of this application;

[0052] Figure 10 This is a schematic block diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0053] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0054] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in sequences other than those illustrated or described herein. In embodiments of the invention, "B corresponding to A" means that B is associated with A. In one implementation, B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or devices. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0055] The technical solution proposed in this application can be applied to technical fields such as private cloud and application software, and can improve the delivery quality and efficiency of projects.

[0056] In project delivery, such as delivery to a private cloud or the delivery of applications, it is necessary to deliver the project developed by the R&D team to the customer. Current project delivery methods typically involve R&D personnel storing the software source materials of the project to be delivered in a development storage module, and delivery personnel copying these materials from the development storage module and then bringing them to the delivery site for deployment. However, the data volume of software source materials is often large, such as hundreds of terabytes. Copying via external hard drives, especially when multiple sites are simultaneously delivering, requires multiple external hard drives, resulting in high costs. Furthermore, it introduces manual copying operations, which are time-consuming and prone to errors. Therefore, using the current project delivery method is prone to data omissions or errors, leading to low project delivery efficiency and poor delivery quality.

[0057] To address this technical problem, this application proposes a standardized project delivery method. First, the management device acquires project information for the target project to be delivered. Based on this information, it downloads a software source component package of the target project from the delivery storage module. This package includes at least the software source components of the target project and N description files. The description files describe the storage addresses of the corresponding software source materials in the R&D storage module, where N is a positive integer. Based on the N description files, the storage address of each of the N software source materials corresponding to the target project in the R&D storage module is determined. Based on the storage addresses of the N software source materials in the R&D storage module and the project information, download addresses for the N software source materials are generated. Based on the software source components and the download addresses of the N software source materials, a delivery package for the target project is generated and stored in the delivery storage module, enabling the delivery device to download the delivery package from the delivery storage module. Correspondingly, the delivery device obtains the project information of the target project to be delivered, and based on the project information, downloads the corresponding delivery package of the target project from the delivery storage module; parses the delivery package to obtain the download addresses of the software source components and N software source materials of the target project; based on the download addresses of the N software source materials, downloads the N software source materials from the R&D storage module; and based on the software source components and N software source materials, completes the delivery of the target project. Therefore, this embodiment of the application packages the software source components and software source materials of the target project together, solving the problem of chaotic management of software source materials, preventing omissions or errors of software source materials, and thus improving the project delivery quality. At the same time, this embodiment of the application generates download addresses for software source materials and packages these download addresses with the software source components in the delivery package, allowing different delivery devices to simultaneously download the software source materials from the R&D storage module through these download addresses, eliminating the need for multiple copies, reducing project delivery costs, and improving project delivery efficiency. In other words, this embodiment of the application uses a standard automated process, reducing manual operations, improving delivery efficiency, and ensuring the synchronization and consistency of software source components, delivery projects, and software source materials, reducing the likelihood of errors and omissions, and improving project delivery quality.

[0058] The implementation environment of the project delivery method provided in the embodiments of this application is described below.

[0059] Figure 1 This is a schematic diagram of an implementation environment for the project delivery method provided in this application, including a delivery device 101, a management device 102, a research and development storage module 103, and a delivery storage module 104. The delivery device 101 and the management device 102 can be connected via wired or wireless means. The management device 102 and the delivery storage module 104 can also be connected via wired or wireless means.

[0060] In this embodiment, the R&D storage module 103 stores the software source materials and description text of the target project. The description describes the storage address of the software source materials corresponding to the target project in the R&D storage module. The delivery storage module 104 stores a software source component package and a delivery package. The software source component package is obtained by packaging the software source components and description files of the target project, and the delivery package is obtained by packaging the download addresses of the software source components and software source materials of the target project.

[0061] This application provides a project delivery platform. The delivery device 101 is equipped with a client for the project delivery platform, and the management device 102 can be understood as the backend of the project delivery platform.

[0062] In this embodiment, the object and the delivery device 101 can interact with each other. For example, the object can open a client of the project delivery platform on the delivery device 101 and then input the project information of the target project to be requested on the client. The management device 102 can download the delivery package of the target project from the delivery storage module based on the project information of the target project and then send the delivery package to the delivery device 101.

[0063] In this embodiment, the management device 102 first creates a delivery package. Specifically, the management device 102 obtains the project information of the target project to be delivered, and based on the project information, downloads the software source component package of the target project from the delivery storage module. This software source component package includes at least the software source components of the target project and N description files. The description files describe the storage addresses of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer. Next, based on the aforementioned N description files, the management device 102 determines the storage address of each of the N software source materials corresponding to the target project in the R&D storage module. Then, based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project, it generates download addresses for the N software source materials. Finally, based on the software source components and the download addresses of the N software source materials, the management device 102 generates the delivery package of the target project and stores the delivery package in the delivery storage module, so that the delivery device can download the delivery package from the delivery storage module.

[0064] At the actual project delivery site, delivery device 101 acquires the project information of the target project to be delivered and, based on the project information, downloads the corresponding delivery package for the target project from the delivery storage module. Next, delivery device 101 parses the delivery package to obtain the download addresses of the target project's software source components and N software source materials, and, based on the download addresses of the N software source materials, downloads the N software source materials from the R&D storage module. Finally, delivery device 101 completes the delivery of the target project based on the software source components and N software source materials.

[0065] As described above, this embodiment of the application packages the software source components and software source materials of the target project together, solving the problem of chaotic management of software source materials, preventing omissions or errors, and thus improving the project delivery quality. Simultaneously, this embodiment generates download addresses for the software source materials and packages these download addresses along with the software source components in the delivery package. This allows different delivery devices to simultaneously download the software source materials from the R&D storage module using these download addresses, eliminating the need for multiple copies, reducing project delivery costs, and improving project delivery efficiency. In other words, this embodiment uses a standard automated process, reducing manual operations, improving delivery efficiency, and ensuring the synchronization and consistency of software source components, delivery projects, and software source materials, reducing the likelihood of errors and omissions, and improving project delivery quality.

[0066] This application does not limit the specific type of delivery device 101. In some embodiments, delivery device 101 may include, but is not limited to, terminal devices such as mobile phones, computers, smart voice interaction devices, smart home appliances, vehicle terminals, aircraft, wearable smart devices, and medical devices. Delivery device 101 is often equipped with a display device, which may also be a monitor, display screen, touch screen, etc., and the touch screen may also be a touch screen, touch panel, etc.

[0067] In some embodiments, the management device 102 may be one or more servers. When there are multiple servers, at least two servers may be used to provide different services, and / or at least two servers may be used to provide the same service, such as providing the same service in a load-balanced manner. This application embodiment does not limit this. The aforementioned servers may be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Servers may also become nodes in a blockchain.

[0068] In this embodiment of the application, the delivery device 101 and the management device 102 can be directly or indirectly connected through wired or wireless communication, and this application does not impose any restrictions.

[0069] It should be noted that the implementation environment of this application embodiment includes, but is not limited to, Figure 1 As shown.

[0070] The technical solutions of the embodiments of this application will be described in detail below through some examples. The following embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0071] The project delivery method in this application includes a management end and a delivery end, firstly combining... Figure 2 Taking the management and delivery ends as examples, the project delivery process of this application embodiment is introduced.

[0072] Figure 2 This is a flowchart illustrating a project delivery method provided in one embodiment of this application.

[0073] like Figure 2 As shown, the project delivery process in this application embodiment includes:

[0074] S101, The management device obtains the project information of the target project to be delivered, and downloads the software source component package of the target project from the delivery storage module based on the project information.

[0075] The software source component package includes at least the software source components of the target project and N description files. The description files are used to describe the storage address of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer.

[0076] This application does not limit the specific type of the target project, which can be a private cloud, a dedicated cloud, a software program, etc.

[0077] Upon project delivery, the software source components and software source materials for the target project must be delivered. The software source components can be understood as the runtime entity of the target project, and the software source materials can be understood as the data resources running on those software source components. For example, if the target project is a video application, then the software source components can be understood as the video application itself, and the software source materials can be understood as the video resource data played on that video application. As another example, if the target project is a private cloud, then the software source components can be understood as the private cloud itself, and the software source materials can be understood as the data resources on that private cloud.

[0078] In this embodiment, to facilitate reliable management of the target project and prevent omissions or errors in software source materials, the software source components of the target project and descriptive text describing the storage addresses of the software source materials in the R&D storage module are packaged together to generate a software source component package. This allows the entire software source component package to be processed during subsequent delivery, preventing omissions or errors in software source materials and thus improving the delivery reliability of the target project.

[0079] As described above, in this embodiment of the application, a software source component package needs to be generated first upon project delivery. The specific process for generating the software source component package for the target project is described below.

[0080] In this embodiment of the application, before the management device downloads the software source component package of the target project from the delivery storage module based on the project information of the target project, it first generates the software source component package of the target project through the following steps A1 to A4:

[0081] Step A1: Manage the device to obtain the software source components and N description files for the target project;

[0082] Step A2: The management device compiles and packages the software source components and N description files to generate a software source component package;

[0083] Step A3: The management device sets a tag for the software source component package and marks the status of the software source component package as released.

[0084] Step A4: The management device stores the software source component package with the status of release in the delivery storage module.

[0085] In this embodiment, for the target project, the total number of software source materials included in the target project is N, meaning the target project includes N software source materials. Each of these N software source materials corresponds to a description file, which describes the storage location of the software source material in the R&D storage module. Thus, N software source materials correspond to N description texts. When generating the software source component package for the target project, the management device first obtains the software source components and N description files for the target project.

[0086] This application embodiment does not restrict the specific storage location of the software source components and N description files of the target project.

[0087] In some embodiments, the software source components of the target project and N description files are all stored in the software source component code library.

[0088] In some embodiments, the software source components of the target project are stored in a software source component code library. N description files are stored in other modules, such as the R&D storage module.

[0089] This application embodiment does not limit the specific triggering conditions for the management device to obtain the software source components and N description files of the target project.

[0090] In one possible implementation, the management device periodically acquires the software source components and N description files of the target project, and determines whether the description files have changed from the description files of the previous moment.

[0091] In one possible implementation, step A1 above may include steps A11 to A13 as follows:

[0092] Step A11: If the management device detects that M addresses have been added to the first address list corresponding to the target project, then the newly added M addresses are obtained. The first address list includes the storage address of the description file corresponding to the target project in the R&D storage module, where M is a positive integer.

[0093] Step A12: The management device downloads M new description files corresponding to the target project from the R&D storage module based on M addresses;

[0094] Step A13: The management device obtains software source components from the software source component code library based on M new description files, and obtains N description files, including M new description files.

[0095] In this implementation, an address list, denoted as the first address list, is set for the target project. This first address list records the storage addresses of the target project's description files in the R&D storage module. Specifically, in this embodiment, the software source materials of the target project are obtained, stored in the R&D storage module, and each software source material is recorded as its storage address in the R&D storage module, forming a description file. Then, the description file is also stored in the R&D storage module, obtaining its storage address, which is then recorded in the first address list. Based on this, the management device can detect the first address list. For example, if the pipeline detects that M new description file storage addresses (e.g., URLs) have been generated in the first address list, these M addresses are used to download M description files of the target project from the R&D storage module. Then, based on these M new description files, the software source components of the target project are obtained from the software source component code library, and N description files of the target project are obtained, including the aforementioned M new description files.

[0096] As can be seen from the above, in this embodiment of the application, the management device also includes a scheme for downloading new software materials for the target project.

[0097] The following describes the process of downloading new software source materials for the target project using the management equipment, based on steps B1 to B5:

[0098] Step B1: Manage the equipment to download M new software source materials corresponding to the target project;

[0099] Step B2: The management device stores M new software source materials in the R&D storage module, and obtains the storage addresses of the M new software source materials in the R&D storage module;

[0100] Step B3: Based on the storage addresses of M new software source materials in the R&D storage module, the management equipment generates M new description files;

[0101] Step B4: The management device stores M new description files in the R&D storage module, and obtains the storage addresses of the M new description files in the R&D storage module;

[0102] Step B5: The management device adds the storage addresses of M new description files in the R&D storage module to the first address list.

[0103] In this embodiment, the management device periodically downloads software source materials for a target project from various sources, such as downloading M new software source materials for the target project. In some embodiments, for different operating systems, the management device can download software source materials for the target project under different operating systems. Next, the management device stores the downloaded M new software source materials in a research and development storage module, obtaining the storage addresses of these M new software source materials in the research and development storage module. This embodiment does not limit the specific representation of the storage address; an exemplary storage address can be a URL. Next, the management device writes the storage address of each of the M new software source materials in the research and development storage module into a separate description file, thereby obtaining M new description files. Then, the management device stores these M new description files in the research and development storage module, obtaining the storage address of each of the M new description files in the research and development storage module. Finally, the management device adds the storage address of each of the M new description files in the research and development storage module to a first address list.

[0104] For example, Table 1 shows the list of the first addresses corresponding to the target project when no M new description files are added to the R&D storage module:

[0105] Table 1

[0106] Serial Number storage address illustrate 1 URL_1 The storage address of the first description file in the R&D storage module 2 URL_2 The storage address of the second description file in the R&D storage module …… …… NM URL_N-M The storage address of the NMth description file in the R&D storage module

[0107] As shown in Table 1, the first address list corresponding to the target project is as follows when no M new description files are added. As shown in Table 1, at that time, the target project included NM software source materials, and these NM software source materials corresponded to NM description files.

[0108] For example, Table 2 shows the list of the first addresses corresponding to the target project when adding M new description files to the R&D storage module:

[0109] Table 2

[0110] Serial Number storage address illustrate 1 URL_1 The storage address of the first description file in the R&D storage module 2 URL_2 The storage address of the second description file in the R&D storage module …… …… NM URL_N-M The storage address of the NMth description file in the R&D storage module N-M+1 URL_N-M+1 The storage address of the N-M+1th description file in the R&D storage module N-M+2 URL_N-M+2 The storage address of the N-M+2th description file in the R&D storage module …… …… N URL_N The storage address of the Nth description file in the R&D storage module

[0111] As shown in Table 2, after adding M new description files, the list of the first addresses corresponding to the target project is as shown in Table 2. As shown in Table 2, the target project now includes N software source materials, which correspond to N description files, including the aforementioned M new description files.

[0112] This application does not limit the storage location of the first address list. In one example, the management device may store the first address list in a payment storage module. In another example, the management device may store the first address list in a database.

[0113] In some embodiments, the management device also stores the unique identifiers, update statuses, return codes, etc. of the N software source materials of the target project into the database.

[0114] In this embodiment, the management device, based on the above steps, downloads M new software source materials for the target project and adds the storage addresses of the M new description files corresponding to these M new software source materials in the R&D storage module to a first address list. Thus, when the management device detects that M addresses have been added to the first address list corresponding to the target project through a pipeline, it acquires these M new addresses. Next, based on these M addresses, it downloads the M new description files corresponding to the target project from the R&D storage module. Then, based on these M new description files, it acquires the software source component from the software source component code library and acquires N description files, which include the aforementioned M new description files.

[0115] In this embodiment of the application, the management device obtains the software source component from the software source component code library based on M new description files, and the specific methods for obtaining N description files include at least the following:

[0116] In Method 1, the management device writes the M new description files obtained above into the software source component code library. Then, it retrieves the software source component and N description files from this software source component code library.

[0117] In this first method, the software source component code library includes the target project's software source components and all description files. If a new description file for the target project is detected, it is first stored in the software source component code library. Thus, when generating the software source component package, the management device retrieves the target project's software source components and all description files (N description files) from the software source component code library.

[0118] Method 2: The management device obtains the software source components and NM description files from the software source component code library; the M new description files and the NM description files are combined to form N description files.

[0119] In this second method, after the management device obtains M new description files for the target project based on the above steps, it does not immediately store these M new description files in the software source component code library. Instead, it obtains the software source components for the target project and NM old description files from the software source component code library. These NM old description files, together with the M new description files obtained above, form N description files for the target project.

[0120] In some embodiments of this method two, the management device also writes the aforementioned M new description files into the software source component code library. This allows for the retrieval of all old description files for the target project from the software source component code library the next time.

[0121] In this embodiment, after obtaining the software source components and N description files of the target project based on the above steps, the management device executes step A2, compiling and packaging the software source components and N description files to generate a software source component package. The management device tags the software source component package and marks its status as released. Then, the management device stores the software source component package with the released status in the delivery storage module.

[0122] In some embodiments, the management device also stores various data involved in the above steps into a database. For example, after tagging a software source component package, it stores the software source component package, the corresponding tag data, the tagging time, etc.

[0123] In this embodiment of the application, the management device stores the software source component package of the target project in the delivery storage module, and the status of the software source component package is marked as published.

[0124] It should be noted that the above description uses a target project as an example to illustrate the process of the management device generating the software source component package for that target project. Following this method, the management device can generate software source component packages for multiple projects and store them in the delivery storage module. Thus, upon delivery, the management device can retrieve the software source component package for the project to be delivered from the delivery storage module based on the project information of the project to be delivered.

[0125] In this embodiment of the application, when a target project needs to be delivered, based on the project information of the target project, the software source component package of the target project is found in the software source component package with the status of "released" in the payment storage module, and the package delivery process is executed.

[0126] This application does not limit the specific content included in the project information of the target project.

[0127] In one example, the project information of the target project includes the project identifier of the target project, so that the management device can download the software source component package of the target project from the delivery storage module based on the project identifier of the target project.

[0128] S102. Based on N description files, the management equipment determines the storage address of each software source material in the R&D storage module among the N software source materials corresponding to the target project.

[0129] In this embodiment, the management device downloads the software source component package of the target project from the delivery storage module based on the project information of the target project. This software source component package includes the software source components of the target project and N description files. As mentioned above, the description files describe the storage address of the software source materials in the R&D storage module. Thus, the management device can determine the storage address of each of the N software source materials corresponding to the target project in the R&D storage module based on the N description files.

[0130] For example, for each of the N description files, parsing the description file yields the storage address of the software source material described in the description file within the R&D storage module. In this way, the N description files can be used to obtain the storage addresses of the N software source materials within the R&D storage module.

[0131] S103. The management device generates download addresses for N software source materials based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project.

[0132] In this embodiment, the storage address of the software source material is not publicly accessible, meaning users cannot download the software source material through the storage address. Therefore, in this embodiment,

[0133] This application does not limit the specific content included in the project information of the target project.

[0134] In some embodiments, the project information of the target project includes the identification information of the target project. In this way, the management device can process the storage addresses of N software source materials in the R&D storage module according to the identification information of the target project, and generate the download addresses of N software source materials.

[0135] In some embodiments, the project information of the target project includes the project identifier, delivery time, and authorization token of the target project. Thus, for each of the N software source materials, such as the i-th software source material, the management device can generate a download address for the i-th software source material based on its storage address in the R&D storage module, and the project identifier, delivery time, and authorization token of the target project. In this implementation, the download address (e.g., download URL) of the software source material includes the project identifier, delivery time, and authorization token (i.e., authorization token) of the target project, which avoids the problem of download failure due to the expiration of the download address when the target project is delivered, caused by a mismatch between the validity period and the current delivery project. It also avoids the security risk of the software source material's download address having no access restrictions, allowing anyone to download it. Therefore, the download address (e.g., download URL) of the software source material in this embodiment includes the project identifier, delivery time, and authorization token of the target project, ensuring the validity and security of the software source material. Furthermore, it is downloaded and delivered along with the software source component, following a standard delivery process and solving the problem of easy omissions.

[0136] S104. The management device generates a delivery package for the target project based on the download addresses of the software source components and N software source materials, and stores the delivery package in the delivery storage module so that the delivery device can download the delivery package from the delivery storage module.

[0137] In this embodiment, the management device obtains the download addresses of the software source components and N software source materials of the target project based on the above steps. Then, based on the download addresses of the software source components and N software source materials, a delivery package for the target project is generated.

[0138] This application embodiment does not limit the specific method by which the management device generates the delivery package of the target project based on the download addresses of the software source components and N software source materials.

[0139] In one possible implementation, the management device packages the download addresses of the software source components and N software source materials together to generate a delivery package for the target project.

[0140] In one possible implementation, to further facilitate the delivery of the target project, the management device obtains the download address of each of the N software source components and generates a download script based on the download address of each of the N software source components. Then, the software source components of the target project and the download script are packaged together to generate the delivery package of the target project.

[0141] Based on the steps described above, the management device generates a delivery package for the target project, marks it as a pending delivery package, and stores it in the delivery storage module. In this way, the delivery device can download the delivery package for the target project from the delivery storage module.

[0142] In some embodiments, the management device stores various data involved in the above steps into a database. For example, the project identifier, delivery time, and authorization token of the target project are stored in the database. Optionally, the management device stores the package release time, delivery package name, and other information in the database.

[0143] In this embodiment of the application, a label is also set for the delivery package, for example, the project name of the target project is determined as the label of the delivery package.

[0144] In this embodiment, the R&D environment typically uses an intranet, while the delivery pipeline is generally connected to both the intranet and the public network. The R&D storage module is also generally connected to both the intranet and the public network. In this embodiment, the management device stores software source materials and description files describing the storage addresses of these source materials in the R&D storage module. Using the R&D storage module as an intermediary, the source code repository, the delivery pipeline, and the R&D environment interact with the R&D storage module, thus solving the problem that the networks of the source code repository, the pipeline, and the R&D environment cannot directly communicate with each other.

[0145] S105. The delivery device obtains the project information of the target project to be delivered, and downloads the delivery package of the target project from the delivery storage module based on the project information.

[0146] It should be noted that S101 to S105 above describe the project delivery process on the management side. S106 to S109 below describe the project delivery process on the delivery side.

[0147] In this embodiment, the management device generates a delivery package for the target project based on steps S101 to S105 described above, and stores the delivery package in the delivery storage module. The delivery device in this embodiment can access the delivery storage module. Thus, when the delivery device needs to deploy the target project, it obtains the project information of the target project and then downloads the delivery package of the target project from the delivery storage module based on the project information.

[0148] In this embodiment of the application, no restrictions are placed on the specific content included in the project information of the target project.

[0149] In some embodiments, the project information of the target project includes the target project's identification information. Based on this, the delivery device can download the delivery package of the target project from the delivery storage module based on the target project's identification information.

[0150] S106. Parse the delivery package to obtain the download addresses of the target project's software source components and N software source materials.

[0151] Based on the above steps, the delivery equipment downloads the delivery package of the target project from the delivery storage module, parses the delivery package, and obtains the download addresses of the software source components and N software source materials of the target project.

[0152] In some embodiments, the delivery package includes software source components and download scripts for the target project. The delivery device can then parse the download scripts to obtain download addresses for N software source materials.

[0153] After obtaining the download addresses of the target project's software source components and N software source materials based on the above parsed delivery package, the delivery equipment executes the following step S107.

[0154] S107. The delivered equipment downloads N software source materials from the R&D storage module based on the download addresses of N software source materials.

[0155] In this embodiment of the application, after obtaining the download addresses of N software source materials for the target project based on the above steps, the delivery device downloads the N software source materials from the R&D storage module based on the download addresses.

[0156] In some embodiments, as described above, the download addresses of the N software source materials in this application embodiment are obtained by processing the storage addresses of the N software source materials based on the project name, project time, and authorization token of the target project. Based on this, after obtaining the download addresses of the N software source materials according to the above steps, the delivery device performs address authentication based on the project identifier, delivery time, and authorization token of the target project, such as determining whether the target project has expired and whether the delivery device has the permission to download the software material. After successful address authentication, the delivery device downloads the N software source materials from the R&D storage module based on the download addresses of the N software source materials.

[0157] S108. Deliver the equipment based on software source components and N software source materials to complete the delivery of the target project.

[0158] In this embodiment of the application, the delivery device obtains the software source components and N software source materials of the target project based on the above steps, and then deploys the software source components and N software source materials of the target project to achieve the delivery of the target project.

[0159] The project delivery method provided in this application first involves a management device acquiring project information of a target project to be delivered. Based on this project information, the device downloads a software source component package of the target project from a delivery storage module. This software source component package includes at least software source components of the target project and N description files. The description files describe the storage addresses of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer. Based on the N description files, the storage address of each of the N software source materials corresponding to the target project in the R&D storage module is determined. Based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project, download addresses for the N software source materials are generated. Based on the software source components and the download addresses of the N software source materials, a delivery package for the target project is generated and stored in the delivery storage module, so that the delivery device can download the delivery package from the delivery storage module. Correspondingly, the delivery device obtains the project information of the target project to be delivered, and based on the project information, downloads the corresponding delivery package of the target project from the delivery storage module; parses the delivery package to obtain the download addresses of the software source components and N software source materials of the target project; based on the download addresses of the N software source materials, downloads the N software source materials from the R&D storage module; and based on the software source components and N software source materials, completes the delivery of the target project. Therefore, this embodiment of the application packages the software source components and software source materials of the target project together, solving the problem of chaotic management of software source materials, preventing omissions or errors of software source materials, and thus improving the project delivery quality. At the same time, this embodiment of the application generates download addresses for software source materials and packages these download addresses with the software source components in the delivery package, allowing different delivery devices to simultaneously download the software source materials from the R&D storage module through these download addresses, eliminating the need for multiple copies, reducing project delivery costs, and improving project delivery efficiency. In other words, this embodiment of the application uses a standard automated process, reducing manual operations, improving delivery efficiency, and ensuring the synchronization and consistency of software source components, delivery projects, and software source materials, reducing the likelihood of errors and omissions, and improving project delivery quality.

[0160] The foregoing provides an overall overview of the project delivery method provided in the embodiments of this application. The following section further describes the project delivery method in the embodiments of this application.

[0161] Figure 3 This is a flowchart illustrating a project delivery method provided in one embodiment of this application.

[0162] like Figure 3 As shown, the project delivery method of this application embodiment includes the following steps:

[0163] S201. Manage the download of M new software source materials corresponding to the target project.

[0164] like Figure 4 As shown, the management device in this application embodiment includes at least the following three modules: a software source material transfer module, a software source material merging module, and a software source material packaging module.

[0165] like Figure 4 As shown, the software source material transfer module executes steps S201 to S205, which means storing software source materials from different sources into the R&D storage bucket, and also storing the file that records its URL in the R&D storage bucket in the R&D storage bucket.

[0166] The software source material merging module executes steps S206 to S211 as follows: The pipeline's polling detects a change in the storage URL of the file storing the software source URL. The pipeline downloads this file from the development storage and updates the source code repository of the software source component with the new file for version management. The pipeline then repackages the source code of the software source component, uploads the packaged component to the delivery storage module, and tags the software source component package, recording it as a release.

[0167] The software source material packaging module is used to execute the following steps S212 to S215: it finds the current version of the software source component package from the software source component package in the published state according to the tag, finds the description file, parses each description file, combines the storage address described by each description file with the project identifier, delivery time, and authorization token to generate a new public network downloadable address, stores it in the download script, and packages it to the site along with the software source component.

[0168] The following is in conjunction with the above. Figure 4 The present application describes the project delivery method according to its embodiments.

[0169] S202. The management device stores M new software source materials in the R&D storage module and obtains the storage addresses of the M new software source materials in the R&D storage module.

[0170] S203. The management device generates M new description files based on the storage addresses of M new software source materials in the R&D storage module.

[0171] S204. The management device stores M new description files in the R&D storage module and obtains the storage addresses of the M new description files in the R&D storage module.

[0172] S205. The management device adds the storage addresses of M new description files in the R&D storage module to the first address list.

[0173] First, such as Figure 5 As shown, for a target project, the management device downloads M new software source materials corresponding to that target project. Next, the management device stores these M new software source materials in the R&D storage module, obtaining their storage addresses within the R&D storage module. The R&D storage module then returns these storage addresses. Based on these storage addresses, the management device can generate M new description files. For example, for each of the M new software source materials, a corresponding description file is generated based on its storage address in the R&D storage module. This description file describes the storage address of the software source material in the R&D storage module. The management device then stores these M description files in the R&D storage module, obtaining their storage addresses within the R&D storage module.

[0174] Furthermore, to facilitate project delivery, the management device writes the storage addresses of these M description files in the R&D storage module into the first address list.

[0175] In some embodiments, the management device also stores the relevant data involved in the above steps in a database, such as the unique identifier of the software source material, the storage address of the description file, the update status of the first address list, and the return code.

[0176] The descriptions of S201 to S205 above can be referred to the description of S101 above, and will not be repeated here.

[0177] S206. If the management device detects that M addresses have been added to the first address list corresponding to the target project, then the management device shall obtain the M newly added addresses.

[0178] The first address list includes the storage address of the description file corresponding to the target project in the R&D storage module, where M is a positive integer.

[0179] S207. The management device downloads M new description files corresponding to the target project from the R&D storage module based on M addresses.

[0180] S208. The management device obtains software source components from the software source component code library based on M new description files, and obtains N description files.

[0181] Among them, the N description files include M new description files.

[0182] Method 1: The management device writes M new description files into the software source component code library; and retrieves the software source component and N description files from the software source component code library.

[0183] Method 2: The management device obtains the software source components and NM description files from the software source component code library; the M new description files and the NM description files are combined to form N description files.

[0184] In one example of Method 2, the management device writes M new description files into the software source component codebase.

[0185] S209. The management device compiles and packages the software source components and N description files to generate a software source component package.

[0186] S210, The management device sets a tag for the software source component package and marks the status of the software source component package as released.

[0187] S211. The management device stores the software source component package with the status of release in the delivery storage module.

[0188] like Figure 6 As shown, the management device detects the first address list through a pipeline or workflow. If M new addresses are detected in the first address list corresponding to the target project, these M new addresses are acquired. Then, based on these M addresses, M new description files corresponding to the target project are downloaded from the R&D storage module. These M new description files are stored in the software source component code library. The management device retrieves the software source component and N description files for the target project from the software source component code library, and then compiles and packages the software source component and N description files to generate a software source component package. Next, the management device tags the software source component package and marks its status as released, storing the released software source component package in the delivery storage module.

[0189] The descriptions of S206 to S211 above can be referred to the descriptions of S101 above, and will not be repeated here.

[0190] S212. The management device obtains the project information of the target project to be delivered, and downloads the software source component package of the target project from the delivery storage module based on the project information.

[0191] The software source component package includes at least the software source components of the target project and N description files. The description files are used to describe the storage address of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer.

[0192] S213. Based on N description files, the management equipment determines the storage address of each software source material in the R&D storage module among the N software source materials corresponding to the target project.

[0193] S214. The management device generates download addresses for N software source materials based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project.

[0194] In one example, if the project information includes the project identifier, delivery time, and authorization token of the target project, for the i-th software source material among N software source materials, the management device generates the download address of the i-th software source material based on the storage address of the i-th software source material in the R&D storage module, as well as the project identifier, delivery time, and authorization token of the target project, where i is a positive integer less than or equal to N.

[0195] S215. The management device generates a delivery package for the target project based on the download addresses of the software source components and N software source materials, and stores the delivery package in the delivery storage module so that the delivery device can download the delivery package from the delivery storage module.

[0196] In this embodiment of the application, when software source needs to be delivered, the software source component corresponding to the target project is found in the software source component package with the status of "released" based on the tag, and the package output process is executed. Specifically, as follows... Figure 7 As shown, the management device obtains the project information of the target project to be delivered. Based on the project information, it queries and downloads the software source component package of the target project from the software source component packages in the delivery storage module that are in the delivery state. Next, based on N description files, it determines the storage address of each of the N software source materials corresponding to the target project in the R&D storage module. Based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project, it generates download addresses for the N software source materials. Based on the software source components and the download addresses of the N software source materials, it generates a delivery package for the target project and stores the delivery package in the delivery storage module so that the delivery device can download the delivery package from the delivery storage module. In some embodiments, the delivery device generates a download script based on the download address of each of the N software source components; based on the software source components and the download script, it generates the delivery package for the target project and marks the status of the delivery package as pending delivery.

[0197] In some embodiments, the relevant data from S212 to S215 described above are stored in a database. For example, by querying the update status of the unique identifier of a software source material in the database and finding an update, the storage address of the corresponding description file is located. After the software source component package is tagged, the tag data of the software source component package, the tagging time, etc., are stored.

[0198] The descriptions of S212 to S215 above can be referred to the descriptions of S102 to S104 above, and will not be repeated here.

[0199] The above S201 to S215 are the technical solutions for the management end. The following section combines S216 to S219, which are the technical solutions for the delivery end.

[0200] S216. The delivery device obtains the project information of the target project to be delivered, and downloads the delivery package of the target project from the delivery storage module based on the project information.

[0201] S217. Parse the delivery package to obtain the download addresses of the target project's software source components and N software source materials.

[0202] S218. The delivered equipment downloads N software source materials from the R&D storage module based on the download addresses of N software source materials.

[0203] In some embodiments, the project information includes the target project's project identifier, delivery time, and authorization token. In this case, the delivery device performs address authentication based on the target project's project identifier, delivery time, and authorization token; after successful address authentication, it downloads N software source materials from the R&D storage module based on the download addresses of N software source materials.

[0204] S219. Deliver the equipment based on software source components and N software source materials to complete the delivery of the target project.

[0205] The specific implementation process of S216 to S219 can be referred to the relevant descriptions of S105 to S108 above, and will not be repeated here.

[0206] The project delivery method provided in this application first involves a management device downloading M new software source materials corresponding to the target project, storing these M new software source materials in a research and development storage module, obtaining the storage addresses of these M new software source materials in the research and development storage module, generating M new description files based on these storage addresses, storing these M new description files in the research and development storage module, obtaining the storage addresses of these M new description files in the research and development storage module, and adding these storage addresses to a first address list. If the management device detects that M addresses have been added to the first address list corresponding to the target project, it obtains these M new addresses, downloads the M new description files corresponding to the target project from the research and development storage module based on these M addresses, obtains software source components from the software source component code library based on these M new description files, and obtains N description files. The management device compiles and packages the software source components and N description files to generate a software source component package. It then tags the software source component package and marks its status as released. The released software source component package is stored in the delivery storage module. The management device obtains the project information of the target project to be delivered and, based on this information, downloads the target project's software source component package from the delivery storage module. Based on the N description files, it determines the storage address of each of the N software source materials corresponding to the target project in the R&D storage module. Based on these storage addresses and the target project information, it generates download addresses for the N software source materials. Finally, based on the software source components and the download addresses of the N software source materials, it generates the target project's delivery package and stores it in the delivery storage module, allowing the delivery device to download it from the delivery storage module. The delivery device acquires project information for the target project to be delivered, and based on this information, downloads the delivery package of the target project from the delivery storage module. It then parses the delivery package to obtain download addresses for the target project's software source components and N software source materials. Based on these download addresses, it downloads the N software source materials from the R&D storage module. Therefore, this embodiment of the application packages the target project's software source components and software source materials together, solving the problem of chaotic software source material management, preventing omissions or errors, and thus improving project delivery quality. Furthermore, this embodiment of the application generates download addresses for the software source materials and packages these addresses along with the software source components in the delivery package. This allows different delivery devices to simultaneously download the software source materials from the R&D storage module using these download addresses, eliminating the need for multiple copies, reducing project delivery costs, and improving project delivery efficiency.In other words, the embodiments of this application use standard automated processes, which reduce manual operations, improve delivery efficiency, and at the same time ensure the synchronization and consistency of software source components, delivery projects and software source materials, making it less prone to errors and omissions, and improving the delivery quality of the project.

[0207] The above text combined Figures 2 to 7 The following describes in detail an embodiment of the project delivery method of this application, in conjunction with... Figure 8 and Figure 9 The following describes in detail the device embodiments of this application.

[0208] Figure 8 This is a schematic block diagram of a project delivery device provided in an embodiment of this application, which is applied to management equipment.

[0209] like Figure 8 As shown, the project delivery device 10 includes:

[0210] The acquisition unit 11 is used to acquire the project information of the target project to be delivered, and based on the project information of the target project, download the software source component package of the target project from the delivery storage module. The software source component package includes at least the software source components of the target project and N description files. The description files are used to describe the storage address of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer.

[0211] Address determination unit 12 is used to determine the storage address of each software source material in the R&D storage module among the N software source materials corresponding to the target project based on the N description files.

[0212] Address generation unit 13 is used to generate download addresses for the N software source materials based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project.

[0213] Delivery unit 14 is used to generate a delivery package for the target project based on the download addresses of the software source components and the N software source materials, and store the delivery package in the delivery storage module so that the delivery device can download the delivery package from the delivery storage module.

[0214] In some embodiments, the project information includes the project identifier, delivery time, and authorization token of the target project. The acquisition unit 11 is specifically used to download the software source component package from the delivery storage module based on the project identifier of the target project. The address generation unit 13 is specifically used to generate a download address for the i-th software source material among the N software source materials, based on the storage address of the i-th software source material in the R&D storage module, and the project identifier, delivery time, and authorization token of the target project, where i is a positive integer less than or equal to N.

[0215] In some embodiments, the delivery unit 14 is specifically configured to generate a download script based on the download address of each of the N software source components; generate a delivery package for the target project based on the software source components and the download script; and mark the status of the delivery package as pending delivery.

[0216] In some embodiments, the acquisition unit 11 is further configured to acquire the software source components and N description files of the target project; compile and package the software source components and the N description files to generate the software source component package; set a tag for the software source component package and mark the status of the software source component package as a release status; and store the software source component package with the release status in the delivery storage module.

[0217] In some embodiments, the acquisition unit 11 is specifically configured to: if M new addresses are detected in the first address list corresponding to the target project, acquire the M new addresses, wherein the first address list includes the storage address of the description file corresponding to the target project in the R&D storage module, and M is a positive integer; download M new description files corresponding to the target project from the R&D storage module based on the M addresses; and acquire the software source component from the software source component code library based on the M new description files, and acquire the N description files, wherein the N description files include the M new description files.

[0218] In some embodiments, the acquisition unit 11 is specifically used to write the M new description files into the software source component code library; and to acquire the software source component and the N description files from the software source component code library.

[0219] In some embodiments, the acquisition unit 11 is specifically used to acquire the software source component and NM description files from the software source component code library; and to combine the M new description files and the NM description files to form the N description files.

[0220] In some embodiments, the acquisition unit 11 is further configured to write the M new description files into the software source component code library.

[0221] In some embodiments, the acquisition unit 11 is further configured to: download M new software source materials corresponding to the target project; store the M new software source materials in the R&D storage module to obtain the storage address of the M new software source materials in the R&D storage module; generate M new description files based on the storage address of the M new software source materials in the R&D storage module; store the M new description files in the R&D storage module to obtain the storage address of the M new description files in the R&D storage module; and add the storage address of the M new description files in the R&D storage module to the first address list.

[0222] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 8 The apparatus shown can perform the above-described embodiments of the management device side method, and the foregoing and other operations and / or functions of each module in the apparatus are respectively for implementing the method embodiments corresponding to the electronic device, which will not be described in detail here for the sake of brevity.

[0223] Figure 9 This is a schematic block diagram of a project delivery device provided in an embodiment of this application, which is applied to delivery equipment.

[0224] like Figure 9 As shown, the project delivery device 20 includes:

[0225] The acquisition unit 21 is used to acquire project information of the target project to be delivered, and download the delivery package of the target project from the delivery storage module based on the project information;

[0226] The parsing unit 22 is used to parse the delivery package to obtain the download addresses of the software source components and N software source materials of the target project;

[0227] Download unit 23 is used to download N software source materials from the R&D storage module based on the download addresses of the N software source materials;

[0228] Delivery unit 24 is used to complete the delivery of the target project based on the software source components and the N software source materials;

[0229] The delivery package is generated based on the download addresses of the software source components and N software source materials of the target project. The download addresses of the N software source materials are generated based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project. The storage addresses of the N software source materials in the R&D storage module are determined based on the N description files corresponding to the target project. The software source components and the N description files are obtained by parsing the software source component package of the target project. The description files are used to describe the storage addresses of the software source materials corresponding to the target project in the R&D storage module. The software source component package is stored in the delivery storage module.

[0230] In some embodiments, the project information includes the project identifier, delivery time, and authorization token of the target project. The download unit 23 is specifically used to perform address authentication based on the project identifier, delivery time, and authorization token of the target project. After the address authentication is successful, it downloads N software source materials from the R&D storage module based on the download addresses of the N software source materials.

[0231] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 9 The apparatus shown can perform the above-described delivery device-side method embodiments, and the foregoing and other operations and / or functions of each module in the apparatus are respectively for implementing the method embodiments corresponding to the electronic device, which will not be described in detail here for the sake of brevity.

[0232] The apparatus of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method disclosed in this application embodiment can be directly embodied as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0233] Figure 10 This is a schematic block diagram of the electronic device provided in the embodiments of this application. Figure 10 The electronic device can be a management device or a delivery device, and can be used to perform the above-described method embodiments.

[0234] like Figure 10 As shown, the electronic device 30 may include:

[0235] The system includes a memory 31 and a processor 32. The memory 31 stores a computer program 33 and transfers the program code 33 to the processor 32. In other words, the processor 32 can retrieve and run the computer program 33 from the memory 31 to implement the methods described in the embodiments of this application.

[0236] For example, the processor 32 can be used to execute the steps in the above method according to the instructions in the computer program 33.

[0237] In some embodiments of this application, the processor 32 may include, but is not limited to:

[0238] General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0239] In some embodiments of this application, the memory 31 includes, but is not limited to:

[0240] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0241] In some embodiments of this application, the computer program 33 may be divided into one or more modules, which are stored in the memory 31 and executed by the processor 32 to complete the page recording method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program 33 in the electronic device.

[0242] like Figure 10 As shown, the electronic device 30 may further include:

[0243] Transceiver 34, which can be connected to processor 32 or memory 31.

[0244] The processor 32 can control the transceiver 34 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 34 may include a transmitter and a receiver. The transceiver 34 may further include antennas, and the number of antennas may be one or more.

[0245] It should be understood that the various components in the electronic device 30 are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.

[0246] According to one aspect of this application, a computer storage medium is provided that stores a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, embodiments of this application also provide a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0247] According to another aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method described in the above-described method embodiments.

[0248] In other words, when implemented using software, it can be implemented wholly or partially in the form of a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0249] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0250] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0251] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0252] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A project delivery method, characterized in that, Applied to the management of equipment, the method includes: Obtain the project information of the target project to be delivered, and based on the project information of the target project, download the software source component package of the target project from the delivery storage module. The software source component package includes at least the software source components of the target project and N description files. The description files are used to describe the storage address of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer. Based on the N description files, determine the storage address of each software source material in the R&D storage module among the N software source materials corresponding to the target project; Based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project, the download addresses of the N software source materials are generated. Based on the download addresses of the software source components and the N software source materials, a delivery package for the target project is generated and stored in the delivery storage module, so that the delivery device can download the delivery package from the delivery storage module.

2. The method according to claim 1, characterized in that, The project information includes the project identifier, delivery time, and authorization token of the target project. The process of downloading the software source component package of the target project from the delivery storage module based on the project information includes: Based on the project identifier of the target project, the software source component package is downloaded from the delivery storage module; The step of generating download addresses for the N software source materials based on their respective storage addresses in the R&D storage module and the project information of the target project includes: For the i-th software source material among the N software source materials, a download address for the i-th software source material is generated based on the storage address of the i-th software source material in the R&D storage module, as well as the project identifier, delivery time, and authorization token of the target project, where i is a positive integer less than or equal to N.

3. The method according to claim 2, characterized in that, The step of generating the delivery package for the target project based on the download addresses of the software source components and the N software source materials includes: A download script is generated based on the download address of each of the N software source components. Based on the software source component and the download script, a delivery package for the target project is generated, and the status of the delivery package is marked as pending delivery.

4. The method according to claim 1, characterized in that, Before downloading the software source component package of the target project from the delivery storage module based on the project information of the target project, the method further includes: Obtain the software source components and N description files of the target project; The software source components and the N description files are compiled and packaged to generate the software source component package; Tag the software source component package and mark its status as released. The software source component package in the release state is stored in the delivery storage module.

5. The method according to claim 4, characterized in that, The acquisition of the software source components and N description files of the target project includes: If M new addresses are detected in the first address list corresponding to the target project, then the M new addresses are obtained. The first address list includes the storage address of the description file corresponding to the target project in the R&D storage module, and M is a positive integer. Based on the M addresses, download the M new description files corresponding to the target project from the R&D storage module; Based on the M new description files, the software source component is obtained from the software source component code library, and the N description files are obtained, including the M new description files.

6. The method according to claim 5, characterized in that, The step of obtaining the software source component from the software source component code library based on the M new description files, and obtaining the N description files, includes: Write the M new description files into the software source component code library; Obtain the software source component and the N description files from the software source component code library.

7. The method according to claim 5, characterized in that, The step of obtaining the software source component from the software source component code library based on the M new description files, and obtaining the N description files, includes: Obtain the software source component and NM description files from the software source component code library; The M new description files and the NM description files are combined to form the N description files.

8. The method according to claim 7, characterized in that, The method further includes: The M new description files are written into the software source component code library.

9. The method according to claim 5, characterized in that, The method further includes: Download the M new software source materials corresponding to the target project; The M new software source materials are stored in the R&D storage module to obtain the storage address of the M new software source materials in the R&D storage module; Based on the storage addresses of the M new software source materials in the R&D storage module, generate M new description files; The M new description files are stored in the R&D storage module to obtain the storage address of the M new description files in the R&D storage module; The storage addresses of the M new description files in the R&D storage module are added to the first address list.

10. A project delivery method, characterized in that, Applied to delivery equipment, the method includes: Obtain the project information of the target project to be delivered, and based on the project information, download the delivery package of the target project from the delivery storage module; Parse the delivery package to obtain the download addresses of the software source components and N software source materials of the target project; Based on the download addresses of the N software source materials, download the N software source materials from the R&D storage module; Based on the software source components and the N software source materials, the target project is delivered. The delivery package is generated based on the download addresses of the software source components and N software source materials of the target project. The download addresses of the N software source materials are generated based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project. The storage addresses of the N software source materials in the R&D storage module are determined based on the N description files corresponding to the target project. The software source components and the N description files are obtained by parsing the software source component package of the target project. The description files are used to describe the storage addresses of the software source materials corresponding to the target project in the R&D storage module. The software source component package is stored in the delivery storage module.

11. The method according to claim 10, characterized in that, The project information includes the project identifier, delivery time, and authorization token of the target project. The downloading of N software source materials from the R&D storage module based on the download addresses of the N software source materials includes: Address authentication is performed based on the target project's project identifier, delivery time, and authorization token. After address authentication is successful, N software source materials are downloaded from the R&D storage module based on their download addresses.

12. A project delivery device, characterized in that, Applied to management equipment, the device includes: An acquisition unit is used to acquire project information of a target project to be delivered, and based on the project information of the target project, download the software source component package of the target project from the delivery storage module. The software source component package includes at least the software source components of the target project and N description files. The description files are used to describe the storage address of the software source materials corresponding to the target project in the R&D storage module, where N is a positive integer. The address determination unit is used to determine the storage address of each software source material in the R&D storage module based on the N description files. The address generation unit is used to generate download addresses for the N software source materials based on their respective storage addresses in the R&D storage module and the project information of the target project. The delivery unit is configured to generate a delivery package for the target project based on the download addresses of the software source components and the N software source materials, and store the delivery package in the delivery storage module so that the delivery device can download the delivery package from the delivery storage module.

13. A project delivery device, characterized in that, Applied to delivery equipment, the device includes: The acquisition unit is used to acquire project information of the target project to be delivered, and download the delivery package of the target project from the delivery storage module based on the project information; The parsing unit is used to parse the delivery package to obtain the download addresses of the software source components and N software source materials of the target project; The download unit is used to download N software source materials from the R&D storage module based on the download addresses of the N software source materials; The delivery unit is used to complete the delivery of the target project based on the software source components and the N software source materials; The delivery package is generated based on the download addresses of the software source components and N software source materials of the target project. The download addresses of the N software source materials are generated based on the storage addresses of the N software source materials in the R&D storage module and the project information of the target project. The storage addresses of the N software source materials in the R&D storage module are determined based on the N description files corresponding to the target project. The software source components and the N description files are obtained by parsing the software source component package of the target project. The description files are used to describe the storage addresses of the software source materials corresponding to the target project in the R&D storage module. The software source component package is stored in the delivery storage module.

14. An electronic device, characterized in that, Including processor and memory; The memory is used to store computer programs; The processor is configured to execute the computer program to implement the method as described in any one of claims 1 to 9 or 10 to 11.

15. A computer-readable storage medium, characterized in that, Used to store computer programs; The computer program causes the computer to perform the method as described in any one of claims 1 to 9 or 10 to 11.

Images