WO2024000917A1

WO2024000917A1 - Non-intrusive, pluggable front-end build transfer acceleration method and apparatus

Info

Publication number: WO2024000917A1
Application number: PCT/CN2022/124463
Authority: WO
Inventors: 郭营; 颜敏; 姚东; 耿术强; 李正求
Original assignee: 上海淇毓信息科技有限公司
Priority date: 2022-07-01
Filing date: 2022-10-10
Publication date: 2024-01-04
Also published as: CN115291879A

Abstract

The present application relates to a non-intrusive, pluggable front-end build transfer acceleration method and apparatus, an electronic device and a computer-readable medium. The method comprises: obtaining project information corresponding to a project to be subjected to front-end build; obtaining a resource address corresponding to the project by means of the project information; obtaining local resource data by using the resource address; generating front-end build data according to the local resource data; and storing the front-end build data in a predetermined position to complete the front-end build of the project. According to the non-intrusive, pluggable front-end build transfer acceleration method and apparatus, the electronic device and the computer-readable medium, compatibility with a front-end build process in the prior art can be realized, and the front-end build efficiency is improved without user awareness, thereby reducing the time cost and improving the user satisfaction.

Description

A non-intrusive and pluggable method and device for speeding up front-end construction and transfer

Technical field

The present application relates to the field of computer information processing. Specifically, it relates to a non-intrusive and pluggable front-end construction transfer speed-up method, device, electronic equipment and computer-readable media.

Background technique

The front-end is the front-end part of the website, which runs on PC, mobile and other browsers and displays the web pages for users to browse. With the development of Internet technology, each platform will provide a front-end that can adapt to various screen resolutions and suitable motion design to bring users a very high user experience. The front end of business products needs to be updated based on product activities or news hot spots. In general, developers first develop front-end code on the local platform, and then submit the development code to the business system to convert it into production code for use by the business front-end. Tools that can convert development code into production code are called build tools.

However, as the complexity of the business carried by the front end increases, more and more dependency files are required when the development code wants to run normally. This causes the front-end code construction time to also increase. Each system build takes a long time to install dependencies, and it is difficult to collect performance data for each stage of the build.

The above information disclosed in the Background section is only for enhancement of understanding of the context of the application and therefore it may contain information that does not form the prior art that is already known to a person of ordinary skill in the art.

Contents of the invention

In view of this, the present application provides a non-intrusive and pluggable front-end construction transfer speed-up method, device, electronic equipment and computer-readable medium, which is compatible with the front-end construction process in the existing technology and improves the speed without the user's perception. Front-end construction efficiency, reducing time costs and improving user satisfaction.

Additional features and advantages of the invention will be apparent from the detailed description which follows, or, in part, may be learned by practice of the invention.

According to one aspect of the present application, a non-intrusive and pluggable front-end construction transfer speed-up method is proposed. The method includes: obtaining project information corresponding to the project to be built; and obtaining resources corresponding to the project through the project information. Address; use the resource address to obtain local resource data; generate front-end construction data according to the local resource data; store the front-end construction data in a predetermined location to complete the front-end construction of the project.

Optionally, before obtaining the project information corresponding to the project to be built on the front end, it also includes: performing local construction of the project; after the local construction is completed, generating local construction data; transmitting the local construction data to the content distribution network .

Optionally, performing local construction of the project includes: pulling the code of the project from a remote warehouse; installing dependency files of the project locally; performing local construction of the project based on the dependency files and the code. Construct.

Optionally, transmitting the local construction data to the content distribution network includes: compressing the local construction data to generate local resource data; verifying the local resource data; and after passing the verification, sending the local resource data to the content distribution network. Resource data is transmitted to the content distribution network.

Optionally, obtaining project information corresponding to the project to be built on the front end includes: obtaining the project ID, project branch name, and submission ID corresponding to the project to be built on the front end through a predetermined interface.

Optionally, obtaining the resource address corresponding to the project through the project information includes: obtaining the record file corresponding to the project information in the background server through the project identification, project branch name, and submission identification in the project information; Obtain the resource address corresponding to the project from the record file.

Optionally, using the resource address to obtain local resource data includes: obtaining the local resource data from a content distribution network through the resource address; and storing the local resource data locally on the server of the project to be built on the front end.

Optionally, generating front-end construction data according to the local resource data includes: decompressing the resource data locally on the server of the project to be front-end built, and generating the front-end construction data.

Optionally, storing the front-end build data in a predetermined location to complete the front-end build of the project includes: determining the target platform and target directory according to the project information of the project; storing the front-end build data in the target platform's target directory to complete the front-end build of the project.

According to one aspect of the present application, a non-intrusive and pluggable front-end construction transfer speed-up device is proposed. The device includes: an information module, used to obtain project information corresponding to the project to be built; an address module, used to pass the required The project information obtains the resource address corresponding to the project; the resource module is used to obtain local resource data using the resource address; the data module is used to generate front-end construction data according to the local resource data; the building module is used to convert all The front-end build data is stored in a predetermined location to complete the front-end build of the project.

According to one aspect of the present application, an electronic device is proposed. The electronic device includes: one or more processors; a storage device for storing one or more programs; when one or more programs are processed by one or more processors, Execution causes one or more processors to implement the method as above.

According to one aspect of the present application, a computer-readable medium is proposed, on which a computer program is stored. When the program is executed by a processor, the above method is implemented.

According to the non-intrusive and pluggable front-end construction transfer speed-up method, device, electronic equipment and computer-readable medium of the present application, project information corresponding to the project to be built is obtained by obtaining the project information; the project is obtained through the project information The corresponding resource address; using the resource address to obtain local resource data; generating front-end construction data according to the local resource data; storing the front-end construction data in a predetermined location to complete the front-end construction of the project, which is compatible with modern There is a front-end construction process in technology that improves front-end construction efficiency without users being aware of it, reduces time costs, and improves user satisfaction.

It should be understood that the above general description and the following detailed description are only exemplary and do not limit the present application.

Description of drawings

The above and other objects, features and advantages of the present application will become more apparent by describing in detail example embodiments thereof with reference to the accompanying drawings. The drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts.

Figure 1 is a schematic diagram of a front-end construction method in the prior art.

Figure 2 is a system block diagram illustrating a non-intrusive and pluggable front-end construction transfer speed-up method and device according to an exemplary embodiment.

FIG. 3 is a flowchart illustrating a non-intrusive and pluggable front-end construction transfer speed-up method according to an exemplary embodiment.

FIG. 4 is a schematic diagram illustrating a non-intrusive and pluggable front-end construction transfer speed-up method according to an exemplary embodiment.

FIG. 5 is a schematic diagram illustrating a non-intrusive and pluggable front-end construction transfer speed-up method according to another exemplary embodiment.

FIG. 6 is a schematic diagram illustrating a non-intrusive and pluggable front-end construction transfer speed-up method according to another exemplary embodiment.

FIG. 7 is a block diagram of a non-invasive pluggable front-end construction transfer speed-up device according to an exemplary embodiment.

FIG. 8 is a block diagram of an electronic device according to an exemplary embodiment.

Figure 9 is a block diagram of a computer-readable medium according to an exemplary embodiment.

Detailed ways

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in various forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of the example embodiments. To those skilled in the art. The same reference numerals in the drawings represent the same or similar parts, and thus their repeated description will be omitted.

Furthermore, the described features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to provide a thorough understanding of embodiments of the present application. However, those skilled in the art will appreciate that the technical solutions of the present application may be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other instances, well-known methods, apparatus, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the present application.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. That is, these functional entities may be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and/or processor devices and/or microcontroller devices. entity.

The flowcharts shown in the drawings are only illustrative, and do not necessarily include all contents and operations/steps, nor must they be performed in the order described. For example, some operations/steps can be decomposed, and some operations/steps can be merged or partially merged, so the actual order of execution may change according to the actual situation.

It will be understood that, although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one component from another component. Accordingly, a first component discussed below may be referred to as a second component without departing from the teachings of the present concepts. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

Those skilled in the art can understand that the accompanying drawings are only schematic diagrams of exemplary embodiments, and the modules or processes in the accompanying drawings are not necessarily necessary to implement the present application, and therefore cannot be used to limit the protection scope of the present application.

Figure 1 is a schematic diagram of a front-end construction method in the prior art. As shown in Figure 1, in the existing technology, front-end construction generally requires the following steps:

1. Pull the project code from the remote warehouse for the first time;

2. Install project dependencies locally;

3. Business development, manually synchronize the code, submit the code, and then go to the publishing platform; (not automatic)

4. Reinstall the project dependencies on the remote platform (limited by the number of project dependencies, network, etc., this process is relatively time-consuming); and then build (limited by project size, server performance, task queuing, etc., this process is also Very time consuming);

5. When there are new requirements for iteration, repeat steps 3 and 4. The overall project cycle will be longer.

In the existing technology, the packaging speed is slow when building the front-end. The average packaging time of a simple front-end activity page project is about 500s. Due to the slow speed, the development experience is not good, and the test and verification cycle is prolonged; the slow speed is mainly reflected in two In terms of aspects, firstly, the front-end construction of the existing technology is based on containers. When there are many packaging tasks at the same time, there will be resource grabbing, resulting in poor server performance. Secondly, it takes too long to install the front-end dependency packages. Moreover, due to fluctuations in network speed, timeouts often occur when installing dependent packages, which can lead to installation failure and ultimately the failure of the entire packaging process.

In order to solve the problems existing in the existing technology, this application proposes a non-intrusive and pluggable method and device for speeding up front-end construction and transfer. It adopts a persistence solution that combines local construction and content distribution network. The front-end is built and runs in the system. Pull resources from the application to avoid repeated installation of dependencies, and the overall front-end construction speed is increased by 2 to 6 times.

The contents of this application will be described in detail below with reference to specific embodiments.

As shown in Figure 2, the system architecture 20 may include

local devices

201, 202, 203, a network 204 and a content distribution network server 205, and

business platforms

206, 207, 208. The network 204 is used between

local devices

201, 202, 203 and content distribution network server 205; between

local devices

201, 202, 203 and

service platforms

206, 207, 208; between content distribution network server 205 and

service platforms

206, 207 , 208 provides the medium for communication links. Network 204 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

Developers can use

local devices

201, 202, 203 to interact with the

business platforms

206, 207, 208 through the network 204 and/or the content distribution network server 205 to receive or send data, etc. Various development client applications can be installed on the

local devices

201, 202, and 203, such as HTML development applications, CSS development applications, JavaScript development applications, ajax development applications, etc.

The

local devices

201, 202, and 203 may, for example, perform local construction of the project; the

local devices

201, 202, and 203 may, for example, generate local construction data after the local construction is completed; the

local devices

201, 202, and 203 may, for example, convert the local The build data is stored locally, and the

local devices

201, 202, 203 can also transmit the local build data to the content distribution network server 205, for example.

The

business platforms

206, 207, and 208 may be servers that provide various services, such as backend management servers that provide support for Internet service websites browsed by users. The

business platforms

206, 207, and 208 can analyze and process the received user data, and feed back the processing results to the administrator and/or the user of the Internet service website.

The

business platforms

206, 207, and 208 can, for example, obtain the project information corresponding to the project to be built on the front end; the

business platforms

206, 207, and 208 can, for example, obtain the resource address corresponding to the project through the project information; the

business platforms

206, 207, 208 can, for example, use the resource address to obtain local resource data; the

business platforms

206, 207, and 208 can, for example, generate front-end construction data according to the local resource data; the

business platforms

206, 207, and 208 can, for example, store the front-end construction data in Book a spot to complete the front-end build for said project.

The

business platform

206, 207, 208 may be an entity server, or may be composed of multiple servers. It should be noted that the non-intrusive and pluggable front-end construction transfer speed-up method provided by the embodiment of the present application can be The

business platforms

206, 207, 208 and/or the content distribution network server 205 and/or the

local devices

201, 202, 203 are executed. Correspondingly, the non-intrusive pluggable front-end construction transfer speed-up device can be set on the

business platforms

206, 207, 208 and/or content distribution network server 205 and/or

local devices

201, 202, 203.

FIG. 3 is a flowchart illustrating a non-intrusive and pluggable method for accelerating front-end build transfer according to another exemplary embodiment. A non-intrusive and pluggable front-end construction transfer speed-up method 30 includes at least steps S302 to S310.

As shown in Figure 3, in S302, project information corresponding to the project to be built on the front end is obtained. Obtain the project ID, project branch name, and submission ID corresponding to the project to be built on the front end through the predetermined interface.

The preset port can be called through the plug-in, which can be, for example, Server Api, and the project information can be obtained from the preset port. The project information can include: project identification, project branch name, and commit ID.

In one embodiment, before obtaining the project information corresponding to the project to be built, the method further includes: performing local construction of the project; after the local construction is completed, generating local construction data; and transmitting the local construction data to the content. distribution network.

More specifically, for example, the code of the project may be pulled from a remote repository; the dependency files of the project may be installed locally; and the project may be built locally based on the dependency files and the code.

In one embodiment, for example, the local construction data may be compressed to generate local resource data; the local resource data may be verified; and after the verification passes, the local resource data may be transmitted to the content distribution network.

The relevant content of "verifying the local resource data" will be described in detail in the embodiment corresponding to FIG. 5 .

In S304, obtain the resource address corresponding to the project through the project information. The record file corresponding to the project information is obtained in the background server through the project identification, project branch name, and submission identification in the project information; the resource address corresponding to the project is obtained from the record file.

In S306, the resource address is used to obtain local resource data. For example, the local resource data can be obtained from the content distribution network through the resource address; and the local resource data can be stored locally on the server of the project to be built on the front end.

Based on the information in this record, resources are downloaded from the content distribution network server to the local location of the business server to be built for front-end construction.

In S308, front-end construction data is generated according to the local resource data. For example, the resource data may be decompressed locally on the server of the project to be built to generate the front-end build data, where the front-end build data is generated based on decompression of the developer's local build data.

In S310, the front-end construction data is stored in a predetermined location to complete the front-end construction of the project. The target platform and target directory can be determined according to the project information of the project; the front-end construction data is stored in the target directory of the target platform to complete the front-end construction of the project.

According to a non-intrusive and pluggable front-end construction transfer speed-up method of the present application, the project information corresponding to the project to be built is obtained; the resource address corresponding to the project is obtained through the project information; and the resource address is used Obtain local resource data; generate front-end construction data according to the local resource data; store the front-end construction data in a predetermined location to complete the front-end construction of the project, which can be compatible with the front-end construction process in the existing technology, and can be used by users Improve front-end construction efficiency without awareness, reduce time costs, and improve user satisfaction.

It should be clearly understood that this application describes how to make and use specific examples, but that the principles of this application are not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of this disclosure.

FIG. 4 is a schematic diagram illustrating a non-intrusive and pluggable front-end construction transfer speed-up method according to an exemplary embodiment. In the front-end construction method of local resource data in this application, different modules can be set up to assist in improving performance. For example, a performance statistics module can be set up to collect data. In order to ensure the consistency of resources, a version comparison module (based on commit Id) can also be built in. ), in order to improve the automation of development, a Git (code) automation module can also be built-in, which can include functions such as automatic submission, automatic retrieval, automatic push, version conflict checking, and version pulling.

The method in this application can be implemented through the plug-in of the build tool. The front-end construction method in this application is independent of the container machine and can be used by docker, node and gitlab ci. In addition, this application can also provide enhanced functions such as compressed upload, which can be used alone or disabled during use; for access, the front-end construction method in this application can achieve pluggable functions, and you can choose Functions are assembled into specific pipelines and can also support the deployment of micro-applications.

FIG. 5 is a schematic diagram illustrating a non-intrusive and pluggable front-end construction transfer speed-up method according to another exemplary embodiment. As shown in Figure 5, the system architecture corresponding to the non-intrusive and pluggable front-end construction and transfer speed-up method in this application may include two parts: local and business front-end.

The local end can undertake the construction of local projects, check the git version of the project before the current project is built, compress the build product after the build is completed, and then upload it.

During this process, the project configuration can also be checked through the version detection and project detection models to check whether the project configuration is correct. The log module is used to record the log output during the process, as well as record the performance, speed, and resource size during the project construction process. Operator, version number and other information.

The business front-end is mainly used for business services. It can be applied in containers or other construction platforms to pull matched resource packages from the content distribution network and decompress them.

The business front-end performs calling functions through the externally exposed interface API.

In a specific application embodiment, the business platform calls the API exposed to the business front-end at runtime, passing in the required parameters (for example, project identification, branch name, submission identification), and the log module will go to the resource library ( A unique record is matched in the background service), and the resource address containing the project is extracted from this record. The download module downloads the resources from the content distribution network to the local area of the business server based on the information in this record, and then decompresses the decompressed The file is placed in the designated directory of the platform where it is located. From this point on, the process ends. The local build results are placed in the designated location according to the requirements of the platform. The remaining tasks are completed by the platform such as publishing and other subsequent steps.

This application's non-intrusive and pluggable front-end construction transfer speed-up method only takes over one step of the platform. It does not change the rules of the platform, but adapts to the platform. This makes developers on the platform almost do not need to pay special attention. These actions are completed by other plug-ins, because the entire process from the platform starting to running to publishing is no different from before, and developers feel good.

In a specific embodiment, the front-end construction method in the prior art can refer to the above description, and the construction method in this application can be as follows:

1. Pull the project code from the remote warehouse for the first time;

2. Install project dependencies locally;

3. Business development, local construction, and then compressing the built product and uploading it to the content distribution network. This is because in most cases the performance of the local build is better than the server performance of the publishing platform, and the construction time is greatly reduced. After the construction is completed, it is published to the business platform;

4. The business platform synchronizes resources into the platform. In this process, since there is no need to reinstall dependencies, and the resources have been quickly built locally and do not need to be rebuilt again, the construction method in this application can It saves the installation and build steps, saves time for processing this project, and quickly releases server resources, allowing the server to handle other tasks;

5. If there are new requirements, iterate and repeat steps 3 and 4.

There are no additional steps in the entire development process. They are the same as those in the existing technology. Developers do not need to undergo special training to adapt to the method in this application. Each step in the development process is integrated with low perception. The entire process It is completely automated and safe, maintaining the original development process, and more importantly, it is pluggable, providing another option for the existing front-end construction solution.

FIG. 6 is a schematic diagram illustrating a non-intrusive and pluggable front-end construction transfer speed-up method according to another exemplary embodiment. Figure 6 is a comparison between the front-end construction method in the prior art and the construction method in this application. It can be seen from Figure 6 that the more time-consuming steps of the process in the existing technology are to install dependencies in the image and build, and the dependencies will be installed every time the package is packaged. Due to intranet network reasons, the installation is very time-consuming, and at the same time, the construction is performed in the container. The efficiency is also low, because the performance of the container will decrease when there are many tasks. Combining the above two points, the original process will take a long time to package each time;

In this application, time-consuming steps are migrated locally. When developing the project, it has been installed locally and there is no need to reinstall it every time, which saves a lot of time; mainstream front-end projects include the build function when initializing the project, so there is no need to add additional configuration in this application , the construction can be realized. Since the build has been completed locally, you only need to compress the static resource package and upload it to the unified file service, and record it.

When building the business front-end, match the unique resource package based on the project information in the business processing command and download it, and then decompress it. After the expansion of the above functions, the same effect as the original process can be achieved, and the installation of dependent packages can be greatly saved. time and also save network resources.

In an actual application scenario, the average construction time of a project according to the existing technology process is about 500s. After using the technology of this application, the average construction time is within 60s, and the efficiency is greatly improved.

Therefore, the non-intrusive and pluggable front-end construction and transfer speed-up method proposed in this application can reduce development costs, access costs, and technician understanding costs, and can also significantly improve system performance and realize automated processes.

Those skilled in the art can understand that all or part of the steps for implementing the above-described embodiments are implemented as computer programs executed by a CPU. When the computer program is executed by the CPU, the above-mentioned functions defined by the above-mentioned method provided by this application are executed. The program can be stored in a computer-readable storage medium, which can be a read-only memory, a magnetic disk or an optical disk.

In addition, it should be noted that the above-mentioned drawings are only schematic illustrations of processes included in the methods according to the exemplary embodiments of the present application, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal sequence of these processes. In addition, it is also easy to understand that these processes may be executed synchronously or asynchronously in multiple modules, for example.

The following are device embodiments of the present application, which can be used to execute method embodiments of the present application. For details not disclosed in the device embodiments of this application, please refer to the method embodiments of this application.

FIG. 7 is a block diagram of a non-invasive pluggable front-end construction transfer speed-up device according to an exemplary embodiment. As shown in FIG. 7 , the non-invasive and pluggable front-end construction and transfer speed-up device 70 includes: an information module 702 , an address module 704 , a resource module 706 , a data module 708 , and a construction module 710 .

The information module 702 is used to obtain the project information corresponding to the project to be built on the front end; the information module 702 is also used to obtain the project identification, project branch name, and submission identification corresponding to the project to be built on the front end through a predetermined interface.

The address module 704 is used to obtain the resource address corresponding to the project through the project information; the address module 704 is also used to obtain the project information in the background server through the project identification, project branch name, and submission identification in the project information. The corresponding record file; obtain the resource address corresponding to the project from the record file.

The resource module 706 is used to obtain the local resource data using the resource address; the resource module 706 is also used to obtain the local resource data from the content distribution network through the resource address; and store the local resource data in the to-be-built front-end Local to the project's server.

The data module 708 is used to generate front-end construction data according to the local resource data; the data module 708 is also used to decompress the resource data locally on the server of the project to be front-end built, and generate the front-end construction data.

The building module 710 is used to store the front-end building data in a predetermined location to complete the front-end building of the project. The construction module 710 is also used to determine the target platform and target directory according to the project information of the project; store the front-end construction data in the target directory of the target platform to complete the front-end construction of the project.

According to the non-intrusive and pluggable front-end construction transfer speed-up device of the present application, the project information corresponding to the project to be built is obtained by obtaining the project information; the resource address corresponding to the project is obtained through the project information; and the local resource address is obtained using the resource address. Resource data; generating front-end construction data according to the local resource data; storing the front-end construction data in a predetermined location to complete the front-end construction of the project, which is compatible with the front-end construction process in the existing technology and is invisible to the user Improve front-end construction efficiency, reduce time costs, and improve user satisfaction.

An electronic device 800 according to this embodiment of the present application is described below with reference to FIG. 8 . The electronic device 800 shown in FIG. 8 is only an example and should not impose any limitations on the functions and usage scope of the embodiments of the present application.

As shown in Figure 8, electronic device 800 is embodied in the form of a general computing device. The components of the electronic device 800 may include, but are not limited to: at least one processing unit 810, at least one storage unit 820, a bus 830 connecting different system components (including the storage unit 820 and the processing unit 810), a display unit 840, and the like.

Wherein, the storage unit stores program code, and the program code can be executed by the processing unit 810, so that the processing unit 810 performs the steps in this specification according to various exemplary embodiments of the present application. For example, the processing unit 810 may perform steps as shown in FIG. 3 .

The storage unit 820 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 8201 and/or a cache storage unit 8202, and may further include a read-only storage unit (ROM) 8203.

The storage unit 820 may also include a program/utility 8204 having a set of (at least one) program modules 8205 including, but not limited to: an operating system, one or more applications, other program modules, and programs. Data, each of these examples or some combination may include an implementation of a network environment.

Bus 830 may be a local area representing one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or using any of a variety of bus structures. bus.

The electronic device 800 may also communicate with one or more external devices 800' (e.g., keyboard, pointing device, Bluetooth device, etc.) so that the user can communicate with the device that the electronic device 800 interacts with, and/or the electronic device 800 can communicate with a Any device (such as a router, modem, etc.) with which multiple other computing devices communicate. This communication may occur through input/output (I/O) interface 850. Furthermore, the electronic device 800 may also communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through a network adapter 860. Network adapter 860 may communicate with other modules of electronic device 800 via bus 830. It should be understood that, although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives And data backup storage system, etc.

Through the above description of the embodiments, those skilled in the art can easily understand that the example embodiments described here can be implemented by software, or can be implemented by software combined with necessary hardware. Therefore, as shown in Figure 9, the technical solution according to the embodiment of the present application can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk etc.) or on a network, including several instructions to cause a computing device (which can be a personal computer, a server, a network device, etc.) to execute the above method according to an embodiment of the present application.

The software product may take the form of any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: electrical connection with one or more conductors, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

The computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave carrying readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable storage medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device. Program code contained on a readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above.

Program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., as well as conventional procedural formulas. Programming language—such as "C" or a similar programming language. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on. In situations involving remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., provided by an Internet service). (business comes via Internet connection).

The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by a device, the computer-readable medium realizes the following functions: perform local construction of the project; after the local construction is completed, the computer-readable medium carries one or more programs. , generate local build data; transmit the local build data to the content distribution network. The computer-readable medium can also realize the following functions: obtain the project information corresponding to the project to be built on the front end; obtain the resource address corresponding to the project through the project information; obtain local resource data using the resource address; The local resource data generates front-end construction data; and the front-end construction data is stored in a predetermined location to complete the front-end construction of the project.

Those skilled in the art can understand that the above-mentioned modules can be distributed in devices according to the description of the embodiments, or can be modified accordingly in one or more devices that are only different from this embodiment. The modules of the above embodiments can be combined into one module, or further divided into multiple sub-modules.

Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described here can be implemented by software, or can be implemented by software combined with necessary hardware. Therefore, the technical solution according to the embodiment of the present application can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network. , including several instructions to cause a computing device (which may be a personal computer, server, mobile terminal, or network device, etc.) to execute the method according to the embodiment of the present application.

Exemplary embodiments of the present application have been specifically shown and described above. It is to be understood that the present application is not limited to the detailed structures, arrangements, or implementation methods described herein; on the contrary, the present application is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

A non-intrusive and pluggable front-end construction transfer speed-up method, which is characterized by including:

Obtain the project information corresponding to the project to be built on the front end;

Obtain the resource address corresponding to the project through the project information;

Use the resource address to obtain local resource data;

Generate front-end build data according to the local resource data;

The front-end build data is stored in a predetermined location to complete the front-end build of the project.
The method according to claim 1, characterized in that before obtaining the project information corresponding to the project to be built on the front end, it further includes:

Do a local build of said project;

After the local build is completed, local build data is generated;

Transmit the locally built data to a content delivery network.
The method of claim 2, wherein performing local construction of the project includes:

Pull the code of said project from the remote repository;

Install the dependency files of the project locally;

Perform a local build of the project based on the dependency files and the code.
The method of claim 2, wherein transmitting the locally constructed data to a content distribution network includes:

Compress the local construction data to generate local resource data;

Verify the local resource data;

After passing the verification, the local resource data is transmitted to the content distribution network.
The method according to claim 1, characterized in that obtaining project information corresponding to the project to be built on the front end includes:

Obtain the project ID, project branch name, and submission ID corresponding to the project to be built on the front end through the predetermined interface.
The method of claim 5, wherein obtaining the resource address corresponding to the project through the project information includes:

Obtain the record file corresponding to the project information from the backend server through the project identification, project branch name, and submission identification in the project information;

Obtain the resource address corresponding to the project from the record file.
The method of claim 1, wherein using the resource address to obtain local resource data includes:

Obtain the local resource data from the content distribution network through the resource address;

The local resource data is stored locally on the server of the project to be built as a front-end.
The method of claim 7, wherein generating front-end construction data according to the local resource data includes:

The resource data is decompressed locally on the server of the project to be built for front-end construction to generate the front-end construction data.
The method of claim 1, wherein storing the front-end construction data in a predetermined location to complete the front-end construction of the project includes:

Determine the target platform and target directory based on the project information of the project;

The front-end build data is stored in the target directory of the target platform to complete the front-end build of the project.
A non-intrusive and pluggable front-end construction transfer speed-up device, which is characterized by including:

Information module, used to obtain project information corresponding to the project to be built on the front end;

The address module is used to obtain the resource address corresponding to the project through the project information;

A resource module, used to obtain local resource data using the resource address;

A data module used to generate front-end construction data based on the local resource data;

A building module is used to store the front-end building data in a predetermined location to complete the front-end building of the project.
An electronic device, characterized by including:

one or more processors;

A storage device for storing one or more programs;

When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method as described in any one of claims 1-9.
A computer-readable medium on which a computer program is stored, characterized in that when the program is executed by a processor, the method according to any one of claims 1-9 is implemented.