Iterative upgrading method, device and equipment for products and projects and storage medium

Abstract

The invention discloses a product and project iterative upgrading method, which comprises the following steps: obtaining product version information, and creating a basic code file according to the product version information; uploading the basic code file to a code library; when a code file acquisition request is received, calling the basic code file from the code library and returning the basic code file to a request sending end of the code file acquisition request; receiving a function packet returned by the request sending end; wherein the function package is created by the request sending end based on the basic code file; and pushing the function package to the code library, so that the product development end calls the function package from the code library to carry out product iteration upgrading and / or the project development end calls the function package from the code library to carry out project iteration upgrading. The project production delivery efficiency is improved, the development cost is reduced, and the system stability is improved. The invention further discloses a product and project iterative upgrading device and equipment and a storage medium, which have corresponding technical effects.

Description

Technical Field

[0001] The present application relates to the field of software development technology, and in particular to a method, device, equipment and computer-readable storage medium for iterative upgrading of products and projects. Background Art

[0002] Enterprises use basic software products to provide information construction services to similar customers. How a product basic platform can quickly and effectively meet the needs of multiple projects is the key to the core competitiveness of software companies.

[0003] Product iteration and project implementation are very important processes. In the software development process, iterative upgrades of products and projects are common requirements. Traditional iterative upgrade methods often require modifications to the product source code, which not only increases development costs, but may also lead to a decrease in system stability. In the implementation of software projects, each project has its own needs and has specialized customized content. As time goes by, the individual requirements of the project become increasingly different from the product and require larger changes. The special functions of the project cannot be extracted separately and quickly synchronized to the product, and cannot be applied to other similar projects. As a result, multiple projects have duplicated functions, wasting resources and time and reducing efficiency.

[0004] To sum up, how to effectively solve the problems of the iterative upgrade methods of current products and projects, such as high development cost, low system stability, serious waste of resources and time, and low iterative upgrade efficiency, is an issue that technical personnel in this field urgently need to solve. Summary of the invention

[0005] The purpose of this application is to provide a method for iterative upgrading of products and projects, which improves the efficiency of project production delivery, reduces development costs, and improves system stability; another purpose of this application is to provide an iterative upgrading device, equipment and computer-readable storage medium for products and projects.

[0006] In order to solve the above technical problems, this application provides the following technical solutions:

[0007] A product and project iterative upgrade method, comprising:

[0008] Obtain product version information, and create a basic code file according to the product version information;

[0009] Upload the basic code file to the code library;

[0010] When receiving a code file acquisition request, retrieving the basic code file from the code library and returning it to the request sender of the code file acquisition request;

[0011] Receiving a function package returned by the request sending end; wherein the function package is a function package created by the request sending end based on the basic code file;

[0012] The function package is pushed to the code library, so that the product development end retrieves the function package from the code library for product iteration upgrade and / or the project development end retrieves the function package from the code library for project iteration upgrade.

[0013] In a specific implementation of the present application, creating a basic code file according to the product version information includes:

[0014] The basic code file is created using the React basic component according to the product version information.

[0015] In a specific implementation of the present application, when the request sending end is a product development end, receiving the function package returned by the request sending end includes:

[0016] Receiving a first product function package and / or a first project function package returned by the product development end;

[0017] Correspondingly, the function package is a function package created by the request sending end based on the basic code file, including:

[0018] The first product function package and / or the first project function package is a function package created by the product development end based on the basic code file;

[0019] Accordingly, pushing the function package to the code library so that the product development end retrieves the function package from the code library for product iteration and upgrade and / or the project development end retrieves the function package from the code library for project iteration and upgrade, includes:

[0020] The first product function package and / or the first project function package is pushed to the code library, so that the product development end retrieves the first product function package and / or the first project function package from the code library for product iteration and upgrade, and / or the project development end retrieves the first product function package and / or the first project function package from the code library for project iteration and upgrade.

[0021] In a specific implementation of the present application, when the request sending end is a project development end, receiving the function package returned by the request sending end includes:

[0022] Receiving a second product function package and / or a second project function package returned by the project development end;

[0023] Correspondingly, the function package is a function package created by the request sending end based on the basic code file, including:

[0024] The second product function package and / or the second project function package is a function package created by the project development end based on the basic code file;

[0025] Accordingly, pushing the function package to the code library so that the product development end retrieves the function package from the code library for product iteration and upgrade and / or the project development end retrieves the function package from the code library for project iteration and upgrade, includes:

[0026] The second product function package and / or the second project function package is pushed to the code library, so that the product development end retrieves the second product function package and / or the second project function package from the code library for product iteration and upgrade, and / or the project development end retrieves the second product function package and / or the second project function package from the code library for project iteration and upgrade.

[0027] In a specific implementation of the present application, a process of creating the function package is also included, and the process of creating the function package includes:

[0028] According to the basic code file, a function package is created by creating a new JS file, configuring routing, configuring forms, and filling in one or more of business logic.

[0029] In a specific implementation of the present application, pushing the function package to the code library includes:

[0030] The function package is pushed to the code base through the Git project management tool, and the function package version is released.

[0031] In a specific implementation of the present application, the product development end retrieves the function package from the code library to perform product iteration upgrade and / or the project development end retrieves the function package from the code library to perform project iteration upgrade, including:

[0032] The product development end retrieves the function package from the code base through the Git project management tool to perform product iteration and upgrade, and / or the project development end retrieves the function package from the code base through the Git project management tool to perform project iteration and upgrade.

[0033] An iterative upgrade device for products and projects, comprising:

[0034] A basic code file creation module, used to obtain product version information and create a basic code file according to the product version information;

[0035] A basic code file uploading module, used to upload the basic code file to the code library;

[0036] A basic code file returning module, used for, when receiving a code file acquisition request, retrieving the basic code file from the code library and returning it to the request sending end of the code file acquisition request;

[0037] A function package receiving module, used for receiving the function package returned by the request sending end; wherein the function package is a function package created by the request sending end based on the basic code file;

[0038] The function package push module is used to push the function package to the code library so that the product development end retrieves the function package from the code library for product iteration and upgrade and / or the project development end retrieves the function package from the code library for project iteration and upgrade.

[0039] An iterative upgrade device for products and projects, including:

[0040] Memory for storing computer programs;

[0041] A processor is used to implement the steps of the iterative upgrade method for products and projects as described above when executing the computer program.

[0042] A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the iterative upgrade method for products and projects as described above.

[0043] The iterative upgrade method for products and projects provided in the present application obtains product version information and creates a basic code file based on the product version information; uploads the basic code file to a code library; when a code file acquisition request is received, retrieves the basic code file from the code library and returns it to the request sender of the code file acquisition request; receives a function package returned by the request sender; wherein the function package is a function package created by the request sender based on the basic code file; pushes the function package to the code library, so that the product development end retrieves the function package from the code library for product iterative upgrade and / or the project development end retrieves the function package from the code library for project iterative upgrade.

[0044] It can be seen from the above technical solution that by creating a basic code file according to the product version information and uploading it to the code library, the basic code file can be directly retrieved from the code library to create the required function package. By creating the required function package and using the code library to uniformly manage each function package, modular product management is achieved. By using the basic code file as the product skeleton and creating function packages based on the basic code file, products and projects can be iteratively upgraded between products and projects with less operation and modification of source code, thereby improving project production delivery efficiency, reducing development costs, and improving system stability.

[0045] Correspondingly, the present application also provides iterative upgrade devices, equipment and computer-readable storage media for products and projects corresponding to the iterative upgrade methods of the above-mentioned products and projects, which have the above-mentioned technical effects and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] 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.

[0047] Figure 1 This is an implementation flow chart of the iterative upgrade method of products and projects in the embodiments of the present application;

[0048] Figure 2 Another implementation flow chart of the iterative upgrade method of products and projects in the embodiment of the present application;

[0049] Figure 3 A swimlane diagram of mutual references between product project modules in an embodiment of the present invention;

[0050] Figure 4 This is a structural block diagram of an iterative upgrade device for a product and project in an embodiment of the present application;

[0051] Figure 5 This is a structural block diagram of an iterative upgrade device for a product and project in an embodiment of the present application;

[0052] Figure 6 A schematic diagram of the specific structure of an iterative upgrade device for a product and project provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0054] See also Figure 1 , Figure 1 This is an implementation flow chart of the iterative upgrade method of products and projects in the embodiment of the present application. The method may include the following steps:

[0055] S101: Obtain product version information, and create a basic code file according to the product version information.

[0056] Software products have their corresponding product version information, and different versions of software products have different corresponding basic code files. Get the product version information and create a basic code file based on the product version information. The created basic code file can be used as the basic foundation of the product skeleton.

[0057] S102: Upload the basic code file to the code library.

[0058] A code library is established in advance. After the basic code file is created, the basic code file is uploaded to the code library, and the code library is used to store the basic code file, so that it is convenient to directly retrieve the basic code file from the code library later.

[0059] S103: When a code file acquisition request is received, a basic code file is retrieved from the code library and returned to the request sender of the code file acquisition request.

[0060] When the request sender needs to obtain the basic code file, it sends a code file acquisition request to the iteration upgrade management center. When the iteration upgrade management center receives the code file acquisition request, it retrieves the basic code file from the code library and returns it to the request sender of the code file acquisition request.

[0061] The request sending end includes the product development end and the project development end.

[0062] The iterative upgrade management center may be a processor, a controller, etc. that has established communication connections with both the request sender and the code library.

[0063] S104: Receive the function package returned by the request sender.

[0064] The function package is a function package created by the request sender based on the basic code file.

[0065] After receiving the basic code file returned by the iteration and upgrade management center, the request sender creates a function package based on the basic code file. For example, when the request sender is a product development end, the product development end creates a product function package or a project function package based on the basic code file. When the request sender is a project development end, the project development end creates a project function package based on the basic code file. After creating the function package, the request sender returns the created function package to the iteration and upgrade management center, and the iteration and upgrade management center receives the function package returned by the request sender.

[0066] S105: Push the function package to the code base, so that the product development end retrieves the function package from the code base for product iteration and upgrade and / or the project development end retrieves the function package from the code base for project iteration and upgrade.

[0067] After receiving the function package returned by the request sender, the iteration upgrade management center pushes the function package to the code library, so that the product development end can call the function package from the code library for product iteration upgrade, and the project development end can also call the function package from the code library for project iteration upgrade.

[0068] It can be seen from the above technical solution that by creating a basic code file according to the product version information and uploading it to the code library, the basic code file can be directly retrieved from the code library to create the required function package. By creating the required function package and using the code library to uniformly manage each function package, modular product management is achieved. By using the basic code file as the product skeleton and creating function packages based on the basic code file, products and projects can be iteratively upgraded between products and projects with less operation and modification of source code, thereby improving project production delivery efficiency, reducing development costs, and improving system stability.

[0069] It should be noted that, based on the above embodiments, the embodiments of the present application also provide corresponding improved solutions. In the subsequent embodiments, the same steps or corresponding steps as those in the above embodiments can be referenced to each other, and the corresponding beneficial effects can also be referenced to each other, which will not be repeated one by one in the following improved embodiments.

[0070] See also Figure 2 , Figure 2 This is another implementation flow chart of the iterative upgrade method of products and projects in the embodiment of the present application. The method may include the following steps:

[0071] S201: Obtain product version information, and create a basic code file using React basic components according to the product version information.

[0072] After obtaining the product version information, use the React basic components to create the basic code files according to the product version information. By setting the product front end based on React, the componentized features of React are fully utilized to facilitate the creation of basic code files.

[0073] S202: Upload the basic code file to the code library.

[0074] S203: When a code file acquisition request is received, a basic code file is retrieved from the code library and returned to the request sender of the code file acquisition request.

[0075] S204: Receive the function package returned by the request sender.

[0076] The function package is a function package created by the request sender based on the basic code file.

[0077] S205: Push the function package to the code base through the Git project management tool, and release the function package version, so that the product development end can call the function package from the code base through the Git project management tool to perform product iteration and upgrade, and / or the project development end can call the function package from the code base through the Git project management tool to perform project iteration and upgrade.

[0078] After receiving the function package returned by the request sender, the function package is pushed to the code base through the Git project management tool (git cherry-pick), and the function package version is released, that is, the function package is submitted and released through the Git commit and push commands, so that the product development end can call the function package from the code base through the Git project management tool for product iteration and upgrade, and the project development end can also call the function package from the code base through the Git project management tool for project iteration and upgrade. The created function package can be used as a filler for the basic base composed of basic code files, so as to achieve iterative upgrades of products or projects. By using Git for management, products and projects can achieve iterative upgrades between products and projects on the basis of less operation and modification of source code. New function points are added to the product, and the project is updated synchronously. New function points are added to the project and synchronized to the product, which can be applied to the next project. The cost of repeated function development is reduced in the project, the project delivery efficiency is improved, and the coupling between product and project business modules is reduced.

[0079] In addition, SVN may also be used to manage function packages, which is not limited in the embodiments of the present application.

[0080] In a specific implementation of the present application, when the request sender is a product development end, receiving the function package returned by the request sender may include the following steps:

[0081] Receiving a first product function package and / or a first project function package returned by a product development end;

[0082] Correspondingly, the function package is a function package created by the request sender based on the basic code file, and may include:

[0083] The first product function package and / or the first project function package is a function package created by the product development end based on the basic code file;

[0084] Accordingly, pushing the function package to the code base so that the product development end retrieves the function package from the code base for product iteration and upgrade and / or the project development end retrieves the function package from the code base for project iteration and upgrade may include the following steps:

[0085] The first product function package and / or the first project function package is pushed to the code library, so that the product development end retrieves the first product function package and / or the first project function package from the code library for product iteration and upgrade, and / or the project development end retrieves the first product function package and / or the first project function package from the code library for project iteration and upgrade.

[0086] For the convenience of description, the above steps can be combined for explanation.

[0087] When the request sender is the product development end, after receiving the basic code file returned by the iterative upgrade management center, the product development end may create only a product function package based on the basic code file, or only a project function package based on the basic code file, or both a product function package and a project function package. The product function package created by the product development end may be recorded as the first product function package, and the project function package created by the product development end may be recorded as the first project function package. After creating the first product function package and / or the first project function package, the product development end returns the created first product function package and / or the first project function package to the upgrade management center. The upgrade management center receives the first product function package and / or the first project function package returned by the product development end.

[0088] After receiving the first product function package and / or the first project function package returned by the product development end, the upgrade management center pushes the first product function package and / or the first project function package to the code base, so that the product development end can retrieve the first product function package and / or the first project function package from the code base for product iteration upgrade, and the project development end can also retrieve the first product function package and / or the first project function package from the code base for project iteration upgrade. When only the first product function package is needed during the upgrade, only the corresponding first product function package is retrieved from the code base; when only the first project function package is needed during the upgrade, only the corresponding first project function package is retrieved from the code base; when both the first product function package and the first project function package are needed during the upgrade, the corresponding first product function package and the corresponding first project function package are retrieved from the code base.

[0089] The product development end retrieves the basic code file to create the corresponding first product function package and / or first project function package, and uploads the created first product function package and first project function package to the code library for unified management, so that other subsequent product development ends and project development ends can directly reference them from the code library, thereby realizing modular management of product and project iteration upgrades and improving project production delivery efficiency.

[0090] In a specific implementation of the present application, when the request sender is a project development end, receiving the function package returned by the request sender may include the following steps:

[0091] Receiving a second product function package and / or a second project function package returned by the project development end;

[0092] Correspondingly, the function package is a function package created by the request sender based on the basic code file, including:

[0093] The second product function package and / or the second project function package is a function package created by the project development end based on the basic code file;

[0094] Accordingly, pushing the function package to the code base so that the product development end retrieves the function package from the code base for product iteration and upgrade and / or the project development end retrieves the function package from the code base for project iteration and upgrade may include the following steps:

[0095] The second product function package and / or the second project function package are pushed to the code library, so that the product development end retrieves the second product function package and / or the second project function package from the code library for product iteration and upgrade, and / or the project development end retrieves the second product function package and / or the second project function package from the code library for project iteration and upgrade.

[0096] When the request sender is the project development end, after receiving the basic code file returned by the iterative upgrade management center, the project development end can create only a product function package based on the basic code file, or only a project function package based on the basic code file, or both a product function package and a project function package. The product function package created by the project development end can be recorded as a second product function package, and the project function package created by the project development end can be recorded as a second project function package. After creating the second product function package and / or the second project function package, the project development end returns the created second product function package and / or the second project function package to the upgrade management center. The upgrade management center receives the second product function package and / or the second project function package returned by the project development end.

[0097] After receiving the second product function package and / or second project function package returned by the project development end, the upgrade management center pushes the second product function package and / or second project function package to the code base, so that the product development end retrieves the second product function package and / or second project function package from the code base for product iteration upgrade, and the project development end can also retrieve the second product function package and / or second project function package from the code base for project iteration upgrade. When only the second product function package is needed during the upgrade, only the corresponding second product function package is retrieved from the code base; when only the second project function package is needed during the upgrade, only the corresponding second project function package is retrieved from the code base; when both the second product function package and the second project function package are needed during the upgrade, the corresponding second product function package and the corresponding second project function package are retrieved from the code base.

[0098] The project development end retrieves the basic code file to create the corresponding second product function package and / or second project function package, and uploads the created second product function package and second project function package to the code library for unified management, so that other subsequent product development ends and project development ends can directly reference them from the code library, thereby realizing modular management of product and project iteration upgrades and improving project production delivery efficiency.

[0099] In a specific implementation of the present application, the method may further include a process of creating a function package, and the process of creating the function package may include the following steps:

[0100] Create a function package based on the basic code file by creating a new JS file, configuring routing, configuring forms, and filling in one or more of the business logic.

[0101] After obtaining the basic code file, the request sender creates a function package according to the basic code file by creating a new JS file, configuring routing, configuring forms, and filling in one or more of the business logic, thereby improving the diversity of the created function package.

[0102] See also Figure 3 , Figure 3 This is a swimlane diagram of mutual references between product project modules in an embodiment of the present invention. The basic code files of the product version are uploaded to the GitLab code base, and the branch name is prodcut-1.0. The basic code files of prodcut-1.0 are pulled down from the GitLab code base to the product development end, and a product function package is built and pushed to the GitLab code base. The product function package is encoded as prodcut-1.0-A. If there are multiple product function packages, they are named prodcut-1.0-B, prodcut-1.0-C, and so on. The basic code files of the project version are uploaded to the GitLab code base, and the branch name is project-1.0. Project-1.0 is based on prodcut-1.0, and the contents are consistent at the beginning. Pull the code files of project-1.0 from the GitLab code base to the project development end. The project retrieves the product function package list as prodcut-1.0-A (or prodcut-1.0-B or prodcut-1.0-C). Through the Git project management tool (the submission record of prodcut-1.0-A), the project project-1.0 integrates the product function package prodcut-1.0-A (or prodcut-1.0-B or prodcut-1.0-C). Based on project-1.0+prodcut-1.0-A, the project development end builds a new function package project-1.0-A and pushes it to the GitLab code base. The prodcut-1.0+prodcut-1.0-A on the product development end enables the product integration project to package project-1.0-A through the Git project management tool. At this time, the product has prodcut-1.0+prodcut-1.0-A+project-1.0-A. If the function in the project is not universal, it does not need to be integrated into the product. If the project releases project-1.0-B and does not need to be synchronized with the product, the version released by the project is project-1.0+prodcut-1.0-A+project-1.0-A+project-1.0-B.

[0103] Corresponding to the above method embodiments, the present application also provides an iterative upgrade device for products and projects. The iterative upgrade device for products and projects described below and the iterative upgrade method for products and projects described above can refer to each other.

[0104] See also Figure 4 , Figure 4 This is a structural block diagram of an iterative upgrade device for a product and project in an embodiment of the present application, and the device may include:

[0105] A basic code file creation module 41 is used to obtain product version information and create a basic code file according to the product version information;

[0106] A basic code file uploading module 42 is used to upload the basic code file to the code library;

[0107] The basic code file returning module 43 is used to retrieve the basic code file from the code library and return it to the request sending end of the code file obtaining request when receiving the code file obtaining request;

[0108] The function package receiving module 44 is used to receive the function package returned by the request sending end; wherein the function package is a function package created by the request sending end based on the basic code file;

[0109] The function package push module 45 is used to push the function package to the code library, so that the product development end retrieves the function package from the code library for product iteration and upgrade and / or the project development end retrieves the function package from the code library for project iteration and upgrade.

[0110] It can be seen from the above technical solution that by creating a basic code file according to the product version information and uploading it to the code library, the basic code file can be directly retrieved from the code library to create the required function package. By creating the required function package and using the code library to uniformly manage each function package, modular product management is achieved. By using the basic code file as the product skeleton and creating function packages based on the basic code file, products and projects can be iteratively upgraded between products and projects with less operation and modification of source code, thereby improving project production delivery efficiency, reducing development costs, and improving system stability.

[0111] In a specific implementation of the present application, the basic code file creation module is specifically a module that creates basic code files using React basic components according to product version information.

[0112] In a specific implementation of the present application, the function package receiving module is specifically a module for receiving the first product function package and / or the first project function package returned by the product development end when the request sending end is the product development end; wherein the first product function package and / or the first project function package is a function package created by the product development end based on the basic code file;

[0113] The function package push module specifically pushes the first product function package and / or the first project function package to the code library, so that the product development end retrieves the first product function package and / or the first project function package from the code library for product iteration and upgrade, and / or the project development end retrieves the first product function package and / or the first project function package from the code library for project iteration and upgrade.

[0114] In a specific implementation of the present application, the function package receiving module is specifically a module for receiving the second product function package and / or the second project function package returned by the project development end when the request sending end is the project development end; wherein the second product function package and / or the second project function package is a function package created by the project development end based on the basic code file;

[0115] The function package push module specifically pushes the second product function package and / or the second project function package to the code library, so that the product development end retrieves the second product function package and / or the second project function package from the code library for product iteration and upgrade, and / or the project development end retrieves the second product function package and / or the second project function package from the code library for project iteration and upgrade.

[0116] In a specific embodiment of the present application, the device may also include a function package creation module, which is specifically a module that creates a function package according to the basic code file by creating a new JS file, configuring routing, configuring forms, and filling in one or more of business logic.

[0117] In a specific implementation of the present application, the function package push module is specifically a module that pushes the function package to the code library through the Git project management tool and releases the function package version.

[0118] In a specific embodiment of the present application, the function package push module is specifically a module that pushes the function package to the code library, so that the product development end can call the function package from the code library through the Git project management tool to perform product iteration and upgrade, and / or the project development end can call the function package from the code library through the Git project management tool to perform project iteration and upgrade.

[0119] Corresponding to the above method embodiment, see Figure 5 , Figure 5 A schematic diagram of the iterative upgrade device for the products and projects provided in this application, which may include:

[0120] A memory 332, for storing computer programs;

[0121] The processor 322 is used to implement the steps of the iterative upgrade method for products and projects of the above method embodiment when executing the computer program.

[0122] For details, please refer to Figure 6 , Figure 6A specific structural diagram of an iterative upgrade device for a product or project provided in this embodiment, which may have relatively large differences due to different configurations or performances, may include a processor (central processing units, CPU) 322 (for example, one or more processors) and a memory 332, and the memory 332 stores one or more computer programs 342 or data 344. Among them, the memory 332 may be a temporary storage or a permanent storage. The program stored in the memory 332 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the data processing device. Furthermore, the processor 322 may be configured to communicate with the memory 332 to execute a series of instruction operations in the memory 332 on the iterative upgrade device 301 for products or projects.

[0123] The product and project iterative upgrade device 301 may also include one or more power supplies 326 , one or more wired or wireless network interfaces 350 , one or more input and output interfaces 358 , and / or one or more operating systems 341 .

[0124] The steps in the iterative upgrade method for products and projects described above can be implemented by the structure of the iterative upgrade device for products and projects.

[0125] Corresponding to the above method embodiment, the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the following steps can be implemented:

[0126] Obtain product version information and create a basic code file based on the product version information; upload the basic code file to the code library; when a code file acquisition request is received, retrieve the basic code file from the code library and return it to the request sender of the code file acquisition request; receive the function package returned by the request sender; wherein the function package is a function package created by the request sender based on the basic code file; push the function package to the code library, so that the product development end retrieves the function package from the code library for product iteration and upgrade and / or the project development end retrieves the function package from the code library for project iteration and upgrade.

[0127] The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0128] For an introduction to the computer-readable storage medium provided in this application, please refer to the above method embodiment, and this application will not go into details here.

[0129] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the devices, equipment and computer-readable storage media disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0130] Specific examples are used herein to illustrate the principles and implementation methods of the present application, and the description of the above embodiments is only used to help understand the technical solution and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the present application.

Claims

1. A method for iterative upgrading of products and projects, characterized in that: include: Obtain product version information, and create a basic code file according to the product version information; Upload the basic code file to the code library; When receiving a code file acquisition request, retrieving the basic code file from the code library and returning it to the request sender of the code file acquisition request; Receiving a function package returned by the request sending end; wherein the function package is a function package created by the request sending end based on the basic code file; The function package is pushed to the code library, so that the product development end retrieves the function package from the code library for product iteration upgrade and / or the project development end retrieves the function package from the code library for project iteration upgrade.

2. The iterative upgrade method for products and projects according to claim 1, characterized in that: Create a basic code file according to the product version information, including: The basic code file is created using the React basic component according to the product version information.

3. The iterative upgrade method for products and projects according to claim 1, characterized in that: When the request sending end is a product development end, receiving the function package returned by the request sending end includes: Receiving a first product function package and / or a first project function package returned by the product development end; Correspondingly, the function package is a function package created by the request sending end based on the basic code file, including: The first product function package and / or the first project function package is a function package created by the product development end based on the basic code file; Accordingly, pushing the function package to the code library so that the product development end retrieves the function package from the code library for product iteration and upgrade and / or the project development end retrieves the function package from the code library for project iteration and upgrade, includes: The first product function package and / or the first project function package is pushed to the code library, so that the product development end retrieves the first product function package and / or the first project function package from the code library for product iteration and upgrade, and / or the project development end retrieves the first product function package and / or the first project function package from the code library for project iteration and upgrade.

4. The iterative upgrade method for products and projects according to claim 1, characterized in that: When the request sending end is a project development end, receiving the function package returned by the request sending end includes: Receiving a second product function package and / or a second project function package returned by the project development end; Correspondingly, the function package is a function package created by the request sending end based on the basic code file, including: The second product function package and / or the second project function package is a function package created by the project development end based on the basic code file; Accordingly, pushing the function package to the code library so that the product development end retrieves the function package from the code library for product iteration and upgrade and / or the project development end retrieves the function package from the code library for project iteration and upgrade, includes: The second product function package and / or the second project function package is pushed to the code library, so that the product development end retrieves the second product function package and / or the second project function package from the code library for product iteration and upgrade, and / or the project development end retrieves the second product function package and / or the second project function package from the code library for project iteration and upgrade.

5. The iterative upgrade method for products and projects according to claim 1, characterized in that: The invention also includes a process of creating the function package, wherein the process of creating the function package includes: According to the basic code file, a function package is created by creating a new JS file, configuring routing, configuring forms, and filling in one or more of business logic.

6. The iterative upgrade method for products and projects according to claim 1, characterized in that: Pushing the function package to the code repository includes: The function package is pushed to the code base through the Git project management tool, and the function package version is released.

7. The iterative upgrade method for products and projects according to claim 1, characterized in that: The product development end retrieves the function package from the code library to perform product iteration upgrade and / or the project development end retrieves the function package from the code library to perform project iteration upgrade, including: The product development end retrieves the function package from the code base through the Git project management tool to perform product iteration and upgrade, and / or the project development end retrieves the function package from the code base through the Git project management tool to perform project iteration and upgrade.

8. A device for iterative upgrading of products and projects, characterized in that: include: A basic code file creation module, used to obtain product version information and create a basic code file according to the product version information; A basic code file uploading module, used to upload the basic code file to the code library; A basic code file returning module, used for, when receiving a code file acquisition request, retrieving the basic code file from the code library and returning it to the request sending end of the code file acquisition request; A function package receiving module, used for receiving the function package returned by the request sending end; wherein the function package is a function package created by the request sending end based on the basic code file; The function package push module is used to push the function package to the code library so that the product development end retrieves the function package from the code library for product iteration and upgrade and / or the project development end retrieves the function package from the code library for project iteration and upgrade.

9. An iterative upgrade device for products and projects, characterized in that: include: Memory for storing computer programs; A processor, used to implement the steps of the iterative upgrade method for products and projects as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the iterative upgrade method for products and projects as described in any one of claims 1 to 7.

Images