CN116627432A - Front-end application automatic deployment method, device, equipment and medium - Google Patents
Front-end application automatic deployment method, device, equipment and medium Download PDFInfo
- Publication number
- CN116627432A CN116627432A CN202310644712.6A CN202310644712A CN116627432A CN 116627432 A CN116627432 A CN 116627432A CN 202310644712 A CN202310644712 A CN 202310644712A CN 116627432 A CN116627432 A CN 116627432A
- Authority
- CN
- China
- Prior art keywords
- end application
- page
- service
- code
- deployment
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 238000010276 construction Methods 0.000 claims abstract description 42
- 238000004590 computer program Methods 0.000 claims description 16
- 238000011161 development Methods 0.000 claims description 12
- 230000008859 change Effects 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000001514 detection method Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a front-end application automatic deployment method, a device, equipment and a medium. The method is performed by an automated deployment system comprising a page service, a build service, and a configuration platform; the method comprises the following steps: if the code compiling triggering event is detected, determining front-end application information through the construction service according to the code compiling triggering event; pulling an object code matched with the front-end application information in a code warehouse through a construction service, and determining a compiling result of the object code; and uploading the compiling result of the target code to the page service through the construction service, and synchronizing the front-end application information to the configuration platform to complete the deployment of the front-end application. The technical scheme solves the problems of poor deployment reliability, difficult version rollback and the like of the front-end application, can ensure that the front-end application is deployed efficiently and reliably while continuously providing service, and brings good access experience to users.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method, an apparatus, a device, and a medium for automatically deploying a front-end application.
Background
With the development of internet technology, the functions to be accepted by the front-end application are more and more, the iteration speed is faster and the complexity of the front-end application is higher and higher. Aiming at the situation, an automatic deployment scheme is needed for the deployment of the front-end application, and the front-end application is ensured to be deployed quickly, safely and efficiently.
At present, deployment schemes of front-end applications can be roughly divided into two types, one type is a traditional manual deployment scheme, and after the front-end applications are compiled, the compiled products are manually uploaded to a server. The other is a continuous integration scheme, the codes of the front-end application are submitted to a code server, a deployment flow is triggered, jenkins automatically scans and pulls target code files on a gitlab server to generate images, and the images are pushed to a harbor server to complete automatic deployment.
However, both existing deployment schemes have significant drawbacks. For the traditional manual deployment mode, the accuracy of deployment operation cannot be ensured by manual operation, the confusion of deployment versions and deployment environments is easily caused, and the software development efficiency is low. For the continuous integration mode, although automatic deployment can be realized, development efficiency is improved, labor cost is saved, service is easily unavailable in the deployment process, and efficient version management, such as quick rollback of a front-end application version, is difficult to realize. Thus, there is a need for a front-end application automation deployment scheme where services are continuously available for different deployment environments.
Disclosure of Invention
The application provides an automatic deployment method, device, equipment and medium for front-end application, which are used for solving the problems of poor deployment reliability, difficult version rollback and the like of the front-end application, and can ensure that the high-efficiency and reliable deployment of the front-end application is realized while the service is continuously provided, so that good access experience is brought to users.
According to an aspect of the present application, there is provided a front-end application automation deployment method, the method being performed by an automation deployment system including a page service, a build service, and a configuration platform; the method comprises the following steps:
if the code compiling triggering event is detected, determining front-end application information through the construction service according to the code compiling triggering event;
pulling an object code matched with the front-end application information in a code warehouse through a construction service, and determining a compiling result of the object code;
and uploading the compiling result of the target code to the page service through the construction service, and synchronizing the front-end application information to the configuration platform to complete the deployment of the front-end application.
According to another aspect of the present application, there is provided a front-end application automation deployment apparatus configured in an automation deployment system including a page service, a build service, and a configuration platform; the device comprises:
the front-end application information determining module is used for determining front-end application information according to the code compiling trigger event through the building service if the code compiling trigger event is detected;
the compiling result determining module is used for pulling the target code matched with the front-end application information in the code warehouse through the construction service and determining the compiling result of the target code;
and the front-end application deployment completion module is used for uploading the compiling result of the target code to the page service through the construction service and synchronizing the front-end application information to the configuration platform so as to complete the deployment of the front-end application.
According to another aspect of the present application, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the front end application automation deployment method of any of the embodiments of the present application.
According to another aspect of the present application, there is provided a computer readable storage medium storing computer instructions for causing a processor to implement the front end application automation deployment method according to any embodiment of the present application when executed.
According to the technical scheme, when the code compiling triggering event is detected, front-end application information is determined through the construction service according to the code compiling triggering event; pulling an object code matched with the front-end application information in a code warehouse through a construction service, and determining a compiling result of the object code; and uploading the compiling result of the target code to the page service through the construction service, and synchronizing the front-end application information to the configuration platform to complete the deployment of the front-end application. The method solves the problems of poor deployment reliability, difficult version rollback and the like of the front-end application, can ensure that the front-end application is deployed efficiently and reliably while continuously providing services, and brings good access experience to users.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the application or to delineate the scope of the application. Other features of the present application will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a front-end application automation deployment method provided in accordance with a first embodiment of the present application;
fig. 2 is a flowchart of a front-end application automation deployment method according to a second embodiment of the present application;
fig. 3 is a schematic structural diagram of a front-end application automation deployment device according to a third embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device implementing a front-end application automation deployment method according to an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus. The technical scheme of the application obtains, stores, uses, processes and the like the data, which all meet the relevant regulations of national laws and regulations.
Example 1
Fig. 1 is a flowchart of a front-end application automation deployment method according to an embodiment of the present application, where the method may be performed by a front-end application automation deployment device, and the device may be implemented in hardware and/or software, and the device may be configured in an electronic device. As shown in fig. 1, the method includes:
s110, if the code compiling trigger event is detected, determining front-end application information through the construction service according to the code compiling trigger event.
The present solution may be performed by an automated deployment system that may include a page service, a build service, and a configuration platform. The configuration platform can realize the configuration of the attributes such as the deployment environment, the use version, the page and the like of the front-end application. The page service may be used to manage front-end build products. The building service is used for generating a front-end building product according to the front-end application matched codes, wherein the front-end building product can be a compiling result of the front-end application matched codes.
If the automatic deployment system detects a code compiling trigger event, the front-end application information is determined by processing the code matched with the front-end application through the construction service. Specifically, the code compiling trigger event may be an event that triggers the build service to compile the code. For example, the code compiling trigger event may be that the code matched by the front-end application changes, or may be a compiling instruction of the code matched by the front-end application. After detecting the code compilation trigger event, the build service may determine front-end application information based on the code compilation trigger event to locate which piece of code needs to be compiled.
In this solution, optionally, the front-end application information includes a deployment environment of the front-end application, an application version, and an item identifier. In particular, the deployment environment may include a development environment, a pre-release environment, and a release environment. The development environment can be an environment in which the front-end application is deployed in a development stage; the pre-release environment can be an environment deployed by a trial stage before release of the front-end application; the publishing environment may be an environment in which the front-end application is deployed after publishing. The application version of the front-end application may be used to mark multiple versions of the same front-end application, such as version 2.0, version 2.5, and version 3.0 of front-end application a. The item identifier of the front-end application may be an identifier of an item to which the front-end application belongs, and the item identifier and the front-end application may be in a one-to-one correspondence.
In one possible implementation, the code compilation triggering event is a change in code of at least one branch of at least one item in a code repository; the branches are matched with the deployment environment of the front-end application;
the method for determining the front-end application information by the construction service according to the code compiling triggering event comprises the following steps:
determining a target item and a target branch according to the code compiling triggering event through the construction service;
determining an item identification according to the target item, and determining a deployment environment according to the target branch.
In this scenario, the automated deployment system triggers the build service to determine the front-end application information upon detecting a change in code of at least one branch of at least one item in the code repository. Specifically, the automated deployment system may determine the target item and the target branch by comparing the current detection period with the codes of the previous detection period in the code repository. The target item may be an item to which the changed code belongs, and the target branch may be a branch to which the changed code belongs. It is readily appreciated that, based on the target project, the build service can determine the project identity, and based on the target branch, the build service can determine the deployment environment.
According to the scheme, when the codes in the code warehouse are changed, the deployment of the front-end application can be automatically triggered, so that the software development efficiency is improved, and the fine management of the front-end application is realized.
S120, pulling the target code matched with the front-end application information in the code warehouse through the construction service, and determining the compiling result of the target code.
After the front-end application information is determined, the building service can pull the target code corresponding to the front-end application information in the code warehouse and compile the target code to obtain a compiling result of the target code.
S130, uploading the compiling result of the target code to the page service through the construction service, and synchronizing the front-end application information to the configuration platform to complete the deployment of the front-end application.
The construction service can upload the compiling result of the target code to the page service, and simultaneously send the front-end application information to the configuration platform, and the configuration platform can store the front-end application information, so that the deployment of the front-end application is completed.
According to the technical scheme, when a code compiling trigger event is detected, front-end application information is determined through a construction service according to the code compiling trigger event; pulling an object code matched with the front-end application information in a code warehouse through a construction service, and determining a compiling result of the object code; and uploading the compiling result of the target code to the page service through the construction service, and synchronizing the front-end application information to the configuration platform to complete the deployment of the front-end application. The method solves the problems of poor deployment reliability, difficult version rollback and the like of the front-end application, can ensure that the front-end application is deployed efficiently and reliably while continuously providing services, and brings good access experience to users.
Example two
Fig. 2 is a flowchart of a method for automatically deploying a front-end application according to a second embodiment of the present application, where the user access process after the front-end application is deployed is refined based on the foregoing embodiment. As shown in fig. 2, the method includes:
and S210, if the code compiling trigger event is detected, determining front-end application information through the construction service according to the code compiling trigger event.
S220, pulling the target code matched with the front-end application information in the code warehouse through the construction service, and determining the compiling result of the target code.
S230, uploading the compiling result of the target code to the page service through the construction service, and synchronizing the front-end application information to the configuration platform to complete the deployment of the front-end application.
In this solution, optionally, after uploading the compiling result of the object code to the page service by the building service, the method further includes:
storing the compiling result of the target code according to a preset storage mode through page service; the preset storage mode is determined based on the deployment environment of the front-end application matched with the target code, the application version and the item identification.
When the compiling result of the target code is stored, the page service can be stored according to a preset storage mode. The storage manner of the compiling result can be determined based on the deployment environment of the front-end application, the application version and the item identification matched with the target code. Therefore, according to the compiling result stored in the page service, the page service can determine the front-end application information, and further meet the page access requirement of the user terminal.
S240, if the page access request is detected, determining front-end application information according to the page access request through the page service.
After receiving the page access request, the page service can analyze the page access request to obtain front-end application information.
In one possible solution, the page access request includes a link address;
the determining front-end application information according to the page access request through the page service comprises the following steps:
and analyzing the link address through the page service to determine front-end application information of the front-end application.
It will be appreciated that the page access request may include information such as request time, link address, user terminal identification, etc. The link address may include information such as a project identifier, an application version, and a deployment environment, so that the page service parses the link address to obtain front-end application information such as the project identifier and the deployment environment. For example, the link address may be dev-a.com/b, where dev represents the development environment and b represents the project identity.
S250, generating page request information according to the front-end application information through the page service, and sending the page request information to the configuration platform.
The page service may generate page request information according to the front-end application information, and send the page request information to the configuration platform to determine the page address. The page request information may include front-end application information such as project identification, deployment environment, etc.
And S260, receiving page request information through the configuration platform, determining a page address according to the page request information, and sending the page address to the page service.
After receiving the page request information, the configuration platform may determine, according to the page request information, a storage address of a code compiling result matched by the front-end application, that is, a page address. The configuration platform can send the page address to the page service for the page service to feed back the target page to the user terminal.
S270, receiving the page address through the page service, and determining a target page according to the page address so as to feed back the target page to the user terminal.
The page service can read the code compiling result matched with the front-end application according to the page address to generate a target page, and send the target page to the user terminal for the user to access the page.
In one particular example, an automated deployment system includes a configuration platform, a page service, and a build service. The configuration platform is used for storing environment variables (development environment, pre-release environment, formal environment and the like), application versions (consistent with code branch version information) and corresponding relations among page information. The page service may be a web server, configured to manage a front-end building product, obtain a corresponding project name and a deployment environment according to the link address after obtaining the link address provided by the user terminal, and then, deconfigurate the platform according to the project name and the environment to obtain a current page, and return to the user terminal. The construction service can construct the codes into front-end static products, and update the latest front-end static products into the page service and update version information, environment information and page information into the configuration platform after the construction is successful.
The automatic deployment flow of the front-end application is as follows:
1. the webhook is configured in a code warehouse (e.g. a gitlab), and when the code of the code warehouse changes, the construction service is triggered to compile the code;
2. after the construction service monitors that the code of the target branch in the target item in the code warehouse changes, pulling the target code in the code warehouse to compile, and obtaining front-end construction products (html, css, js and other files);
3. and uploading the front-end building product to a page service, and storing in a mode of deployment environment, application version, project name and hash. The deployment environment and the branches are bound, for example, a master branch corresponds to an online environment, a pre branch corresponds to a pre-release environment, and a dev branch corresponds to a development environment. Binding the application version with a version field in a package. Json file of the target code;
4. and synchronizing information such as deployment environment, application version, project name and the like to the configuration platform.
The access flow of the front-end application is as follows:
1. the user terminal accesses the page service through the link address;
2. the page service obtains information such as project names, deployment environments and the like according to the link addresses, such as a.com/b, pre-a.com/b and dev-a.com/b, wherein pre represents a pre-release environment, dev represents a development environment, no prefix represents a formal environment and b represents a project name;
3. the page service makes a page address request to the configuration platform according to the deployment environment and the project name, and the configuration platform returns the page address of the project in the current deployment environment;
4. and the page service finds a target page according to the page address returned by the configuration platform and returns the target page to the user terminal.
In the scheme, the front-end application does not need manual deployment, so that the error rate and the complexity in the deployment process can be greatly reduced, and the development efficiency of research and development personnel is improved. Through non-coverage type release, the resources are organized in a mode of deployment environment, application version, project name and hash, so that the page service is always online in the release process, and the high availability of the page service is ensured. Millisecond version rollback can be performed through the configuration platform, and user experience is improved.
According to the technical scheme, when a code compiling trigger event is detected, front-end application information is determined through a construction service according to the code compiling trigger event; pulling an object code matched with the front-end application information in a code warehouse through a construction service, and determining a compiling result of the object code; and uploading the compiling result of the target code to the page service through the construction service, and synchronizing the front-end application information to the configuration platform to complete the deployment of the front-end application. The method solves the problems of poor deployment reliability, difficult version rollback and the like of the front-end application, can ensure that the front-end application is deployed efficiently and reliably while continuously providing services, and brings good access experience to users.
Example III
Fig. 3 is a schematic structural diagram of an automatic deployment device for front-end application according to a third embodiment of the present application. The device is configured in an automated deployment system comprising a page service, a build service, and a configuration platform. As shown in fig. 3, the apparatus includes:
the front-end application information determining module 310 is configured to determine front-end application information according to the code compilation triggering event through the building service if the code compilation triggering event is detected;
a compiling result determining module 320, configured to pull, by the build service, the object code matching the front-end application information in the code repository, and determine a compiling result of the object code;
the front-end application deployment completion module 330 is configured to upload the compiling result of the object code to the page service through the build service, and synchronize the front-end application information to the configuration platform, so as to complete the deployment of the front-end application.
In this solution, optionally, the front-end application information includes a deployment environment of the front-end application, an application version, and an item identifier.
On the basis of the scheme, the code compiling triggering event is that the code of at least one branch of at least one item in the code warehouse is changed; the branches are matched with the deployment environment of the front-end application;
the front-end application information determining module 310 is specifically configured to:
determining a target item and a target branch according to the code compiling triggering event through the construction service;
determining an item identification according to the target item, and determining a deployment environment according to the target branch.
In a preferred embodiment, the apparatus comprises:
the page access request processing module is used for determining front-end application information according to the page access request through the page service if the page access request is detected;
the page request information generation module is used for generating page request information according to the front-end application information through the page service and sending the page request information to the configuration platform;
the page address sending module is used for receiving page request information through the configuration platform, determining a page address according to the page request information and sending the page address to the page service;
and the target page feedback module is used for receiving the page address through the page service, and determining a target page according to the page address so as to feed back the target page to the user terminal.
On the basis of the scheme, the page access request comprises a link address;
the page access request processing module is specifically configured to:
and analyzing the link address through the page service to determine front-end application information of the front-end application.
In one possible implementation, the apparatus further includes:
the compiling result storage module is used for storing the compiling result of the target code according to a preset storage mode through page service; the preset storage mode is determined based on the deployment environment of the front-end application matched with the target code, the application version and the item identification.
Optionally, the deployment environment includes a development environment, a pre-release environment, and a release environment.
The front-end application automatic deployment device provided by the embodiment of the application can execute the front-end application automatic deployment method provided by any embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method.
Example IV
Fig. 4 shows a schematic diagram of an electronic device 410 that may be used to implement an embodiment of the application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the applications described and/or claimed herein.
As shown in fig. 4, the electronic device 410 includes at least one processor 411, and a memory, such as a Read Only Memory (ROM) 412, a Random Access Memory (RAM) 413, etc., communicatively connected to the at least one processor 411, wherein the memory stores computer programs executable by the at least one processor, and the processor 411 may perform various suitable actions and processes according to the computer programs stored in the Read Only Memory (ROM) 412 or the computer programs loaded from the storage unit 418 into the Random Access Memory (RAM) 413. In the RAM 413, various programs and data required for the operation of the electronic device 410 may also be stored. The processor 411, the ROM 412, and the RAM 413 are connected to each other through a bus 414. An input/output (I/O) interface 415 is also connected to bus 414.
Various components in the electronic device 410 are connected to the I/O interface 415, including: an input unit 416 such as a keyboard, a mouse, etc.; an output unit 417 such as various types of displays, speakers, and the like; a storage unit 418, such as a magnetic disk, optical disk, or the like; and a communication unit 419 such as a network card, modem, wireless communication transceiver, etc. The communication unit 419 allows the electronic device 410 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.
The processor 411 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 411 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 411 performs the various methods and processes described above, such as the front-end application automation deployment method.
In some embodiments, the front-end application automation deployment method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 418. In some embodiments, some or all of the computer program may be loaded and/or installed onto the electronic device 410 via the ROM 412 and/or the communication unit 419. When the computer program is loaded into RAM 413 and executed by processor 411, one or more steps of the front-end application automation deployment method described above may be performed. Alternatively, in other embodiments, the processor 411 may be configured to perform the front-end application automation deployment method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present application, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present application may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present application are achieved, and the present application is not limited herein.
The above embodiments do not limit the scope of the present application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application should be included in the scope of the present application.
Claims (10)
1. An automatic deployment method of a front-end application is characterized in that the method is executed by an automatic deployment system, and the automatic deployment system comprises a page service, a construction service and a configuration platform; the method comprises the following steps:
if the code compiling triggering event is detected, determining front-end application information through the construction service according to the code compiling triggering event;
pulling an object code matched with the front-end application information in a code warehouse through a construction service, and determining a compiling result of the object code;
and uploading the compiling result of the target code to the page service through the construction service, and synchronizing the front-end application information to the configuration platform to complete the deployment of the front-end application.
2. The method of claim 1, wherein the front-end application information includes a deployment environment of the front-end application, an application version, and an item identification.
3. The method of claim 2, wherein the code compilation triggering event is a change in code for at least one branch of at least one item in a code store; the branches are matched with the deployment environment of the front-end application;
the method for determining the front-end application information by the construction service according to the code compiling triggering event comprises the following steps:
determining a target item and a target branch according to the code compiling triggering event through the construction service;
determining an item identification according to the target item, and determining a deployment environment according to the target branch.
4. A method according to claim 3, wherein after completing the deployment of the front-end application, the method further comprises:
if the page access request is detected, determining front-end application information according to the page access request through the page service;
generating page request information according to front-end application information through a page service, and sending the page request information to a configuration platform;
receiving page request information through a configuration platform, determining a page address according to the page request information, and sending the page address to a page service;
and receiving the page address through the page service, and determining a target page according to the page address so as to feed back the target page to the user terminal.
5. The method of claim 4, wherein the page access request includes a link address;
the determining front-end application information according to the page access request through the page service comprises the following steps:
and analyzing the link address through the page service to determine front-end application information of the front-end application.
6. The method of claim 1, wherein after uploading the compiled result of the object code to the page service by the build service, the method further comprises:
storing the compiling result of the target code according to a preset storage mode through page service; the preset storage mode is determined based on the deployment environment of the front-end application matched with the target code, the application version and the item identification.
7. The method of claim 2, wherein the deployment environment comprises a development environment, a pre-release environment, and a release environment.
8. The front-end application automatic deployment device is characterized by being configured in an automatic deployment system, wherein the automatic deployment system comprises a page service, a construction service and a configuration platform; the device comprises:
the front-end application information determining module is used for determining front-end application information according to the code compiling trigger event through the building service if the code compiling trigger event is detected;
the compiling result determining module is used for pulling the target code matched with the front-end application information in the code warehouse through the construction service and determining the compiling result of the target code;
and the front-end application deployment completion module is used for uploading the compiling result of the target code to the page service through the construction service and synchronizing the front-end application information to the configuration platform so as to complete the deployment of the front-end application.
9. An electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the front end application automation deployment method of any of claims 1-7.
10. A computer readable storage medium storing computer instructions for causing a processor to implement the front end application automation deployment method of any of claims 1-7 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310644712.6A CN116627432A (en) | 2023-06-01 | 2023-06-01 | Front-end application automatic deployment method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310644712.6A CN116627432A (en) | 2023-06-01 | 2023-06-01 | Front-end application automatic deployment method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116627432A true CN116627432A (en) | 2023-08-22 |
Family
ID=87641523
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310644712.6A Pending CN116627432A (en) | 2023-06-01 | 2023-06-01 | Front-end application automatic deployment method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116627432A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117492822A (en) * | 2023-12-29 | 2024-02-02 | 杭州新中大科技股份有限公司 | Change contrast method, device, electronic equipment and storage medium |
-
2023
- 2023-06-01 CN CN202310644712.6A patent/CN116627432A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117492822A (en) * | 2023-12-29 | 2024-02-02 | 杭州新中大科技股份有限公司 | Change contrast method, device, electronic equipment and storage medium |
| CN117492822B (en) * | 2023-12-29 | 2024-03-29 | 杭州新中大科技股份有限公司 | Change contrast method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN116627432A (en) | Front-end application automatic deployment method, device, equipment and medium | |
| CN116107589A (en) | Automatic compiling method, device and equipment of software codes and storage medium | |
| CN114389969A (en) | Client test method and device, electronic equipment and storage medium | |
| CN117520195A (en) | Method, apparatus, device, storage medium and program product for testing interface | |
| CN116545905A (en) | Service health detection method and device, electronic equipment and storage medium | |
| CN116303013A (en) | Source code analysis method, device, electronic equipment and storage medium | |
| CN116450176A (en) | Version updating method and device, electronic equipment and storage medium | |
| CN114997329A (en) | Method, apparatus, device, medium and product for generating a model | |
| CN115766697A (en) | File downloading method, device, equipment and storage medium | |
| CN115080003A (en) | Zero code platform operation method and device, electronic equipment and storage medium | |
| CN114610511B (en) | Input verification method and device, electronic equipment and storage medium | |
| CN113609145B (en) | Database processing method, device, electronic equipment, storage medium and product | |
| CN118260226A (en) | Real machine preview method, device, medium and equipment of application program | |
| CN117370209A (en) | Application program performance test method, device, medium and electronic equipment | |
| CN115617616A (en) | Operation monitoring method, device and equipment of server FRU and storage medium | |
| CN117193825A (en) | Method and device for calling update function, electronic equipment and storage medium | |
| CN116627442A (en) | Version update prompting method, device, equipment and medium of application program interface | |
| CN116628107A (en) | Data comparison method, device, equipment and medium | |
| CN117472361A (en) | Service modeling method, device, equipment and storage medium | |
| CN118394323A (en) | Visual control processing method, device, equipment and medium | |
| CN117609150A (en) | Data migration method, device, equipment and medium | |
| CN117632149A (en) | Control method and device of application program, electronic equipment and storage medium | |
| CN114564133A (en) | Application program display method, device, equipment and medium | |
| CN117806702A (en) | Target software acquisition method and device, electronic equipment and storage medium | |
| CN118567659A (en) | System deployment method, device, equipment and medium |
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 |