Software information synchronization method, development platform, component warehouse system and sales platform

Abstract

The invention relates to a software information synchronization method, a development platform, a component warehouse system and a sales platform. The method is applied to a development platform and comprises the steps that software information corresponding to a first project is generated, the software information corresponding to the first project comprises a plurality of component identifiers corresponding to the first project, and each component identifier corresponds to at least one product identifier; sending the software information corresponding to the first item to a component warehouse system; the software product corresponding to the first product identifier is obtained from a product library of the first project, the software product corresponding to the first product identifier is sent to the component warehouse system, and the first product identifier is any one or more product identifiers included in the software information corresponding to the first project.

Description

Technical Field

[0001] The present application relates to the field of digital technology, and in particular to a software information synchronization method, a development platform, a component warehouse system and a sales platform. Background Art

[0002] In the field of software development, package management is a crucial link. There are many types of package managers, such as operating system-based package managers, package managers for programming languages, product repositories for cloud-native systems, and comprehensive software repository managers. These package managers play an important role in their respective fields, but they also have certain limitations.

[0003] The existing software package management system cannot cope well with complex scenarios where a software application contains multiple types of software packages, such as a website service that covers front-end, back-end, container, source code and other product forms. Moreover, these software warehouse management systems do not fully consider the integration with the development platform and the subsequent sales issues in the software mall. Ultimately, this affects the efficiency of software development, management, distribution and sales. Summary of the invention

[0004] Based on this, it is necessary to provide a software information synchronization method, development platform, component warehouse system, sales platform, computer equipment, computer-readable storage medium and computer program product to address the above technical problems.

[0005] In a first aspect, the present application provides a software information synchronization method, which is applied to a development platform, and the method comprises:

[0006] Generating software information corresponding to the first project, the software information corresponding to the first project comprising: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier;

[0007] sending software information corresponding to the first project to a component warehouse system;

[0008] Acquire a software product corresponding to a first product identifier from the product library of the first project, and send the software product corresponding to the first product identifier to a component warehouse system. The first product identifier is any one or more product identifiers included in the software information corresponding to the first project.

[0009] In a second aspect, the present application also provides a software information synchronization method, which is applied to a component warehouse system, and the method includes:

[0010] Receive software information corresponding to a first project sent by a development platform, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier;

[0011] If the software product corresponding to the first product identifier is not stored locally, obtaining the software product corresponding to the first product identifier from the development platform, where the first product identifier is any one or more product identifiers included in the software information corresponding to the first project;

[0012] A listing request message is sent to a sales platform associated with the component warehouse system, wherein the listing request message includes software information corresponding to the first project.

[0013] In a third aspect, the present application also provides a software information synchronization method, which is applied to a sales platform, and the method includes:

[0014] Receiving a listing request message sent by an associated component warehouse system, wherein the listing request message includes software information corresponding to the first project, wherein the software information includes: a plurality of component identifiers, each component identifier corresponding to at least one product identifier;

[0015] selecting at least one component identification from the plurality of component identifications;

[0016] generating software product information based on the at least one component identifier and at least one product identifier corresponding to each component identifier in the at least one component identifier;

[0017] Display the software product information.

[0018] In a fourth aspect, the present application further provides a development platform, the development platform comprising:

[0019] A generating module, configured to generate software information corresponding to a first project, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier;

[0020] A sending module, used for sending the software information corresponding to the first project to a component warehouse system;

[0021] A synchronization module is used to obtain a software product corresponding to a first product identifier from the product library of the first project, and send the software product corresponding to the first product identifier to a component warehouse system. The first product identifier is any one or more product identifiers included in the software information corresponding to the first project.

[0022] In a fifth aspect, the present application further provides a component warehouse system, the component warehouse system comprising:

[0023] A receiving module, configured to receive software information corresponding to a first project sent by a development platform, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier;

[0024] an acquisition module, configured to acquire the software product corresponding to the first product identifier from the development platform if the software product corresponding to the first product identifier is not stored locally, wherein the first product identifier is any one or more product identifiers included in the software information corresponding to the first project;

[0025] A publishing module is used to send a listing request message to a sales platform associated with the component warehouse system, wherein the listing request message includes software information corresponding to the first project.

[0026] In a sixth aspect, the present application further provides a sales platform, the sales platform comprising:

[0027] A receiving module, configured to receive a listing request message sent by an associated component warehouse system, wherein the listing request message includes software information corresponding to the first project, wherein the software information includes: a plurality of component identifiers, each component identifier corresponding to at least one product identifier;

[0028] A generating module, configured to select at least one component identifier from the plurality of component identifiers; and generate software commodity information based on the at least one component identifier and at least one product identifier corresponding to each component identifier in the at least one component identifier;

[0029] The display module is used to display the software product information.

[0030] In a seventh aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, at least one of the following methods is implemented:

[0031] The method as described in the first aspect, the method as described in the second aspect, and the method as described in the third aspect.

[0032] In an eighth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, at least one of the following methods is implemented:

[0033] The method as described in the first aspect, the method as described in the second aspect, and the method as described in the third aspect.

[0034] In a ninth aspect, the present application further provides a computer program product, including a computer program, which implements at least one of the following methods when executed by a processor:

[0035] The method as described in the first aspect, the method as described in the second aspect, and the method as described in the third aspect.

[0036] In the above-mentioned software information synchronization method, the development platform can generate software information corresponding to the first project, and the software information corresponding to the first project includes: multiple component identifiers corresponding to the first project, each component identifier corresponds to at least one product identifier; and the software information corresponding to the first project can be sent to the component warehouse system; the software product corresponding to the first product identifier is obtained from the product library of the first project, and the software product corresponding to the first product identifier is sent to the component warehouse system, and the first product identifier is any one or more product identifiers included in the software information corresponding to the first project. In this way, the component warehouse system and the development platform can be integrated, so that after the project is developed, the software product can be synchronized to the component warehouse system to wait for sales, which can improve the efficiency of software development, management, distribution and sales.

[0037] In the above-mentioned software information synchronization method, the component warehouse system can receive the software information corresponding to the first project sent by the development platform, and the software information corresponding to the first project includes: multiple component identifiers corresponding to the first project, and each component identifier corresponds to at least one product identifier; if the software product corresponding to the first product identifier is not stored locally, then the software product corresponding to the first product identifier is obtained from the development platform, and the first product identifier is any one or more product identifiers included in the software information corresponding to the first project; and a listing request message is sent to the sales platform associated with the component warehouse system, and the listing request message includes the software information corresponding to the first project. In this way, the component warehouse system can synchronize the software products after the software platform develops the project, and request the sales of the software products after the project is developed by sending a listing request message to the sales platform. Not only can the component warehouse system be integrated with the development platform, but also with the sales platform, so that the efficiency of software development, management, distribution and sales can be improved.

[0038] In the above-mentioned software information synchronization method, the sales platform can receive a listing request message sent by the associated component warehouse system, the listing request message includes software information corresponding to the first project, and the software information corresponding to the first project includes: multiple component identifiers, each component identifier corresponds to at least one product identifier; select at least one component identifier from the multiple component identifiers; generate software product information based on the at least one component identifier and at least one product identifier corresponding to each component identifier in the at least one component identifier; and display the software product information. The sales platform itself does not store software products, and obtains software products through the associated component warehouse system. And the sales platform can select software products corresponding to some components from the developed components according to the software information to generate software product information. In this way, when selling multiple developed components, some parts can be selected for combined sales according to demand, so that the sales of software products can be diversified. This not only improves the efficiency of sales, but also diversifies the sales of goods. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 A system architecture diagram for implementing a method for synchronizing software information in an embodiment of the present application;

[0041] Figure 2 A flowchart of a software information synchronization method is provided;

[0042] Figure 3 It is a software architecture diagram of a component warehouse system;

[0043] Figure 4 A schematic diagram of a component form;

[0044] Figure 5 A schematic diagram of a certain software product;

[0045] Figure 6 is a flowchart of another software information synchronization method;

[0046] Figure 7 The overall process diagram of the software information synchronization method in the embodiment of the present application is as follows: Figure 1 ;

[0047] Figure 8 The overall process diagram of the software information synchronization method in the embodiment of the present application is as follows: Figure 2 ;

[0048] Fig. 9 A structural block diagram of a development platform in one embodiment;

[0049] Fig.10 is a structural block diagram of a component warehouse system in one embodiment;

[0050] Fig.11 A structural block diagram of a sales platform in one embodiment;

[0051] Fig.12 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0053] DevOps is a culture, methodology and practice of software development and operation, which aims to shorten the software development cycle, improve product quality and quickly deliver value through automation, collaboration and continuous feedback. It emphasizes the collaborative communication between the development team and the operation team, and uses automated tools and processes to implement practices such as continuous integration, continuous delivery and continuous deployment. The artifact repository is a key component of the DevOps practice. It is used to store software artifacts, such as code, build packages, container images, etc. Its purpose is to facilitate sharing and access by team members, ensure version control and consistency of software artifacts, and support automated build, test and deployment processes. DevOps platforms usually integrate functional modules such as code bases, artifact repositories, and pipelines to achieve seamless connection between development, building, testing and deployment, and achieve continuous delivery goals. Through the artifact repository, the team can manage and track the change history of software artifacts, ensure environmental consistency, and accelerate the speed and quality of software delivery.

[0054] However, the traditional product warehouse model has defects: first, there are many types of product warehouses, with different management models and a lack of uniformity; second, there is a lack of a unified software warehouse system, resulting in the problem of reinventing the wheel; third, products developed by DevOps cannot be sold directly and cannot generate economic benefits; fourth, software purchased by users from software stores cannot be redeveloped, which has a serious impact on software that requires secondary customized development.

[0055] A package management system is a collection of tools that facilitate users to install, upgrade, configure and delete software packages. It plays an important role in software distribution and maintenance. It can be divided into three categories: operating system-based package managers, package managers for programming languages ​​and enterprise-level software repository managers.

[0056] Operating system-based package managers such as Apt's dpkg and yum's rpm are mainly used for operating system installation package management and dependency management. Among them, dpkg is the abbreviation of "Debian Package", which means "Debian package", and its full name is "Debian package manager". It is used to install, uninstall and manage software packages in Debian and its derivative systems (such as Ubuntu). Yum's rpm is "Red Hat Package Manager", and its full name is "Yellowdog Updater, Modified" and "Red Hat Package Manager". It is widely used in Red Hat-based systems (such as CentOS, Fedora, etc.). Yum is an rpm-based package manager used to more conveniently manage software package installation, update and uninstall operations. However, these operating system-based package managers are relatively old and not suitable for cloud-native DevOps platforms.

[0057] Package managers for programming languages, such as the Maven repository for Java and the Pypi repository for Python, are suitable for specific programming languages. Maven is a project management and build tool whose repository is used to store various libraries and dependencies required for Java projects. Its full name is "Apache Maven". Pypi, or "Python Package Index", is a software repository for the Python language from which developers can obtain various Python libraries. They support version management and dependency management, and can solve software component dependency issues during development.

[0058] Product repositories used for cloud-native systems such as Kubernetes, such as Helm and other K8s application store management systems, are application release management systems for Kubenetes. The full name is "The Kubernetes Package Manager". They can simplify the process of deploying applications on Kubernetes and support application packaging, release, installation, rollback and other functions, but can only support the release of Docker image applications and cannot handle products like Maven packages.

[0059] Enterprise-level software repository managers such as JFrog Artifactory and Nexus Repository Manager support multiple package management systems, provide advanced binary repository management capabilities, support build integration, dependency resolution, and efficient software package distribution, and are suitable for enterprise-level applications.

[0060] Each type of manager has unique functions and advantages. Package managers based on operating systems focus on system-level software installation management, emphasizing compatibility and integrity with operating systems; package managers for programming languages ​​focus on dependency management and module sharing for specific languages ​​or frameworks; enterprise-level software repository managers provide cross-language and cross-format software repository management capabilities to meet different levels of needs. However, for software applications that include multiple types of software packages, such as a website service that may include front-end, back-end, container, source code and other product forms at the same time, the existing software package management system is not very suitable, and because it does not fully consider the DevOps platform and subsequent software mall sales issues, the subsequent release and secondary development of the software will encounter many difficulties.

[0061] The software information synchronization method provided in the embodiments of the present application can solve the problem that the software product warehouse system used by the current DevOps platform cannot be directly published to the software store for sale, and how the software purchased by users in the software store can be reversely synchronized to DevOps for secondary development and then delivery, thereby realizing a closed loop of the software component production, listing, sales, ordering, secondary development, and delivery process, and improving the efficiency of software development, management, distribution and sales.

[0062] For example, Figure 1 The system architecture diagram of the software information synchronization method implemented in the embodiment of the present application is shown, and the system includes the following parts:

[0063] The development platform 101 is used to manage software development projects and provide management functions such as requirements, codes, products, pipelines, and tests.

[0064] The component warehouse system 102 is used to provide functions such as software component release, version management, and synchronization management.

[0065] The sales platform 103 is used to provide functions such as listing, selling, ordering, and delivering components.

[0066] Through the above system, the synchronization process of component release and ordering between the development platform and the sales platform can be realized. Its core is the multi-product and multi-version software component management capability based on the component warehouse system, as well as the fast two-way product synchronization capability between the development platform and the component warehouse system. The software production produced by the development platform can be seamlessly connected with the sale and ordering of the sales platform, thus realizing a closed business loop.

[0067] The above system enables the software products to be automatically synchronized and returned to the designated DevOps platform project after the software product is ordered, thereby avoiding the purchaser's manual reconstruction of the product library and simplifying the operation steps.

[0068] In an exemplary embodiment, Figure 2 As shown, a flowchart of a software information synchronization method is provided, and the method is applied to Figure 1 The system in is taken as an example to illustrate, including the following steps:

[0069] 201. The development platform generates software information corresponding to the first project.

[0070] The software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier.

[0071] In some embodiments, the development platform in the embodiment of the present application may be a DevOps platform. The DevOps platform in the embodiment of the present application may support conventional DevOps software development functions, including but not limited to project management, demand management, code warehouse, CI / CD pipeline, product warehouse, deployment management, test management, resource management, etc., as well as personnel authority configuration and other functions. And support component publishing, subscription and other processes with the component warehouse system. Exemplary ones may include:

[0072] (1) Supports publishing software products in DevOps projects into the component warehouse system in the form of components.

[0073] (2) Support synchronization of software artifacts from the component repository system to the artifact repository of a specified DevOps development project.

[0074] The software development process of the first project can be created on the development platform, and software development can be performed, which can include: firstly creating software development requirements corresponding to the first project, then performing code development, compilation and construction, deployment, testing, and review processes according to the software development requirements, and finally obtaining the developed software content.

[0075] In the embodiment of the present application, after the software content is developed, the software information corresponding to the first project can be determined according to the software content.

[0076] 202. The development platform sends software information corresponding to the first project to the component warehouse system.

[0077] The first product identifier is any one or more product identifiers included in the software information corresponding to the first project.

[0078] The development platform sends the software information corresponding to the first project to the component warehouse system, so that the component warehouse system can determine whether the software product indicated in the software information corresponding to the first project is stored locally.

[0079] 203. The component warehouse system determines that the software product corresponding to the first product identifier is not stored locally.

[0080] When the component warehouse system determines that part or all of the software products indicated in the software information corresponding to the first project are not stored locally, the corresponding software products can be obtained from the development platform. After the software products are obtained, they can be stored according to the type of the software products.

[0081] like Figure 3 As shown in Figure 1, it is a software architecture diagram of a component warehouse system. Figure 3 As shown, the component warehouse system may include: component management, dependency management, synchronization management, quality information management, version management, product management and other functions, which are used to manage the stored software products. The lower layer of the component warehouse system also includes a product library for storing various types of software products. Figure 3 The following are the Maven artifact library, Docker artifact library, Go artifact library, NPM artifact library, Pypi artifact library, and Generice artifact library.

[0082] Among them, Maven is a project management and construction tool, and the Maven artifact library is used to store components of software projects based on the Maven build system.

[0083] Docker is a containerization technology. The Docker repository is used to store Docker container images.

[0084] The Go artifact library is for projects developed in the Go language and is used to store Go language-related software artifacts, which may include executable files, library files, etc.

[0085] NPM (Node Package Manager) is a package management tool for Node.js. NPM is used to store module packages for Node.js projects. Node.js is a JavaScript runtime environment based on the Chrome V8 engine. Chrome V8 is a high-performance engine developed by Google. It is mainly used to quickly execute JavaScript code. JavaScript is a programming language widely used in web development and server-side programming.

[0086] PyPi (Python Package Index) is a software repository for Python. The Pypi product library is used to store packages for Python projects.

[0087] The Generice artifact library is a repository that can be used to store common types of software artifacts.

[0088] 204. The component warehouse system obtains the software product corresponding to the first product identifier from the development platform.

[0089] If the software product corresponding to the first product identifier is not stored locally, the component warehouse system obtains the software product corresponding to the first product identifier from the development platform.

[0090] After the software version of the first project is developed, the developer can package the software products in the software content into components and store them in the component warehouse system. Before storage, relevant reviews and compliance checks can be performed, which may include but are not limited to: 1) Checking the product path rules corresponding to the product list to avoid path conflicts; 2) Based on the quality information of the software, compliance checks can be performed including security scan results, component component analysis results, and test report results. Exemplarily, the security scan results include information such as Fortify vulnerability scans. Fortify usually refers to a software security scanning tool. It can perform static and dynamic analysis on software code to detect various security vulnerabilities. Exemplarily, the component component analysis results may include: the component's Software Bill of Materials (SBOM) list, license risks, etc.

[0091] In the embodiments of the present application, for example, Figure 4 The following is a schematic diagram of a component form. The component form can be a component package, which can be composed of the following parts:

[0092] (1) Component metadata:

[0093] Component metadata can include basic information and dependencies with other components.

[0094] The basic information may include description information and version information, etc. The description information may include but is not limited to: component name, label, icon, introduction, detailed description, etc., and may also include information such as submitter, submitting organization, and submission time.

[0095] Component dependencies: The dependencies of this component on other components.

[0096] (2) Artifact list: A component can contain multiple types of software artifacts, including one or more artifact lists of different types. For example: Docker artifact list, Maven artifact list, Pypi artifact list, each artifact list stores one or more software artifact identifiers. Figure 4 As shown in , the Docker artifact list includes Docker image 1 and Docker image 2; the Maven artifact list includes Maven library 1 and Maven library 2; and the Pypi artifact list includes Pypi library 1.

[0097] (3) Product dependency information: Depending on the product type, some products will carry dependency information. For example, Docker images have dependencies on other base images, and package management systems such as Maven and Pypi will carry the dependency information of a product package on other product packages. Figure 4 As shown in , the artifact dependency information includes Docker image 1 dependency, Docker image 2 dependency, Maven library 1 dependency, and Pypi library 1 dependency.

[0098] (4) Quality information (i.e. component quality information): Components carry multi-dimensional software quality information data, such as security scan reports, component composition reports, version test reports, etc., to facilitate process auditors and end users to evaluate the quality of the software.

[0099] Among them, security scanning information includes security risk information of the products involved in the component, including: code quality, security vulnerabilities, etc. Component component information is the list of upstream products that the software product depends on or the source code involved. The version test report contains the test status of this component, such as: test requirement coverage, test case passing status, defect legacy status, test summary and other information.

[0100] 205. The component warehouse system sends a listing request message to a sales platform associated with the component warehouse system, where the listing request message includes software information corresponding to the first project.

[0101] 206. The sales platform selects at least one component identifier from the multiple component identifiers.

[0102] 207. The sales platform generates software product information based on the at least one component identifier and at least one product identifier corresponding to each component identifier in the at least one component identifier.

[0103] In some embodiments, the sales platform uses the above-mentioned component warehouse system as its warehouse management system. Software products are defined with components as the smallest shelf unit.

[0104] After the sales platform obtains the software information corresponding to the first project, it can be learned how many components the first project has developed and what software products are included in each component. The sales platform can selectively combine these components to form different software products. Each software product can be sold separately, or the combined software products can be provided as different packages of the same software product for users to choose from.

[0105] For example, Figure 5 The following is a schematic diagram of a certain software product. Figure 5 As shown, the software product includes multiple packages for users to choose from, namely Figure 5 Package A, Package B and Package C. Each package may include a combination of different components. For example, Figure 5 Package A in may include: component 1, component 2 and component 3. Component 1 includes multiple software products: product 1, product 2 and product 3. Corresponding to product 1, there is some product dependency information: product dependency A, product dependency B, product dependency C.

[0106] In the embodiment of the present application, a software product listing process can be initiated on the sales platform. It can choose to create a new software product or update the version based on an existing software product. It includes:

[0107] (1) Select one or more components from the software component warehouse system to form a package, and set the package name, such as basic version, advanced version, etc.

[0108] (2) Set a pricing strategy for each package, which can include fixed price, time-based charging, pay-per-use charging, etc.

[0109] (3) Business contracts and other information related to software sales, as well as intellectual property information, are available for review by mall managers.

[0110] In some embodiments, before the sales platform puts the software product on the shelves, it can first go through the shelf approval process, and then put the components in the software warehouse on the shelves as software products that users can purchase. The approval process may include business, intellectual property, functional testing and other review and verification processes, which can be handled manually or automatically.

[0111] 208. The sales platform displays software product information.

[0112] After the software products are listed, they will be displayed on the sales platform. The software buyers can search and find the required software products on the sales platform and place an order. When placing an order, users can select one or more software products to add to an order and make payment.

[0113] After payment, the user can find the corresponding order. The order will display the components ordered by the user and the corresponding software product list and other information. The user can choose to download the relevant software products.

[0114] In the above software information synchronization method, the component warehouse system can synchronize the software products after the software platform has developed the project, and request the sales of the software products after the project has developed by sending a listing request message to the sales platform. The component warehouse system can be integrated not only with the development platform, but also with the sales platform, which can improve the efficiency of software development, management, distribution and sales.

[0115] In an exemplary embodiment, Figure 6 As shown, a flowchart of another software information synchronization method is provided, in which the method is applied to Figure 1 The system in is taken as an example to illustrate, including the following steps:

[0116] 601. The sales platform detects a purchase operation for the target software product, and the purchase operation is bound to the second project to be redeveloped.

[0117] Some software purchasers have special needs such as secondary development. In this case, the purchaser can choose the second ordering mode and bind the purchase order to the second project.

[0118] After detecting a purchase operation for the target software product, if it is detected that the purchase order of the target software product is bound to a software development project of the development platform (ie, the second project mentioned above), the user can choose to create a new project on the development platform (eg, DevOps platform) or bind an existing project.

[0119] Upon detecting that the sales platform has completed the purchase operation for the target software product, that is, the payment has been completed, the sales platform can trigger the automatic synchronization function of the component warehouse system to synchronize the software products corresponding to the components of the ordered target software product to the product warehouse of the corresponding development platform, so as to facilitate secondary development based on the development platform.

[0120] 602. Determine software information corresponding to the second item based on the software product information corresponding to the target software product.

[0121] The software information corresponding to the second project includes: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier.

[0122] 603. Send software information corresponding to the second project to the development platform.

[0123] In some embodiments, the software information corresponding to the second project is sent to a development platform and / or a component repository system.

[0124] 604. The development platform determines that the software product corresponding to the second product identifier is not stored locally.

[0125] The development platform can determine, based on the received software information, whether the corresponding software product in the second project has been stored locally.

[0126] The second product identifier is any one or more product identifiers included in the software information corresponding to the second project.

[0127] If the development platform determines that the software product corresponding to the second product identifier is not stored locally, then it is necessary to obtain the software product corresponding to the second product identifier from the component warehouse system.

[0128] 605. The development platform obtains the software product corresponding to the second product identifier from the component warehouse system.

[0129] In some embodiments, if the software product corresponding to the second product identifier is not stored locally, a second synchronization request is sent to the component warehouse system, the second synchronization request carries the second product identifier, and the second synchronization request is used to request the software product corresponding to the second product identifier. Then, the software product corresponding to the second product identifier sent by the component warehouse system is received.

[0130] In some embodiments, the component warehouse system may first obtain software information corresponding to the second project to be redeveloped, then obtain the software product corresponding to the second product identifier corresponding to the second project locally, and finally send the software product corresponding to the second product identifier to the development platform.

[0131] In some embodiments, the component repository system can receive a second synchronization request sent by the development platform, the second synchronization request carries a second product identifier, and the second synchronization request is used to request the software product corresponding to the second product identifier. The software product corresponding to the second product identifier corresponding to the second project can then be obtained locally, and finally the software product corresponding to the second product identifier is sent to the development platform.

[0132] The above-mentioned component warehouse system can support multi-version management of components. Users can repeatedly publish a component, and the component warehouse system saves component information of each version for users to query.

[0133] That is, the software artifacts are synchronized from the component warehouse system to the artifact library of the specified DevOps platform project.

[0134] 606. The development platform performs secondary development based on the existing software products corresponding to the second project.

[0135] After the secondary development project completes software development on the development platform, the software platform can go through the component release process again, select the corresponding secondary development order for delivery, send a secondary development completion message notification to the secondary development orderer, and download the final software component deliverables of the secondary development order from the software mall.

[0136] The above-mentioned re-release process may include but is not limited to: selecting a component warehouse system;

[0137] Modify basic component information: such as component name, version, icon, label and other additional information; modify component artifact list: you can add or delete the original artifact list of the component; after confirming the release, the component enters the release approval process, and after approval, the software artifacts in the component artifact list will be copied from the project artifact library to the artifact library managed by the component warehouse system. Among them, you can see that the component has multiple versions from the component management list.

[0138] With the above-mentioned software information synchronization method, when secondary development is needed, the sales platform can initiate the secondary development process, and the component warehouse system can synchronize the software products corresponding to the secondary development project to the development platform to facilitate the development platform to perform secondary development, thereby improving the efficiency of software development, management, distribution and sales.

[0139] In the above embodiment, a component-based software warehouse system is provided, and an automatic synchronization mechanism between a DevOps platform and a software warehouse based on software components is supported, and a sales platform supporting a secondary development process is also provided.

[0140] like Figure 7 As shown in FIG. 1 , a schematic diagram of implementing the software information synchronization method provided in an embodiment of the present application in an exemplary system. Figure 7 As shown, the example system includes a DevOps platform, a software store, and a component warehouse system, wherein the DevOps platform is a development platform and the software store is a sales platform. The DevOps platform is provided with a project artifact library and a virtual artifact library, and the DevOps platform has a project artifact library management function and a virtual artifact library management function. The virtual artifact library includes multiple shared libraries, such as Figure 7 The shared library 1 and shared library 2 shown in FIG. 1 are used to store different types of software products. The component repository system can be as follows: Figure 3As shown. The software store can call component and product services to read data from the component warehouse system, or the software store can write data to the component warehouse system to obtain the software products of the components corresponding to the software project, and manage the software products in the component warehouse system. Among them, the above-mentioned component and product services are application programming interfaces (Application Programming Interface, API) with open capabilities. In the software information synchronization method provided in the embodiment of the present application, in the release process, after the DevOps platform completes the development of the software project, the software products in the components corresponding to the software project can be synchronized from the project product library to the component warehouse system for storage; in the secondary development process, after purchasing a software product in the software store, the component ordering synchronization project of the software product can be executed, that is, the software products of the components in the software product in the component warehouse system are synchronized to the shared library corresponding to the DevOps platform, so as to provide the DevOps platform for secondary development.

[0141] like Figure 8 As shown, a schematic diagram of an exemplary component generation and secondary development process in an embodiment of the present application.

[0142] like Figure 8 As shown, during the component generation process, the DevOps platform creates a DevOps project, completes the development in the DevOps project, and publishes the developed components. In the release mode, these component contents can be synchronized to the software component warehouse, and then synchronized from the software component warehouse to the software mall to put software products on the shelves, and the software mall sells software products.

[0143] like Figure 8As shown, in the secondary development process, when the software mall detects that the user has ordered a product and chooses to conduct secondary development of the software product in the component of the ordered software product, the software mall can associate the information of the ordered software product with the DevOps platform project (which can be a newly created project, or an existing project), and notify the software component warehouse so that the software component warehouse synchronizes the software product in the component corresponding to the purchased software product to the DevOps project of the DevOps platform, so that the DevOps platform can complete the secondary development. Among them, after the DevOps platform completes the secondary development, the component can be released again. In the delivery mode, the developed component is synchronized with the software component warehouse so that the software component warehouse can deliver the contract, that is, deliver it to the software mall to show it to the user for acceptance. Among them, the above-mentioned component release process can also include a release review process, which can be an online automatic review process or a manual review process. The above-mentioned software component warehouse and the DevOps platform can realize the process of automatic synchronization of products, thereby greatly improving the efficiency of software development and sales.

[0144] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0145] Based on the same inventive concept, the embodiments of the present application also provide a development platform, a component warehouse system, and a sales platform for implementing the software information synchronization method involved above. The implementation solutions provided by the development platform, the component warehouse system, and the sales platform are similar to the implementation solutions recorded in the above method, so the specific limitations in one or more development platform, component warehouse system, and sales platform embodiments provided below can refer to the limitations of the software information synchronization method above, and will not be repeated here.

[0146] In an exemplary embodiment, Fig. 9 As shown, a structural block diagram of a development platform is provided, including:

[0147] A generating module 901 is used to generate software information corresponding to a first project, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier;

[0148] A sending module 902, configured to send the software information corresponding to the first project to a component warehouse system;

[0149] The synchronization module 903 is used to obtain the software product corresponding to the first product identifier from the product library of the first project, and send the software product corresponding to the first product identifier to the component warehouse system. The first product identifier is any one or more product identifiers included in the software information corresponding to the first project.

[0150] In some embodiments, the development platform further includes a receiving module 904 for receiving a first synchronization request sent by the component repository system, wherein the first synchronization request carries the first product identifier, and the first synchronization request is used to request the software product corresponding to the first product identifier.

[0151] In some embodiments, the synchronization module 903 is further used to:

[0152] Acquire software information corresponding to a second project to be redeveloped, the software information corresponding to the second project comprising: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier;

[0153] If the software product corresponding to the second product identifier is not stored locally, obtaining the software product corresponding to the second product identifier from the component warehouse system, wherein the first product identifier is any one or more product identifiers included in the software information corresponding to the second project;

[0154] The development platform also includes:

[0155] The development module 905 is used to perform secondary development based on the existing software product corresponding to the second project.

[0156] In some embodiments, the synchronization module 903 is specifically used to:

[0157] If the software product corresponding to the second product identifier is not stored locally, sending a second synchronization request to the component warehouse system, wherein the second synchronization request carries the second product identifier, and the second synchronization request is used to request the software product corresponding to the second product identifier;

[0158] Receive the software product corresponding to the second product identifier sent by the component warehouse system.

[0159] In an exemplary embodiment, Fig.10 As shown, a structural block diagram of a component warehouse system is provided, including:

[0160] The receiving module 1001 is used to receive software information corresponding to a first project sent by a development platform, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier;

[0161] The synchronization module 1002 is configured to obtain the software product corresponding to the first product identifier from the development platform if the software product corresponding to the first product identifier is not stored locally, wherein the first product identifier is any one or more product identifiers included in the software information corresponding to the first project;

[0162] The publishing module 1003 is used to send a listing request message to a sales platform associated with the component warehouse system, wherein the listing request message includes software information corresponding to the first project.

[0163] In some embodiments, the synchronization module 1002 is specifically used to: send a first synchronization request to the development platform, the first synchronization request carries the first product identifier, and the first synchronization request is used to request the software product corresponding to the first product identifier;

[0164] The software product corresponding to the first product identifier is received and saved.

[0165] In some embodiments, the synchronization module 1002 is further used to: obtain software information corresponding to a second project to be redeveloped, the software information corresponding to the second project including: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier;

[0166] Acquire a software product corresponding to a second product identifier corresponding to the second project from a local computer, where the second product identifier is any one or more product identifiers included in the software information corresponding to the second project;

[0167] The software product corresponding to the second product identifier is sent to the development platform.

[0168] In some embodiments, the receiving module 1001 is further used to: receive a second synchronization request sent by the development platform, the second synchronization request carries the second product identifier, and the second synchronization request is used to request the software product corresponding to the second product identifier.

[0169] In an exemplary embodiment, Fig.11 As shown, a structural block diagram of a sales platform is provided, including:

[0170] The receiving module 1101 is used to receive a listing request message sent by an associated component warehouse system, wherein the listing request message includes software information corresponding to a first project, wherein the software information corresponding to the first project includes: a plurality of component identifiers, each component identifier corresponding to at least one product identifier;

[0171] A generating module 1102 is configured to select at least one component identifier from the plurality of component identifiers; and generate software product information based on the at least one component identifier and at least one product identifier corresponding to each component identifier in the at least one component identifier;

[0172] The display module 1103 is used to display the software product information.

[0173] In some embodiments, the sales platform further includes:

[0174] The determination module 1104 is configured to determine, if a purchase operation for the target software product is detected and the purchase operation is bound to a second project to be secondary developed, software information corresponding to the second project based on the software product information corresponding to the target software product, the software information corresponding to the second project including: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier;

[0175] The sending module 1105 is used to send the software information corresponding to the second project to the development platform and / or the component warehouse system.

[0176] Each module in the above development platform, component warehouse system and sales platform can be implemented in whole or in part by software, hardware and their combination. Each module can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0177] In an exemplary embodiment, a computer device is provided, which may be the above-mentioned development platform, component warehouse system and sales platform. Its internal structure diagram may be as follows: Fig.12As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a software information synchronization method is implemented.

[0178] Those skilled in the art will understand that Fig.12 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0179] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory.

[0180] In the case where the computer device is the above-mentioned development platform, the processor implements the following steps when executing the computer program:

[0181] Generating software information corresponding to the first project, the software information corresponding to the first project comprising: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier;

[0182] sending software information corresponding to the first project to a component warehouse system;

[0183] Acquire a software product corresponding to a first product identifier from the product library of the first project, and send the software product corresponding to the first product identifier to a component warehouse system. The first product identifier is any one or more product identifiers included in the software information corresponding to the first project.

[0184] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0185] After sending the software information corresponding to the first project to the component warehouse system and before acquiring the software product corresponding to the first product identifier from the product library of the first project, the method further includes:

[0186] A first synchronization request sent by the component warehouse system is received, wherein the first synchronization request carries the first product identifier, and the first synchronization request is used to request a software product corresponding to the first product identifier.

[0187] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0188] Acquire software information corresponding to a second project to be redeveloped, the software information corresponding to the second project comprising: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier;

[0189] If the software product corresponding to the second product identifier is not stored locally, obtaining the software product corresponding to the second product identifier from the component warehouse system, wherein the first product identifier is any one or more product identifiers included in the software information corresponding to the second project;

[0190] Conduct secondary development based on the existing software products corresponding to the second project.

[0191] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0192] If the software product corresponding to the second product identifier is not stored locally, obtaining the software product corresponding to the second product identifier from the component warehouse system includes:

[0193] If the software product corresponding to the second product identifier is not stored locally, sending a second synchronization request to the component warehouse system, wherein the second synchronization request carries the second product identifier, and the second synchronization request is used to request the software product corresponding to the second product identifier;

[0194] Receive the software product corresponding to the second product identifier sent by the component warehouse system.

[0195] In the case where the computer device is the above-mentioned component warehouse system, the processor implements the following steps when executing the computer program:

[0196] Receive software information corresponding to a first project sent by a development platform, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier;

[0197] If the software product corresponding to the first product identifier is not stored locally, obtaining the software product corresponding to the first product identifier from the development platform, where the first product identifier is any one or more product identifiers included in the software information corresponding to the first project;

[0198] A listing request message is sent to a sales platform associated with the component warehouse system, wherein the listing request message includes software information corresponding to the first project.

[0199] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0200] If the software product corresponding to the first product identifier is not stored locally, obtaining the software product corresponding to the first product identifier from the development platform includes:

[0201] Sending a first synchronization request to the development platform, wherein the first synchronization request carries the first product identifier, and the first synchronization request is used to request the software product corresponding to the first product identifier;

[0202] The software product corresponding to the first product identifier is received and saved.

[0203] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0204] Acquire software information corresponding to a second project to be redeveloped, the software information corresponding to the second project comprising: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier;

[0205] Acquire a software product corresponding to a second product identifier corresponding to the second project from a local computer, where the second product identifier is any one or more product identifiers included in the software information corresponding to the second project;

[0206] The software product corresponding to the second product identifier is sent to the development platform.

[0207] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0208] Before locally acquiring the software product corresponding to the second product identifier corresponding to the second project, a second synchronization request sent by the development platform is received, the second synchronization request carries the second product identifier, and the second synchronization request is used to request the software product corresponding to the second product identifier.

[0209] In the case where the computer device is the above-mentioned sales platform, the processor implements the following steps when executing the computer program:

[0210] Receiving a listing request message sent by an associated component warehouse system, wherein the listing request message includes software information corresponding to a first project, wherein the software information corresponding to the first project includes: a plurality of component identifiers, each component identifier corresponding to at least one product identifier;

[0211] selecting at least one component identification from the plurality of component identifications;

[0212] generating software product information based on the at least one component identifier and at least one product identifier corresponding to each component identifier in the at least one component identifier;

[0213] Display the software product information.

[0214] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0215] If a purchase operation for the target software product is detected, and the purchase operation is bound to a second project to be secondary developed, then based on the software product information corresponding to the target software product, software information corresponding to the second project is determined, the software information corresponding to the second project including: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier;

[0216] The software information corresponding to the second project is sent to the development platform and / or the component warehouse system.

[0217] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the software information synchronization method implemented by at least one of the development platform, component warehouse system and sales platform in the above embodiment is implemented.

[0218] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements the software information synchronization method implemented by at least one of the development platform, component warehouse system and sales platform in the above-mentioned embodiment.

[0219] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0220] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0221] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A software information synchronization method, characterized in that: Applied to a component warehouse system, the method comprises: Receive software information corresponding to a first project sent by a development platform, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier; If the software product corresponding to the first product identifier is not stored locally, obtaining the software product corresponding to the first product identifier from the development platform, where the first product identifier is any one or more product identifiers included in the software information corresponding to the first project; A listing request message is sent to a sales platform associated with the component warehouse system, wherein the listing request message includes software information corresponding to the first project.

2. The method according to claim 1, characterized in that: If the software product corresponding to the first product identifier is not stored locally, obtaining the software product corresponding to the first product identifier from the development platform includes: Sending a first synchronization request to the development platform, wherein the first synchronization request carries the first product identifier, and the first synchronization request is used to request the software product corresponding to the first product identifier; The software product corresponding to the first product identifier is received and saved.

3. The method according to claim 1, characterized in that The method further comprises: Acquire software information corresponding to a second project to be redeveloped, the software information corresponding to the second project comprising: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier; Acquire a software product corresponding to a second product identifier corresponding to the second project from a local computer, where the second product identifier is any one or more product identifiers included in the software information corresponding to the second project; The software product corresponding to the second product identifier is sent to the development platform.

4. The method according to claim 3, characterized in that Before locally acquiring the software product corresponding to the second product identifier corresponding to the second project, the method further includes: A second synchronization request sent by the development platform is received, wherein the second synchronization request carries the second product identifier, and the second synchronization request is used to request the software product corresponding to the second product identifier.

5. A software information synchronization method, characterized in that: Applied to the development platform, the method comprises: Generating software information corresponding to the first project, the software information corresponding to the first project comprising: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier; sending software information corresponding to the first project to a component warehouse system; Acquire a software product corresponding to a first product identifier from the product library of the first project, and send the software product corresponding to the first product identifier to a component warehouse system. The first product identifier is any one or more product identifiers included in the software information corresponding to the first project.

6. The method according to claim 5, characterized in that After sending the software information corresponding to the first project to the component warehouse system and before acquiring the software product corresponding to the first product identifier from the product library of the first project, the method further includes: A first synchronization request sent by the component warehouse system is received, wherein the first synchronization request carries the first product identifier, and the first synchronization request is used to request a software product corresponding to the first product identifier.

7. The method according to claim 5, characterized in that The method further comprises: Acquire software information corresponding to a second project to be redeveloped, the software information corresponding to the second project comprising: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier; If the software product corresponding to the second product identifier is not stored locally, obtaining the software product corresponding to the second product identifier from the component warehouse system, where the second product identifier is any one or more product identifiers included in the software information corresponding to the second project; Conduct secondary development based on the existing software products corresponding to the second project.

8. The method according to claim 7, characterized in that If the software product corresponding to the second product identifier is not stored locally, obtaining the software product corresponding to the second product identifier from the component warehouse system includes: If the software product corresponding to the second product identifier is not stored locally, sending a second synchronization request to the component warehouse system, wherein the second synchronization request carries the second product identifier, and the second synchronization request is used to request the software product corresponding to the second product identifier; Receive the software product corresponding to the second product identifier sent by the component warehouse system.

9. A software information synchronization method, characterized in that: Applied to a sales platform, the method comprises: Receiving a listing request message sent by an associated component warehouse system, wherein the listing request message includes software information corresponding to a first project, wherein the software information corresponding to the first project includes: a plurality of component identifiers, each component identifier corresponding to at least one product identifier; selecting at least one component identification from the plurality of component identifications; generating software product information based on the at least one component identifier and at least one product identifier corresponding to each component identifier in the at least one component identifier; Display the software product information.

10. The method according to claim 9, characterized in that The method further comprises: If a purchase operation for the target software product is detected, and the purchase operation is bound to a second project to be secondary developed, then based on the software product information corresponding to the target software product, software information corresponding to the second project is determined, the software information corresponding to the second project including: a plurality of component identifiers corresponding to the second project, each component identifier corresponding to at least one product identifier; The software information corresponding to the second project is sent to the development platform and / or the component warehouse system.

11. A development platform, characterized in that: The development platform includes: A generating module, configured to generate software information corresponding to a first project, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier; A sending module, used for sending the software information corresponding to the first project to a component warehouse system; A synchronization module is used to obtain a software product corresponding to a first product identifier from the product library of the first project, and send the software product corresponding to the first product identifier to a component warehouse system. The first product identifier is any one or more product identifiers included in the software information corresponding to the first project.

12. A component warehouse system, characterized in that: The component warehouse system includes: A receiving module, configured to receive software information corresponding to a first project sent by a development platform, wherein the software information corresponding to the first project includes: a plurality of component identifiers corresponding to the first project, each component identifier corresponding to at least one product identifier; a synchronization module, configured to obtain the software product corresponding to the first product identifier from the development platform if the software product corresponding to the first product identifier is not stored locally, wherein the first product identifier is any one or more product identifiers included in the software information corresponding to the first project; A publishing module is used to send a listing request message to a sales platform associated with the component warehouse system, wherein the listing request message includes software information corresponding to the first project.

13. A sales platform, characterized in that: The sales platform includes: A receiving module, configured to receive a shelf request message sent by an associated component warehouse system, wherein the shelf request message includes software information corresponding to a first project, wherein the software information corresponding to the first project includes: a plurality of component identifiers, each component identifier corresponding to at least one product identifier; A generating module, configured to select at least one component identifier from the plurality of component identifiers; and generate software commodity information based on the at least one component identifier and at least one product identifier corresponding to each component identifier in the at least one component identifier; The display module is used to display the software product information.

14. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 10 are implemented.

15. A software information synchronization system, characterized in that: include: A development platform, a component warehouse system and a sales platform, wherein the component warehouse system is used to implement the method as described in any one of claims 1 to 4, the development platform is used to implement the method as described in any one of claims 5 to 8, and the sales platform is used to implement the method as described in claim 9 or 10.

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

Images