CN117331599A

CN117331599A - Application release method and device

Info

Publication number: CN117331599A
Application number: CN202311357800.4A
Authority: CN
Inventors: 方海波; 范庚标
Original assignee: Zhejiang Geely Holding Group Co Ltd; Zhejiang Zeekr Intelligent Technology Co Ltd
Current assignee: Zhejiang Geely Holding Group Co Ltd; Zhejiang Zeekr Intelligent Technology Co Ltd
Priority date: 2023-10-18
Filing date: 2023-10-18
Publication date: 2024-01-02

Abstract

The specification provides an application publishing method and device. The release control center is respectively in butt joint with a plurality of application release systems, and the release control center stores a preset release time period. The method is applied to any application release system in the application release systems. The method comprises the following steps: acquiring a preset release time period in the release control center; judging whether the current moment is within the release time period or not; the release time period is composed of a first moment and a second moment which is larger than the first moment; if the current time is not in the release time period, determining the time difference between the current time and the first time of the release time period, and releasing the target application to be released into the corresponding target environment after the time corresponding to the time difference.

Description

Application release method and device

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to an application publishing method, an application publishing device, an electronic device, and a machine-readable storage medium.

Background

In the development process of the application program, the newly developed application program generally needs to be subjected to multiple rounds of testing and then be overtly online. Ideally, a developer will generally choose to release an application program into the test environment for testing during a period of time (i.e., a window period) in which the test environment is not highly available, so that the available period of time in the entire test environment can be increased. However, developers always issue applications in non-windowed periods for various reasons, thereby affecting the overall development efficiency.

Disclosure of Invention

In a first aspect, the present application provides an application publishing method, where a publishing control center interfaces with a plurality of application publishing systems respectively, and the publishing control center stores a preset publishing time period; the method is applied to any application release system in the plurality of application release systems; the method comprises the following steps:

acquiring a preset release time period in the release control center;

judging whether the current moment is within the release time period or not; the release time period is composed of a first moment and a second moment which is larger than the first moment;

if the current time is not in the release time period, determining the time difference between the current time and the first time of the release time period, and releasing the target application to be released into the corresponding target environment after the time corresponding to the time difference.

In an illustrated embodiment, the frequency of use of the target environment during the release time period is less than a preset threshold.

In an illustrated embodiment, the target environment includes a plurality of devices therein; the publishing the target application to be published to the corresponding target environment comprises the following steps:

determining target equipment corresponding to a target application to be issued from a plurality of pieces of equipment contained in a target environment, and issuing the target application to the target equipment; wherein the target environment is a test environment or a production environment.

In one illustrated embodiment, the distribution control center maintains a plurality of preset distribution time periods;

and if the current time is not in the release time period, determining a time difference between the current time and the first time of the release time period, including:

if the current time is not in any one of the plurality of release time periods, determining a release time period closest to the current time from the plurality of release time periods, and calculating a time difference between the current time and the first time of the release time period.

In an illustrated embodiment, the method further comprises:

and if the current moment is within the release time period, releasing the target application to be released into the corresponding target environment.

In an embodiment, the obtaining a preset release time period in the release control center includes:

and calling a query interface provided by the release control center to query a preset release time period in the release control center.

In an illustrated embodiment, the query interface includes an application programming interface that complies with REST specifications.

In an embodiment, before acquiring the release time period preset in the release control center, the method further includes:

and aiming at the target application to be released, constructing and compiling codes and performing static inspection on the codes.

In an illustrated embodiment, the application publishing system includes any of a jenkins system, a Lotus system, a Starlink system.

In a second aspect, the present application provides an application publishing device, where a publishing control center interfaces with a plurality of application publishing systems respectively, and the publishing control center stores a preset publishing time period; the device is applied to any application release system in the application release systems; the device comprises:

an acquisition unit, configured to acquire a release time period preset in the release control center;

the judging unit is used for judging whether the current moment is in the release time period or not; the release time period is composed of a first moment and a second moment which is larger than the first moment;

and the first issuing unit is used for determining the time difference between the current time and the first time of the issuing time period if the current time is not in the issuing time period, and issuing the target application to be issued into the corresponding target environment after the time corresponding to the time difference.

The application also provides electronic equipment, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;

the memory stores machine readable instructions, and the processor executes the application issuing method according to the first aspect by calling the machine readable instructions.

The present application also provides a machine-readable storage medium storing machine-readable instructions which, when invoked and executed by a processor, implement the application publishing method of the first aspect.

The technical scheme provided by the application at least can comprise the following beneficial effects:

through the above embodiments, the present application may pre-construct a distribution control center, which may interface with a plurality of distribution systems, respectively. Further, an ideal release time period may be preset in the release control center, where the release time period may be formed by a first time and a second time that is greater than the first time. Further, any application release system of the plurality of application release systems may acquire a preset release time period from the release control center before releasing the application, and check whether the current time is within the release time period. If the current time is not within the release time period, the application release system can determine the time difference between the current time and the first time of the release time period, and release the target application to be released into the corresponding target environment after the time corresponding to the time difference. Therefore, the application of each application release system can be released in a window period (namely, a period of time with low target environment utilization rate), so that the available period of the whole target environment is improved, and the research and development efficiency is further ensured.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description will briefly introduce the drawings that are required to be used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may also be obtained according to these drawings for a person having ordinary skill in the art.

FIG. 1 is a system architecture diagram illustrating an application release in accordance with an exemplary embodiment.

FIG. 2 is a flow chart illustrating an application publishing method in accordance with an exemplary embodiment.

Fig. 3 is a hardware configuration diagram of an electronic device in which an application publishing device is located, according to an exemplary embodiment.

FIG. 4 is a block diagram of an application publishing device, as shown in an exemplary embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments.

As described above, in the development process of an application program (or software), a newly developed application program generally needs to be subjected to multiple rounds of testing and then be exposed and online. Typically, a developer will publish an application program to a test environment for testing through an application publishing system. The test environment (Testing environment) refers to a general term for computer hardware, software, network devices, and history data necessary for completing the application test work. In short, through a well-planned and managed test environment, adverse effects of environmental changes on the test work can be reduced as much as possible, and positive effects on the efficiency and quality of the test work can be exerted, etc., and detailed description thereof will not be given here.

The stability of the test environment is the most important basis for ensuring that the test can be continuously and effectively performed, and the nonstandard release of the application program can seriously influence the stability of the test environment. Ideally, a developer will typically choose to release an application during a period of time (i.e., window period) where the test environment is not highly available, which can promote the available period of time for the entire test environment. However, developers always issue applications in non-windowed periods for various reasons, thereby affecting the overall development efficiency.

In view of this, the present application aims to propose an application publishing method. The method can be used for constructing the release control center in advance, presetting a release time period, acquiring the release time period preset by the release control center before releasing the application by the release system, checking whether the current moment is in the release time period, and if not, waiting for the release time period to release the application so as to avoid releasing the application program in a non-window period.

When the method is realized, the release control center is respectively in butt joint with a plurality of application release systems, and the release control center stores a preset release time period. Any application release system in the plurality of application release systems can acquire a release time period preset in the release control center.

Further, the application publishing system can judge whether the current moment is within the publishing time period; the release time period is composed of a first moment and a second moment which is larger than the first moment;

further, if the current time is not within the release time period, the application release system may determine a time difference between the current time and the first time of the release time period, and release the target application to be released into the corresponding target environment after a duration corresponding to the time difference.

The following describes the present application through specific embodiments and in connection with specific application scenarios.

Referring to fig. 1, fig. 1 is a schematic diagram illustrating a system architecture of an application publishing system according to an exemplary embodiment. One or more embodiments provided herein may be embodied in the system architecture shown in fig. 1 or a similar system architecture. As shown in fig. 1, the system architecture includes a release control center 10 and a plurality of application release systems, and may specifically include an application release system 20a, an application release system 20b, an application release system 20c, and so on.

Wherein the distribution control center 10 can establish communication connection with the application distribution system 20a, the application distribution system 20b, the application distribution system 20c, and the like, respectively, in any possible manner. In an illustrated embodiment, the issue control center 10 may establish communication connections with the application issue system 20a, the application issue system 20b, the application issue system 20c, and the like, respectively, by way of a wired or wireless network.

The specific types of the application distribution system 20a, the application distribution system 20b, and the application distribution system 20c are not particularly limited in this application. In an illustrated embodiment, the application publishing system 20a, the application publishing system 20b, and the application publishing system 20c may be any one of jenkins (open source persistent integration tool), lotus (quasi-machine distribution system), starlink (container cloud publishing system), and the like, which is not specifically limited in this specification.

In an illustrated embodiment, the release control center 10, as well as the application release systems 20a, 20b, 20c, may interface with a target environment (not shown in FIG. 1). The application publishing system 20a, the application publishing system 20b, the application publishing system 20c may publish the developed target application (or one or more micro-services contained by the target application) into a target environment.

For example, the target environment may be a test environment, and accordingly, the application release systems 20a, 20b, and 20c may release the developed target application program into the test environment for application testing. The target environment may be a production environment, and accordingly, the application release system 20a, the application release system 20b, the application release system 20c may release the developed and tested target application program to the production environment for online processing of the application, and the like, which is not particularly limited in this specification.

In one illustrated embodiment, a user (e.g., a developer) may set a suitable distribution time period (i.e., a distribution window) in the distribution control center 10. The release time period may be formed by a first time and a second time that is greater than the first time, i.e., the release time period is a time period between the first time and the second time.

It should be noted that, how to set the distribution time period is not particularly limited in the present application. In an illustrated embodiment, the frequency of use of the target environment during the publication time period may be less than a preset threshold. For example, the target environment may be a test environment, and accordingly, a test frequency of the test environment in the release period may be less than a preset threshold. The target environment may also be a production environment, etc., by way of example, and the present specification is not limited in detail.

Specifically, the user may set the release time period based on various factors such as the current development activity requirement, the importance of the application to be released, and the stability of the application release system.

By way of example, research and development activities may include various activities such as application development, testing, and online, as this specification is not intended to be limiting in any way.

By way of example, where research and development activities are mostly conducted in the morning and afternoon, and where research and development activities are not substantially conducted in the noon, the release time period may be set to 2 hours between 12:00 and 14:00, 1 hour between 12:00 and 13:00, and so on, which is not particularly limited in this specification.

In an illustrated embodiment, the distribution control center 10 may output a preset distribution time period setting interface to the user, and accordingly, the user may set one or more distribution time periods through the setting interface.

In an illustrated embodiment, taking the application publishing system 20a of the plurality of application publishing systems as an example, the application publishing system 20a may acquire a publishing period preset in the publishing control center 10 before publishing a target application to be published to a target environment. Further, the application publishing system 20a may determine whether the current time is within the publishing period. If the current time is within the publishing time period, the application publishing system 20a may directly publish the target application to be published to the corresponding target environment. If the current time is not within the release time period, the application release system 20a may determine a time difference between the current time and the first time of the release time period, and release the target application to be released into the corresponding target environment after a duration corresponding to the time difference (and after reaching the release time period) has elapsed.

The specific type of the target application is not particularly limited in the present application. In an embodiment, the target application may be any one of a video application, a shopping application, a music application, a reading application, a drawing application, a social application, and the like, which is not specifically limited in this specification.

In the illustrated embodiment, the distribution control center may be a server having the above functions, a server cluster including a plurality of servers, or the like, which is not specifically limited in this specification.

Referring to fig. 2, fig. 2 is a flowchart illustrating an application publishing method according to an exemplary embodiment. The method can be applied to the system architecture shown in fig. 1, and in particular can be applied to any one of the application distribution system 20a, the application distribution system 20b and the application distribution system 20c which are in butt joint with the distribution control center shown in fig. 1. The release control center stores a preset release time period. As shown in fig. 2, the method may specifically include the following steps S202-S206.

Step 202, acquiring a preset release time period in a release control center.

In an illustrated embodiment, as described above, the application publishing system may acquire a publishing period preset in the publishing control center before formally publishing the target application. As indicated above, the frequency of use of the target environment within the release period may be less than or equal to a preset threshold.

In an illustrated embodiment, the application publishing system may first perform a series of processes such as code construction and compilation and static check of the code for the target application to be published, and then the application publishing system may acquire a publishing time period preset in the publishing control center.

The present application is not particularly limited to a specific implementation of how to obtain the distribution time period from the distribution control center.

In an illustrated embodiment, the application publishing system may send a get request to a publishing control center related to a publishing time period. Accordingly, the release control center may return a preset release time period to the application release system in response to the received acquisition request.

In an embodiment, the publishing control center may provide a corresponding query interface to the outside, and the application publishing system may query a preset publishing time period in the publishing control center by calling the query interface provided by the publishing control center.

It should be noted that, the specific type of the query interface provided by the issue control center is not particularly limited in this application. In an illustrated embodiment, the query interface may be an application programming interface (REST pi) compliant with REST specifications or any other possible type of interface.

Step 204, judging whether the current moment is within the release time period; the distribution time period is composed of a first time and a second time greater than the first time.

Further, after the release time period is acquired, the application release system may determine whether the current time is within the release time period.

Wherein, as described above, the distribution time period may be constituted by a first time and a second time greater than the first time. For example, the release time period may be 11:00-13:00, i.e., the first time is 11:00 and the second time is 13:00. For example, the publishing time period may also be 12:00-13:00, i.e. the first time is 12:00 and the second time is 13:00. For example, the distribution time period may also be 12:00-15:00, that is, the first time is 12:00, the second time is 15:00, and so on, which is not specifically limited in this specification.

And step 206, if the current time is not in the release time period, determining a time difference between the current time and the first time of the release time period, and releasing the target application to be released into the corresponding target environment after the time corresponding to the time difference.

In an illustrated embodiment, if the current time is within the publishing period, the application publishing system may publish the target application to be published to the corresponding target environment.

For example, taking a publishing time period of 12:00-13:00 as an example, if the current time is 12:15, the application publishing system may directly publish the target application to be published to the corresponding target environment. In an illustrated embodiment, the application publishing system may also publish the target application to a corresponding target environment through a publishing control center. For example, in response to the current time being within the release time period, the application release system may directly submit the target application to be released to the release control center, further, the release control center may release the received target application to the corresponding target environment, and so on, which is not limited in this specification.

In an illustrated embodiment, multiple devices (or machines) may be included in a target environment. The application publishing system may specifically include: and determining target equipment corresponding to the target application to be issued from a plurality of pieces of equipment contained in the target environment, and issuing the target application to the target equipment or deploying the target application to the target equipment. In an illustrated embodiment, the target device may be a more idle device of the plurality of devices.

In an embodiment, the target environment may be a test environment, and accordingly, after the application publishing system publishes the target application to a corresponding target device in the test environment, the target device may perform a corresponding application test on the target application, for example, including testing the functionality and security of the target application, which is not specifically limited in this specification.

In an illustrated embodiment, if the current time is not within the publishing time period, the application publishing system may determine a time difference between the current time and a first time (i.e., a start time) of the publishing time period, and publish the target application to be published to the corresponding target environment after a duration corresponding to the time difference.

For example, taking a publication time period of 12:00-13:00 as an example, if the current time is 11:35, the application publication system may determine a time difference between the waiting time periods of 11:35 and 12:00, that is, 25 minutes. After 25 minutes (i.e., when 12:00 is reached), the application publishing system may publish the target application to be published into the corresponding target environment.

For example, taking a publication time period of 11:00-14:00 as an example, if the current time is 10:55, the application publication system may determine a time difference between the waiting time period of 10:55 and 11:00, that is, 5 minutes. After 5 minutes (i.e., 11:00 reached), the application publishing system may publish the target application to be published into the corresponding target environment.

In an illustrated embodiment, the distribution control center may hold a plurality of distribution time periods set in advance. Correspondingly, if the current time is not in any one of the plurality of release time periods, the application release system can determine the release time period closest to the current time from the plurality of release time periods, calculate the time difference between the current time and the first time of the release time period, and further release the target application to be released into the corresponding target environment after the duration corresponding to the time difference.

For example, taking the case that 2 preset release time periods in the release control center are 11:00-13:00 and 22:00-23:00 respectively, and the current time is 10:20, the application release system may determine that the release time period closest to 10:20 is 11:00-13:00, and further determine that the waiting duration is the time difference between 10:20 and 11:00, that is, 40 minutes. After 40 minutes (i.e., 11:00 reached), the application publishing system may publish the target application to be published into the corresponding target environment.

It should be noted that, in addition to the application of the distribution system, the above steps S202 to S206 may also be applied to the distribution control center. In an illustrated embodiment, the application publishing system may directly submit the target application to be published to the publishing control center after completing a series of processes such as code build compilation and code static inspection for the target application. The issuing control center responds to the received target application and can directly judge whether the current moment is in a preset issuing period, if yes, the issuing control center can issue the received target application to a corresponding target environment, otherwise, the issuing control center can wait until the first moment of the issuing period and then issue the received target application to the corresponding target environment, and the like, and the specification is not limited in detail.

In summary, the present application may pre-build a release control center, which may interface with multiple release systems, respectively. Further, an ideal release time period may be preset in the release control center, where the release time period may be formed by a first time and a second time that is greater than the first time. Further, any application release system of the plurality of application release systems may acquire a preset release time period from the release control center before releasing the application, and check whether the current time is within the release time period. If the current time is not within the release time period, the application release system can determine the time difference between the current time and the first time of the release time period, and release the target application to be released into the corresponding target environment after the time corresponding to the time difference. Therefore, the application of each application release system can be released in a window period (namely, a period of time with low target environment utilization rate), so that the available period of the whole target environment is improved, and the research and development efficiency is further ensured.

Corresponding to the embodiment of the application publishing method, the specification also provides an embodiment of the application publishing device.

Referring to fig. 3, fig. 3 is a hardware configuration diagram of an electronic device in which an application publishing device is located in an exemplary embodiment. The electronic device may be an electronic device in the application distribution system (e.g., any one of the application distribution system 20a, the application distribution system 20b, and the application distribution system 20 c) shown in fig. 1 described above. At the hardware level, the device includes a processor 302, an internal bus 304, a network interface 306, memory 308, and non-volatile storage 310, although other hardware required for the service is possible. One or more embodiments of the present description may be implemented in a software-based manner, such as by the processor 302 reading a corresponding computer program from the non-volatile storage 310 into the memory 308 and then running. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.

Referring to fig. 4, fig. 4 is a block diagram illustrating an application publishing device according to an exemplary embodiment. The release control center is respectively in butt joint with a plurality of application release systems, and the release control center stores a preset release time period. Accordingly, the apparatus 40 may be applied to any application publishing system of the multiple application publishing systems, and in particular, may be applied to the electronic device shown in fig. 3, so as to implement the technical solution of the present disclosure. As shown in fig. 4, the apparatus 40 may include:

an obtaining unit 402, configured to obtain a preset release time period in the release control center;

a judging unit 404, configured to judge whether the current time is within the release time period; the release time period is composed of a first moment and a second moment which is larger than the first moment;

and the first issuing unit 406 is configured to determine a time difference between the current time and a first time of the issuing time period if the current time is not within the issuing time period, and issue the target application to be issued to a corresponding target environment after a duration corresponding to the time difference.

In an illustrated embodiment, the target environment includes a plurality of devices therein; the first distributing unit 406 is specifically configured to:

the first distributing unit 406 is specifically configured to:

In an illustrated embodiment, the apparatus 40 further comprises a second issuing unit for:

In an illustrated embodiment, the obtaining unit 402 is specifically configured to:

In an illustrated embodiment, before acquiring the release time period preset in the release control center, the apparatus 40 further includes a code checking unit for:

The implementation process of the functions and roles of each unit in the above-mentioned apparatus 40 is specifically detailed in the implementation process of the corresponding steps in the method, and will not be repeated here.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are illustrative only, in that the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

The system, apparatus, module or unit illustrated in the embodiments may be implemented in particular by a computer chip or entity or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

Specific embodiments of the present description have been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.

User information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to herein are both user-authorized or fully authorized information and data by parties, and the collection, use and processing of relevant data requires compliance with relevant laws and regulations and standards of the relevant country and region, and is provided with corresponding operation portals for user selection of authorization or denial.

Claims

1. The application release method comprises the steps that a release control center is respectively in butt joint with a plurality of application release systems, and a preset release time period is saved by the release control center; the method is applied to any application release system in the plurality of application release systems; the method comprises the following steps:

acquiring a preset release time period in the release control center;

2. The method of claim 1, wherein a frequency of use of the target environment during the publication time period is less than a preset threshold.

3. The method of claim 1, comprising a plurality of devices in the target environment; the publishing the target application to be published to the corresponding target environment comprises the following steps:

4. The method of claim 1, wherein the distribution control center maintains a plurality of preset distribution time periods;

5. The method of claim 1, the method further comprising:

6. The method of claim 1, wherein the obtaining a release time period preset in the release control center includes:

7. The method of claim 6, the query interface comprising an application programming interface compliant with REST specifications.

8. The method of claim 1, prior to acquiring a publication time period preset in the publication control center, the method further comprising:

9. The method of any of claims 1-8, wherein the application publishing system comprises any of a jenkins system, a Lotus system, a Starlink system.

10. An application release device is characterized in that a release control center is respectively in butt joint with a plurality of application release systems, and the release control center stores a preset release time period; the device is applied to any application release system in the application release systems; the device comprises:

11. An electronic device comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;

the memory stores machine readable instructions, the processor executing the method of any of claims 1 to 9 by invoking the machine readable instructions.

12. A machine-readable storage medium storing machine-readable instructions which, when invoked and executed by a processor, implement the method of any one of claims 1 to 9.