Small program operation and maintenance method, equipment and product

Abstract

The invention provides an applet operation and maintenance method, equipment and a product. The applet operation and maintenance method comprises the following steps: in response to an operation and maintenance request for an applet, adding a construction script for constructing a main project and / or a sub-project in the applet in a project root directory of the applet; performing construction processing on the applet by utilizing the construction script to obtain a product package; wherein the product package comprises a code file and a configuration file of the main project and / or the sub-project; performing plate sealing processing on the product package by utilizing the plate sealing script to obtain an applet package and plate sealing information; and performing volume inspection on the applet package and the product package, and releasing the applet on line after the inspection is passed.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and particularly to a method, device, and product for mini-program operation and maintenance. Background Art

[0002] With the development of mini-program technology, it has been applied in more and more scenarios. As a lightweight application program, mini-programs have been widely welcomed and applied since their launch.

[0003] During the development, operation, and maintenance process of mini-programs, mini-programs have to go through many links from development to online launch, such as version sealing, building, and submission for review (review by the background of the mini-program running server), and need to operate on many different platforms, which is very chaotic. Moreover, during the operation and maintenance process, the status notifications of various links such as mini-program building and version sealing are not perfect, and it often depends on the offline communication between developers and testers to promote the development and testing progress of mini-programs, resulting in low efficiency. During the version sealing process, many tasks need to be manually operated, with a relatively large workload and prone to errors. Summary of the Invention

[0004] The present disclosure provides a method, device, and product for mini-program operation and maintenance.

[0005] According to a first aspect of the present disclosure, a method for mini-program operation and maintenance is provided. The method specifically includes: in response to an operation and maintenance request for a mini-program, adding a build script for building the main project and / or sub-projects in the root directory of the mini-program project; using the build script to perform a build process on the mini-program to obtain a product package, where the product package includes code files and configuration files of the main project and / or sub-projects; using a version sealing script to perform a version sealing process on the product package to obtain a mini-program package and version sealing information; performing a volume check on the mini-program package and the product package, and after passing the check, releasing the mini-program online.

[0006] Based on the above, it can be seen that during the mini-program operation and maintenance process, corresponding functional scripts are written for mini-program building and mini-program version sealing respectively. In the operation and maintenance platform, staff only need to provide relevant parameters and information, and do not need to manually participate in building and version sealing, which can effectively improve the efficiency of mini-program operation and maintenance work and avoid errors in the manual operation and maintenance (building, version sealing) of staff.

[0007] According to at least one embodiment of the present disclosure, using the build script to perform a build process on the mini-program to obtain a product package includes: configuring the project information and build parameters of the main project and / or sub-projects on the build configuration page of the operation and maintenance platform; based on the configured project information and build parameters, executing the build script to generate a visual product package.

[0008] After generating a visual product package by executing a build script according to at least one embodiment of the present disclosure, the following steps are further included: displaying detailed information of the product package; the detailed information includes at least one of the product package size, project information, and file size change information; backing up the product package to an operation and maintenance platform; uploading the product package to a running server; obtaining a preview code feedback by the running server; and browsing the applet by identifying the preview code.

[0009] After obtaining a preview code feedback by the running server according to at least one embodiment of the present disclosure, the following steps are further included: starting a valid countdown for the preview code; after the countdown ends, in response to a re-preview request, automatically re-uploading the product package to the running server by using a versioning script; obtaining a preview code feedback by the running server, and starting a valid countdown.

[0010] Executing a build script to generate a visual product package based on the configured project information and build parameters according to at least one embodiment of the present disclosure includes: when performing operation and maintenance processing on multiple applets in the operation and maintenance platform simultaneously, using the build script to perform build processing on a first applet; when using the build script to perform build processing on the first applet, in response to an operation and maintenance request for the main project and / or sub-projects in a second applet, using the build script to perform build processing on the second applet; generating a first product package of the first applet and a second product package of the second applet that are visual.

[0011] Performing versioning processing on the product package by using a versioning script to obtain an applet package and versioning information according to at least one embodiment of the present disclosure includes: backing up the product package to an operation and maintenance platform; inserting the versioning script into a script trigger interface provided by the backed-up product package; in response to a trigger operation on the versioning script, determining the project information of the product package, the iterative branch corresponding to the main project, and the sub-package branches corresponding to the sub-projects; executing the versioning script, and associating multiple sub-package branches to the iterative branch to generate an applet package and versioning information.

[0012] Storing the versioning information in a database for storing historical versioning records according to at least one embodiment of the present disclosure; adding a backtracking index corresponding to the versioning information to a backtracking directory in the order of generation of the versioning information.

[0013] After generating the versioning information according to at least one embodiment of the present disclosure, the following steps are further included: obtaining first identification information of the latest code update of the sub-project; obtaining second identification information of the latest code update of the main project; comparing whether the first identification information and the second identification information are consistent; if they are not consistent, sending a prompt message of missing code to the client.

[0014] Performing volume checks on the applet package and the product package according to at least one embodiment of the present disclosure includes: during the build process, determining the business line to which the product package belongs and the first volume value corresponding to the business line; if the first volume value is greater than the first volume threshold, aborting the build process task; during the versioning process, determining the second volume value of each sub-package in the applet package and the volume increment of each sub-package; if the second volume value is greater than the second volume threshold and / or the volume increment is greater than the increment threshold, aborting the versioning process task; after the applet is launched, determining the access volume of each page in the applet; if the access volume of the target page is less than the access threshold, sending a prompt message to the client to take the target page offline.

[0015] According to a second aspect of the present disclosure, there is provided an electronic device, including: a memory that stores execution instructions; and a processor that executes the execution instructions stored in the memory, such that the processor executes the method described in the first aspect of any one of the embodiments of the present disclosure.

[0016] According to a third aspect of the present disclosure, there is provided a readable storage medium in which execution instructions are stored, and when the execution instructions are executed by a processor, they are used to implement the method described in the first aspect of any one of the embodiments of the present disclosure.

[0017] According to a fourth aspect of the present disclosure, there is provided a computer program product including a computer program, and when the computer program is executed by a processor, it implements the method described in the first aspect of any one of the embodiments of the present disclosure. Description of the Drawings

[0018] The drawings illustrate exemplary embodiments of the present disclosure and, together with the description thereof, are used to explain the principles of the present disclosure. These drawings are included to provide a further understanding of the present disclosure and are included in this specification and form a part of this specification.

[0019] Figure 1 It is a flowchart showing a method for applet operation and maintenance provided by the present disclosure.

[0020] Figure 2 It is a schematic diagram of the interface of the applet operation and maintenance platform illustrated by the present disclosure.

[0021] Figure 3 It is a schematic diagram of the Git repository structure provided by the present disclosure.

[0022] Figure 4 It is a schematic diagram of the build success notification provided by the present disclosure.

[0023] Figure 5 It is a schematic diagram of the build failure notification provided by the present disclosure.

[0024] Figure 6 Structural schematic block diagram of a mini-program operation and maintenance device according to an embodiment of the present disclosure.

[0025] Figure 7 Structural schematic block diagram of an electronic device according to an embodiment of the present disclosure. Detailed implementation manners

[0026] The present disclosure will be further described in detail below with reference to the accompanying drawings and examples. It can be understood that the specific examples described herein are only used to explain the relevant content and do not limit the present disclosure. Additionally, it should be noted that for the sake of convenience of description, only parts related to the present disclosure are shown in the accompanying drawings.

[0027] It should be noted that, without conflict, the embodiments in the present disclosure and the features in the embodiments can be combined with each other. The technical solutions of the present disclosure will be described in detail below with reference to the accompanying drawings and embodiments.

[0028] In the mini-program application scenario, it can meet the application needs of users in a lightweight form. A mini-program is an application that can be used without being downloaded and installed, and has a good cross-platform compatibility effect. However, in subsequent applications, the mini-program still needs to be maintained accordingly. For example, when it is necessary to upgrade the code of a certain sub-package in the mini-program, in order not to affect the normal use of the mini-program, a branch needs to be established and the corresponding sub-project needs to be built. After obtaining the product package, testing is also required, and after the test passes, in order to ensure the safety and reliability of the upgraded sub-package, it also needs to be sealed. However, all the above series of tasks require the cooperation of different staff members. Even for a very simple upgrade, a lot of people need to cooperate with each other, consuming a large amount of manpower and time. In addition, since there are many contents that need to be manually operated by the staff, not only is the efficiency low, but various errors are also likely to occur. Therefore, the present disclosure proposes a solution that can achieve simple and efficient operation and maintenance of the mini-program.

[0029] Term explanation.

[0030] For the sake of convenience of description and to make the technical solutions of the specific implementation manners of the present disclosure easier to understand, before describing the mini-program operation and maintenance method implemented in the present disclosure, the technical terms involved in the specific implementation manners of the present disclosure are explained as follows.

[0031] Mini-program: An application that can be used without being downloaded and installed. It realizes the dream of "applications at your fingertips", and users can open the application by scanning or searching. It also reflects the concept of "use and leave". Users don't need to worry about whether too many applications are installed. Applications will be everywhere and available at any time, but there is no need to install or uninstall them.

[0032] Mini Program Building: Generally refers to a specific process in the development process, which is the process of compiling, linking, and packaging the source code into an executable program or application. The building process may include multiple steps such as code optimization, resource packaging, and dependency management to ensure that the finally generated mini program can run properly on the target platform.

[0033] Mini Program Freezing: Means that the current version of the mini program has been fully tested and is considered stable without serious errors. To ensure the consistency of the user experience and avoid new problems that may be introduced by new versions, the developer or operator decides to stop updating this version for a period of time. This is similar to the "freezing" strategy in traditional software, aiming to reduce the risks that may be brought by version updates.

[0034] Script: Is an executable file written in a specific descriptive language according to a certain format. Scripts are usually saved as text (ASCⅡ) and are only interpreted or compiled when called. When a script is executed, the computer will perform a series of operations. Scripting languages are also known as extended languages or dynamic languages and are a type of programming language used to control software applications.

[0035] Figure 1 It is a flowchart showing a method for mini program operation and maintenance provided by the present disclosure. As Figure 1 shown, the method includes steps 101 to 104. Among them, the method can be executed by an electronic device such as a server running the operation and maintenance platform.

[0036] Specifically, Figure 1 the shown method includes: Step 101: In response to an operation and maintenance request for a mini program, add a build script in the project root directory of the mini program for building the main project and / or sub-projects in the mini program.

[0037] As Figure 2 It is an interface schematic diagram of the mini program operation and maintenance platform illustrated by the present disclosure. The operation and maintenance platform mentioned here is a platform that can comprehensively maintain the running of the mini program and code optimization and other work. And, as Figure 2 can be seen from it, in the interactive interface of this operation and maintenance platform, a development and build module, a release module, a version management module, and a project management module are provided for users.

[0038] Among them, the release module includes a version locking function module, a submission for review function module, and a release record function module. In the version management module, there is an overall volume overview for understanding the overall volume information of the current mini-program; there are also sub-package volume information and business line volume information for analyzing the volume information of the mini-program from the dimensions of sub-packages and business lines respectively, which helps to better guide developers and operators to more accurately control the size of the mini-program and avoid the situation where the mini-program cannot be launched or runs slowly due to excessive volume.

[0039] In Figure 2 it can be seen that in the build interface, users can select the name of the mini-program to be built according to their needs. Users can achieve online building of multiple mini-programs through the operation and maintenance platform. Moreover, previous build records can also be shown to users, including build ID, build branch, build status, build duration, built package volume, and build operator. In addition, preview codes and built product packages are also stored, and users can rebuild based on historical records.

[0040] 102: Use a build script to build the mini-program to obtain a product package; among them, the product package contains code files and configuration files of the main project and / or sub-projects.

[0041] In practical applications, when building a mini-program, it can be divided into main project building and sub-project building. Since the content involved in the mini-program is relatively extensive, during the build operation and maintenance process, the main project and sub-projects usually require different personnel to be responsible. Moreover, a main project contains many branched sub-projects, and in some cases, different personnel are also required to be responsible for different sub-projects.

[0042] In the present disclosure solution, using a build script to build the mini-program can reduce the workload of personnel and also assist in efficient communication between personnel responsible for different projects (such as those responsible for the main project and sub-projects). Moreover, using this build script can not only be used for main project building but also for sub-project building. It makes the cumbersome build work clearly visible (as Figure 2 shown). It can effectively improve the build efficiency.

[0043] Each time a build task is executed, a corresponding product package will be obtained. In this product package, there are code files, configuration files, resource files, etc. of the main project and / or sub-projects participating in operation and maintenance. This product package is used to be uploaded to the background of the running server to implement iterative updates of the mini-program.

[0044] 103: Use a version locking script to perform version locking processing on the product package to obtain a mini-program package and version locking information.

[0045] After obtaining the product package in the manner described above, the mini-program also needs to be tested. After passing the test, the mini-program will be frozen. After freezing, the relevant files of the mini-program will not be allowed to be modified anymore.

[0046] In practical applications, version control software (Git) can be used to manage the versions of mini-programs. For example, Figure 3 is the schematic diagram of the Git repository structure provided by this disclosure. As can be seen from Figure 3 it, the relevant code of the main project is stored in isolation in a Git repository. The relevant code files of the sub-projects are stored in another isolation repository. During the operation and maintenance process, a branch relationship needs to be established separately for each operation and maintenance. That is, the association relationship between the main project and each sub-project needs to be built. As can be seen from Figure 3 it, the subpackages of the main project Git repository are associated with and store each sub-project repository. For example, the second-hand Git repository, the platform Git repository, the new house Git repository, etc. The specific implementation process of freezing will be elaborated in the following embodiments and will not be repeated here.

[0047] 104: Check the volumes of the mini-program package and the product package, and release the mini-program online after passing the check.

[0048] It should be noted that in order to ensure that the mini-program can run in a lightweight and fast manner, each mini-program running server will strictly limit the volume of the mini-program. Since the mini-program does not need to be installed and needs to be loaded every time the user uses it, if the volume of the mini-program is too large, it will cause a long loading time and a slow loading speed, and at the same time, it will also consume more traffic of the user. Therefore, during the operation and maintenance process of the mini-program, the volume of the mini-program needs to be strictly limited. In the solution of this disclosure, the volumes of the mini-program package and the product package will be checked from different dimensions. If the volume check result significantly exceeds the specified threshold, the mini-program will be restricted from going online, and the staff will be reminded to correct it in time. The client here can be understood as the terminal device of the staff, and the interactive interface of the operation and maintenance platform is displayed on the client.

[0049] Based on the above disclosure solution, it can be seen that during the operation and maintenance process of the mini-program, corresponding function scripts are written for the mini-program construction and the mini-program freezing respectively. In the operation and maintenance platform, the staff only needs to provide relevant parameters and information, and does not need to manually participate in the construction and freezing, which can effectively improve the operation and maintenance work efficiency of the mini-program and avoid errors caused by manual operations of the staff.

[0050] In one or more embodiments of the present application, a build script is used to perform a build process on a mini-program to obtain a product package, including: in the configuration page of the build and operation and maintenance platform, configuring the project information and build parameters of the main project and / or sub-projects; based on the configured project information and build parameters, executing the build script to generate a visual product package.

[0051] To facilitate the management of mini-program development and operation and maintenance on the operation and maintenance platform, each mini-program has its own project management directory. First, the build script needs to be added to the root directory of the mini-program project so that the mini-program build can be achieved through the build script. In addition, in the build configuration page, the staff fills in the project information and build parameters. Among them, the project information includes: project name, appId, private key, etc. The build parameters include interface environment, main project branch or sub-project sub-package branch name, version information, etc.

[0052] After the staff fills in the project information and build parameters, the build script is executed to generate a visual product package. The product package may include the following parts: Code files: These include the logical code of the mini-program, such as JavaScript files, which define the behavior and interaction logic of the mini-program. Resource files: These files include multimedia resources such as pictures, audio, and video, as well as font files that may be required. These resource files are used by the mini-program to display to users or provide an interactive experience. Configuration files: Configuration files usually include the page configuration, global configuration, etc. of the mini-program, which define the structure, style, permission settings, etc. of the mini-program. For example, the app.json file defines the global configuration of the mini-program, and the.json file of each page defines the configuration of that page. Compilation products: During the build process, the development tool compiles the source code and resource files into a format that can run on the target platform. These compilation products may include bytecode, binary files, or other platform-specific formats.

[0053] The obtained product package is usually uploaded to the background running server, and then after review, it is released to the mini-program store for users to download and use. In this process, the developer tool of the running server provides a series of build and upload options, such as whether to include the source code, whether to compress the resource files, etc., to help the staff optimize the size and performance of the product package.

[0054] It should be noted that the implementation method of building multiple mini-programs on one operation and maintenance platform mainly relies on cross-platform development frameworks and technologies in modern software development. Such as uni-app and Taro.

[0055] In one or more embodiments of the present disclosure, after executing a build script to generate a visual product package, the following steps are further included: displaying the detailed information of the product package; the detailed information includes at least one of the product package size, project information, and file size change information. Backing up the product package to an operation and maintenance platform; uploading the product package to a running server; obtaining a preview code feedback by the running server; browsing the applet by identifying the preview code.

[0056] After obtaining the product package according to the foregoing solution, in order to enable the staff to intuitively understand the actual situation of the product package, after generating the product package, the detailed information of the product package can be displayed in the interaction interface of the staff client. It includes the total volume size of the product package, the name of the built project, the name of the built project branch, the build environment, and the sizes of each sub-file in the product package. In addition, the volume change amount and the volume change amounts of each sub-file are also displayed.

[0057] When the total volume of the product package does not exceed the limit value, the product package can be uploaded to the running server, and the running server will provide a preview code. After the staff scans the preview code with their client, they can open the applet and browse and use the corresponding applet functions.

[0058] The running server mentioned here can be understood as a server that supports the online operation of the applet.

[0059] The preview code mentioned here is that after the applet is uploaded to the running server and before it is officially run, the staff can preview the online effect first to ensure that there are no problems when users use it. This preview code is generated by the running server and displayed to the staff on the client. The staff can directly open the just-uploaded applet by scanning the code (for example, scanning a QR code) so as to check whether the applet runs normally.

[0060] When using the build script to execute the build task, relevant information of the product package will be collected and externally displayed, eliminating the need for the staff to manually collect and count the relevant information of the product package, which can effectively improve the operation and maintenance efficiency of the applet.

[0061] In one or more embodiments of the present disclosure, after obtaining the preview code feedback by the running server, the following steps are further included: when performing operation and maintenance processing on multiple applets simultaneously in the operation and maintenance platform, or when performing operation and maintenance processing on multiple sub-projects in one applet, after uploading the first product package corresponding to the first applet or the first sub-project to the running server, obtaining the first preview code corresponding to the first product package from the running server; after uploading the second product package corresponding to the second applet or the second sub-project to the running server, obtaining the second preview code corresponding to the second product package from the running server.

[0062] In practical applications, assume that a build task is currently being executed on the first applet or the first sub-project in a certain applet, and a corresponding first product package is generated. After uploading the first product package to the running server, a first preview code for the first product will be automatically generated. Staff can simulate the real state of the applet going live through this first preview code.

[0063] Further, after uploading the second product to the running server, a second preview code corresponding to the second product can be generated. These two preview codes are generated in sequence according to the upload order of the product packages.

[0064] In one or more embodiments of the present disclosure, after obtaining the preview code feedback from the running server, it further includes: starting the effective countdown of the preview code; after the countdown ends, in response to a re-preview request, automatically re-upload the product package to the running server using the version-locked script; obtaining the preview code feedback from the running server, and starting the effective countdown.

[0065] In practical applications, since the running server limits the time allowed for preview each time, this preview time is not enough in the case of more changes. For example, it is valid within 20 minutes. After scanning the code by the staff, they can complete the browsing and trial use of the relevant functions of the applet within the valid time. After expiration, the staff needs to perform the trial use of the functions related to the next preview code (the second preview code). Generally by default, the staff need to modify and upload a new applet package again to generate a preview code again.

[0066] In the solution of the present disclosure, if the preview time is not enough, the staff can trigger a request to re-generate the preview code in the interaction interface of the operation and maintenance platform. The version-locked script will automatically re-upload the applet package again and receive the re-generated QR code from the running server and display it to the user. It does not require the staff to perform cumbersome operations, which can effectively improve the work efficiency of the staff in browsing and checking the applet.

[0067] As described above, when building the applet package, it can be a full-scale build for the main project or a non-full-scale build for the sub-projects and sub-packages. Because in the actual operation and maintenance process, it is not necessarily necessary to modify the main project every time. Sometimes, it may only be necessary to make partial modifications to the sub-projects. In this case, a non-full-scale build can be performed, which can effectively save the build time and improve the work efficiency.

[0068] In one or more embodiments of the present disclosure, a build script is used to perform a build process on a mini-program to obtain a product package. It further includes: when performing operation and maintenance processing on multiple mini-programs in an operation and maintenance platform simultaneously, using the build script to perform a build process on a first mini-program; when using the build script to perform a build process on the first mini-program, in response to an operation and maintenance request for the main project and / or sub-projects in a second mini-program, using the build script to perform a build process on the second mini-program to generate a first product package of the first mini-program and a second product package of the second mini-program that are visualizable.

[0069] In this operation and maintenance platform, it is possible to achieve the build work for multiple mini-programs or multiple sub-projects simultaneously. When performing a build operation, the name of the mini-program to be built currently, the branch name, etc. can be selected on the build configuration page. Since the operation and maintenance platform often takes a certain amount of time (for example, 5 minutes or 10 minutes) to execute a build task. During this period, the staff does not need to wait and can start the build work for another mini-program at the same time.

[0070] For example, when currently using a build script to build a first product package, during the waiting time, the build task for a second product package can be started through the operation and maintenance platform. In an operation and maintenance platform, through this parallel build working mode, the work efficiency of mini-program building can be effectively improved.

[0071] In addition, the build result of the product package will also be notified to the relevant staff in a timely manner through the operation and maintenance platform. For example, if the product package is jointly completed by 10 staff members, the build result will also be notified to these 10 staff members. This saves the offline communication cost of the staff and also avoids the problem that relevant staff are not notified in a timely manner.

[0072] Such as Figure 4 is a schematic diagram of a build success notification provided by the present disclosure. As can be seen from Figure 4 it, after the build is successful, not only each relevant staff member is notified that the build is successful, but also detailed information related to the build will be provided. For example, the build project name, build branch name, build environment, build version, etc. will be displayed. In addition, the volume information of the product package is also provided, including the total volume information, the total volume change information, the sub-file volume information, and the sub-file volume change information.

[0073] Such as Figure 5 is a schematic diagram of a build failure notification provided by the present disclosure. As can be seen from Figure 5As can be seen, after the build fails, relevant staff will be notified of the build failure. The reason for the failure cannot be determined, so each relevant staff member needs to be notified so that the root cause can be identified through targeted troubleshooting. Since the build has failed, only detailed build-related information needs to be displayed, and volume information does not need to be shown. This facilitates the staff to quickly find the cause of the failure.

[0074] For ease of understanding, the following will illustrate the mini-program build process through specific embodiments.

[0075] First, the staff writes a build script for the project that can implement the relevant functions of automatic building. The general build script is hosted on the operation and maintenance platform, and the pulled build script is stored in the project root directory.

[0076] During the operation and maintenance process, the staff can fill in the build parameters on the operation and maintenance platform, click OK, trigger the script pulling, and pull the build script hosted on Polaris to the project root directory. Since the build parameters can be directly filled in on this operation and maintenance platform without the need for professional programming skills or testing capabilities, it is more user-friendly to the staff, and more users can effectively use this operation and maintenance platform.

[0077] The staff can enter project information on the interactive interface of the operation and maintenance platform, including appId, privateKey, etc. In addition, build parameters can also be input on the operation and maintenance platform, including interface environment, sub-package information, version information, etc.

[0078] After executing the build task using the project information and build parameters, a product package is generated, and a visual file size analysis report is generated in the product package, including the overall size of the product package and the sizes of each sub-package. Further, the product package is uploaded to the operation and maintenance platform for backup.

[0079] After the file size analysis report is approved, the file size analysis report can be deleted, the product package is uploaded to the background running server through Continuous Integration (CI), and a preview code is obtained from the running server.

[0080] This preview code can be set with a certain validity period. For example, it is stored in the operation and maintenance platform for 24 hours.

[0081] Based on the above embodiments, by writing a build script, it supports non-research and development personnel to fill in build parameters as needed, and this operation and maintenance platform supports multiple mini-programs to execute build tasks simultaneously. In addition, this operation and maintenance platform can also automatically generate an analysis of the product package volume. In addition, there is a certain probability of failure when uploading the product package to the running server. By caching the product package in advance, it supports the analysis of the cause of failure and retry after failure.

[0082] After the construction of the product package is completed, if the test passes, the relevant files of the mini-program will be sealed in a timely manner. Next, the sealing process of the mini-program will be described in detail through specific embodiments.

[0083] In one or more embodiments of the present disclosure, the product package is sealed using a sealing script to obtain a mini-program package and sealing information, including: backing up the product package to the operation and maintenance platform; inserting the sealing script into the script trigger interface provided by the backed-up product package; in response to the trigger operation on the sealing script, determining the project information of the product package, the iteration branch corresponding to the main project, and the sub-package branch corresponding to the sub-project; executing the sealing script to associate multiple sub-package branches with the iteration branch and generate a mini-program package and sealing information.

[0084] In a version control system (such as Git), a branch is an independent path in the code repository that allows developers to develop, test, and fix bugs without interfering with the main code repository. In this way, new features or modifications can be developed independently on a branch until they are ready to be merged back into the main code repository.

[0085] It should be noted that the branch mentioned in the solution of the present disclosure can be understood as a pointer or reference in the version control system that points to a specific commit in the code repository. It allows developers to work in an environment separated from the main code repository (or another branch).

[0086] The main branch (usually denoted as main or master) is the main path in the code repository and usually contains the most stable and well-tested code. All development branches will eventually be merged back into the main branch. It represents the "official" version of the project and is the benchmark for releasing new versions of the code.

[0087] The sub-package branch is derived from the main branch or other branches and is used to develop specific functions or modules (i.e., sub-packages). The sub-package branch allows developers to focus on specific parts of the project without affecting the development of other parts. They will eventually be merged back into the main branch or the corresponding integration branch. Generally, different sub-package branches are responsible for different staff members.

[0088] Based on the above disclosure solution, through the operation and maintenance platform, steps such as branch creation, sealing operation, and merging are automated and centrally managed, improving efficiency. The information during sealing is recorded and stored, facilitating version backtracking and problem tracking. Generally speaking, the use of branches is a key practice in software project management, and by introducing automated and centralized management tools, the software management efficiency and effect of Git are further optimized.

[0089] In one or more embodiments of the present disclosure, it further includes: storing the versioning information in a database for storing historical versioning records; adding the backtracking index corresponding to the versioning information to the backtracking directory in the order of generation of the versioning information.

[0090] To facilitate the search for historical versioning records, the versioning information needs to be stored in a database. And a corresponding backtracking index is established for each versioning information, that is, each versioning information has a unique index representation to facilitate subsequent backtracking. It should be noted that during the process of establishing the backtracking index and adding the backtracking index to the backtracking directory, no staff intervention is required and it can be automatically executed by the versioning script. This can effectively improve the work efficiency and accuracy of establishing the backtracking directory.

[0091] The following will illustrate the backtracking implementation process through specific embodiments. When executing the versioning task using the versioning script, a unique backtracking index is generated for each versioning information, and this index can be a hash value based on the version number or other unique identifiers.

[0092] Create a backtracking directory (which can also be created in advance) for storing the backtracking index and its corresponding version information. The backtracking directory can be a simple key-value store, where the key is the backtracking index and the value is the version number or other identifiers that can locate the specific versioning information.

[0093] After the versioning information is successfully stored in the database, the backtracking index is generated. The backtracking index and the corresponding version information are added to the backtracking directory. Ensure the atomicity of the update of the backtracking directory and the database storage operation to avoid data inconsistency problems.

[0094] When the staff has a backtracking query requirement, the staff can query the historical versioning records by providing the backtracking index. The system first searches for the corresponding version information in the backtracking directory according to the backtracking index. Then, it retrieves the specific versioning content in the database according to the version information.

[0095] In summary, by improving the storage structure of the versioning information, the design of the backtracking index, and the maintenance of the backtracking directory, an efficient, secure, and easy-to-use backtracking solution can be achieved.

[0096] In one or more embodiments of the present disclosure, after generating the versioning information, it further includes: obtaining the first identification information of the latest code update submitted by the sub-project; obtaining the second identification information of the latest code update submitted by the main project; comparing whether the first identification information and the second identification information are consistent; if they are inconsistent, sending a prompt message of code omission to the client.

[0097] When completing the versioning, it is also necessary to check the code consistency. The following will illustrate the code consistency check process.

[0098] The first identification information and the second identification information mentioned here refer to the commit ID in Git. The commit ID is the unique identifier used to identify each commit in the Git version control system. Each commit generates a unique commit ID, which is usually a 40-digit hexadecimal string generated by the SHA-1 algorithm.

[0099] The main function of the commit ID is to identify the content and changes of each commit, ensuring the uniqueness and traceability of version control. Each commit generates a unique commit ID, which is a 40-digit hexadecimal string generated by the SHA-1 algorithm.

[0100] In practical applications, the Git log command can be used to view the commit history of the subpackage branch corresponding to the current subproject. Each commit will display its ID, author, commit date, and commit message. By specifying the commit ID, the Git show [commit_id] command can be used to view the detailed information of the commit.

[0101] If you know a part of the commit ID, you can use the Git log --grep=[commit_id_keyword] command to search for commit IDs that contain the specified keyword.

[0102] In summary, it can be seen that the commit ID is very important in version control. It not only identifies the content and changes of each commit, but also allows users to roll back to a specified version at any time in the future using the Git reset command. This makes version control more flexible and reliable, facilitating developers to manage and trace the historical changes of the code.

[0103] In practical applications, in order to check whether there are any missing code issues, it is necessary to use the method of comparing commit IDs for inspection.

[0104] In order to compare whether the sub-Git associated commit ID on a regular branch (such as the feature-branch) is consistent with the commit ID of the latest commit on the sub-Git main branch (such as main or master), it can be achieved by using Git commands combined with scripting languages (such as Shell, Python, or Node.js). The following is an example of using a Shell script and Git commands to implement this function. The specific steps are as follows: Switch to the regular branch: Ensure that you are currently on the regular branch and use the Git command to obtain the commit ID of the latest commit on the current branch.

[0105] Next, switch to the master branch to get its latest commit ID. Use the Git command to get the latest commit ID of the master branch. Compare the two commit IDs to see if they are consistent.

[0106] Use commitID to perform consistency checks to ensure that all business codes are correctly included before closing the version to avoid omissions.

[0107] In one or more embodiments of the present disclosure, a volume check is performed on mini-program packages and product packages, including: during the build process, determining the business line to which the product package belongs, and a first volume value corresponding to the business line; if the first volume value is greater than a first volume threshold, terminating the build process task.

[0108] Staff can divide sub-packages according to business line dimensions as needed, and allocate corresponding volume quotas (that is, the first volume threshold) to different business lines. Multiple sub-packages of the same business line can share volume quotas, but if there are product packages with cross-business dependencies, pay attention to configuring additional sub-packages to ensure smooth construction. The first volume threshold for early warning can be set. If the first volume value of a business line exceeds the first volume threshold, the person in charge of the relevant business line will be notified in a targeted manner. Further measures can be taken to interrupt the build, and no preview code will be generated, so as to create test checkpoints and force the business to effectively control the package volume.

[0109] During the closing plate processing, the second volume value of each sub-package in the small program package and the volume increment of each sub-package are determined; if the second volume value is greater than the second volume threshold and / or the volume increment is greater than the increment threshold, the closing plate processing task is terminated.

[0110] After the version is sealed, the mini-program package is uploaded to the running server. After the running server parses and analyzes the mini-program package, it sends the analysis results to the operation and maintenance platform. The analysis results include the second volume value of each sub-package. Next, the operation and maintenance platform will compare the second volume values ​​of different versions of the same sub-package. It can also be made into a volume change trend chart, so that the staff can intuitively understand the volume changes of each sub-package in the historical version.

[0111] If the staff finds that the second volume value is greater than the second volume threshold, or finds that the volume increment is greater than the increment threshold, it is considered that the volume of one or more sub-packages in the current version of the mini program package is too large, seriously affecting the running performance of the mini program, or there is a risk of exceeding the volume upper limit specified by the running server.

[0112] After the mini program is launched, the number of visits to each page in the mini program is determined; if the number of visits to the target page is less than the visit threshold, a prompt message to take the target page offline is sent to the client.

[0113] During subsequent operation and maintenance, the operation and maintenance platform collects information related to the operation of the mini-program from the running servers. This related information includes the overall access volume of the mini-program and the access volume of each page in the mini-program. On the interaction page of the operation and maintenance platform, it can be sorted and displayed according to the access volume of the mini-program.

[0114] In summary, each running server has clear regulations on the size of the mini-program. For example, the running server stipulates that the total file size of its mini-program shall not exceed a certain limit. Staff need to monitor the size of the mini-program to ensure that it complies with the platform regulations and avoid being rejected for release or taken off the shelf due to excessive size. Monitoring the size of the mini-program is considered for multiple aspects such as optimizing the user experience, improving development efficiency, ensuring platform stability, and complying with platform rules. Through size monitoring, developers can continuously optimize the mini-program and improve its quality and performance.

[0115] For the convenience of understanding, the version sealing process will be elaborated below through specific embodiments.

[0116] The version sealing module can efficiently integrate all sub-packages and generate a stable version when preparing for launch. A multi-sub-package mini-program usually contains multiple business modules or functional components, which are divided into different sub-packages. In terms of sub-package code organization, the Git repository of the mini-program source code corresponding to the main and sub-package structures is selected for isolation.

[0117] Git Submodule allows a Git repository to be used as a subdirectory of another Git repository, which is very useful in multi-sub-package mini-programs. Through Git Submodule, sub-packages that do not belong to the platform business can have their own independent Git repositories, thus achieving more independent and free iteration. Each sub-package can be developed and maintained in its independent repository, and the main package can reference these sub-packages through Git Submodule.

[0118] When the mini-program is ready for launch, the staff create an iterative branch in the operation and maintenance platform to integrate all sub-packages. In this iterative branch, the platform side needs to perform a series of operations to associate the branches of numerous sub-packages with the main package. This usually includes updating the references of Git Submodule to ensure that each sub-package points to the correct version.

[0119] Next, the operation and maintenance platform will conduct an overall test to ensure that the integration of all sub-packages in the main package is stable and meets the launch requirements.

[0120] To simplify the version sealing process, the present disclosure solution introduces automated tools and scripts. For example, scripts can be written to automatically update the references of Git Submodule and check whether the code and size of each subpackage meet the requirements. In addition, continuous integration (CI) and continuous deployment (CD) tools can be used to automate the testing and deployment processes to further improve efficiency.

[0121] During the version sealing process, it is necessary to carefully record the versions of each subpackage and the iteration branch information of the main package. This helps to quickly trace back to the correct version when problems occur. At the same time, the tag function of Git can also be used to mark each released version for subsequent management and maintenance.

[0122] In summary, the version sealing module plays a crucial role in multi-subpackage mini-programs. Through reasonable code organization, the application of Git Submodule, and the support of automated tools, it can ensure that the mini-program undergoes a comprehensive and efficient integration process before going online.

[0123] Based on any of the above embodiments, the present disclosure also provides a mini-program operation and maintenance device. This device can be applied to a microservices architecture. Figure 6 It is a structural schematic block diagram of a mini-program operation and maintenance device according to an embodiment of the present disclosure. As Figure 6 shown, the mini-program operation and maintenance device includes: an adding module 61, configured to respond to an operation and maintenance request for a mini-program and add a build script for building the main project and / or sub-projects in the project root directory of the mini-program.

[0124] A building module 62, configured to perform a building process on the mini-program by using the build script to obtain a product package; wherein, the product package includes code files and configuration files of the main project and / or sub-projects.

[0125] A version sealing module 63, configured to perform a version sealing process on the product package by using a version sealing script to obtain a mini-program package and version sealing information.

[0126] An inspection module 64, configured to perform a volume inspection on the mini-program package and the product package, and release the mini-program online after the inspection passes.

[0127] The building module 62 is further configured to configure the project information and build parameters of the main project and / or sub-projects in the build configuration page of the operation and maintenance platform; and execute the build script to generate a visual product package based on the configured project information and build parameters.

[0128] The building module 62 is also used to display the detailed information of the product package; the detailed information includes at least one of the product package size, project information, and file size change information; back up the product package to the operation and maintenance platform; upload the product package to the running server; obtain the preview code feedback by the running server; browse the applet by identifying the preview code.

[0129] The building module 62 is also used to start the valid countdown of the preview code; after the countdown ends, in response to a re-preview request, automatically re-upload the product package to the running server using the versioning script; obtain the preview code feedback by the running server, and start the valid countdown.

[0130] The building module 62 is also used to, when performing operation and maintenance processing on multiple applets in the operation and maintenance platform at the same time, perform building processing on the first applet using the building script; when performing building processing on the first applet using the building script, in response to an operation and maintenance request for the main project and / or sub-project in the second applet, perform building processing on the second applet using the building script; generate the first product package of the first applet and the second product package of the second applet that are visual.

[0131] The versioning module 63 is also used to back up the product package to the operation and maintenance platform; insert the versioning script into the script trigger interface provided by the backed-up product package; in response to a trigger operation on the versioning script, determine the project information of the product package, the iteration branch corresponding to the main project, and the sub-package branch corresponding to the sub-project; execute the versioning script, and generate the applet package and versioning information after associating multiple sub-package branches to the iteration branch.

[0132] The versioning module 63 is used to store the versioning information in a database for storing historical versioning records; add the backtracking index corresponding to the versioning information to the backtracking directory in the order of generation of the versioning information.

[0133] The versioning module 63 is used to obtain the first identification information of the code update submitted by the sub-project most recently; obtain the second identification information of the code update submitted by the main project most recently; compare whether the first identification information and the second identification information are consistent; if they are not consistent, send a prompt message of missing code to the client.

[0134] The inspection module 64 is also used to, during building processing, determine the business line to which the product package belongs, and the first volume value corresponding to the business line; if the first volume value is greater than the first volume threshold, abort the building processing task; during versioning processing, determine the second volume value of each sub-package in the applet package and the volume increment of each sub-package; if the second volume value is greater than the second volume threshold and / or the volume increment is greater than the increment threshold, abort the versioning processing task; after the applet goes online, determine the access volume of each page in the applet; if the access volume of the target page is less than the access threshold, send a prompt message to the client to take offline the target page.

[0135] The implementation processes of the functions and roles of the various modules in the above device are specifically described in the implementation processes of the corresponding steps in the above method, and will not be elaborated here.

[0136] The execution subject of the mini-program operation and maintenance method in the specific implementation manner of the present disclosure can be an electronic device such as a server (including a local server or a cloud server).

[0137] Therefore, based on any of the above embodiments, the present disclosure also provides an electronic device that can execute the mini-program operation and maintenance method of any of the above embodiments described in the present disclosure.

[0138] Figure 7 It is a structural schematic block diagram of an electronic device according to an embodiment of the present disclosure.

[0139] The hardware structure of the electronic device 1000 can be implemented using a bus architecture. The bus architecture can include any number of interconnected buses and bridges, depending on the specific application of the hardware and the overall design constraints. The bus 1100 connects various circuits including one or more processors 1200, a memory 1300, and / or hardware modules together. The bus 1100 can also connect various other circuits 1400 such as peripheral devices, voltage regulators, power management circuits, external antennas, etc.

[0140] The bus 1100 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Component (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one connection line is shown in this figure, but it does not mean that there is only one bus or one type of bus.

[0141] The present disclosure also provides a readable storage medium. A computer program is stored in the readable storage medium, and when the computer program is executed by a processor, it is used to implement the above method. The "readable storage medium" can be any device that can contain, store, communicate, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. More specific examples of the readable storage medium include the following: an electrical connection part (electronic device) having one or more wirings, a portable computer disk cartridge (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable read-only memory (CDROM), etc.

[0142] The present disclosure also provides a computer program product. The method of the present disclosure can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed, the processes or functions of the present disclosure are executed in whole or in part.

[0143] The computer program or instructions can be stored in a readable storage medium, or transmitted from one readable storage medium to another. For example, the computer program or instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The readable storage medium can be any available medium that can be accessed, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc; or it can be a semiconductor medium, such as a solid state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile types of storage media.

[0144] Those skilled in the art should understand that the embodiments of the present disclosure can be provided as a method, system, or computer program product. Therefore, the present disclosure can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present disclosure can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) that contain computer-usable program code.

[0145] The present disclosure is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable small program operation and maintenance devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable small program operation and maintenance devices generate means for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0146] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable apparatus for operation and maintenance to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufacture including an instruction device that implements the functions specified in one process Figure 1 or more processes and / or blocks Figure 1 or more blocks specified in one block or more blocks.

[0147] These computer program instructions can also be loaded onto a computer or other programmable apparatus for operation and maintenance, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one process Figure 1 or more processes and / or blocks Figure 1 or more blocks specified in one block or more blocks.

[0148] In the description of this specification, the descriptions referring to terms such as "one embodiment / way", "some embodiments / ways", "example", "specific example", or "some examples", etc. mean that the specific features, structures, or characteristics described in connection with the embodiment / way or example are included in at least one embodiment / way or example of the present disclosure. In this specification, the schematic expressions of the above terms do not necessarily refer to the same embodiment / way or example. Moreover, the specific features, structures, or characteristics described can be combined in a suitable manner in any one or more embodiments / ways or examples. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments / ways or examples described in this specification and the features of different embodiments / ways or examples.

[0149] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" can explicitly or implicitly include at least one of the features. In the description of the present disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise specifically defined.

[0150] Those skilled in the art should understand that the above embodiments are only for clearly explaining the present disclosure and not for limiting the scope of the present disclosure. For those skilled in the art, other changes or modifications can be made based on the above disclosure, and these changes or modifications are still within the scope of the present disclosure.

Claims

1. A mini program operation and maintenance method, characterized in that: Applied to the operation and maintenance platform, the method includes: In response to an operation and maintenance request for a mini-program, adding a build script for building a main project and / or a sub-project in the mini-program in a project root directory of the mini-program; Using the construction script to construct the mini-program, a product package is obtained; wherein the product package includes the code files and configuration files of the main project and / or sub-project; Using the version sealing script to perform version sealing processing on the product package, and obtain the mini program package and version sealing information; The mini program package and the product package are checked for volume, and the mini program is released online after the check is passed.

2. The method according to claim 1, characterized in that The mini-program is constructed by using the construction script to obtain a product package, including: In the construction configuration page of the operation and maintenance platform, configure the project information and construction parameters of the main project and / or sub-project; Based on the configured project information and the construction parameters, the construction script is executed to generate the visualized product package.

3. The method according to claim 2, characterized in that After executing the construction script to generate the visualized product package, the method further includes: Displaying detailed information of the product package; the detailed information includes: at least one of product package size, project information, and file size change information; Backing up the product package to the operation and maintenance platform; Uploading the product package to the running server; Obtaining the preview code fed back by the running server; The mini program is browsed by identifying the preview code.

4. The method according to claim 3, characterized in that After obtaining the preview code fed back by the running server, the method further includes: Starting a validity countdown for the preview code; After the countdown ends, in response to the preview request, the product package is automatically re-uploaded to the running server using the cover script; Obtain the preview code fed back by the running server and start the effective countdown.

5. The method according to claim 2, characterized in that: Based on the configured project information and the construction parameters, executing the construction script to generate the visualized product package includes: When the operation and maintenance platform is simultaneously operating and maintaining multiple mini-programs, the first mini-program is constructed and processed using the construction script; When the first applet is constructed by using the construction script, in response to an operation and maintenance request for a main project and / or a sub-project in the second applet, the second applet is constructed by using the construction script; Generate a visualized first product package of the first applet and a second product package of the second applet.

6. The method according to claim 1, characterized in that The method of using the sealing script to seal the product package to obtain the mini program package and sealing information includes: Backing up the product package to the operation and maintenance platform; Insert the version-closing script into the script triggering interface provided by the backup product package; In response to the triggering operation of the version closing script, determining the project information of the product package, the iteration branch corresponding to the main project, and the sub-package branch corresponding to the sub-project; The version closing script is executed to associate the plurality of sub-package branches with the iteration branch, thereby generating the small program package and the version closing information.

7. The method according to claim 6, characterized in that Also includes: Storing the cover information in a database for storing historical cover records; The backtracking index corresponding to the cover information is added to the backtracking directory according to the generation order of the cover information.

8. The method according to claim 6, characterized in that After generating the cover information, it also includes: Get the first identification information of the latest code update submitted by the sub-project; Get the second identification information of the latest code update submitted by the main project; comparing whether the first identification information and the second identification information are consistent; If they are inconsistent, a code missing prompt message will be sent to the client.

9. The method according to claim 1, characterized in that: The checking the volumes of the mini-program package and the product package includes: During the construction process, determining the business line to which the product package belongs and the first volume value corresponding to the business line; If the first volume value is greater than a first volume threshold, terminating the construction processing task; During the plate sealing process, determining the second volume value of each sub-package in the mini-program package and the volume increment of each sub-package; If the second volume value is greater than a second volume threshold and / or the volume increment is greater than an increment threshold, terminating the plate sealing processing task; After the mini program is launched, determining the number of visits to each page in the mini program; If the number of visits to the target page is less than the visit threshold, a prompt message to log off the target page is sent to the client.

10. An electronic device, characterized in that: include: A memory storing execution instructions; as well as A processor, wherein the processor executes the execution instructions stored in the memory, so that the processor executes the method according to any one of claims 1 to 9.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images