CN111142884B - Version deployment method and device of applet, electronic equipment and storage medium - Google Patents
Version deployment method and device of applet, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111142884B CN111142884B CN201911274244.8A CN201911274244A CN111142884B CN 111142884 B CN111142884 B CN 111142884B CN 201911274244 A CN201911274244 A CN 201911274244A CN 111142884 B CN111142884 B CN 111142884B
- Authority
- CN
- China
- Prior art keywords
- applet
- version
- code
- version deployment
- deployment request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000006835 compression Effects 0.000 claims abstract description 24
- 238000007906 compression Methods 0.000 claims abstract description 24
- 238000011161 development Methods 0.000 claims description 20
- 230000006837 decompression Effects 0.000 claims description 7
- 238000011981 development test Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 9
- 238000007726 management method Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure relates to a version deployment method, device, electronic equipment and storage medium of an applet, comprising: receiving a version deployment request of an applet sent by a platform client, wherein the version deployment request carries a download address of the applet; downloading the corresponding branch code compression packet according to the download address; decompressing the branch code compression packet to obtain an actual compiled code; and calling a preset interface to instruct a developer tool deployed in the server to acquire the actual compiled code, and deploying the applet according to the actual compiled code. On one hand, the platform client interacts with the developer tool to replace the developer tool of the manual operation applet, so that the time cost of development test can be effectively reduced; on the other hand, by integrating an automation flow oriented to the branch code at the platform client, the risk of version deployment misoperation can be effectively reduced.
Description
Technical Field
The disclosure relates to the field of computer technology, and in particular, to a method and a device for deploying versions of applets, electronic equipment and a storage medium.
Background
Today, the development rules and development ecology of the applet prove the own innovation and value with time and events.
At present, because the applet is limited by development ecology and development environment, the development, release and other processes of the applet are strongly dependent on local developer tools of the developer, and especially the test and release processes, the developer is required to manually construct, submit codes and other operations in the local place through the developer tools. For example, when an experience version applet needs to be uploaded, it is typically required that: (1) compiling the code locally; (2) Opening a locally installed developer tool, in which the compiled project is opened; (3) triggering an uploading instruction; (4) inputting information such as a relevant version number; and (5) triggering a completion instruction to complete release of the experience edition. However, each release in the related art requires a developer to manually operate one time, which has a problem of excessively high time cost.
Disclosure of Invention
The disclosure provides a version deployment method, device, electronic equipment and storage medium of an applet, so as to at least solve the problem of overhigh time cost of deploying the applet in the related technology. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a version deployment method of an applet, applied to a server, including:
receiving a version deployment request of an applet sent by a platform client, wherein the version deployment request carries a download address of the applet;
downloading the corresponding branch code compression packet according to the download address;
decompressing the branch code compression packet to obtain an actual compiled code;
and calling a preset interface to instruct a developer tool deployed in the server to acquire the actual compiled code, and deploying the applet according to the actual compiled code.
In one embodiment, before the step of receiving the version deployment request of the applet sent by the platform client, the method further includes:
acquiring branch submitting information of the applet in the starting process of the platform client;
sending the branch submitting information to a page of a platform client for display;
and acquiring a compiled file generated by compiling the applet, wherein the compiled file comprises a download address, and the branch submitting information and the compiled file have an association relation.
In one embodiment, the download address carried by the version deployment request is the download address in the compiled file associated with the selected branch commit information.
In one embodiment, the version deployment request is a development preview version deployment request; the method comprises the steps of instructing a developer tool deployed in a server to obtain actual compiled codes by calling a preset interface, and deploying the applet according to the actual compiled codes, wherein the steps comprise:
by calling the preview interface, a developer tool is instructed to preview an actual compiled code, and a two-dimensional code character string is generated;
acquiring a two-dimensional code character string returned by a developer tool;
and sending the two-dimensional code character string to a page of the platform client to display the corresponding two-dimensional code.
In one embodiment, the version deployment request is an experience version deployment request, and the experience version deployment request also carries version information of the applet; the method comprises the steps of instructing a developer tool deployed in a server to obtain actual compiled codes by calling a preset interface, and deploying the applet according to the actual compiled codes, wherein the steps comprise:
and by calling the uploading interface, the developer tool is instructed to acquire the actual compiled code, and the actual compiled code is uploaded to complete the deployment of the experience version applet corresponding to the version information.
According to a second aspect of the embodiments of the present disclosure, there is provided an applet version deployment apparatus, comprising:
the receiving module is configured to execute a version deployment request of the applet sent by the receiving platform client, wherein the version deployment request carries a download address of the applet;
a download module configured to execute downloading of the corresponding branch code compression packet according to the download address;
the decompression module is configured to execute decompression of the branch code compression packet to obtain an actual compiled code;
and the interface calling module is configured to execute the operation of calling a preset interface, instruct a developer tool deployed in the server to acquire actual compiled codes, and deploy the applet according to the actual compiled codes.
In one embodiment, the apparatus further comprises:
the acquisition module is configured to acquire branch submission information of the applet in the starting process of the platform client;
the sending module is configured to execute sending the branch submitting information to a page of the platform client for displaying;
the acquisition module is further configured to execute a compiled file of the acquisition applet, the compiled file including a download address, the branch commit information and the compiled file having an association.
In one embodiment, the version deployment request is a development preview version deployment request; the interface calling module is configured to instruct a developer tool to preview an actual compiling code by calling a preview interface so as to generate a two-dimensional code character string;
the acquisition module is further configured to execute acquisition of the two-dimensional code character string returned by the developer tool;
and the sending module is further configured to send the two-dimension code character string to a page of the platform client to display the corresponding two-dimension code.
In one embodiment, the version deployment request is an experience version deployment request; and the interface calling module is also configured to instruct a developer tool to acquire the actual compiled code by calling the uploading interface, upload the actual compiled code and complete the deployment of the experience version applet corresponding to the version information.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:
a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute instructions to implement the applet version deployment method according to any one of the first aspects.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the version deployment method of the applet as described in any one of the first aspects.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product implementing the steps of the version deployment method of the applet as described in any one of the first aspects, when said computer program product is executed on a processor.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
downloading a corresponding branch code compression packet according to a download address carried in a version deployment request sent by a platform client, and decompressing to obtain an actual compiled code; and calling a preset interface to instruct a developer tool deployed in the server to acquire the actual compiled code, so that the developer tool deploys the applet according to the actual compiled code. On one hand, the platform client interacts with the developer tool to replace the developer tool of the manual operation applet, so that the time cost of development test can be effectively reduced; on the other hand, by integrating an automation flow oriented to the branch code at the platform client, the risk of version deployment misoperation can be effectively reduced.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is an application environment diagram illustrating a version deployment method of an applet, according to an exemplary embodiment;
FIG. 2 is a flowchart illustrating a method of version deployment of an applet, according to an exemplary embodiment;
FIG. 3 is a flowchart illustrating one method of obtaining branch commit information and compiled files in accordance with an exemplary embodiment;
FIG. 3a is a schematic diagram showing the display of branch commit information on a platform client page, according to an example embodiment;
FIG. 4 is a flowchart illustrating a version deployment of a develop preview applet, according to an exemplary embodiment;
FIG. 4a is a schematic diagram showing a development preview version of a two-dimensional code displayed on a platform client page, according to an example embodiment;
FIG. 5 is a flowchart illustrating a method of version deployment of an applet, according to an exemplary embodiment;
FIG. 6 is a block diagram of an applet version deployment apparatus, shown in accordance with an exemplary embodiment;
fig. 7 is a block diagram of an apparatus according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the embodiments described in the following exemplary examples do not represent all embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
The version deployment method of the applet provided by the disclosure can be applied to an application environment as shown in fig. 1. The application environment includes a platform client 110 and a server 120. Platform client 110 communicates with server 120 over a network. The server 120 has a developer tool deployed therein. The server 120 may be built by using a node, js, java, etc. programming language, and is configured to receive an operation request sent by the platform client 110, and operate a developer tool on the server 120 under a corresponding condition. Specifically, the server 120 receives a version deployment request of the applet sent by the platform client 110, where the version deployment request carries a download address of the applet; the server 120 downloads the corresponding branch code compression packet according to the download address; the server 120 decompresses the branch code compression packet to obtain an actual compiled code; by calling a preset interface, a developer tool deployed in the server 120 is instructed to acquire the actual compiled code, and the applet is deployed according to the actual compiled code. The platform client 110 may be, but not limited to, various personal computers, notebook computers, smartphones, tablet computers, and portable wearable devices, and the server 120 may be implemented by a server or a server cluster formed by a plurality of servers.
Fig. 2 is a flowchart illustrating a method for deploying versions of an applet, according to an exemplary embodiment, as shown in fig. 1, the method for deploying versions of an applet is applied to the server 120 in fig. 1, and includes the following steps:
in step S100, a version deployment request of the applet, which is sent by the platform client, is received, where the version deployment request carries a download address of the applet.
In step S200, the corresponding branch code compression packet is downloaded according to the download address.
The download address is used for enabling the server to acquire the branch code compression packet to be deployed. Specifically, the download address may be input by the user, or obtained by browsing the designated address, or searched according to information association such as a commit id (commit identifier) generated when the branch code is submitted, which is not limited herein. The version deployment request may be triggered by the user through the platform client, for example, clicking a virtual button displayed on the platform client. After receiving the version deployment request, the platform client sends the version deployment request to the server, so that the server can download the branch code compression package of the applet needing version deployment according to the download address in the version deployment request. The download branch code compression packet may operate, but is not limited to, over an IO (input output) stream.
In step S300, the branch code compression packet is decompressed to obtain the actual compiled code.
Wherein the actual compiled code may refer to actual executable code. Specifically, since the downloaded branch code compression packet cannot be directly used for execution, the server needs to decompress the branch code compression packet to obtain the actually executable branch code. The decompression mode may be, but is not limited to, decompression through an IO stream.
In step S400, a developer tool deployed in the server is instructed to obtain an actual compiled code by calling a preset interface, and the applet is deployed according to the actual compiled code.
In this embodiment, the developer tool may be set to open the service port in advance. By opening the service port, interfaces such as command lines or HTTP services of the developer tool can be called, so that operations on the platform client are converted into operations such as opening the developer tool, opening projects, logging in, previewing and uploading through the server through the command lines or HTTP requests. Specifically, after decompressing to obtain the actual compiled code, the server may send a related command line or HTTP request to a developer tool deployed on the server, and instruct the developer tool to perform a corresponding operation on the applet by calling a corresponding interface. For example, if the request received by the server is a preview request, the server may instruct the developer tool to preview the actual compiled code by calling the preview interface; the received request is an upload request, and then the server may instruct the developer tool to upload the actual compiled code by calling an upload interface, which is not further described herein.
FIG. 3 is a flowchart illustrating a method for retrieving branch commit information and compiled files, according to an example embodiment. As shown in fig. 3, the method comprises the following steps:
in step S302, during the start-up of the platform client, branch commit information of the applet is acquired.
In step S304, the branch commit information is sent to the page of the platform client for display.
The starting process of the platform client may refer to a process of opening or logging in the platform. Branch commit information may refer to a historical gitmergerrequest record of the applet. Git is an open-source distributed version control system that can efficiently handle project version management from very small to very large at high speed. Specifically, the server may perform an initialization operation during a startup process of the platform client. In a first aspect of the initialization operation, the branch commit information of the applet can be obtained through the GitLab (a web service that is an open source project for the warehouse management system, uses Git as a code management tool, and builds on this basis) interface. After acquiring the historical branch submission information of the applet, the server side can send the branch submission information to the platform client side, and display the branch submission information on a page of the platform client side. FIG. 3a is a schematic diagram illustrating branch commit information displayed on a platform client page in an exemplary embodiment.
In step S306, a compiled file of the applet is acquired, the compiled file including a download address, and the branch commit information and the compiled file have an association relationship.
The compiled file may refer to output information corresponding to a certain submission of the branch. Specifically, in the second aspect of the server side initialization, the output information of each branch submission can be obtained through a preset interface (the preset interface can be set according to actual requirements), where the output information can further include a "commit-id" generated when the branch code is submitted, and a commit identifier. Each time the branch code is committed using the git, a commit-id may be generated, which may be made up of a 40-bit hash value. The branch commit information obtained in the first aspect of initialization and the yield information of the branch obtained in the second aspect can be associated through the commit-id.
In the above embodiment, the server side obtains the accurate branch submitting information and the corresponding branch compiled file from the GitLab interface and the preset interface defined according to the actual requirement in the initialization process, so that the version of the applet will not couple with the local compiling result of the developer, thereby avoiding that some codes which are not synchronized to the git are issued due to the error operation of the developer, and ensuring the accuracy of the deployment of the applet version.
In an exemplary embodiment, the download address carried by the version deployment request is the download address in the compiled file associated with the selected branch commit information.
Specifically, continuing to refer to fig. 3a, the server may send the acquired historical multiple branch commit information (corresponding to the yield version in fig. 3 a) to the platform client for display. The obtained branch commit information may be all historical commit information corresponding to the applet, or may be commit information of a preset number (for example, 100) or a preset time period (for example, within 1 month), which is not limited herein. The user may select branch commit information to be deployed through the platform client, for example, through a drop down menu of the platform client. After the corresponding branch commit information is selected, the version deployment request acquired by the platform client carries a download address corresponding to the selected branch commit information. In this embodiment, by displaying multiple historical branch submission information of the branch-oriented compilation on the platform client page, a user can roll back any historical version according to actual requirements, so that the user can freely select and control the branch submission version to be used.
FIG. 4 is a flowchart illustrating a version deployment of a develop preview applet, according to an exemplary embodiment. As shown in fig. 4, by calling a preset interface, a developer tool deployed in a server is instructed to obtain the actual compiled code, and deploy the applet according to the actual compiled code, including the following steps:
in step S410, the developer tool is instructed to preview the actual compiled code by calling the preview interface, and a two-dimensional code string is generated.
Specifically, a development preview applet may be used for internal testing. In the related art, when a development preview applet is required, a developer is usually required to manually upload an actual compiled code using a developer tool, and trigger the uploading in the developer tool to develop a preview instruction, which instructs the developer tool to generate a two-dimensional code for testing. Generally, the two-dimensional code is time-efficient (for example, effective for 20 minutes), so that the development of the preview applet in the related art brings much extra workload to the developer. In this embodiment, when the version deployment request acquired by the server is a version deployment request for developing a preview version, after the server decompresses to acquire an actual compiled code, the server may automatically send a "preview request" to the developer tool in a manner of calling a command line or an HTTP service interface, etc., and instruct the developer tool to preview the actual compiled code through the preview interface.
In step S420, a two-dimensional code string returned by the developer tool is acquired.
In step S430, the two-dimensional code character string is sent to the page of the platform client to display the corresponding two-dimensional code.
Specifically, after the developer tool obtains the command line or the HTTP request sent by the server, the actual compiled code may be previewed through a preview interface, so as to generate a corresponding two-dimensional code, where the format of the two-dimensional code may be a base64 string, a picture, or the like. And the developer tool sends the generated two-dimensional code to the server. After receiving the two-dimension code, the server returns the two-dimension code to the page of the platform client for display. Fig. 4a is a schematic diagram showing a two-dimensional code of a development preview version displayed on a platform client page in an exemplary embodiment.
In the above embodiment, after the developer submits the branch code, the tester may select the compiled file of the development branch to issue the development preview version by himself, without communicating with the developer to obtain the two-dimensional code. The developer does not need to perform compiling operation and provide two-dimensional codes for the testers continuously, so that huge time cost and communication cost are saved for the developer and the testers.
In an exemplary embodiment, the version deployment request is an experience version deployment request, and the experience version deployment request further carries version information of the applet; the method includes the steps that a preset interface is called, a developer tool deployed in a server side is instructed to obtain actual compiled codes, and the applet is deployed according to the actual compiled codes, and the method comprises the following steps: and by calling the uploading interface, the developer tool is instructed to acquire the actual compiled code, and the actual compiled code is uploaded to complete the deployment of the experience version applet corresponding to the version information.
Specifically, when the version deployment request acquired by the server is the version deployment request of the experience version, after decompressing to acquire the actual compiled code, the server can automatically send an uploading request to a developer tool in a mode of calling a command line or an HTTP service interface and the like, instruct the developer tool to acquire the actual compiled code, and upload the actual compiled code to a background where the parent program is located or the server, thereby completing the deployment of the experience version of the applet. The parent program refers to an application program for running an applet, such as an instant messaging application program, a mobile payment program, and the like. The parent program may display the pages of the applet by loading the applet code. Further, in this embodiment, when the experience version applet is deployed, the user may also input version information of the applet to be deployed through a page of the platform client, where the version information includes a version number and a corresponding version description, so that an experimenter can learn specific information of the experienced applet.
FIG. 5 is a version deployment method of an applet, according to an exemplary embodiment. As shown in fig. 5, the method comprises the following steps:
in step 501, a developer tool deployed in a server is set, and a service port of the developer tool is opened.
In step 502, a server is built. The server can be built by adopting programming languages such as node.
In step 503, the platform client boots up.
In step 504, during the start-up process of the platform client, the server performs an initialization operation.
Specifically, the initialization operation includes two aspects. In a first aspect, branch commit information for an applet is obtained. Multiple branch commit information of the history commit may be obtained through a gitlab interface. Second, a history compiled file of the applet is obtained, the compiled file including the download address, and branch commit information and the compiled file can be associated by commit-id generated at the time of commit of the branch code.
In step 505, the server sends the branch commit information to the page of the platform client for display.
In step 506, the user triggers a branch commit message that selects the branch code.
In step 507, the platform client obtains a version deployment request for a development preview version of the user-triggered applet. The download address carried by the version deployment request is the download address in the compiled file associated with the selected branch commit information.
In step 508, the server receives the version deployment request of the development preview version sent by the platform client.
In step 509, the server downloads the corresponding branch code compression packet according to the selected branch commit information and the corresponding download address.
In step 510, the server decompresses the component code compression packet to obtain the actual compiled code.
In step 511, the server sends a preview request to the developer tool, invoking the developer tool's preview interface.
In step 512, the developer tool obtains the actual compiled code according to the preview request, and generates a corresponding two-dimensional code.
In step 513, the developer tool sends the two-dimensional code to the server.
In step 514, the server sends the two-dimensional code to the page of the platform client for displaying.
In step 515, the platform client obtains a version deployment request for the experience version of the applet. The version deployment request also carries version information and download addresses of the applet.
In step 516, the server receives a version deployment request of the experience version sent by the platform client. The server may repeat steps 509 and 510 to obtain the actual compiled code.
In step 517, the server sends an upload experience version request to the developer tool, invoking the upload interface of the developer tool.
In step 518, the developer tool uploads the obtained actual compiled code according to the request for uploading the experience version, and completes deployment of the experience version applet corresponding to the version information.
FIG. 6 is a block diagram of an applet version deployment device, according to an exemplary embodiment. Referring to fig. 6, the apparatus includes a receiving module 601 downloading module 602, a decompressing module 603, and an interface calling module 604.
The receiving module 601 is configured to execute a version deployment request of the applet sent by the receiving platform client, where the version deployment request carries a download address of the applet;
the download module 602 is configured to execute downloading the corresponding branch code compression packet according to the download address;
the decompression module 603 is configured to perform decompression on the component code compression packet to obtain an actual compiled code;
the interface calling module 604 is configured to execute an instruction to a developer tool deployed in the server to obtain the actual compiled code by calling a preset interface, and deploy the applet according to the actual compiled code.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
FIG. 7 is a block diagram illustrating an apparatus 700 for version deployment of applets, according to an exemplary embodiment. For example, the apparatus 700 may be provided as a server. Referring to fig. 7, apparatus 700 includes a processing component 722 that further includes one or more processors and memory resources represented by memory 732 for storing instructions, such as applications, executable by processing component 722. The application programs stored in memory 732 may include one or more modules that each correspond to a set of instructions. Further, the processing component 722 is configured to execute instructions to perform the version deployment method of the applet described above.
The apparatus 700 may further comprise a power component 726 configured to perform power management of the apparatus 700, a wired or wireless network interface 750 configured to connect the apparatus 700 to a network, and an input output (I/O) interface 758. The apparatus 700 may operate based on an operating system stored in memory 732, such as windowservertm, macOS XTM, unixTM, linuxTM, freeBSDTM, or the like.
In an exemplary embodiment, a storage medium is also provided, such as a memory 732, comprising instructions executable by a processor of the apparatus 700 to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. The utility model provides a version deployment method of an applet, which is characterized in that the method is applied to a server, a developer tool corresponding to the applet is deployed in the server in advance, the developer tool is preset to open a service port, and the local operation originally executed on a platform client is converted into the automatic execution operation through the server by opening the service port, and the method comprises the following steps:
receiving a version deployment request of an applet sent by a platform client, wherein the version deployment request carries a download address of the applet, and the version deployment request comprises a development preview version deployment request and an experience version deployment request;
downloading the corresponding branch code compression packet according to the downloading address;
decompressing the branch code compression packet to obtain an actual compiled code;
the developer tool deployed in the server is instructed to acquire the actual compiling code by calling a preset interface of the developer tool, and deployment corresponding to the called interface is performed on the applet according to the actual compiling code;
and when the version deployment request is a development preview version deployment request, the step of instructing a developer tool deployed in a server to acquire the actual compiled code and deploy the applet according to the actual compiled code by calling a preset interface includes:
the developer tool is instructed to preview the actual compiling code by calling a preview interface, and a two-dimensional code character string is generated;
acquiring the two-dimensional code character string returned by the developer tool;
and sending the two-dimensional code character string to a page of the platform client to display the corresponding two-dimensional code.
2. The method for deploying an applet version according to claim 1, wherein before the step of receiving the applet version deployment request sent by the platform client, further comprises:
acquiring branch submitting information of the applet in the starting process of the platform client;
the branch submitting information is sent to a page of the platform client for display;
and acquiring a compiled file generated by compiling the applet, wherein the compiled file comprises the download address, and the branch submitting information and the compiled file have an association relation.
3. The applet version deployment method according to claim 2, wherein the download address carried by the version deployment request is a download address in a compiled file associated with selected branch commit information.
4. The applet version deployment method as in claim 1, wherein the version deployment request is an experience version deployment request, the experience version deployment request also carrying version information of the applet; the step of instructing a developer tool deployed in a server to obtain the actual compiled code and deploying the applet according to the actual compiled code by calling a preset interface includes:
and by calling an uploading interface, the developer tool is instructed to acquire the actual compiled code, and the actual compiled code is uploaded to complete the deployment of the experience version applet corresponding to the version information.
5. A version deployment device of an applet, applied to a server, in which a developer tool corresponding to the applet is deployed in advance, the developer tool being preset to open a service port, and by opening the service port, converting a local operation originally performed on a platform client into an operation automatically performed by the server, the device comprising:
the receiving module is configured to execute a version deployment request of an applet sent by a receiving platform client, wherein the version deployment request carries a download address of the applet, and the version deployment request comprises a development preview version deployment request and an experience version deployment request;
a download module configured to execute downloading of the corresponding branch code compression packet according to the download address;
the decompression module is configured to decompress the branch code compression packet to obtain an actual compiled code;
the interface calling module is configured to execute an interface of the developer tool which is preset by calling, instruct the developer tool deployed in the server to acquire the actual compiling code, and deploy the applet corresponding to the called interface according to the actual compiling code;
when the version deployment request is a development preview version deployment request, the interface calling module is configured to instruct the developer tool to preview the actual compiled code by calling a preview interface to generate a two-dimensional code character string; the apparatus further comprises: the acquisition module is further configured to acquire the two-dimensional code character string returned by the developer tool; and the sending module is further configured to send the two-dimension code character string to the page of the platform client to display the corresponding two-dimension code.
6. The applet version deployment apparatus of claim 5, wherein the acquisition module is configured to acquire branch commit information of the applet during a boot process of the platform client;
the sending module is configured to send the branch submitting information to the page of the platform client for display;
the acquisition module is further configured to perform acquisition of a compiled file generated by compiling the applet, the compiled file including the download address, and the branch commit information and the compiled file having an association relationship.
7. The applet version deployment apparatus as in claim 6, wherein the version deployment request carries a download address in the compiled file associated with the selected branch commit information.
8. The applet version deployment device of claim 5, wherein the version deployment request is an experience version deployment request, the experience version deployment request also carrying version information of the applet; the interface calling module is further configured to instruct the developer tool to obtain the actual compiled code by calling an uploading interface, upload the actual compiled code, and complete deployment of the experience version applet corresponding to the version information.
9. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the applet version deployment method according to any one of claims 1 to 4.
10. A storage medium, characterized in that instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the version deployment method of the applet according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911274244.8A CN111142884B (en) | 2019-12-12 | 2019-12-12 | Version deployment method and device of applet, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911274244.8A CN111142884B (en) | 2019-12-12 | 2019-12-12 | Version deployment method and device of applet, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111142884A CN111142884A (en) | 2020-05-12 |
| CN111142884B true CN111142884B (en) | 2024-03-26 |
Family
ID=70518044
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911274244.8A Active CN111142884B (en) | 2019-12-12 | 2019-12-12 | Version deployment method and device of applet, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111142884B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111737139A (en) * | 2020-06-28 | 2020-10-02 | 深圳前海微众银行股份有限公司 | Method and device for generating preview two-dimensional code of applet |
| JP2022542203A (en) | 2020-06-28 | 2022-09-30 | ベイジン バイドゥ ネットコム サイエンス テクノロジー カンパニー リミテッド | Mini-program batch processing method, device, electronic device and readable storage medium |
| CN112558982B (en) * | 2020-12-23 | 2024-06-21 | 平安银行股份有限公司 | Code detection method and device and computer equipment |
| CN112558985B (en) * | 2021-02-23 | 2021-08-27 | 鲁班(北京)电子商务科技有限公司 | Sub-application deployment method and device |
| CN113268266B (en) * | 2021-05-19 | 2024-02-02 | 上海视九信息科技有限公司 | Multi-version coexistence management method, system and medium for applet rendering framework |
| CN113835745A (en) * | 2021-08-30 | 2021-12-24 | 蔚星科技有限公司 | Workflow-based WeChat applet development and delivery method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104793946A (en) * | 2015-04-27 | 2015-07-22 | 广州杰赛科技股份有限公司 | Application deployment method and system based on cloud computing platform |
| CN106104467A (en) * | 2014-06-30 | 2016-11-09 | 北京新媒传信科技有限公司 | A kind of Automation arranging method and terminal |
| CN108897547A (en) * | 2018-06-27 | 2018-11-27 | 北京神州泰岳软件股份有限公司 | A kind of software automatic deployment and device |
| CN110377290A (en) * | 2019-07-22 | 2019-10-25 | 阿里巴巴集团控股有限公司 | A kind of method, device and equipment of purpose project compiling |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8683430B2 (en) * | 2011-01-07 | 2014-03-25 | International Business Machines Corporation | Synchronizing development code and deployed executable versioning within distributed systems |
-
2019
- 2019-12-12 CN CN201911274244.8A patent/CN111142884B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106104467A (en) * | 2014-06-30 | 2016-11-09 | 北京新媒传信科技有限公司 | A kind of Automation arranging method and terminal |
| CN104793946A (en) * | 2015-04-27 | 2015-07-22 | 广州杰赛科技股份有限公司 | Application deployment method and system based on cloud computing platform |
| CN108897547A (en) * | 2018-06-27 | 2018-11-27 | 北京神州泰岳软件股份有限公司 | A kind of software automatic deployment and device |
| CN110377290A (en) * | 2019-07-22 | 2019-10-25 | 阿里巴巴集团控股有限公司 | A kind of method, device and equipment of purpose project compiling |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111142884A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111142884B (en) | Version deployment method and device of applet, electronic equipment and storage medium | |
| US11467816B1 (en) | Method and system of running an application | |
| US10162624B1 (en) | Web shell for dynamically generated cross-platform applications | |
| US20210182170A1 (en) | Overlapping-in-time execution of load tests on applications in a centralized system | |
| US11138518B1 (en) | Right for me deployment and customization of applications with customized widgets | |
| CN108293081B (en) | Deep linking of program playback to mobile application state through user interface events | |
| US11389960B2 (en) | Systems and methods for robotic process automation | |
| JP5171790B2 (en) | Information processing apparatus, communication system, and program | |
| US20220391221A1 (en) | Providing a different configuration of added functionality for each of the stages of predeployment, deployment, and post deployment using a layer of abstraction | |
| US11314497B2 (en) | Deployment and customization of applications at the widget level | |
| CN112685035B (en) | Project development method and device, computer readable storage medium and electronic equipment | |
| CN111563220A (en) | Business website project construction method and device, computer equipment and storage medium | |
| US9672032B2 (en) | Mobile enabled application | |
| CN112596714A (en) | Webpage development method, device, terminal, server and storage medium | |
| CN114297056A (en) | Automatic testing method and system | |
| CN110989986B (en) | Software template-based software generation method and device and computer equipment | |
| CN112115056B (en) | Project deployment method and device, server and storage medium | |
| JP6843007B2 (en) | Application generation support system | |
| Manases et al. | Automation of Network Traffic Monitoring using Docker images of Snort3, Grafana and a custom API | |
| CN112395096A (en) | Remote function call processing method and device, electronic equipment and storage medium | |
| US11030087B2 (en) | Systems and methods for automated invocation of accessibility validations in accessibility scripts | |
| CN115016775A (en) | Interface simulation method and device, storage medium and electronic equipment | |
| CN113608996B (en) | Mirror image compiling test method, system, device and readable storage medium | |
| EP4254171A1 (en) | Generation program, generation method, and information processing device | |
| US20220164207A1 (en) | System for providing an adaptable plugin framework for application transformation to cloud |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |