A production-research collaboration system and application method

Abstract

The present invention discloses a production-research collaboration system and application method, and relates to the field of production-research collaboration management. The system includes several container applications, each of which is configured with a pluggable micro-frontend application associated with an IT research and development project; wherein the container application includes at least: a collaboration management module, which is used to isolate the data of the IT research and development project, and is also used to associate users with IT research and development projects so that the corresponding users have operation permissions; a log aggregation module, which is used to collect the first log information of the IT research and development project, and display the first log information to users with operation permissions; a deployment management module, which is used to generate deployment configuration information in response to an editing request from a user with operation permissions for the IT research and development project. Compared with the prior art, the present invention can meet the personalized needs of different IT research and development projects, improve the efficiency of collaborative work, and reduce the difficulty of subsequent deployment and maintenance, and is particularly suitable for large-scale project group collaboration scenarios.

Description

Technical Field

[0001] The present invention relates to the technical field of production-research collaboration management, and more specifically, to an production-research collaboration system and an application method. Background Art

[0002] At present, large-scale IT R&D projects are characterized by cross-team cooperation and multi-task parallelism, and their collaborative management is becoming increasingly difficult. For example, different IT R&D projects need to access different tools or component services for collaboration, and existing management tools lack deep integration of production and research collaboration processes and cannot support personalized needs. In addition, in the development and deployment of IT R&D projects, deployable resources and authorization codes are often managed by different R&D organizations or members, which complicates subsequent deployment and maintenance. Summary of the invention

[0003] In order to overcome the defects of the above-mentioned prior art in that it cannot support personalized needs and the subsequent deployment and maintenance are complicated, the present invention provides a production-research collaboration system and an application method.

[0004] In order to solve the above technical problems, the technical solution of the present invention is as follows:

[0005] In a first aspect, a production-research collaboration system is implemented based on a micro-frontend architecture, and includes a plurality of container applications, each of which is configured with a pluggable micro-frontend application associated with an IT research and development project; wherein the container application includes at least:

[0006] A collaboration management module, used to isolate the data of the IT R&D project, and also used to associate a user with the IT R&D project so that the corresponding user has the operation authority of the IT R&D project; the user is an organizational member belonging to at least one R&D organization;

[0007] a log aggregation module, configured to collect first log information of the IT R&D project and display the first log information to the user with the operation authority;

[0008] The deployment management module is used to generate deployment configuration information in response to an editing request of the user who has the operation authority for the IT R&D project; the deployment configuration information is used to indicate the deployment environment of the authorization code associated with the IT R&D project.

[0009] In a second aspect, an application method of the production-research collaboration system, using the system described in the first aspect, includes:

[0010] In the case where the system is configured with corresponding resources of users and IT R&D projects, the data of the IT R&D projects are isolated through the collaboration management module, and the users are associated with the IT R&D projects so that the corresponding users have the operation rights of the IT R&D projects; the users are members of at least one R&D organization;

[0011] Collecting first log information of the IT R&D project through the log aggregation module, and displaying the first log information in response to a log query request of the user with the operation authority;

[0012] The deployment management module generates deployment configuration information in response to an editing request from the user who has the operation authority for the IT R&D project; the deployment configuration information is used to indicate a deployment environment of the authorization code associated with the IT R&D project.

[0013] In a third aspect, an electronic device comprises a processor and the production-research collaboration system as described in the first aspect; wherein the processor is used to execute at least one instruction, at least one program, code set or instruction set, so that the production-research collaboration system executes the method as described in the second aspect.

[0014] In a fourth aspect, a computer-readable storage medium stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, at least one program, a code set or an instruction set is loaded and executed by a processor to implement the method described in the second aspect.

[0015] In a fifth aspect, a computer program product comprises a computer program or computer executable instructions, wherein when the computer program or computer executable instructions are executed by a processor, the method described in the second aspect is implemented.

[0016] Compared with the prior art, the technical solution of the present invention has the following beneficial effects:

[0017] The present invention proposes a production-research collaboration system and an application method. The system is implemented based on a microservice architecture and includes a plurality of container applications configured with pluggable micro-frontend applications associated with IT research and development projects, so as to configure different micro-frontend applications according to the personalized needs of different IT research and development projects; wherein the container application includes a collaboration management module, a log aggregation module and a deployment management module. By configuring operation permissions in the collaboration management module, a many-to-many mapping relationship of projects across multiple research and development organizations, projects and teams, a many-to-many mapping relationship between organizational members and projects, a many-to-many mapping relationship between project requirements / tasks / defects / production problems and organizational members, etc. can be established to achieve efficient collaboration of large-scale project group operations. The first log information of the IT research and development project is collected and displayed through the log aggregation module. The separation of code and deployment configuration is achieved through the deployment management module, which greatly improves the system maintenance and problem handling capabilities, reduces the maintenance difficulty of IT research and development projects, and improves the efficiency of collaborative work. The system is particularly suitable for large-scale project group collaboration scenarios and is conducive to achieving rapid iteration and optimization of products. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 This is a schematic diagram of the structure of the production-research collaboration system described in Example 1 of the present application;

[0019] Figure 2 This is a schematic diagram of the front-end visualization interface of the production-research collaboration system described in Example 1 of the present application;

[0020] Figure 3 This is a schematic diagram of the collaborative mapping relationship of a large project group in Example 1 of the present application;

[0021] Figure 4 This is a schematic diagram of the log content structure in Example 1 of the present application;

[0022] Figure 5 This is a schematic diagram of the process of the application method described in Example 2 of the present application. DETAILED DESCRIPTION

[0023] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged in appropriate cases, which is only to describe the distinction mode adopted by the objects of the same attributes in the embodiments of the present application when describing. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment containing a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment. The term "determine" widely covers various actions, and may include acquisition, calculation, calculation, processing, derivation, investigation, search (for example, search in a table, database or other data structure), ascertainment, and similar actions, and may also include reception (for example, receiving information), access (for example, accessing data in a memory) and similar actions, and may also include generation, creation, establishment and similar actions, as well as parsing, selection, selection and similar actions, etc. The relevant definitions of other terms will be given in the following description.

[0024] The drawings are for illustrative purposes only and should not be construed as limiting the present patent;

[0025] In order to better illustrate the present embodiment, some parts in the drawings may be omitted, enlarged or reduced, and do not represent the size of the actual product;

[0026] It is understandable to those skilled in the art that some well-known structures and their descriptions may be omitted in the drawings.

[0027] The technical solution of the present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0028] Example 1

[0029] This embodiment provides a production-research collaboration system, referring to FIG1 , which is implemented based on a micro-frontend architecture and includes a plurality of container applications, each of which is configured with a pluggable micro-frontend application associated with an IT research and development project; wherein the container application includes at least:

[0030] A collaboration management module, used to isolate the data of the IT R&D project, and also used to associate a user with the IT R&D project so that the corresponding user has the operation authority of the IT R&D project; the user is an organizational member belonging to at least one R&D organization;

[0031] a log aggregation module, configured to collect first log information of the IT R&D project and display the first log information to the user with the operation authority;

[0032] The deployment management module is used to generate deployment configuration information in response to an editing request of the user who has the operation authority for the IT R&D project; the deployment configuration information is used to indicate the deployment environment of the authorization code associated with the IT R&D project.

[0033] In some specific implementations, the visual interface of the system is shown in FIG2 .

[0034] In the above embodiment, the design idea of ​​separating the front-end and the back-end is adopted, and data isolation is achieved through the collaborative management module, and operation permissions are assigned to users to ensure that in the log aggregation module and the deployment management module, only authorized users can access and edit the corresponding resources to improve security; at the same time, through the collaborative management module, cross-team and cross-project requirements in the R&D and production process of large-scale projects can also be realized, which is particularly suitable for large-scale project group collaboration scenarios. See Figure 3 to reduce the difficulty of collaboration and help improve development and production efficiency. In addition, the setting of the deployment management module realizes the separation of deployment configuration and code, reduces the complexity of deployment, and improves the portability of the product. In addition, based on the setting of the micro-front-end application, sufficient customization and scalability can be provided, flexibility and cost-effectiveness can be improved, the needs of different IT R&D projects and teams can be met, and various existing tools or self-developed tools can be easily accessed.

[0035] It should be noted that the collaboration management module, log aggregation module and deployment management module all belong to the container application. Based on this understanding, the collaboration management module, log aggregation module and deployment management module are all configured with pluggable micro-frontend applications associated with IT R&D projects, and the micro-frontend applications configured in the collaboration management module, log aggregation module and deployment management module are different to realize different module functions.

[0036] Those skilled in the art will appreciate that the container application is responsible for coordinating and loading the micro-frontend application, and providing standard APIs and protocols to communicate and share data with the micro-frontend program. Similarly, the micro-frontend application needs to provide APIs and protocols to communicate and share data with the container application, such as registering custom events of the container application, synchronous or asynchronous communication, etc.

[0037] It should also be noted that for different IT R&D projects and / or users with different operating permissions, the micro-frontend applications associated with them may be different.

[0038] It should be understood that regarding the operation rights of the IT R&D projects, the same user may have different operation rights for different IT R&D projects, or different users may have different operation rights for the same IT R&D project. For example, user A can only access the relevant resources of IT project 1, and user B can only access the relevant resources of IT project 2; or user A can read and edit IT project 1, and user B can only read IT project 1 but not edit it.

[0039] In some examples, the deployment environment includes a development environment, a test environment, and a production environment.

[0040] In some specific implementations, the container application and / or the front-end application are written using a React framework.

[0041] In some examples, the micro-frontend application can be an external technical tool, such as Lark, Git, or Jenkins, or it can be a self-developed tool within the R&D organization.

[0042] In some specific implementations, the micro-frontend application is packaged into one or more Web components, which are then used in a container application to reduce coupling between applications and improve maintainability and reusability.

[0043] In some preferred embodiments, each of the container applications is also configured with a shared code base or communication protocol to enable communication and data sharing between different micro-frontend applications.

[0044] In some specific implementations, React Route is used in the container application to manage the routing of the entire application. In the micro-frontend application, a routing library is used to manage the routing of the sub-application.

[0045] In some preferred embodiments, in the deployment management module, generating deployment configuration information in response to an editing request of the user having the operation authority includes:

[0046] Determine the IT research and development projects for which the user accessing the deployment management module has the operation authority and display them to the user;

[0047] In response to the user's selection and determination operation of at least one of the IT R&D projects, the environment configuration parameters of the authorization code associated with the IT R&D project are displayed to the user; the environment configuration parameters are used to dynamically inject into the corresponding authorization code when the system service corresponding to the IT R&D project is started to replace the default environment configuration parameters specified therein;

[0048] In response to the user's editing operation on the environment configuration parameters, displaying the editing result of the environment configuration information to the user;

[0049] In response to a confirmation request of the user for the editing result, the deployment configuration information is generated according to the editing result.

[0050] As a non-limiting example, the environment configuration parameters include one or more of database configuration, third-party call URL, and message / cache middleware.

[0051] It should be understood that the deployment configuration information can be manually injected into the code configuration by a user whose role is a deployer, or the system can synchronously inject it into the code configuration after generating the deployment configuration information, thereby realizing the separation of code and configuration, solving the problem of difficult maintenance of configurations in different environments, avoiding frequent changes and modifications of code due to changes in environmental configuration parameters and spending a lot of time on compilation and construction, and greatly improving development efficiency.

[0052] In some optional embodiments, before the deployment management module generates the deployment configuration information in response to the user's confirmation request for the editing result, the deployment management module further includes:

[0053] Confirm whether there is a previous version of deployment configuration information: if so, store the previous version of deployment configuration information as a deployment configuration history record; otherwise, do not perform other operations.

[0054] In this optional embodiment, by setting the deployment configuration history record, the difference comparison between different deployment configuration versions can be achieved to quickly locate the modification point.

[0055] Furthermore, in response to the rollback request of the user, the environment configuration parameters are quickly rolled back according to the deployment configuration history record.

[0056] In some optional embodiments, the deployment management module is further used to perform non-stop deployment in the deployment environment according to the deployment configuration information, including:

[0057] Configure a new system service in the deployment environment according to the deployment configuration information and the deployment sequence, and put it in an offline state after the configuration is completed so as not to process business requests;

[0058] After confirming that all the new system services are started normally and ready, the business traffic is switched to the new system services, so that the new system services are online, and the original system services are shut down using the graceful shutdown technology to ensure that all active threads are fully processed before terminating the process.

[0059] In this optional embodiment, by deploying without downtime, business will not be interrupted when a new version is released in the production environment at the lowest cost, ensuring that the business runs continuously 24 hours a day, improving stability and availability.

[0060] In some preferred embodiments, in the log aggregation module, collecting the log information of the IT R&D project and displaying the log information to the user with the operation authority include:

[0061] Capturing the request, flow, call time and / or call result of the system service (background service) corresponding to each IT R&D project through an agent (Instrumentation Agent) to generate call link information;

[0062] Acquire the second log information generated by each of the system services according to the call link information, and configure the tracking ID and feature information to form the first log information;

[0063] Determine the IT research and development project for which the user accessing the log aggregation module has the operation authority, and record it as authorized project information;

[0064] In response to the user's query request for the first log information, content in the first log information associated with the authorization item information is displayed to the user.

[0065] Those skilled in the art should understand that before using an agent to capture call link information, a tracer needs to be embedded in the application code.

[0066] In the above preferred embodiment, an aggregate log is established with the call chain as a chain, which is convenient for users (such as R&D personnel or operation and maintenance personnel) to locate problems and conduct R&D debugging.

[0067] As a non-limiting example, the feature information (feature code) includes the environment to which the log belongs, the server IP, etc.

[0068] It should be understood that the characteristic information can be customized and extended by those skilled in the art according to the actual needs of the IT R&D project. In some examples, the log content structure is shown in FIG4 .

[0069] In some optional implementation examples, the log aggregation module is also used to display a log retrieval interface, and in response to the user's log query request with query keywords, display the corresponding log content in the log retrieval interface to improve log query efficiency.

[0070] Exemplarily, the query keyword may be a tracking ID, a log keyword, feature information, etc.

[0071] In some preferred embodiments, the container application also includes a resource management module, which is used to configure the user information and role of the user to enable the user to log in to the system, and is also used to configure the project resource information of the IT R&D project to enable the association of the IT R&D project in the system.

[0072] In some specific implementation processes, the role of the user may be a project manager, a requirements person, a developer, a tester, or an operation and maintenance person.

[0073] Those skilled in the art should understand that different user roles may correspond to different operating permissions.

[0074] In some preferred embodiments, the container application ensures through JWT authentication, CORS header and / or Sandbox that only the user with the operation permission can access the micro-frontend application, and only authorized code can be loaded and run.

[0075] Example 2

[0076] This embodiment provides an application method of the production-research collaboration system, using the system described in Example 1, referring to Figure 5 ,include:

[0077] In the case where the system is configured with corresponding resources of users and IT R&D projects, the data of the IT R&D projects are isolated through the collaboration management module, and the users are associated with the IT R&D projects so that the corresponding users have the operation rights of the IT R&D projects; the users are members of at least one R&D organization;

[0078] Collecting first log information of the IT R&D project through the log aggregation module, and displaying the first log information in response to a log query request of the user with the operation authority;

[0079] The deployment management module generates deployment configuration information in response to an editing request from the user who has the operation authority for the IT R&D project; the deployment configuration information is used to indicate a deployment environment of the authorization code associated with the IT R&D project.

[0080] It can be understood that the options in the above-mentioned embodiment 1 are also applicable to this embodiment, so they will not be described again here.

[0081] Example 3

[0082] This embodiment provides a computer-readable storage medium, on which is stored at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor, so that the processor executes part or all of the steps of the method provided in Example 2 of the present application.

[0083] It is understood that the storage medium may be transient or non-transient. Exemplarily, the storage medium includes, but is not limited to, a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0084] Exemplarily, the processor may be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP), or a field programmable gate array (FPGA).

[0085] Exemplarily, the read-only memory includes but is not limited to MASK ROM, PROM, EPROM, EEPROM, Flash, etc.

[0086] Exemplarily, the random access memory includes but is not limited to DRAM, SRAM, SDRAM, DDR SDRAM, etc.

[0087] In some examples, a computer program product is provided, which can be implemented in hardware, software or a combination thereof. As a non-limiting example, the computer program product can be embodied as the storage medium, or as a software product, such as an SDK (Software Development Kit).

[0088] As a non-limiting example, a computer program product is provided, the computer program product includes a computer program or a computer executable instruction, the computer program or the computer executable instruction is stored in a computer-readable storage medium. A processor of an electronic device reads the computer program or the computer executable instruction from the computer-readable storage medium, and the processor executes the computer executable instruction, so that the electronic device performs some or all steps of the method described in the embodiment of the present application.

[0089] In some examples, a computer program is provided, comprising a computer-readable code, and when the computer-readable code is run in a computer device, a processor in the computer device executes a part or all of the steps in the method.

[0090] This embodiment also proposes an electronic device, including a processor and the production and research collaborative system described in Example 1; wherein the processor is used to execute at least one instruction, at least one program, code set or instruction set, so that the production and research collaborative system executes the method described in Example 2.

[0091] This embodiment also proposes another electronic device, including a memory and a processor, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and when the processor executes the at least one instruction, at least one program, a code set or an instruction set, it implements part or all of the steps of the method described in Example 2.

[0092] In some examples, a hardware entity of the electronic device is provided, including: a processor, a memory and a communication interface; wherein the processor generally controls the overall operation of the electronic device; the communication interface is used to enable the electronic device to communicate with other terminals or servers through a network; the memory is configured to store instructions and applications executable by the processor, and can also cache data to be processed or processed by the processor and various modules in the electronic device (including but not limited to image data, audio data, voice communication data and video communication data), which can be implemented by flash memory (FLASH), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or random access memory (RAM).

[0093] The processor may include one or more processing elements. Thus, the processor may include one or more integrated circuits (ICs) configured to perform the functions of the processor. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, and other circuits, etc.) configured to perform the functions of the processor.

[0094] Furthermore, data may be transmitted between the processor, the communication interface and the memory via a bus, which may include any number of interconnected buses and bridges, and the bus connects various circuits of one or more processors and memories together.

[0095] It can be understood that the options in the above-mentioned embodiment 1 are also applicable to this embodiment, so they will not be described again here.

[0096] The same or similar reference numerals correspond to the same or similar components;

[0097] The terms used to describe the positional relationship in the drawings are only used for illustrative purposes and should not be construed as limiting the present application;

[0098] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application may be combined with each other.

[0099] In different specific implementations, the method or system described in the present application can be implemented in software, hardware or a combination thereof. In addition, the order of the steps of the method can be changed, and various elements can be added, reordered, combined, omitted, modified, etc.

[0100] Obviously, the above-mentioned embodiments of the present application are merely examples for clearly illustrating the present application, and are not intended to limit the implementation methods of the present application, and are not intended to limit the present application. For those of ordinary skill in the art, other different forms of changes or modifications can be made based on the above description. Each discrete structure / function module or unit can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part, and the structure and function of the discrete components can be implemented as a combined structure or component. It is not necessary and impossible to enumerate all the implementation methods here. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the claims of the present application.

Claims

1. A production-research collaboration system, characterized in that: Based on the micro-frontend architecture, it includes several container applications, each of which is configured with a pluggable micro-frontend application associated with an IT R&D project; wherein the container application includes at least: A collaboration management module, used to isolate the data of the IT R&D project, and also used to associate a user with the IT R&D project so that the corresponding user has the operation authority of the IT R&D project; the user is an organizational member belonging to at least one R&D organization; a log aggregation module, configured to collect first log information of the IT R&D project and display the first log information to the user having the operation authority; A deployment management module, for generating deployment configuration information in response to an editing request of the user who has the operation authority for the IT R&D project, and for performing non-stop deployment in a deployment environment according to the deployment configuration information; the deployment configuration information is used to indicate a deployment environment of an authorization code associated with the IT R&D project; Wherein, in the log aggregation module, collecting the first log information of the IT R&D project and displaying the first log information to the user with the operation authority include: Capturing, through an agent, requests, flows, call times and / or call results of system services corresponding to each of the IT R&D projects, and generating call link information; Acquire the second log information generated by each of the system services according to the call link information, and configure the tracking ID and feature information to form the first log information; Determine the IT research and development project for which the user accessing the log aggregation module has the operation authority, and record it as authorized project information; In response to the user's query request for the first log information, displaying to the user the content in the first log information associated with the authorization item information; and, In the deployment management module, generating deployment configuration information in response to an editing request of the user having the operation authority includes: Determine the IT research and development projects for which the user accessing the deployment management module has the operation authority and display them to the user; In response to the user's selection and determination operation of at least one of the IT R&D projects, the environment configuration parameters of the authorization code associated with the IT R&D project are displayed to the user; the environment configuration parameters are used to dynamically inject into the corresponding authorization code when the system service corresponding to the IT R&D project is started to replace the default environment configuration parameters specified therein; In response to the user's editing operation on the environment configuration parameter, displaying the editing result of the environment configuration parameter to the user; In response to a confirmation request of the user for the editing result, generating the deployment configuration information according to the editing result; and, The performing non-stop deployment in the deployment environment according to the deployment configuration information includes: Obtaining the dependency relationships between the original system services corresponding to each of the IT R&D projects, and determining the deployment order according to the dependency relationships; Configure a new system service in the deployment environment according to the deployment configuration information and the deployment sequence, and put it in an offline state after the configuration is completed so as not to process business requests; After confirming that all the new system services are started normally and ready, the business traffic is switched to the new system services, so that the new system services are online, and the original system services are shut down using the graceful shutdown technology to ensure that all active threads are fully processed before terminating the process.

2. The production-research collaboration system according to claim 1, characterized in that: Before the deployment management module generates the deployment configuration information in response to the user's confirmation request for the editing result, the deployment management module further includes: Confirm whether there is a previous version of deployment configuration information: if so, store the previous version of deployment configuration information as a deployment configuration history record; otherwise, do not perform other operations.

3. The production-research collaboration system according to claim 1, characterized in that: The container application also includes a resource management module, which is used to configure the user information and role of the user to enable the user to log in to the system, and is also used to configure the project resource information of the IT R&D project to enable the association of the IT R&D project in the system.

4. A production-research collaboration system according to any one of claims 1 to 3, characterized in that: The container application ensures through JWT authentication, CORS header and / or Sandbox that only the user with the operation permission can access the micro-frontend application, and only authorized code can be loaded and run.

5. An application method of an industry-research collaboration system, using the system according to any one of claims 1 to 4, characterized in that: include: In the case where the system is configured with corresponding resources of users and IT R&D projects, the data of the IT R&D projects are isolated through the collaboration management module, and the users are associated with the IT R&D projects so that the corresponding users have the operation rights of the IT R&D projects; the users are members of at least one R&D organization; Collecting first log information of the IT R&D project through the log aggregation module, and displaying the first log information in response to a log query request of the user with the operation authority; By means of the deployment management module, in response to an editing request of the user who has the operation authority for the IT R&D project, deployment configuration information is generated, and the deployment is also performed in a deployment environment without downtime according to the deployment configuration information; the deployment configuration information is used to indicate a deployment environment of the authorization code associated with the IT R&D project; The collecting of the first log information of the IT R&D project and displaying the first log information to the user with the operation authority include: Capturing, through an agent, requests, flows, call times and / or call results of system services corresponding to each of the IT R&D projects, and generating call link information; Acquire the second log information generated by each of the system services according to the call link information, and configure the tracking ID and feature information to form the first log information; Determine the IT research and development project for which the user accessing the log aggregation module has the operation authority, and record it as authorized project information; In response to the user's query request for the first log information, displaying to the user the content in the first log information associated with the authorization item information; and, The generating, in response to the editing request of the user having the operation authority, the deployment configuration information comprises: Determine the IT research and development projects for which the user accessing the deployment management module has the operation authority and display them to the user; In response to the user's selection and determination operation of at least one of the IT R&D projects, the environment configuration parameters of the authorization code associated with the IT R&D project are displayed to the user; the environment configuration parameters are used to dynamically inject into the corresponding authorization code when the system service corresponding to the IT R&D project is started to replace the default environment configuration parameters specified therein; In response to the user's editing operation on the environment configuration parameter, displaying the editing result of the environment configuration parameter to the user; In response to a confirmation request of the user for the editing result, generating the deployment configuration information according to the editing result; and, The performing non-stop deployment in the deployment environment according to the deployment configuration information includes: Obtaining the dependency relationships between the original system services corresponding to each of the IT R&D projects, and determining the deployment order according to the dependency relationships; Configure a new system service in the deployment environment according to the deployment configuration information and the deployment sequence, and put it in an offline state after the configuration is completed so as not to process business requests; After confirming that all the new system services are started normally and ready, the business traffic is switched to the new system services, so that the new system services are online, and the original system services are shut down using the graceful shutdown technology to ensure that all active threads are fully processed before terminating the process.

6. An electronic device, characterized in that: It comprises a processor and an industry-research collaboration system as described in any one of claims 1 to 4; wherein the processor is used to execute at least one instruction, at least one program, code set or instruction set, so that the industry-research collaboration system executes the application method as described in claim 5.

7. A computer program product comprising a computer program or computer executable instructions, characterized in that When the computer program or computer executable instruction is executed by a processor, the application method described in claim 5 is implemented.

Images