CN115509573A

CN115509573A - Method and device for deploying front-end project, electronic equipment and storage medium

Info

Publication number: CN115509573A
Application number: CN202211150176.6A
Authority: CN
Inventors: 闫珍珍
Original assignee: Ping An Life Insurance Company of China Ltd
Current assignee: Ping An Life Insurance Company of China Ltd
Priority date: 2022-09-21
Filing date: 2022-09-21
Publication date: 2022-12-23

Abstract

The embodiment provides a method and a device for deploying a front-end project, electronic equipment and a storage medium, belonging to the technical field of artificial intelligence and research and development management, wherein the method comprises the following steps: acquiring a front-end code to be issued in a front-end project, and determining project information corresponding to the front-end code; constructing a JAR packet based on the front-end code and project information corresponding to the front-end code, and recording the closing time of the JAR packet; setting effective time for the JAR packet and storing the JAR packet so that the JAR packet is tested by a back end; under the condition that the rear end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined, issuing the JAR packet and recording the issuing time of the JAR packet; updating resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project; according to the method and the system, fine management can be performed on deployment of a large number of front-end projects, and personalized configuration is provided.

Description

Method and device for deploying front-end project, electronic equipment and storage medium

Technical Field

The present application relates to the technical field of artificial intelligence and research and development management, and in particular, to a method and an apparatus for front-end project deployment, an electronic device, and a storage medium.

Background

The enterprise-level project usually adopts a project group form to develop the business, a rapid iteration mode is adopted for developing the front-end project corresponding to each business, the front-end projects of each version are released and managed, the types of the on-line application programs are continuously increased along with the development of computer technologies such as artificial intelligence and the like, and the product updating speed is high; there is a need to manage multiple front-end projects in an enterprise level project, and each front-end project for multiple versions.

Therefore, how to perform fine management on the deployment of a large number of front-end projects and provide personalized configuration becomes a technical problem to be solved urgently.

Disclosure of Invention

The embodiments of the present application mainly aim to provide a method and an apparatus for front-end project deployment, an electronic device, and a storage medium, which aim to perform fine management on deployment of a large number of front-end projects and provide personalized configurations.

To achieve the above object, a first aspect of an embodiment of the present application provides a method for front-end project deployment, where the method includes:

acquiring a front-end code to be issued in a front-end project, and determining project information corresponding to the front-end code; the project information comprises project group information, project information and a version number;

constructing a JAR packet based on the front-end code and project information corresponding to the front-end code, and recording the closing time of the JAR packet; wherein the closing time is the time for completing the construction of the JAR package;

setting effective time for the JAR packet and storing the JAR packet so that a back end can test the JAR packet;

under the condition that the rear end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined, issuing the JAR packet and recording the issuing time of the JAR packet; wherein the validation time is after the publication time;

and updating resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project.

In some embodiments, the constructing a JAR package based on the front-end code and project information corresponding to the front-end code includes:

determining a node _ modules folder corresponding to the project information;

configuring a building module corresponding to the project information in the node _ modules folder;

and acquiring project information corresponding to the front-end code, calling the construction module to construct the front-end code and the project information corresponding to the front-end code, and generating a JAR package.

In some embodiments, the setting an effective time for the JAR package and storing the JAR package so that a backend tests the JAR package includes:

obtaining a JAR packet obtained by construction;

setting the effective time of the JAR packet, adding the effective time to the JAR packet, and uploading the JAR packet to MongoDB;

the backend accesses the JAR package in the montgodb through DevOps and tests the JAR package.

In some embodiments, the updating, based on the JAR package issued in the front-end project, the resources of the JAR package that has not been issued in the front-end project includes:

respectively setting independent resource packages for JAR packages corresponding to each version number in a front-end project, and storing resources of the JAR packages into corresponding resource packages;

after the JAR package in the front-end project is released, determining the changed resources in the front-end project, and merging the changed resources in the front-end project into the resource package corresponding to the JAR package which is not released.

In some embodiments, after issuing the JAR package, the method further comprises:

uploading the JAR packet released in the front-end project to a resource management platform;

taking the JAR packet which reaches the effective time in the resource management platform as an effective JAR packet, counting access records of resources corresponding to the effective JAR packet, and updating the resources in the cache in real time based on the access records of the resources corresponding to the effective JAR packet.

In some embodiments, the counting access records of the resource corresponding to the effective JAR package, and updating the resource in the cache in real time based on the access records of the resource corresponding to the effective JAR package includes:

acquiring an access record of a resource corresponding to the effective JAR packet in the resource management platform by a front-end point burying method;

determining the access amount of each resource based on the access record of the resource corresponding to the effective JAR packet in the resource management platform;

preferentially caching the resources with the access amount higher than a first preset access amount threshold value, and performing cache cleaning on the resources with the access amount lower than a second preset access amount threshold value; and the first preset access amount threshold value is greater than the second preset access amount threshold value.

In some embodiments, the method further comprises:

if the version abnormality of the front-end project is detected, determining a version number corresponding to the version abnormality, and switching the front-end project to a version number before the version number corresponding to the version abnormality; the version exception comprises one of a closing plate exception and a publishing exception.

To achieve the above object, a second aspect of an embodiment of the present application proposes an apparatus for front-end project deployment, where the apparatus includes:

the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring a front-end code to be issued in a front-end project and determining project information corresponding to the front-end code; the project information comprises project group information, project information and a version number;

the construction module is used for constructing a JAR package based on the front-end code and the project information corresponding to the front-end code, and recording the closing plate time of the JAR package; wherein the closing time is the time for completing the construction of the JAR package;

the storage module is used for storing the JAR packet after setting the effective time so as to enable a back end to test the JAR packet;

the issuing module is used for issuing the JAR packet and recording the issuing time of the JAR packet under the condition that the back end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined; wherein the validation time is after the publication time;

and the updating module is used for updating resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project.

In order to achieve the above object, a third aspect of the embodiments of the present application provides an electronic device, which includes a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for implementing connection communication between the processor and the memory, where the program implements the method of the first aspect when executed by the processor.

To achieve the above object, a fourth aspect of the embodiments of the present application proposes a computer-readable storage medium for a computer-readable storage, the storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the method of the first aspect.

According to the method and the device for deploying the front-end project, the electronic equipment and the storage medium, the front-end code to be issued in the front-end project is obtained, and project information corresponding to the front-end code is determined; the project information comprises project group information, project information and a version number; the corresponding front-end code can be uniquely determined through the project information, so that a plurality of different front-end codes can be managed conveniently; constructing a JAR packet based on the front-end code and project information corresponding to the front-end code, and recording the closing time of the JAR packet; wherein the closing time is the time for completing the construction of the JAR package; then setting effective time for the JAR packet and storing the JAR packet so that a back end can test the JAR packet; the traceability of historical data is ensured, and high-efficiency delivery and automatic operation and maintenance are realized; by adopting a front-end VUE frame and a rear-end java frame, high-efficiency delivery and automatic operation and maintenance are realized; under the condition that the rear end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined, issuing the JAR packet and recording the issuing time of the JAR packet; wherein the validation time is after the publication time. And the front-end project is released in advance and takes effect on time after the effective time. And updating resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project, so that the resource synchronism and real-time performance in the front-end project are ensured.

According to the scheme provided by the embodiment of the application, the JAR packet can be stored after the validation time is set by adopting a front-end VUE frame and a rear-end java frame, so that the traceability of historical data is ensured; by managing the closing plate time, the release time and the effective time of different versions of the front-end project, the release platform isolates the JAR packets in the front-end project, so that the advanced release of a plurality of different JAR packets in the front-end project can be supported, and the JAR packets take effect on time after the effective time, and the personalized configuration of the release of the front-end project is realized; and updating the resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project, so as to ensure the synchronization and the real-time performance of the resources in the front-end project. According to the embodiment of the application, fine management can be performed on deployment of a large number of front-end projects, and personalized configuration is provided.

Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

FIG. 1 is a flowchart of a method for front-end project deployment provided by an embodiment of the present application;

FIG. 2 is a flowchart of step S200 in FIG. 1;

FIG. 3 is a flowchart of step S300 in FIG. 1;

FIG. 4 is a flowchart of step S500 in FIG. 1;

fig. 5 is a flowchart after step S400 in fig. 1;

fig. 6 is a flowchart of step S620 in fig. 5;

FIG. 7 is a schematic structural diagram of an apparatus for front-end project deployment according to an embodiment of the present application;

fig. 8 is a schematic hardware structure diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

It is noted that while functional block divisions are provided in device diagrams and logical sequences are shown in flowcharts, in some cases, steps shown or described may be performed in sequences other than block divisions within devices or flowcharts. The terms first, second and the like in the description and in the claims, and the drawings described above, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.

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 give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the application.

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

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

First, several terms referred to in the present application are resolved:

artificial Intelligence (AI): is a new technical science for researching and developing theories, methods, technologies and application systems for simulating, extending and expanding human intelligence; artificial intelligence is a branch of computer science that attempts to understand the essence of intelligence and produces a new intelligent machine that can react in a manner similar to human intelligence, and research in this field includes robotics, language recognition, image recognition, natural language processing, and expert systems, among others. The artificial intelligence can simulate the information process of human consciousness and thinking. Artificial intelligence is also a theory, method, technique and application system that uses a digital computer or a machine controlled by a digital computer to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use the knowledge to obtain the best results.

CMS (content management system): it is a software system between the WEB front end (Web server) and the back end office system or process (content creation, editing). The content creators, editors, and publishers use the content management system to submit, modify, approve, and publish content. The "content" referred to herein may include files, tables, pictures, data in a database, even video, and the like. The content management optionally provides a content capture tool to automatically capture the content of the third-party information source, such as text files, HTML Web pages, web services, relational databases, etc., and then put the content into its own content library after analysis. With the development of personalization, content management also assists the WEB front end to provide content to content users in a personalized manner, i.e. a personalized portal framework is provided, so as to better push the content to the browser end of the user based on WEB technology.

DevOps (a combination word of Development and Operations): is a collective term for a set of processes, methods and systems that facilitate communication, collaboration and integration between development (application/software engineering), technical operations and Quality Assurance (QA) departments. DevOps contains definitions and operations, which are the general term for development and operation and maintenance. DevOps-based software development can be applied to a test environment, and simultaneously, data packages can be integrated into the software environment. DevOps stands on the global angle, analyzes the development effect, strengthens cooperation and communication among personnel, is also the key point of software development and design work, and reasonably arranges the personnel. Under a DevOps framework, software is developed to realize automatic operation, so that the application of a human-computer interaction scheme is feasible.

In the related technology, the adopted scheme is that Jenkins is used for packing and deploying, and the Jenkins is a continuous integration tool based on Java development, so that software projects can be continuously integrated; however, due to the fact that Jenkins is slow in reaction speed, troublesome in debugging, weak in version control and incapable of being personalized in combination with the characteristics of front-end project deployment, the use scenario of deployment of a large number of front-end projects in enterprise-level projects cannot be met.

Based on this, in order to solve the technical problems in the background art, the present application provides a method and an apparatus for front-end project deployment, an electronic device, and a storage medium, which are intended to perform fine management on the deployment of a large number of front-end projects and provide personalized configurations.

The embodiment of the present application provides a method and an apparatus for deploying a front-end project, an electronic device, and a storage medium, which are specifically described in the following embodiments, and first a method for deploying a front-end project in the embodiment of the present application is described.

The embodiment of the application can acquire and process related data based on an artificial intelligence technology. Among them, artificial Intelligence (AI) is a theory, method, technique and application system that simulates, extends and expands human Intelligence using a digital computer or a machine controlled by a digital computer, senses the environment, acquires knowledge and uses the knowledge to obtain the best result.

The artificial intelligence infrastructure generally includes technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and the like.

The embodiment of the application provides a method for deploying a front-end project, and relates to the fields of artificial intelligence and research and development management. The method for deploying the front-end project provided by the embodiment of the application can be applied to a terminal, a server and software running in the terminal or the server. In some embodiments, the terminal may be a smartphone, tablet, laptop, desktop computer, smart watch, or the like; the server side can be configured as an independent physical server, or a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like; the software may be an application or the like that implements a method of front-end project deployment, but is not limited to the above form.

Embodiments of the application are operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In each embodiment of the present application, when data related to the user identity or characteristic, such as user information, user behavior data, user history data, and user location information, is processed, permission or consent of the user is obtained, and the data collection, use, and processing comply with relevant laws and regulations and standards of relevant countries and regions. In addition, when the embodiment of the present application needs to acquire sensitive personal information of a user, individual permission or individual consent of the user is obtained through a pop-up window or a jump to a confirmation page, and after the individual permission or individual consent of the user is definitely obtained, necessary user-related data for enabling the embodiment of the present application to operate normally is acquired.

The embodiments of the present application will be further explained with reference to the drawings.

Fig. 1 is an optional flowchart of a method for front-end project deployment according to an embodiment of the present application, where the method in fig. 1 may include, but is not limited to, step S100 to step S500.

Step S100, acquiring a front end code to be issued in a front end project, and determining project information corresponding to the front end code; the project information comprises project group information, project information and a version number;

in step S100 of some embodiments, the creating module may be logged in by using an account and a password; if the building module is not logged in, the building module can also be logged in by adopting a mock test mode, wherein the mock test refers to a test method for creating a virtual object for testing some objects which are not easy to construct or obtain in the test process. If the mock user exists, logging in by using the mock user, or authorizing after a system administrator manually audits the newly registered mock user;

after logging in a creating module, creating a project group to which the front-end code belongs, and setting project group information of the project group, wherein the project group information is used for identifying a service corresponding to the project group; then creating a project of the front-end code in the project group, and setting project information of the project, wherein the project information is used for identifying a sub-service corresponding to the project; after the project is created, creating a version number of the front-end code in the project, wherein the version number is used for identifying a version serial number iterated by the front-end code; and finishing the project information configuration corresponding to the front-end code. The corresponding front-end code can be uniquely determined through the project information, so that management of a plurality of different front-end codes is facilitated.

Step S200, constructing a JAR packet based on the front end code and project information corresponding to the front end code, and recording the closing time of the JAR packet; wherein the closing time is the time for completing the construction of the JAR package;

in step S200 of some embodiments, the JAR packet is constructed with a closing time as a timestamp of the JAR packet.

The JAR package in the embodiment of the application refers to a JAR file and is generated by packaging the front-end code; in the software field, JAR files (Java ARchive) is a software package file format that is typically used to aggregate a large number of Java class files, associated metadata and resource (text, pictures, etc.) files into one file in order to develop Java platform application software or libraries. The JAR file is an archived file, constructed in ZIP format, with JAR as the file extension. The user can create or extract a JAR file using the JDK's own JAR command. Other zip compression tools may also be used, with the filename within the JAR file being Unicode text. JAR files are used not only for compression and publishing, but also for deploying and packaging libraries, components, and plug-ins, and can be used directly by tools like compilers and JVMs.

Step S300, setting effective time for the JAR packet and storing the JAR packet so that a back end tests the JAR packet;

in step S300 of some embodiments, the validation time is a time at which the JAR package takes effect after release; setting effective time for the JAR packet and then storing the JAR packet to ensure that historical data can be traced; the front end adopts a VUE frame mode, the back end adopts a java frame mode, the front end sets the validation time of the JAR package based on DevOps, then the JAR package is stored, and the back end tests the JAR package, so that efficient delivery and automatic operation and maintenance are realized.

Step S400, issuing the JAR packet and recording the issuing time of the JAR packet under the condition that the rear end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined; wherein the validation time is after the publication time.

In step S400 of some embodiments, after completing the test of the JAR package, the operation and maintenance of the backend confirms whether the validation time of the JAR package needs to be updated, and after confirming that the validation time of the JAR package is not changed or resetting the validation time of the JAR package, uploads the JAR package to the CMS through the DevOps and attaches the validation time of the JAR package; and the CMS stores the JAR package, updates the front-end project to the JAR package of the latest version after the validation time by updating the json file, realizes the early release of the front-end project and takes effect on time after the validation time. Because the closing time, the release time and the effective time of the JAR packets in the front-end project are recorded, each JAR packet in the front-end project can be accurately associated by combining the project information corresponding to the JAR packets, accurate positioning and control can be performed on any JAR packet in the front-end project, version switching control can be performed on the front-end project more completely, effective control can be performed on the JAR packets of the corresponding versions, each JAR packet in the front-end project can be monitored, and the like, so that efficient management can be performed on a large number of front-end projects.

And step S500, updating resources of the JAR packet which is not issued in the front-end project based on the JAR packet issued in the front-end project.

In step S500 of some embodiments, the issued JAR package may cause a change in resources, and the JAR package that has not been issued in the front-end project is updated with resources based on the issued JAR package, so as to ensure resource synchronization and real-time performance in the front-end project; the resources in this embodiment refer to type files such as js files, css files, and pictures used by the front-end project.

In steps S100 to S500 illustrated in the embodiment of the present application, a front-end code to be issued in a front-end project is acquired, and project information corresponding to the front-end code is determined; the project information comprises project group information, project information and a version number; the corresponding front-end code can be uniquely determined through the project information, so that a plurality of different front-end codes can be managed conveniently; constructing a JAR package based on the front-end code and the project information corresponding to the front-end code, and recording the closing time of the JAR package; wherein the closing time is the time for completing the construction of the JAR package; then setting effective time for the JAR packet and storing the JAR packet so that a back end tests the JAR packet; the traceability of historical data is ensured, and high-efficiency delivery and automatic operation and maintenance are realized; by adopting a mode of separating a front end from a rear end, namely a front end VUE frame and a rear end java frame, high-efficiency delivery and automatic operation and maintenance are realized; under the condition that the rear end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined, issuing the JAR packet and recording the issuing time of the JAR packet; wherein the validation time is subsequent to the publication time. The method realizes the early release of the front-end project and takes effect on time after the effective time. And updating the resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project, so as to ensure the synchronization and the real-time performance of the resources in the front-end project.

According to the scheme provided by the embodiment of the application, the JAR packet can be stored after setting the validation time by adopting a front end VUE frame and a rear end java frame, so that the traceability of historical data is ensured; by managing the closing plate time, the release time and the effective time of different versions of the front-end project, the release platform isolates the JAR packets in the front-end project, so that the advanced release of a plurality of different JAR packets in the front-end project can be supported, the JAR packets take effect on time after the effective time, and the personalized configuration of the release of the front-end project is realized; and updating the resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project, so as to ensure the synchronization and the real-time performance of the resources in the front-end project. Therefore, fine management is carried out on deployment of a large number of front-end projects, and personalized configuration is provided.

Referring to fig. 2, in step S200 of some embodiments, the building a JAR package based on the front end code and the project information corresponding to the front end code may include, but is not limited to, step S210 to step S230:

step S210, determining a node _ modules folder corresponding to the project information;

step S220, configuring a construction module corresponding to the project information in the node _ modules folder;

step S230, acquiring the project information corresponding to the front-end code, calling the construction module to construct the front-end code and the project information corresponding to the front-end code, and generating a JAR package.

It should be noted that, in step S200 in some embodiments, the node _ modules folder is a folder used for storing the package to be installed downloaded by the package management tool after the node is installed. Such as webpack, gulp, grunt building blocks. Each item information corresponds to a node _ modules folder, the node _ modules folder is uniquely corresponding to one version number of the front-end code, and a construction module for compiling and constructing the front-end code is stored in the node _ modules folder; in an embodiment, whether a node _ modules folder corresponding to the item information exists is determined, if not, a node _ modules folder corresponding to the item information is manually uploaded, a building module is configured in the node _ modules folder, and the front-end code is built into a JAR package through the building module.

In some embodiments, as shown in fig. 3, step S300 may include, but is not limited to, steps S310 to S330:

step S310, obtaining a JAR packet obtained by construction;

step S320, setting the effective time of the JAR packet, adding the effective time to the JAR packet, and uploading the JAR packet to a MongoDB;

in step S320 of some embodiments, a project Version time is adopted to add a timestamp to the JAR package, where the timestamp is used as an effective time of the JAR package, and the JAR package is uploaded to a MongoDB deployed in a cloud server after the effective time is added; mongoDB is a database based on distributed file storage, and data can be stored persistently through MongoDB, so that the traceability of historical data is guaranteed.

And step S330, the back end accesses the JAR packet in the MongoDB through the DevOps and tests the JAR packet.

In step S330 of some embodiments, the operation and maintenance of the back end accesses the JAR package in the montogdb through the DevOps, so as to perform the pre-release test on the JAR package.

In some embodiments, as shown in fig. 4, step S500 may include, but is not limited to, step S510 to step S520:

step S510, independent resource packages are respectively set for JAR packages corresponding to each version number in a front-end project, and resources of the JAR packages are stored into the corresponding resource packages;

in step S510 of some embodiments, for the release management of the front-end item, the version number of the front-end item and the resource corresponding to each version number need to be managed, and especially, in the case that a plurality of parallel JAR packages exist in the front-end item, an independent resource package is respectively set for the resource of the version number corresponding to each JAR package, so as to perform isolation management.

Step S520, after the JAR packet in the front-end project is issued, the resources changed in the front-end project are determined, and the resources changed in the front-end project are merged into the resource packet corresponding to the JAR packet which is not issued.

In step S520 of some embodiments, after the JAR package is released, the resource that has been changed in the front-end project is merged into the resource package corresponding to the JAR package that has not been released, so as to ensure the resource synchronization in the front-end project.

In some embodiments, as shown in fig. 5, after issuing the JAR package, the method further comprises:

step S610, uploading the JAR packet released in the front-end project to a resource management platform;

in step S610 of some embodiments, uploading the JAR packages issued in the front-end project to a resource management platform, so as to perform unified management on resources of each issued JAR package in the resource management platform, and count access conditions of each resource in the resource management platform;

step S620, taking the JAR packet which reaches the effective time in the resource management platform as an effective JAR packet, counting the access records of the resources corresponding to the effective JAR packet, and updating the resources in the cache in real time based on the access records of the resources corresponding to the effective JAR packet.

In step S620 of some embodiments, it is determined, for a front-end item uniformly published on a publishing platform, whether a JAR package in the resource management platform reaches an effective time, the JAR package reaching the effective time in the resource management platform is used as an effective JAR package, a resource in the effective JAR package can be accessed by a user, an access condition of the resource is counted based on an actual use condition of the resource corresponding to the effective JAR package by the user, and a resource access report is output to form an access record of the resource in the published JAR package.

In some embodiments, as shown in fig. 6, in step S620, the counting is performed on the access record of the resource corresponding to the effective JAR packet, and the resource in the cache is updated in real time based on the access record of the resource corresponding to the effective JAR packet, which may include, but is not limited to, steps S621 to S623:

step S621, obtaining access records of resources corresponding to the effective JAR packet in the resource management platform by a front-end point burying method;

step S622, determining the access amount of each resource based on the access record of the resource corresponding to the effective JAR packet in the resource management platform;

step S623, caching the resources with the access amount higher than the first preset access amount threshold preferentially, and caching and cleaning the resources with the access amount lower than the second preset access amount threshold; and the first preset access amount threshold value is larger than the second preset access amount threshold value.

In step S623 of some embodiments, the first preset access amount threshold and the second preset access amount threshold may be preset according to an actual situation, and the specific first preset access amount threshold and the specific second preset access amount threshold are not limited in this embodiment; if the cache capacity is large, on the premise of not influencing the access efficiency, more resources can be stored, the first preset access amount threshold value can be set to be a small value, and the second preset access amount threshold value is set to be a large value, so that more resources are stored; otherwise, the first preset access amount threshold is set to a smaller value, and the second preset access amount threshold is set to a larger value.

In some embodiments, access conditions of various resources are recorded through a front-end point burying method, resources most frequently accessed are screened out for special-level caching, specifically, the condition that a user uses the resources at a mobile phone end is recorded, the resources with larger usage are calculated in real time and serve as real-time hot resources, the real-time hot resources are uploaded to a cloud server, meanwhile, the real-time hot resources are automatically refreshed to a CDN (content distribution network), and the access performance of a front-end project is improved through real-time resource updating of access caching; meanwhile, when the mobile phone sends a packet, resources which are not accessed within a period of time are pushed to corresponding developers periodically; the method comprises the following steps that a developer carries out cache cleaning operation on resources which are not accessed or have a small access amount within a period of time, so that the cache space can be saved under the condition of maximally improving the access performance by combining the access condition of the resources;

in some embodiments further provided by step S620, by caching the real-time hot resources, the management of the H5 and the mobile phone resources is unified, the resources most frequently accessed by the user can be calculated according to the use condition of the user, and the resources are managed according to various rules such as the operation requirements of the product itself, so that the user can access the resources conveniently, the back-end traffic and the cost are saved, the loading speed of the front-end resources is increased, and the user experience is improved.

In some embodiments, the method further comprises:

In some embodiments, under the conditions that a closing plate is abnormal and a version is abnormal, a support version rapidly notifies a responsible person of abnormal front-end project condition mails to timely deal with the abnormality; abnormal scenes such as complete monitoring, no sealing plate, no timely release and the like can be quickly notified to a resolver. If the version of the newly released front-end project has problems, the newly released front-end project can be restored to the designated historical version by one key, and both the package resources and the version records of the historical version can be persistently stored; because the resource access can be switched to the historical version of the published front-end project at will, the effects of quick response to problems and convenient rollback are achieved.

Therefore, the embodiment of the application integrates construction and deployment, can provide personalized functions such as resource access caching, CDN refreshing and the like by combining self research and development ecology, and is more complete in aspects of version switching control, effective control, monitoring and the like.

The embodiment of the application provides a method and a device for deploying a front-end project, electronic equipment and a storage medium, wherein the method for deploying the front-end project comprises the following steps: acquiring a front-end code to be issued in a front-end project, and determining project information corresponding to the front-end code; the project information comprises project group information, project information and a version number; constructing a JAR packet based on the front-end code and project information corresponding to the front-end code, and recording the closing time of the JAR packet; wherein the closing time is the time for completing the construction of the JAR package; setting effective time for the JAR packet and storing the JAR packet so that a back end tests the JAR packet; under the condition that the rear end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined, issuing the JAR packet and recording the issuing time of the JAR packet; wherein the validation time is subsequent to the publication time; and updating resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project.

According to the scheme provided by the embodiment of the application, the front-end code to be issued in the front-end project can be obtained, and the project information corresponding to the front-end code is determined; the project information comprises project group information, project information and a version number; the corresponding front-end code can be uniquely determined through the project information, so that a plurality of different front-end codes can be managed conveniently; constructing a JAR package based on the front-end code and the project information corresponding to the front-end code, and recording the closing time of the JAR package; wherein the closing time is the time for completing the construction of the JAR package; then setting effective time for the JAR packet and storing the JAR packet so that a back end tests the JAR packet; the traceability of historical data is ensured, and high-efficiency delivery and automatic operation and maintenance are realized; the mode of adopting a front-end VUE frame and a rear-end java frame is adopted, so that efficient delivery and automatic operation and maintenance are realized; under the condition that the rear end is determined to finish testing the JAR packet and the effective time of the JAR packet is determined, issuing the JAR packet and recording the issuing time of the JAR packet; wherein the validation time is subsequent to the publication time. And the front-end project is released in advance and takes effect on time after the effective time. And updating resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project, so that the resource synchronism and real-time performance in the front-end project are ensured.

According to the scheme provided by the embodiment of the application, the JAR packet can be stored after the validation time is set by adopting a front-end VUE frame and a rear-end java frame, so that the traceability of historical data is ensured; by managing the closing plate time, the release time and the effective time of different versions of the front-end project, the release platform isolates the JAR packets in the front-end project, so that the advanced release of a plurality of different JAR packets in the front-end project can be supported, the JAR packets take effect on time after the effective time, and the personalized configuration of the release of the front-end project is realized; and updating resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project, so that the resource synchronism and real-time performance in the front-end project are ensured. Therefore, fine management is carried out on deployment of a large number of front-end projects, and personalized configuration is provided.

Referring to fig. 7, an embodiment of the present application further provides a device for front-end project deployment, which may implement the method for front-end project deployment, where the device includes:

an obtaining module 100, configured to obtain a front-end code to be issued in a front-end project, and determine project information corresponding to the front-end code; the project information comprises project group information, project information and a version number;

a constructing module 200, configured to construct a JAR package based on the front-end code and the item information corresponding to the front-end code, and record a closing time of the JAR package; wherein the closing time is the time for completing the construction of the JAR package;

the storage module 300 is configured to set an effective time for the JAR packet and store the effective time so that a back end tests the JAR packet;

the issuing module 400 is configured to issue the JAR package and record the issuing time of the JAR package when it is determined that the back end completes the test on the JAR package and the validation time of the JAR package is determined; wherein the validation time is after the publication time;

an updating module 500, configured to update a resource of the JAR package that is not published in the front-end project based on the JAR package published in the front-end project.

The specific implementation of the apparatus for front-end project deployment is substantially the same as the specific implementation of the method for front-end project deployment, and is not described herein again.

An embodiment of the present application further provides an electronic device, where the electronic device includes: the system comprises a memory, a processor, a program stored on the memory and capable of running on the processor, and a data bus for implementing a connection communication between the processor and the memory, the program, when executed by the processor, implementing the method of front-end item deployment described above. The electronic equipment can be any intelligent terminal including a tablet computer, a vehicle-mounted computer and the like.

Referring to fig. 8, fig. 8 illustrates a hardware structure of an electronic device according to another embodiment, where the electronic device includes:

the processor 801 may be implemented by a general-purpose CPU (Central-Processing Unit), a microprocessor, an Application-Specific-Integrated-Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solution provided in the embodiments of the present Application;

the Memory 802 may be implemented in the form of a Read-Only-Memory (ROM), a static storage device, a dynamic storage device, or a Random-Access-Memory (RAM). The memory 802 may store an operating system and other application programs, and when the technical solution provided in the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 802, and the processor 801 calls the method for executing the front-end project deployment according to the embodiments of the present application;

an input/output interface 803 for realizing input and output of information;

the communication interface 804 is used for realizing communication interaction between the device and other devices, and can realize communication in a wired manner (such as USB, network cable, and the like) or in a wireless manner (such as mobile network, WIFI, bluetooth, and the like);

a bus 805 that transfers information between the various components of the device (e.g., the processor 801, memory 802, input/output interfaces 803, and communication interface 804);

wherein the processor 801, the memory 802, the input/output interface 803 and the communication interface 804 are communicatively connected to each other within the device via a bus 805.

Embodiments of the present application further provide a computer-readable storage medium for a computer-readable storage, where the storage medium stores one or more programs, and the one or more programs are executable by one or more processors to implement the method for front-end project deployment.

The memory, as a non-transitory computer-readable storage medium, may be used to store non-transitory software programs as well as non-transitory computer-executable programs. Further, the memory may include high speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory located remotely from the processor, and these remote memories may be connected to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

According to the method and the device for deploying the front-end project, the electronic equipment and the storage medium, the front-end code to be issued in the front-end project is obtained, and the project information corresponding to the front-end code is determined; the project information comprises project group information, project information and a version number; the corresponding front-end code can be uniquely determined through the project information, so that a plurality of different front-end codes can be managed conveniently; constructing a JAR packet based on the front-end code and project information corresponding to the front-end code, and recording the closing time of the JAR packet; wherein the closing time is the time for completing the construction of the JAR package; then setting effective time for the JAR packet and storing the JAR packet so that a back end tests the JAR packet; the traceability of historical data is ensured, and high-efficiency delivery and automatic operation and maintenance are realized; the mode of adopting a front-end VUE frame and a rear-end java frame is adopted, so that efficient delivery and automatic operation and maintenance are realized; under the condition that the rear end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined, issuing the JAR packet and recording the issuing time of the JAR packet; wherein the validation time is after the publication time. And the front-end project is released in advance and takes effect on time after the effective time. And updating resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project, so that the resource synchronism and real-time performance in the front-end project are ensured.

According to the scheme provided by the embodiment of the application, the JAR packet can be stored after the validation time is set by adopting a front-end VUE frame and a rear-end java frame, so that the traceability of historical data is ensured; by managing the closing plate time, the release time and the effective time of different versions of the front-end project, the release platform isolates the JAR packets in the front-end project, so that the advanced release of a plurality of different JAR packets in the front-end project can be supported, and the JAR packets take effect on time after the effective time, and the personalized configuration of the release of the front-end project is realized; and updating the resources of the JAR packet which is not released in the front-end project based on the JAR packet released in the front-end project, so as to ensure the synchronization and the real-time performance of the resources in the front-end project. Therefore, fine management is carried out on deployment of a large number of front-end projects, and personalized configuration is provided.

The embodiments described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided in the embodiments of the present application, and it is obvious to those skilled in the art that the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems with the evolution of technologies and the emergence of new application scenarios.

It will be appreciated by those skilled in the art that the solutions shown in fig. 1-6 are not intended to limit the embodiments of the present application and may include more or fewer steps than those shown, or some of the steps may be combined, or different steps may be included.

The above-described embodiments of the apparatus are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, i.e. may be located in one place, or may also be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, and functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof.

The terms "first," "second," "third," "fourth," and the like (if any) in the description of the present application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Moreover, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" is used to describe the association relationship of the associated object, indicating that there may be three relationships, for example, "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b and c may be single or plural.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes multiple instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing programs, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The preferred embodiments of the present application have been described above with reference to the accompanying drawings, and the scope of the claims of the embodiments of the present application is not limited thereto. Any modifications, equivalents and improvements that may occur to those skilled in the art without departing from the scope and spirit of the embodiments of the present application are intended to be within the scope of the claims of the embodiments of the present application.

Claims

1. A method of front-end project deployment, the method comprising:

constructing a JAR package based on the front-end code and the project information corresponding to the front-end code, and recording the closing time of the JAR package; wherein the closing time is the time for completing the construction of the JAR package;

setting effective time for the JAR packet and storing the JAR packet so that a back end tests the JAR packet;

2. The method according to claim 1, wherein the constructing the JAR package based on the front end code and the project information corresponding to the front end code comprises:

determining a node _ modules folder corresponding to the item information;

configuring a construction module corresponding to the project information in the node _ modules folder;

3. The method according to claim 1, wherein the storing the JAR packet after setting the validation time so that a backend tests the JAR packet comprises:

obtaining a JAR packet obtained by construction;

setting the effective time of the JAR packet, adding the effective time to the JAR packet, and uploading the JAR packet to the MongoDB;

4. The method of claim 1, wherein the updating the resource of the JAR package that has not been published in the front-end project based on the JAR package published in the front-end project comprises:

after the JAR package in the front-end project is released, the resource changed in the front-end project is determined, and the resource changed in the front-end project is merged to the resource package corresponding to the JAR package which is not released.

5. The method of claim 1, wherein after issuing the JAR package, the method further comprises:

6. The method according to claim 5, wherein the counting access records of the resource corresponding to the effective JAR package, and updating the resource in the cache in real time based on the access record of the resource corresponding to the effective JAR package comprises:

preferentially caching the resources with the access amount higher than a first preset access amount threshold value, and performing cache cleaning on the resources with the access amount lower than a second preset access amount threshold value; and the first preset access amount threshold value is larger than the second preset access amount threshold value.

7. The method of any of claims 1 to 6, further comprising:

8. An apparatus for front-end project deployment, the apparatus comprising:

the system comprises an acquisition module, a distribution module and a distribution module, wherein the acquisition module is used for acquiring front-end codes to be issued in front-end projects and determining project information corresponding to the front-end codes; the project information comprises project group information, project information and a version number;

the issuing module is used for issuing the JAR packet and recording the issuing time of the JAR packet under the condition that the rear end is determined to finish the test of the JAR packet and the effective time of the JAR packet is determined; wherein the validation time is after the publication time;

9. An electronic device, characterized in that the electronic device comprises a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for enabling a connection communication between the processor and the memory, which program, when executed by the processor, realizes the steps of the method according to any one of claims 1 to 7.

10. A computer readable storage medium for computer readable storage, characterized in that the storage medium stores one or more programs, which are executable by one or more processors, to implement the steps of the method of any of claims 1 to 7.