Methods, apparatus, equipment, storage media, and program products for deployment
By receiving natural language input to instruct the intelligent system to deploy development products and provide status feedback, and by using plugins to provide functional components, the system solves the inefficiency caused by repetitive configuration and interface switching during the deployment of development products, thus achieving more efficient information processing and interaction.
Patent Information
- Application Number
- CN202611374193.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-04
- Publication Date
- 2026-11-17
AI Technical Summary
During the deployment of the developed products, existing technologies suffer from high data processing and interaction overhead and low efficiency due to repetitive configuration, querying, and interface switching.
By receiving input in the form of natural language, the intelligent system can deploy development artifacts and provide functional components using associated plugins, providing real-time feedback on deployment status and reducing interface switching and repetitive query operations.
It improves the efficiency of information processing and interface interaction during the deployment of development products, and reduces data processing and communication overhead.
Smart Images

Figure CN123114492A_ABST
Abstract
Description
Technical Field
[0001] The examples in this article generally relate to the field of computers, and in particular to methods, apparatus, devices, computer storage media, and computer program products for deployment. Background Technology
[0002] With the development of computer technology, users can process different types of development products through electronic devices. The process of processing these products may involve multiple steps and generate corresponding information. Therefore, improving the interactive efficiency of the development product processing process is a matter of concern. Summary of the Invention
[0003] In a first aspect, a method for deploying an artifact is provided. The method includes: receiving a first input, the first input being in natural language form, the first input instructing an intelligent system to deploy a development artifact, the intelligent system being associated with a plugin, the plugin including at least one functional component for deploying the development artifact; and presenting first information, the first information originating from the intelligent system, the first information describing the deployment status of the development artifact.
[0004] In a second aspect, an apparatus for deploying an artifact is provided. The apparatus includes: a first receiving module configured to receive a first input in natural language form, the first input instructing an intelligent system to deploy a development artifact, the intelligent system being associated with a plug-in including at least one functional component for deploying the development artifact; and a first presenting module configured to present first information from the intelligent system, the first information describing the deployment status of the development artifact.
[0005] In a third aspect, an electronic device is provided. The device includes at least one processor; and at least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor. When executed by the at least one processor, the instructions cause the device to perform the method of the first aspect.
[0006] In a fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions that can be executed by a processor to implement the method of the first aspect.
[0007] In a fifth aspect, a computer program product is provided, which is tangibly stored in a computer storage medium and includes computer-executable instructions that, when executed by a device, cause the device to perform the method of the first aspect.
[0008] In this way, by instructing the intelligent system to call related plugins to deploy development artifacts and provide feedback on deployment status through natural language input, the data processing and interaction overhead caused by repeated configuration, querying and interface switching during deployment can be reduced, and the deployment processing efficiency and interface interaction efficiency can be improved.
[0009] It should be understood that the content described in this section is not intended to limit the key or important features of the examples in this article, nor is it intended to restrict the scope of the solution. Other features will become readily apparent from the following description. Attached Figure Description
[0010] The above and other features, advantages, and aspects of the various examples herein will become more apparent when taken in conjunction with the accompanying drawings and the following detailed description. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein: Figure 1 A schematic diagram of the example environment is shown; Figures 2A to 2K Example interfaces for some scenarios are shown; Figure 3 Flowcharts of example processes for deploying artifacts in some scenarios are shown; Figure 4 Schematic structural block diagrams of example devices for deploying products in some scenarios are shown; and Figure 5 A block diagram of an electronic device capable of implementing multiple illustrative scenarios is shown. Detailed Implementation
[0011] The examples in this document will now be described in more detail with reference to the accompanying drawings. While some examples are shown in the drawings, it should be understood that solutions can be implemented in various forms and should not be construed as limited to the examples presented herein. Rather, these examples are provided to provide a more thorough and complete understanding of the solutions. It should be understood that the drawings and examples in this document are for illustrative purposes only and are not intended to limit the scope of protection of the solutions.
[0012] It should be noted that the headings of any section / subsection provided herein are not restrictive. Various examples are described throughout this document, and examples of any type may be included under any section / subsection. Furthermore, examples described in any section / subsection may be combined in any way with any other examples described in the same section / subsection and / or different sections / subsections.
[0013] In the description of the examples in this document, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an example" or "the example" should be understood as "at least one example". The term "some examples" should be understood as "at least some examples". The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.
[0014] The examples in this document may involve user data, data acquisition, and / or use. All of these aspects comply with relevant laws, regulations, and rules. In the examples, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, when implementing each example, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained through appropriate means, in accordance with relevant laws and regulations. The specific methods of notification and / or authorization can vary depending on the actual situation and application scenario; the scope of the solution is not limited in this regard.
[0015] In this manual and the sample solutions, any processing of personal information will be conducted only under legal grounds (such as obtaining the consent of the data subject or being necessary for the performance of a contract) and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.
[0016] In one context, an intelligent system is an information processing system. This intelligent system uses at least one or more models to process one or more inputs. The intelligent system may include the one or more models as components, or it may use models external to the system for processing. Those skilled in the art will recognize that there are various implementations of intelligent systems in the industry, including but not limited to agents, artificial intelligence (AI) assistants, AI workers, copilot systems, and chatbots. The inputs include data in one or more modalities. The modal data includes, but is not limited to, text, audio, images, video, application-specific data, or scientific computing data. The models include, but are not limited to, one or more combinations of the following: large-scale parametric models, deep learning models, neural network models, machine learning models, statistical models, rule-based models, or other models capable of processing the inputs. The specific implementation of the models can employ various existing or improved models. The intelligent system may involve one or more of the following operations: receiving single-round or multi-round input; recognizing and / or understanding the input; generating answers, decisions, or processing results using one or more models; invoking one or more external tools, interfaces, knowledge bases, or other systems to obtain information or perform operations; processing in a self-decision-making or human-machine collaborative manner, or transferring tasks to human or other systems for processing. Self-decision-making refers to execution without human intervention. Human-machine collaboration refers to partial human participation or confirmation. The above explanation of "intelligent system" is illustrative, and each description is an example, not necessarily necessary, and does not constitute an exhaustive list.
[0017] As used in this document, the term "development artifact" refers to a software product that has been developed and can be deployed, run, and / or continuously managed. Development artifacts may include, but are not limited to, applications, applets, workflows, model services, or other suitable types of software products. In some cases, a development artifact may correspond to one or more versions. Different versions may correspond to different code content, configuration content, build results, or deployment results.
[0018] As used herein, the term "plugin" refers to a set of capabilities that can be associated with an intelligent system and provide one or more functional capabilities to the intelligent system. A plugin may include one or more functional components. In some cases, a plugin may be associated with the intelligent system in advance, or it may be associated with the intelligent system in response to a corresponding operation.
[0019] As used herein, the term "functional component" refers to a component in a plugin that provides at least one functional capability to an intelligent system. In some cases, a functional component may include a skill component and / or a tool component.
[0020] As used in this document, the term "skill component" refers to a functional component used to describe and / or provide the processing capabilities of an intelligent system to perform one or more types of tasks. Skill components may include task-specific processing flows, processing rules, operational steps, or other information related to task execution.
[0021] As used in this article, the term "tool component" refers to a functional component that can be invoked by an intelligent system to perform corresponding operations. Tool components can provide corresponding capabilities to an intelligent system through interfaces, commands, preset protocols, or other appropriate means.
[0022] The term "natural language form" as used in this paper refers to the form in which information is expressed using natural language. Information in natural language form may include text, speech, or other input forms that can be converted into natural language content. Natural language form does not require the expression of information in a predefined command format.
[0023] As used in this document, the term "input component" refers to an interface component used to receive information for interaction with an intelligent system. Input components may include text input areas, voice input areas, or other areas suitable for receiving input.
[0024] As used in this document, the term "plugin identifier" refers to information used to identify a specific plugin. Plugin identifiers may include, but are not limited to, plugin names, icons, text, labels, cards, or other content that identifies a specific plugin.
[0025] As used in this document, the term "element" refers to a unit of the interface that can be presented and / or manipulated within the interface. Elements can include, but are not limited to, text, images, icons, labels, cards, buttons, entry points, or any combination thereof.
[0026] As used in this document, the term "deployment" refers to the process by which a development artifact is enabled to run and / or provide functionality in a given runtime environment. Deployment can include the initial deployment of a development artifact or an updated deployment of an already deployed development artifact.
[0027] The term "deployment information" as used in this article refers to information related to the deployment of development artifacts. Deployment information may include, but is not limited to, development artifacts, runtime environment, deployment version, code version, configuration version, service specifications, or other deployment-related information.
[0028] As used in this document, the term "deployment parameters" refers to information used to determine at least part of how a development artifact is deployed. Deployment parameters may include, but are not limited to, runtime environment, service specifications, resource specifications, build parameters, runtime parameters, domain name, environment variables, or other deployment-related parameters.
[0029] The term "deployment status" as used in this document refers to information describing the state of the deployment process of development artifacts. Deployment status may include, but is not limited to, waiting, processing, building, deploying, deployment successful, deployment failed, canceled, interrupted, status unknown, or other appropriate statuses.
[0030] As used in this document, the term "status information" refers to information describing the deployment and / or operational status of development artifacts. Status information may include configuration information, operational information, deployment history information, logs, operational metrics, or other information related to the status of development artifacts.
[0031] As used in this document, the term "configuration information" refers to information used to configure the deployment and / or operation of development artifacts. Configuration information may include at least one deployment parameter of the development artifact.
[0032] The term "runtime information" as used in this article refers to information used to describe the running status of development artifacts. Runtime information may include, but is not limited to, at least one of the following: running status, online version, deployment time, access point, running metrics, or logs.
[0033] As used in this document, the term "online version" refers to the development artifact version currently used to provide the corresponding service and / or in a valid running state. An online version can be determined separately from the deployment result corresponding to a deployment process.
[0034] As used in this document, "deployment history information" refers to information describing the historical deployment process of a development artifact. Deployment history information can describe one or more deployment processes and may include, but is not limited to, deployment time, deployment version, deployment status, deployment results, or other information related to the deployment process. A development artifact can have corresponding deployment history information.
[0035] As used in this article, the term "session" refers to the process of information interaction between a user and an intelligent system. A session can be used to receive input provided by the user and present responses or other interactive information provided by the intelligent system. An intelligent system can be associated with one or more sessions.
[0036] As used in this document, the term "description information" refers to information used to describe the plugin and / or the functional components within it. Description information may include one or more entries. Different entries may describe the respective functional components.
[0037] As used in this document, the term "entry" refers to interface content used to organize and present at least one piece of information. Entries may include, but are not limited to, text, icons, cards, labels, names, descriptions, or any combination thereof.
[0038] As used in this article, the term "entry point" refers to a UI element that can trigger a corresponding function, interface, or process in response to a user action. Entry points can include, but are not limited to, buttons, text, icons, cards, or other UI content that can receive trigger actions.
[0039] As used in this document, the term "prompt information" refers to information used to instruct a user about an object, state, or process. Prompt information may include, but is not limited to, text, icons, cards, status indicators, or any combination thereof.
[0040] The term "failure state" as used in this article refers to an object that is no longer in a currently valid state. In the case where a development artifact corresponds to an application version, an failure state can indicate that the corresponding version is no longer the currently valid version.
[0041] As used in this document, the term "deployment instruction" refers to information that can be used to trigger a deployment system to perform at least one deployment process. Deployment instructions can be generated by an intelligent system based on user input, functional capabilities provided by plugins, and / or deployment information.
[0042] The term "Command-Line Interface (CLI)" as used in this article refers to an interface that can receive operational information and trigger corresponding processing via one or more commands. In some cases, intelligent systems can provide deployment instructions to the deployment system through the command-line interface.
[0043] As used herein, the term "deployment system" refers to a computing system capable of performing at least one process related to the deployment of development artifacts. A deployment system can perform the deployment of development artifacts and can provide information related to the deployment process and / or deployment results.
[0044] As used in this article, the term "runtime environment" refers to the computing environment used to run development artifacts. A runtime environment can be provided by computing resources, network resources, software resources, or any combination thereof.
[0045] As mentioned above, users can process different types of development artifacts through electronic devices. The process of processing these artifacts may involve multiple steps and generate corresponding information. For example, when deploying a development artifact, the user may need to perform certain operations to trigger the deployment and obtain information related to the deployment process. With the increasing types of development artifacts and processing demands, it is worthwhile to focus on how to enable users to conveniently initiate deployments of development artifacts and obtain corresponding deployment status information.
[0046] This paper proposes a scheme for deploying artifacts. According to this scheme, a first input can be received. The first input is in natural language form and instructs an intelligent system to deploy the development artifact. The intelligent system is associated with plugins, and each plugin includes at least one functional component for deploying the development artifact. Furthermore, first information can be presented. The first information comes from the intelligent system and describes the deployment status of the development artifact.
[0047] In this way, users can instruct the intelligent system to deploy development artifacts via a first input in natural language. Plugins associated with the intelligent system can provide deployment capabilities for development artifacts through at least one functional component. This allows deployment requests for development artifacts to be processed through the association between the intelligent system and the plugins, eliminating the need to establish separate interaction paths for different deployment processes. Furthermore, the deployment status of the development artifacts can be fed back via first information. This first information comes from the intelligent system and is associated with the aforementioned deployment request. This reduces the need to switch between different functional interfaces or repeatedly initiate information queries to obtain the deployment status. Correspondingly, it reduces the number of times the electronic device performs data loading, processing, and rendering on different interfaces. It also reduces data interaction between the electronic device and the server due to repeated retrieval of deployment-related information. In addition, it reduces the data processing and communication overhead of the electronic device and improves the information processing efficiency and interface interaction efficiency during the deployment process of development artifacts.
[0048] The following describes various examples of this scheme in further detail with reference to the accompanying drawings.
[0049] Example Environment Figure 1 A schematic diagram of example environment 100 is shown. (e.g.) Figure 1 As shown, environment 100 may include electronic device 110.
[0050] In this example environment 100, electronic device 110 can run an application 120 that supports user interface interaction. Application 120 can be any suitable type of application for user interface interaction, including but not limited to: software applications, development applications, smart system applications, or other suitable applications. User 140 can interact with application 120 via electronic device 110 and / or its attached devices.
[0051] exist Figure 1 In environment 100, if application 120 is active, electronic device 110 can use application 120 to present interface 150 for supporting interface interaction.
[0052] In some cases, electronic device 110 communicates with server 130 to provide services to application 120. Electronic device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, handheld computers, portable gaming terminals, virtual reality (VR) / augmented reality (AR) devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some cases, electronic device 110 can also support any type of user-facing interface (such as "wearable" circuitry).
[0053] Server 130 can be a single physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and data processing and intelligent computing platforms. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for applications 120 that support user interface interaction in electronic devices 110.
[0054] A communication connection can be established between server 130 and electronic device 110. This communication connection can be established via wired or wireless means. The communication connection can include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections. In some cases, server 130 and electronic device 110 can exchange signaling information through their communication connection.
[0055] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the scheme.
[0056] The following description of the example will continue with reference to the accompanying drawings.
[0057] Example Interaction Figures 2A to 2K Example interfaces 200A to 200K are shown according to some scenarios. Interfaces 200A to 200K can, for example, be derived from... Figure 1 The illustrated electronic device 110 is provided via application 120. As an example, interfaces 200A to 200D can represent different display states in a session associated with the intelligent system, such as generating development artifacts, selecting plugins, initiating deployment, and obtaining deployment results. Interfaces 200E to 200G can represent different display states after deployment is complete, such as viewing and managing development artifacts. Interfaces 200H and 200I can represent different display states for associating plugins with the intelligent system and viewing the functional components of those plugins. Interfaces 200J and 200K can represent different display states for selecting a deployed development artifact and selecting the intelligent system to continue processing that artifact.
[0058] It should be understood that interfaces 200A to 200K do not all need to be presented sequentially according to their drawing numbers. For example, interfaces 200A to 200D can form an interactive path from generating development artifacts to deploying development artifacts within the same session. Interfaces 200E to 200G can follow the deployment completion status shown by interface 200D and form a management path for deployed development artifacts. Interfaces 200H and 200I can form another interactive path for associating plugins with the intelligent system, and can be used in... Figures 2A to 2D The deployment process shown is presented beforehand, or in response to determining that the current intelligent system has not yet associated a plugin for deploying development artifacts. Interfaces 200J and 200K can form an interaction path that selects a development artifact to be processed from multiple development artifacts and further selects the intelligent system to continue processing that development artifact.
[0059] Figure 2A A schematic diagram of the session interface 200A according to some scenarios is shown. See below for reference. Figure 2A This describes a process of generating development artifacts and proceeding to initiate deployments within a session associated with an intelligent system.
[0060] like Figure 2A As shown, the electronic device 110 can present an interface 200A. Interface 200A may include a navigation area 204 and a main session area 202. The navigation area 204 can be used to present one or more function entry points and / or object entry points to support users in accessing different functions or selecting different objects. The main session area 202 can be used to carry messages and corresponding input interactions between the user and the current intelligent system.
[0061] As an example, electronic device 110 may present intelligent system entry points 206-1, 206-2, and 206-3 in navigation area 204. Different intelligent system entry points may correspond to different intelligent systems. Electronic device 110 may determine the intelligent system associated with the current session based on the user's selection operation for the corresponding intelligent system entry point.
[0062] In some cases, the electronic device 110 may also present a settings entry 205 in the interface 200A. The settings entry 205 can be used to access the settings interface. The electronic device 110 can receive a trigger operation on the settings entry 205 and, in response to the trigger operation, present the corresponding settings interface. The following is based on... Figure 2J The process of presenting at least one development artifact through a settings interface and selecting one of the development artifacts is described further.
[0063] For example, in Figure 2A In the indicated state, the smart system entry 206-1 can be selected. The electronic device 110 can accordingly display the smart system identifier 208 at the top of the main session area 202 to indicate that the current session is associated with the smart system corresponding to the smart system entry 206-1.
[0064] In some situations, different intelligent systems can be associated with different functional capabilities. For example, some intelligent systems may already be associated with plugins used to deploy development artifacts, while others may not yet be associated with such plugins. When presenting multiple intelligent systems, electronic device 110 can distinguish between different intelligent systems based on the association status of the plugins.
[0065] Electronic device 110 can present input component 210 in interface 200A. Input component 210 can be used to interact with the current intelligent system. For example, input component 210 can receive input in the form of text, voice, or other natural language. In some cases, input component 210 can also be used to present or carry references to plugins.
[0066] like Figure 2A As shown, a session may include messages 212-1 and 212-2. Message 212-1 may be a message sent by the user to the intelligent system, instructing the intelligent system to generate development artifacts. For example, message 212-1 may describe the functionality of the application to be generated or other development requirements. Message 212-2 may be a response from the intelligent system to message 212-1. For example, message 212-2 may indicate that development artifacts have been generated, the development process has been completed, and / or the corresponding verification has been completed. Generating development artifacts and subsequently deploying development artifacts can occur within the same session. When the intelligent system receives a subsequent deployment request, it can utilize the development context already established in the previous session without requiring the user to reselect development artifacts or re-enter all development information.
[0067] In some scenarios, multiple development artifacts can be associated within the context of the same session. Users can specify the specific development artifact to be deployed in subsequent natural language input. For example, users can specify the development artifact to be deployed by referring to an application, a service, or other information that distinguishes different development artifacts.
[0068] Alternatively or additionally, the electronic device 110 or the server 130 communicating with it may determine the development product to be deployed this time based on the association between the development product and the application, messages in the current session, the identifier of the development product, or other contextual information. For development products that already have a corresponding online version, it may also be determined whether this operation is an initial deployment or an update deployment for an existing development product based on the association and the online version.
[0069] In some scenarios, electronic device 110 or server 130 can associate multiple objects and states related to a single deployment operation. For example, it can associate the current deployment request, application, deployment unit, runtime environment, code version, configuration version, current online version, the intelligent system performing the operation, and the plugins associated with that intelligent system. This allows subsequent deployment confirmations and actual execution to target the same development artifacts and corresponding versions. In this way, users can continue to initiate deployments via natural language within the context of a completed session, without having to switch from the session to a separate deployment configuration interface and relocate the development artifacts.
[0070] Figure 2BA schematic diagram of interface 200B for selecting a plugin in input component 210 according to certain scenarios is shown. Interface 200B can represent another display state following interface 200A. See below for further details. Figure 2A and Figure 2B This describes a process for selecting a plugin in an input component to deploy development artifacts.
[0071] As an example, electronic device 110 can receive a sixth operation for input component 210. In response to the sixth operation, electronic device 110 can display multiple plug-in identifiers.
[0072] For example, such as Figure 2B As shown, electronic device 110 can present a plugin trigger identifier 214 and a plugin candidate area 216 in input component 210. For example, plugin trigger identifier 214 can be a preset keyword (e.g., "@") manually entered by the user. Plugin candidate area 216 can include multiple plugin candidates, such as plugin candidate 218-1, plugin candidate 218-2, and plugin candidate 218-3. The multiple plugin candidates can each correspond to different plugins. As an example, plugin candidate 218-2 can correspond to a plugin used for deploying and managing development artifacts. Electronic device 110 can receive a seventh operation. The seventh operation can be used to select plugin candidate 218-2. For example, the seventh operation can include a trigger operation on plugin candidate 218-2 (e.g., a click operation, etc.). In response to the seventh operation, electronic device 110 can present a first element indicating the plugin in input component 210.
[0073] For example, the first element may include the plugin name, plugin icon, plugin identifier, or other interface content that can indicate the corresponding plugin. The first element, together with the natural language content entered by the user in input component 210, constitutes the first input to be sent.
[0074] As an example, after the user selects plugin candidate 218-2, the plugin reference content corresponding to that plugin can be backfilled into input component 210, and together with other natural language content entered by the user, form a subsequent message.
[0075] Additionally or alternatively, the electronic device 110 may also display multiple plug-in icons in response to a trigger operation on the plus sign control 220. For example, the plug-in candidate area 216 may be triggered and displayed via the plug-in trigger icon 214, the plus sign control 220, or other interface entry points for selecting plug-ins.
[0076] Figure 2CA schematic diagram of an interface 200C is shown, instructing an intelligent system to deploy development artifacts via natural language input under certain circumstances. Interface 200C can represent a display state when a user initiates a deployment request for a development artifact. See below for reference. Figure 2C Describes a process for initiating deployment via natural language input.
[0077] like Figure 2C As shown, the electronic device 110 can present user message 222. User message 222 may include natural language content and a first element 223 for indicating the plugin (e.g., "deployment and maintenance"). User message 222 can represent an example of a first input. For example, a user can... Figure 2B In the input component 210 shown, the user selects the appropriate plugin and enters natural language content to instruct on the deployment of the development artifact. In response to the user sending the corresponding content, the electronic device 110 can display user message 222.
[0078] exist Figure 2C In the example shown, the natural language content in user message 222 can be used to instruct the intelligent system to deploy development artifacts, and the first element 223 can be used to instruct the user to request the intelligent system to process the deployment request using the corresponding plugin. It should be understood that the first input does not necessarily require a reference to a plugin. Additionally or alternatively, the first input may only include natural language content instructing the deployment of development artifacts. For example, the first input may include "Start Deployment," "Deploy Current Application," or other natural language content instructing the deployment of development artifacts, without including a first element instructing a specific plugin.
[0079] Electronic device 110 can receive a first input via input component 210. The first input is in natural language and instructs the intelligent system to deploy a development artifact. The intelligent system can determine the operation to be performed based on the first input. For example, the intelligent system can determine based on the first input that a user requests to perform a deployment operation, and further determine the development artifact to which the deployment operation is targeted.
[0080] In some scenarios, an intelligent system can determine the development artifact to be deployed based on an initial input and at least one historical message from the current session. For example, Figure 2A Messages 212-1 and 212-2 in the input can form a context related to the development artifact. For example, if the first input includes natural language content such as "deploy the current application", the intelligent system can determine the development artifact that the first input is for by combining the context of the current session, without requiring the user to provide all the information of the development artifact again in the first input.
[0081] When multiple development artifacts are associated with the same session, the first input can also include information to distinguish the artifacts. For example, a user can specify the application or service to be deployed using natural language. The intelligent system can then determine the artifact to be deployed based on this information and the context of the current session.
[0082] In some situations, an intelligent system can determine the functional capabilities required to process a first input based on that first input. For example, if the first input indicates the deployment of a development artifact, the intelligent system can determine that the first input needs to be processed using a plugin for deploying the development artifact.
[0083] If the first input includes a first element indicating the plugin, the intelligent system can determine the plugin to be used based on the first element. For example, in Figure 2C In the example shown, the first element can indicate a plugin used to deploy the development artifact. The intelligent system can determine, based on the first element, to use that plugin to process the first input.
[0084] Alternatively or additionally, if the first input does not specify a particular plugin, the intelligent system may determine the plugin corresponding to the task indicated by the first input. For example, if the first input indicates the deployment of a development artifact, the intelligent system may determine from the plugins associated with the current intelligent system whether there exists a plugin that can be used to deploy the development artifact.
[0085] If the intelligent system is determined to be associated with a plugin for deploying development artifacts, it can invoke that plugin to process the first input. For example, the intelligent system can utilize at least one functional component provided by the plugin to determine deployment information, generate deployment instructions, and / or perform other deployment-related processes.
[0086] If it is determined that the current intelligent system has not yet associated with a plugin for deploying development artifacts, the electronic device 110 may present second information. The second information may be presented in response to the first input and may indicate that the current intelligent system lacks a corresponding plugin for processing the first input. For example, if the first input indicates the deployment of a development artifact, and the current intelligent system has not yet associated with a plugin capable of deployment, the second information may indicate that the current intelligent system has not yet associated with a plugin for deploying the development artifact.
[0087] In some cases, the second information may also include an entry point for associating the corresponding plugin. The electronic device 110 can receive a first operation. The first operation can be used to associate the plugin with the current smart system. For example, the first operation may include a trigger operation to add an entry point for the corresponding plugin.
[0088] Alternatively or additionally, the first operation may include a second input. The second input may be in natural language and may be used to instruct the intelligent system to acquire the plugin. For example, a user may input natural language content via input component 210 to instruct the addition of a corresponding plugin or the acquisition of a corresponding deployment capability. In response to the second input, electronic device 110 may display the following reference. Figure 2H and Figure 2I The interface described is used to obtain and / or associate plugins.
[0089] After successfully associating the corresponding plugin with the current intelligent system, the intelligent system can use the plugin to continue processing the previously received initial input. In some cases, the user does not need to provide the initial input again to instruct the deployment of development artifacts. Therefore, the plugin association process can remain connected to the previously initiated deployment request.
[0090] In the event of a plugin association failure, the electronic device 110 can maintain the current interface or return to the display state before the plugin association. In some cases, the previous first input and / or the deployment request corresponding to the first input can also be retained so that processing can continue after the corresponding plugin can be associated.
[0091] In some cases, plugins associated with intelligent systems may include at least one functional component for deploying development artifacts. This functional component can provide functions such as deployment, configuration, status query, log query, runtime metric query, service control, and / or domain name management.
[0092] As an example, a functional component may include at least one skill component and / or at least one tool component. The skill component can be used to provide the intelligent system with information regarding how the corresponding task is handled. The tool component can be used to enable the intelligent system to invoke interfaces or instructions for performing corresponding operations.
[0093] In some scenarios, intelligent systems can generate deployment instructions based on plugins and execute them via a command-line interface. The command-line interface can be used to connect to the deployment system. The intelligent system can translate the deployment request expressed by the initial input into deployment instructions that can be processed by the deployment system.
[0094] For example, deployment instructions may include the identifier of the development artifact, the deployment type, and one or more deployment parameters. The deployment system can then perform deployment processing on the development artifact based on the deployment instructions.
[0095] In some scenarios, before deployment, the intelligent system can also obtain information related to the development artifacts through plugins. For example, it can determine the application corresponding to the development artifact, the current online version, the version to be deployed, the operating environment, service specifications, and / or configurations to be activated. Based on the obtained information, the intelligent system can determine the deployment object and corresponding deployment information for this deployment.
[0096] For initial deployments, it can be determined whether the development artifacts meet the corresponding deployment requirements. For development artifacts with existing online versions, it can be further determined whether this operation is an update deployment targeting existing development artifacts.
[0097] In some cases, if the information used to perform the deployment is incomplete or the conditions for performing the corresponding deployment process are not currently met, the intelligent system may stop or postpone the corresponding deployment process and may present corresponding prompt information through electronic device 110.
[0098] In this way, the first input can either explicitly indicate the plugin to be used, or simply describe the deployment task to be performed in natural language. If no plugin is explicitly indicated, the intelligent system can determine the plugin required to process the deployment request based on the first input. If the corresponding plugin is already associated with the intelligent system, it can continue processing the first input using that plugin; if the corresponding plugin is not yet associated with the intelligent system, it can present second information in response to the first input and continue processing the previous deployment request after associating the corresponding plugin.
[0099] Figure 2D A schematic diagram of interface 200D is shown, illustrating deployment confirmation and results under certain circumstances. Interface 200D can accept... Figure 2C The deployment request is shown below. See below for reference. Figure 2C and Figure 2D This describes a process of confirming deployment information before deployment and presenting the deployment status after deployment is completed.
[0100] like Figure 2D As shown, the electronic device 110 can present first deployment information 224. The first deployment information 224 can originate from an intelligent system and can describe one or more deployment parameters corresponding to this deployment. For example, the first deployment information 224 may include development artifacts, deployment environment, version to be deployed, source code location of the development artifacts, service specifications, or other information used to perform the deployment. In some cases, the first deployment information 224 may also include build commands, build artifacts, run commands, computing resource specifications, or other deployment parameters. By presenting the corresponding deployment information before performing the deployment, the user can learn about the development artifacts targeted by this deployment and the deployment parameters to be used.
[0101] Electronic device 110 can receive a second operation. The second operation is used to confirm the first deployment information 224. As an example, the second operation may include receiving user input for confirming the first deployment information 224 via input component 210. For example, such as... Figure 2D As shown, the electronic device 110 can display a user confirmation message 226. The user confirmation message 226 can instruct the user to confirm the first deployment information 224.
[0102] Additionally or alternatively, the second operation may include a triggering action on a confirmation control. For example, electronic device 110 may present a confirmation control in the display area corresponding to the first deployment information 224. In response to a user's click, touch, or other triggering action on the confirmation control, electronic device 110 may determine that the user has confirmed the first deployment information 224.
[0103] In some cases, the second operation may also include triggering an operation on the first deployment information 224 as a whole, on a card associated with the first deployment information 224, or on other confirmation entry points. The specific interaction form of the second operation is not limited, as long as it can be used to instruct the user to confirm the first deployment information 224.
[0104] In response to receiving the second operation, the intelligent system can deploy the development artifacts based on the first deployment information 224. In some cases, after receiving the second operation, confirmation information corresponding to this deployment can be generated, and the confirmation information can be associated with the current operating entity, the intelligent system executing this operation, the operation type, the development artifacts, the deployment environment, the code version, and / or the configuration version.
[0105] Before actually deploying, it's possible to reconfirm whether the above information has changed. If the development artifacts, code version, configuration version, or other deployment parameters change after user confirmation, deployment based on the previous confirmation can be stopped, and the deployment information awaiting confirmation can be presented again.
[0106] In some scenarios, the same confirmation can be used to trigger a corresponding deployment operation only once. For repeated triggers of the same deployment operation, the already accepted deployment status can be returned, without creating a new deployment process again.
[0107] In some cases, if a deployment operation is already in progress on the same deployment unit, a new deployment request can be responded to by presenting a state indicating that a deployment is in progress, without creating another deployment process.
[0108] In some situations, users can adjust deployment information before confirming deployment. As an example, electronic device 110 may first present second deployment information from the intelligent system. This second deployment information may include default server specifications, deployment version, or other parameters.
[0109] Electronic device 110 can receive a third input. The third input can be used to adjust the second deployment information. For example, a user can adjust computing resource specifications, build commands, artifacts to be deployed, or other deployment parameters through natural language instructions.
[0110] In response to a third input, electronic device 110 can present third deployment information. This third deployment information can originate from an intelligent system and can be obtained based on adjustments made by the user to the second deployment information. The intelligent system can then deploy development artifacts based on the third deployment information.
[0111] For example, if the second deployment information indicates that the development artifacts should be deployed using the first resource specification, but the user requests a different resource specification, the user can indicate the use of the second resource specification through a third input in natural language. The intelligent system can then generate the third deployment information accordingly and, after user confirmation, execute the deployment based on the second resource specification.
[0112] During deployment, the intelligent system can query the deployment status based on plugins. The deployment status can represent one of the following states of the development artifacts: waiting, packaging, compiling, deploying, successful deployment, failed deployment, canceled, or interrupted.
[0113] In some situations, electronic device 110 can update the deployment information presented in the session as the deployment status changes. For example, after deployment begins, information indicating that deployment is in progress can be presented; after deployment is completed, information indicating that deployment was successful can be presented.
[0114] like Figure 2D As shown, after deployment is complete, the electronic device 110 can display a deployment result card 228. The deployment result card 228 may include first information. The first information comes from the intelligent system and describes the deployment status of the development artifact. For example, the first information may indicate that the deployment of the development artifact has been completed.
[0115] In some situations, the initial information can also indicate that the development artifact is in a state such as being deployed, deployment failed, canceled, interrupted, or unknown. For situations where the deployment outcome cannot be determined temporarily, information indicating an unknown state can be presented instead of prematurely declaring the deployment successful.
[0116] In some cases, deployment results can be based on the state maintained by the deployment system. Therefore, even if the session interface or operations and maintenance interface is refreshed during the state update process, the corresponding deployment results can be restored according to the actual state of the deployment system.
[0117] In some scenarios, electronic device 110 can obtain the updated deployment status from server 130 and update the corresponding information on the interface based on the updated deployment status. The deployment status can be updated via event push, relevant protocols, server-sent events (SSE), polling, or other appropriate methods. Regardless of the status update method used, the deployment status presented on the interface can be based on the current status provided by the deployment system.
[0118] For update deployments, the current online version and the deployment result can be maintained separately. The current online version can represent the successful version that is currently providing services, while the deployment result can indicate whether the deployment is successful, failed, canceled, or in another state.
[0119] For example, if an update deployment fails or is canceled, the previously successful version can continue to provide services, rather than determining that the entire development artifact is unavailable solely based on this failure. Once the new deployment is successful, the current online version can be switched to the corresponding new version.
[0120] In some scenarios, different deployment states can be associated with incremental state version information. Electronic device 110 or server 130 can determine whether to update the current interface based on the state version information, thereby reducing the possibility that earlier generated state information will overwrite newer deployment results.
[0121] In some cases, the development deliverables correspond to the first version of the application. In response to the successful deployment of the first version, the electronic device 110 may also display a notification message. This notification message may indicate that the second version of the application is disabled. The second version may be a different application version from the first version.
[0122] For example, after a new version is successfully deployed and becomes the version currently being provided, versions that were previously in a pending state, replaced, or no longer used for the current service can be identified as the second version and a message indicating that the second version is in an invalid state will be displayed.
[0123] like Figure 2D As shown, the first information may further include a first entry point 232 and a second entry point 230. The first entry point 232 may correspond to a development product and is used to access the management interface of the development product. The second entry point 230 may be used to obtain an application corresponding to the development product. For example, if the development product corresponds to an installable application, triggering the second entry point 230 may cause the electronic device 110 to provide an installation product corresponding to the corresponding application. The installation product may include software content that can be used to install the corresponding application.
[0124] Alternatively, the electronic device 110 may also display an entry point 234 in the side area of the interface. Entry point 234 can be used to access the deployment and maintenance panel of the developed product. In the case where entry point 234 corresponds to the current developed product, entry point 234 can also serve as an example of a first entry point. Therefore, the first entry point can be presented in the deployment result card 228, or it can be presented in other areas of the interface. The specific location and form of presentation of the first entry point are not limited.
[0125] Figure 2E This diagram illustrates the interface 200E after entering the development artifact management interface under certain circumstances. See below for reference. Figure 2D and Figure 2E This describes a process for accessing the development artifact management interface.
[0126] Electronic device 110 can receive a third operation. The third operation can be used to trigger the first entry point. As an example, the third operation may include targeting... Figure 2D The triggering operation of entry 232. Additionally or alternatively, if entry 234 corresponds to the current development artifact, the third operation may also include a triggering operation for entry 234.
[0127] In response to the third operation, the electronic device 110 can display the first interface. For example, as Figure 2E As shown, a deployment and maintenance panel for managing development artifacts can be displayed on one side of the current session, resulting in interface 200E.
[0128] In some cases, the deployment and maintenance panel can be presented alongside the original session, allowing users to continue interacting with the intelligent system through input component 210 while viewing the status of development artifacts.
[0129] Alternatively, the deployment and maintenance panel can be implemented as a full-screen interface, an embedded interface, or other interface forms different from the session area.
[0130] like Figure 2E As shown, the electronic device 110 can display application cards 236 on a first interface. Application cards 236 can correspond to deployed development artifacts and may include the artifact's name, most recent deployment time, or other summary information. The electronic device 110 can also display a viewing control 238. The viewing control 238 can be used to view multiple deployed development artifacts.
[0131] As an example, in response to a trigger operation on application card 236, electronic device 110 can further present Figure 2F The status information of the development product is shown.
[0132] The electronic device 110 can also display a creation control 240 on the first interface. The creation control 240 can be used to initiate new deployment requests from the development artifact management interface. Therefore, deployment requests can be initiated not only from... Figures 2A to 2C The session can be initiated from the page corresponding to the development artifact, the deployment results, or the development artifact management interface.
[0133] In some scenarios, deployment requests initiated from different entry points can be converted into the same type of deployment operation information and processed based on the same development artifact identification, intelligent system determination, plugin determination, deployment information determination, and confirmation process. This ensures that deployment operations initiated from different interface entry points maintain consistent development artifacts and deployment status.
[0134] Figure 2F A schematic diagram of an interface 200F presenting development artifact status information according to certain scenarios is shown. Interface 200F can represent another display state of the first interface. See below for reference. Figure 2E and Figure 2F This describes a process for viewing the status information of deployed development artifacts.
[0135] like Figure 2F As shown, the electronic device 110 can display the application name 242 at the top of the deployment and maintenance panel to indicate the development artifact corresponding to the current first interface. The electronic device 110 can further display an overview label 244, a deployment history label 252, an observation label 254, and a configuration label 256. Different labels can be used to present different status information related to the development artifact. Status information may include configuration information and / or operational information, and may also include other information related to the deployment process of the development artifact.
[0136] exist Figure 2F In the displayed state, overview label 244 can be selected. Electronic device 110 can display online environment information card 246 in the display area corresponding to overview label 244. Online environment information card 246 can display at least some status information of the development product. For example, online environment information card 246 can display deployment version, server specifications, access point, deployment time, current online version, or other information related to the development product. Server specifications or other deployment-related parameters can be part of the configuration information. Access point, deployment time, current online version, or other information describing the current operating status of the development product can be part of the operating information.
[0137] The electronic device 110 can also respond to a trigger operation on the deployment history tag 252 to present status information related to the historical deployment process of the development artifact. For example, it can present the deployment time, deployment version, deployment status, or other deployment history information corresponding to one or more deployments. In some cases, deployment history information corresponding to multiple deployments can be presented in chronological order, and more information related to the historical deployment process can be viewed through pagination or other means.
[0138] The electronic device 110 can also respond to a trigger operation on the observation tag 254 to present at least some operational information of the development artifact. For example, the operational information may include access status, operational metrics, operational observation information, logs, or other information that can describe the operational status of the development artifact. Thus, the user can view the relevant status of the development artifact during its operation through the observation tag 254.
[0139] Electronic device 110 can also respond to a trigger operation on configuration tag 256 by presenting at least a portion of the configuration information of the development artifact. The configuration information may include at least one deployment parameter of the development artifact. For example, the configuration information may include environment variables, domain names, server specifications, resource specifications, or other parameters related to the deployment and / or operation of the development artifact.
[0140] In some cases, the online environment information card 246 can simultaneously display the entry point for accessing the development artifact, the most recent deployment time, the current deployment version, and the service specifications.
[0141] The electronic device 110 can also display usage information 248. Usage information 248 can be used to describe the computing, network, or other resources consumed or occupied during the operation of the developed product. For example, it can display computing resource usage, network resource usage, or other resource usage.
[0142] The electronic device 110 may also display a deployment information area 250. The deployment information area 250 may include deployment history information corresponding to one or more deployments. For example, the deployment history information may describe the deployment time, deployment version, and deployment status of the corresponding deployment.
[0143] In some cases, deployment information area 250 may only display deployment history information within a preset range. In response to a triggered operation on deployment history tag 252, electronic device 110 may display more deployment history information or a more complete deployment history. The deployment history may also be presented using a paginated or segmented loading method.
[0144] Different deployment processes can correspond to different application versions. The information corresponding to the current online version and a single deployment can be saved and presented separately, enabling users to distinguish between the currently running version and the execution result of a particular deployment.
[0145] In some situations, certain configuration details may not be displayed directly. For example, for configuration items that are not suitable for direct presentation in the interface or session, only the configuration item name, configuration status, or processed content may be displayed.
[0146] The version, running status, deployment history, logs, running metrics, and configuration content of the development artifacts after deployment can be presented in the first interface associated with the corresponding development artifacts.
[0147] In some cases, the status information presented on the first interface can also serve as context for subsequent interactions by the intelligent system.
[0148] For example, electronic device 110 can receive a fourth input in natural language form through input component 210 presented alongside the first interface. The fourth input can request the intelligent system to analyze the current state of the development product, query logs, interpret operating metrics, adjust configurations, redeploy, or perform other operations related to the development product.
[0149] The electronic device 110 can present third information from the intelligent system. The third information can be obtained based on the fourth input and the status information in the first interface.
[0150] For example, if a user inquires about the reason for a failed deployment via a fourth input, the intelligent system can generate third information based on the deployment's status information and corresponding logs. As another example, if a user requests to adjust a configuration via a fourth input, the intelligent system can determine the configuration to be adjusted based on the current configuration information and the fourth input, and organize subsequent configuration operations. Furthermore, if a user requests to stop, cancel, or redeploy development artifacts, the intelligent system can invoke the corresponding service control or deployment capabilities based on plugins.
[0151] In some cases, users can select relevant content from the first interface for logs or operational metrics. Electronic device 110 can input the selected content, along with associated development artifacts, time ranges, and / or filter criteria, into input component 210.
[0152] Users can supplement natural language content in input component 210 and send corresponding input. The intelligent system can analyze the input based on the referenced state information and the natural language content supplemented by the user.
[0153] When sending input, this input can be associated with the development artifacts and corresponding filter conditions. Therefore, users do not need to re-describe the development artifacts to be analyzed and their corresponding status information after returning to the session from the operations panel.
[0154] In some cases, log content can be provided to the intelligent system as data to be analyzed, rather than as instructions to change the rules that the intelligent system executes.
[0155] When a user requests to modify the configuration, redeploy, stop the service, cancel the deployment, roll back, or perform other operations that can change the running status of the development artifacts, the pending confirmation information can be displayed again, and the corresponding operation can be performed after receiving the confirmation.
[0156] In some situations, rollback can be used to redeploy development artifacts based on previous versions. In response to a rollback operation, deployment history information corresponding to this rollback can be generated. Previously generated deployment history information can be retained. Therefore, the deployment history information can reflect the deployment status before and after the rollback.
[0157] In some scenarios, intelligent systems can perform the above operations by calling command-line interfaces through plugins. Plugins can provide intelligent systems with operational capabilities such as deployment, configuration, status query, log query, performance metric query, service control, and domain name management.
[0158] In this way, the first interface can be used to present the more critical deployment and operation information, while the complex processing related to specific operations can be completed by the intelligent system in combination with plugins.
[0159] Figure 2G A schematic diagram shows an interface 200G that switches between managed development artifacts according to certain conditions. Interface 200G can represent... Figure 2F This is another display state of the first interface shown.
[0160] The following is for reference. Figure 2F and Figure 2G This describes a process for switching between different development artifacts in the deployment and operations panel.
[0161] Electronic device 110 can receive a trigger operation on application switching control 258. In response to the trigger operation, electronic device 110 can present application selection component 260.
[0162] The application selection component 260 may include application option 262 and application option 264. Different application options may correspond to different deployed development artifacts.
[0163] As an example, application option 262 may correspond to the first development artifact, and application option 264 may correspond to the second development artifact. Each application option may present the identifier of the corresponding development artifact, recent deployment information, or other status summary.
[0164] Electronic device 110 can receive a selection operation for one of the application options. In response to the corresponding selection operation, electronic device 110 can stop displaying the status information of the currently developed product and display the status information of the selected developed product.
[0165] For example, when a user switches from application option 262 to application option 264, Figure 2F The contents of the online environment information card 246, usage information 248, and deployment information area 250 can be updated to the contents associated with the development artifacts corresponding to application option 264.
[0166] In some cases, users can manage multiple deployed development artifacts through the same intelligent system.
[0167] Alternatively, and where appropriate, the same development artifact can be managed through different intelligent systems. Different intelligent systems can perform corresponding operations using their respective associated plugins, based on the scope of operations currently available to the user on the development artifact.
[0168] In some cases, if a user has already referenced the logs or runtime metrics of the first development artifact to the input component 210, but switches to the second development artifact through the application selection component 260 before sending the corresponding input, the referenced content previously associated with the first development artifact may become invalid, or the user may be prompted to reselect the status information to be referenced.
[0169] Figure 2H A schematic diagram of the plugin browsing interface 200H is shown, depending on certain scenarios. Interface 200H can be used to add plugins to a smart system. See below for reference. Figure 2H Describes a process for obtaining plugins used to deploy development artifacts.
[0170] like Figure 2H As shown, the electronic device 110 can display an extended navigation item 266 that is selected. In response to a triggering operation on the extended navigation item 266, the electronic device 110 can display multiple plugins. As an example, the multiple plugins can be organized according to different types. For example, a design creation category 268-1 and a programming development category 268-2 can be displayed.
[0171] The electronic device 110 can display display components corresponding to multiple plugins under different categories. For example, it can display plugin display component 270, plugin display component 272-1, and plugin display component 272-2. Different plugin display components can display the name, icon, function information, and / or other information used to describe the plugin.
[0172] As an example, the plugin display component 272-2 can correspond to a deployment and maintenance plugin used to deploy development artifacts. The plugin display component 272-2 may include an add control 274. The add control 274 can be used to associate the deployment and maintenance plugin with the current intelligent system.
[0173] Electronic device 110 can receive the first operation. In response to the first operation, the deployment and maintenance plugin can be associated with the current intelligent system. For example, the first operation may include triggering the addition of control 274.
[0174] In some cases, Figure 2H The plugin browsing interface 200H shown can be displayed in response to the user actively accessing the extended functions.
[0175] Additional or alternative land, in Figure 2C Once it is determined during the process that the current intelligent system lacks a plugin for deploying development artifacts, an entry point for accessing interface 200H can be presented. Interface 200H can be displayed in response to a user's triggering action on this entry point. In some cases, the plugin display component 272-2 corresponding to the deployment and maintenance plugin can also be presented or located within interface 200H.
[0176] In other cases, the user can instruct the intelligent system to obtain the corresponding plugin via a second input in the form of natural language. In response to the second input, the electronic device 110 can present the plugin display component 272-2 corresponding to the plugin, or present the plugin details interface 200I described later.
[0177] Before associating a plugin, the user can be presented with the plugin name, plugin function, or other information indicating the plugin to be associated. The electronic device 110 can receive a trigger operation for the add control 274 and, in response to the trigger operation, associate the corresponding plugin with the current smart system.
[0178] In the event of a plugin association failure, the original intelligent system, session, and deployment request can be preserved. In some cases, the first input received can also be retained so that processing of that first input can continue once the corresponding plugin can be associated.
[0179] Figure 2I This diagram illustrates the plugin details interface 200I under various scenarios. Interface 200I can accept... Figure 2HThe plugin browsing interface shown. For example, in response to... Figure 2H The plugin display component 272-2 triggers the operation, and the electronic device 110 can display the interface 200I.
[0180] like Figure 2I As shown, the electronic device 110 can display a plugin details panel 276. The plugin details panel 276 may include a name and description area 278, add controls 280, applicable scenario information 282, skill entries 284-1 to 284-3, tool capability entries 286, and preview panel entries 288. The name and description area 278 can display the plugin's name and information describing its purpose. For example, it can indicate that the plugin is used for the deployment and maintenance of development artifacts.
[0181] Adding control 280 can be used to associate the current plugin with the smart system. Electronic device 110 can receive a first operation (e.g., a trigger operation) on adding control 280 and associate the plugin with the smart system in response to the first operation. Applicable scenario information 282 can describe one or more applicable scenarios for the plugin. For example, it can indicate that the plugin is used to deploy corresponding software artifacts.
[0182] Electronic device 110 can also present descriptive information in plugin details panel 276. The descriptive information may include at least one entry, and each entry may describe at least one functional component of the plugin. For example, skill entries 284-1, 284-2, and 284-3 may describe different skill components. Each skill entry may include a skill name and a description of the functions supported by the corresponding skill. In some cases, a skill component may be used to describe the execution process of deploying development artifacts, enabling the intelligent system to determine the tools or operations to be invoked or performed during deployment. Another skill component may be used to describe post-deployment status queries or maintenance processes. For example, it may describe how to query deployment status, running status, logs, or running metrics. Yet another skill component may be used to describe configuration adjustments, service control, or other processes related to the continuous management of development artifacts.
[0183] Tool capability entry 286 may describe at least one tool component in a plugin. For example, a tool component may provide an interface or command that can be invoked to the intelligent system. The tool component may support at least one of deployment, configuration query, status query, log query, runtime metric query, service control, or domain name management. In some cases, the tool component may include a command-line interface for connecting to the deployment system. The intelligent system may generate deployment instructions based on the process described by the skill component and the user's natural language input, and execute the corresponding deployment instructions through the command-line interface.
[0184] For example, an intelligent system can determine the development artifact and deployment type based on the first input, and generate deployment instructions based on the artifact's identifier and one or more deployment parameters. A command-line interface can then provide these deployment instructions to the deployment system to execute the deployment of the development artifact.
[0185] In some cases, development artifacts may include or be associated with predefined deployment specification information. Deployment specification information can be used to describe how the development artifact is built, operated, and / or other deployment-related processes. Intelligent systems can determine at least part of the deployment process for a development artifact based on the deployment specification information. For example, an intelligent system can determine the build and operation methods of a development artifact based on the deployment specification information, and generate corresponding deployment instructions by combining the artifact's identifier, deployment type, and deployment parameters.
[0186] In some scenarios, intelligent systems can also query deployment status via command-line interfaces. For example, after triggering a deployment, the intelligent system can query whether the current deployment is in the packaging, compilation, deployment, or completion stage, and then transmit the queried deployment status through a message in the session or... Figure 2D The first piece of information shown is presented to the user.
[0187] Similarly, intelligent systems can also query the logs, operating metrics, or configuration status of development artifacts through command-line interfaces, and provide third-party information to users based on the corresponding query results.
[0188] Preview panel entry 288 describes the panel capabilities associated with the plugin. For example, the plugin can be associated with the panel mentioned in the previous reference. Figures 2E to 2G The deployment and operations dashboard is described below. It can be used to present key status information of development artifacts deployed or managed by intelligent systems through plugins.
[0189] Plugins can be formed by multiple functional components of different types. For example, a plugin may include skill components for describing the execution process, tool components for invoking specific deployment or maintenance capabilities, and panel capabilities for presenting the status information of development artifacts. Different functional components can work together to enable the intelligent system to complete the deployment and subsequent management of development artifacts based on natural language input.
[0190] In some cases, plugins can be pre-built into the intelligent system or associated with the intelligent system in response to user actions. Plugins can also be provided by one or more external capabilities. The specific implementation is unrestricted, as long as the plugin can provide the aforementioned deployment and / or operational capabilities to the intelligent system.
[0191] In some cases, a plugin can declare the functionalities it supports. Electronic device 110 or server 130 can determine whether a given intelligent system can execute user requests based on these functionalities. For example, if a user requests to deploy development artifacts, it can be determined whether the current intelligent system is associated with a plugin that has deployment capabilities. If a user requests to query logs or stop service, it can be further determined whether the plugin supports the corresponding log query or service control capabilities.
[0192] In some situations, when multiple intelligent systems are available, their presentation order can be determined based on whether these intelligent systems are already associated with the corresponding plugins. For example, intelligent systems that are already associated with plugins for deploying development artifacts can be presented first.
[0193] Figure 2J A schematic diagram of an interface 200J displaying multiple development artifacts according to certain scenarios is shown. Interface 200J can respond to... Figure 2A The settings entry 205 is triggered and displayed. See below for reference. Figure 2J This describes a process for selecting a first development product to be processed from multiple development products.
[0194] like Figure 2J As shown, the electronic device 110 can display at least one development product, such as development product 292-1, development product 292-2, and development product 292-3, in response to a trigger operation on the entry 290 or when the entry 290 is selected. Different development products can correspond to different applications, services, or other software products.
[0195] In some cases, the interface 200J can be used to display development artifacts that have been deployed. For example, the display area corresponding to the development artifact can present the artifact's name, graphical representation, deployment status, online version, or other information related to that development artifact.
[0196] As an example, electronic device 110 may receive a fourth operation. The fourth operation may be used to select a first development product from at least one development product. For example, the fourth operation may include a trigger operation on the first development product (e.g., development product 292-1). Alternatively, electronic device 110 may be associated with a processing entry 294 for development product 292-1. The fourth operation may include a trigger operation on processing entry 294. For example, selection of the first development product may be used to instruct a user to request subsequent processing for the first development product. Subsequent processing may include continuing to edit the first development product, redeploying the first development product, updating the first development product, or performing other processing related to the first development product.
[0197] Figure 2KA schematic diagram is shown of an interface 200K for a smart system used to process the first development product, selected according to certain circumstances. The interface 200K can be presented in response to a fourth operation.
[0198] like Figure 2K As shown, after the first developed product is selected, the electronic device 110 can present at least one intelligent system. The at least one intelligent system can be used to process the first developed product. For example, the at least one intelligent system may include intelligent system option 296-1, intelligent system option 296-2, and intelligent system option 296-3. Different intelligent system options can correspond to different intelligent systems.
[0199] In some cases, different intelligent systems may have different functional capabilities. For example, different intelligent systems may each have the ability to edit development artifacts, generate development artifacts, deploy development artifacts, adjust development artifact configurations, or perform other processing. Electronic device 110 and / or server 130 may determine one or more intelligent systems capable of processing the first development artifact and present intelligent system options corresponding to the determined intelligent systems.
[0200] In some cases, at least one intelligent system can be determined based on the attributes of a first development product. The attributes of the first development product may include the type of development product, the technical framework used, the code type, the functional type, the deployment status, the functional capabilities associated with the development product, or other information that can be used to determine the processing method. Alternatively, at least one intelligent system may be an intelligent system associated with corresponding plugins (e.g., having deployment capabilities).
[0201] For example, if the first development product includes code that can be processed by a first type of intelligent system, an intelligent system with the corresponding code processing capability can be identified. As another example, if the first development product has been deployed and the user requests its redeployment, an intelligent system capable of invoking the plugin used to deploy the development product can be identified.
[0202] By identifying at least one intelligent system based on the attributes of the first development product, the number of intelligent systems presented to the user that cannot handle the first development product can be reduced. It also reduces the need to re-determine the processing object or re-select an intelligent system after selection.
[0203] Electronic device 110 can receive a fifth operation. The fifth operation can be used to select a second intelligent system from at least one intelligent system. For example, the fifth operation may include a trigger operation for an intelligent system option corresponding to the second intelligent system.
[0204] In response to the fifth operation, electronic device 110 can display a fourth interface. The fourth interface can display a conversation with the second intelligent system. As an example, the fourth interface can be implemented as follows: Figure 2A The interface 200A or has the same Figure 2A The interface structure is similar to that shown in the session interface, and the current session can be associated with the second intelligent system.
[0205] Upon entering the fourth interface, the first development artifact can be associated with the session within that interface. For example, the identifier, code content, version information, deployment status, and / or other information related to the first development artifact can be associated with that session. The second intelligent system can then determine the development artifact that needs to be processed in subsequent steps without requiring the user to relocate the first development artifact.
[0206] Users can continue to provide natural language input to the second intelligent system through the fourth interface. For example, users can instruct the second intelligent system to continue editing the first development product, adjust the functionality of the first development product, modify the code and / or configuration of the first development product, or redeploy the first development product.
[0207] In some cases, the second intelligent system can generate a second development product based on the first development product. For example, the second intelligent system can edit or otherwise process the first development product based on the first development product and user input received through the fourth interface to obtain the second development product.
[0208] The second development product may include a development product that has undergone at least partial changes based on the first development product. For example, the second development product may include code content, configuration content, functional content, interface content, or other development content that has changed relative to the first development product. In some cases, the second development product may correspond to an updated version of the first development product.
[0209] Electronic device 110 can receive a second development product from a second intelligent system. For example, after completing the corresponding processing for the first development product, the second intelligent system can provide the second development product to electronic device 110 or indicate that the second development product has been generated. Alternatively, deployment can be updated based on the second development product. For example, the deployment system can perform new deployment processing based on the second development product to update the existing deployment corresponding to the first development product to the deployment corresponding to the second development product. Additionally or alternatively, the version to be deployed, deployment content, or other information related to deployment can be updated based on the second development product.
[0210] In some cases, before updating the deployment based on the second development product, deployment information corresponding to the second development product can be presented, and confirmation operations for the corresponding deployment information can be received. Furthermore, corresponding deployment instructions can be generated using plugins associated with the second intelligent system, and the deployment instructions can be executed via a command-line interface.
[0211] This allows for a continuous interactive process, from viewing deployed development artifacts to selecting artifacts, choosing intelligent systems, further editing artifacts, and updating deployments. Users can continue processing and updating deployments based on existing artifacts without having to recreate development tasks or re-enter information about the first artifact.
[0212] In some scenarios, after a user selects a first development product, subsequent operations can be determined based on the user's requested processing for that product. For example, if a user requests to continue editing the first development product, at least one intelligent system capable of editing it can be presented. If a user requests to redeploy the first development product, at least one intelligent system capable of performing deployment processing can be presented. If the intelligent system possesses both editing and deployment capabilities, the editing and update deployment of the first development product can be completed sequentially within the same session.
[0213] Based on the process described above, a continuous interaction path can be formed within the session associated with the intelligent system. This interaction path can include the generation of development artifacts, initiation of deployment requests, plugin identification, confirmation of deployment information, deployment execution, deployment status feedback, and subsequent management. Users can instruct the intelligent system to deploy development artifacts using natural language. If the first input does not explicitly indicate a plugin, the intelligent system can determine the plugin to handle the deployment request based on the first input. If the intelligent system lacks a corresponding plugin, a corresponding prompt can be presented. After the plugin is associated with the intelligent system, it can continue processing the previous deployment request. This reduces the number of operations that interrupt the deployment process or re-initiate the deployment request due to the lack of corresponding functional capabilities. By presenting deployment information and receiving confirmation before deployment, the development artifacts, deployment environment, and deployment parameters confirmed by the user can be kept consistent with the subsequent deployment operations. After deployment is completed, the deployment status can be fed back through the first information. Users can also access the first interface associated with the development artifact through the first entry point. The first interface can centrally present status information such as configuration information, running information, deployment history information, logs, and running metrics. Users can also continue to interact with the intelligent system using natural language based on this status information. This reduces the need to repeatedly switch between different functional interfaces. It can also reduce the need to relocate development artifacts and repeatedly enter deployment-related information. This shortens the interaction path for development artifact deployment and subsequent management.
[0214] Furthermore, the intelligent system can invoke corresponding deployment and management capabilities through functional components in its associated plugins. This allows deployment requests in natural language to be translated into corresponding processing operations. Operations initiated from different entry points can be processed based on the same development artifacts, versions, configurations, and deployment status. This reduces the possibility of inconsistencies in the processing objects corresponding to different interaction paths. The current online version and the result of a single deployment can be maintained separately. This ensures that the currently running version is accurately reflected even if the update deployment fails, is canceled, or is interrupted. This reduces the possibility of inconsistencies between deployment results and the actual running status. The status information of development artifacts can also be associated with interactions in the session. This reduces the need to repeatedly obtain and transmit context information for analyzing logs, operating metrics, or configuration status. Consequently, it reduces the number of times electronic devices load, process, and render data across multiple interfaces. It also reduces data interaction between electronic devices and servers caused by repeatedly querying deployment status or repeatedly obtaining deployment-related information. In addition, it reduces data processing and communication overhead and improves information processing efficiency and interface interaction efficiency during the deployment and subsequent management of development artifacts.
[0215] Example process Figure 3 A flowchart of an example process 300 for deploying artifacts under certain circumstances is shown. Process 300 can be implemented at electronic device 110. See below for reference. Figure 1 To describe process 300.
[0216] In box 310, electronic device 110 can receive a first input in natural language form, which instructs intelligent system to deploy development products. The intelligent system is associated with plug-ins, which include at least one functional component for deploying development products.
[0217] In frame 320, electronic device 110 can present first information, which comes from the intelligent system and describes the deployment status of the developed product.
[0218] In some cases, receiving the first input includes: presenting an input component for interacting with the intelligent system; presenting a first element in the input component, the first element indicating a plugin; and receiving the first input through the input component.
[0219] In some cases, presenting the first element in the input component includes: receiving a sixth operation in the input component to present multiple plugin identifiers, the plugin identifiers including a first identifier corresponding to a plugin; receiving a seventh operation for selecting the first identifier; and presenting the first element in the input component.
[0220] In some cases, process 300 further includes: presenting second information indicating that the smart system lacks a plug-in; and receiving a first operation for associating the plug-in with the smart system.
[0221] In some cases, receiving the first operation includes receiving a second input, which is in natural language form, and is used to instruct the intelligent system to retrieve the plugin.
[0222] In some cases, process 300 further includes: presenting first deployment information from an intelligent system; and receiving a second operation to confirm the first deployment information, the intelligent system deploying the development product based on the first deployment information.
[0223] In some cases, process 300 further includes: presenting second deployment information from an intelligent system; receiving a third input for adjusting the second deployment information; and presenting third deployment information from an intelligent system, which deploys the development product based on the third deployment information.
[0224] In some cases, the first information indicates that the deployment of the development product has been completed, and process 300 further includes: presenting a first entry point, the first entry point corresponding to the development product; and receiving a third operation, presenting a first interface, the first interface including the status information of the development product, and the third operation being used to trigger the first entry point.
[0225] In some cases, the first information includes a first entry point and a second entry point, with the second entry point used to obtain the application corresponding to the development product.
[0226] In some cases, status information includes at least one of the following: configuration information, which includes at least one deployment parameter of the development artifact; and runtime information, which describes the runtime status of the development artifact.
[0227] In some cases, process 300 may further include: receiving a fourth input, which is in the form of natural language; and presenting third information, which is derived from the intelligent system based on the fourth input and state information.
[0228] In some cases, the development product is a first development product, the intelligent system is a first intelligent system, and process 300 further includes: displaying at least one development product; receiving a fourth operation for selecting the first development product; presenting at least one intelligent system for processing the first development product; receiving a fifth operation for selecting a second intelligent system, the second intelligent system being one of the at least one intelligent system; and presenting a fourth interface displaying a conversation with the second intelligent system.
[0229] In some cases, presenting at least one intelligent system includes: presenting at least one intelligent system, wherein the at least one intelligent system is determined based on the properties of a first development product.
[0230] In some cases, process 300 further includes: receiving a second development product, the second development product being generated from a second intelligent system, the second development product being generated based on the first development product; and updating the deployment of the first development product based on the second development product.
[0231] In some cases, process 300 further includes: presenting descriptive information on a first interface, the descriptive information including at least one entry, each of which describes at least one functional component.
[0232] In some cases, receiving the first input includes receiving the first input in a session associated with the intelligent system, the session including at least one message, the at least one message being used to instruct the intelligent system to generate a development artifact.
[0233] In some cases, at least one functional component includes at least one of the following: at least one skill component, at least one tool component.
[0234] In some cases, the intelligent system deploys development artifacts based on the following process: the intelligent system generates deployment instructions based on plugins; and the deployment instructions are executed via a command-line interface to deploy the development artifacts, which is used to connect to the deployment system.
[0235] In some cases, the development artifact corresponds to the first version of the application, and process 300 further includes: in response to the successful deployment of the first version, displaying a prompt message indicating that the second version of the application is in a disabled state.
[0236] In this way, by using plugins associated with intelligent systems, development products can be deployed based on input in the form of natural language, and the deployment status can be presented through information from the intelligent system, thereby connecting deployment instructions and status feedback; the confirmation or adjustment of deployment information and the presentation of post-deployment status information can also support interactive processing of the deployment process and running status of development products.
[0237] Example devices and equipment A corresponding apparatus for implementing the above methods or processes is also provided. Figure 4 A schematic structural block diagram of an example device 400, representing a deployment product under certain circumstances, is shown. Device 400 can be implemented as or included in electronic device 110. The various modules / components in device 400 can be implemented by hardware, software, firmware, or any combination thereof.
[0238] like Figure 4As shown, the device 400 includes: a first receiving module 410 configured to receive a first input, the first input being in natural language form, the first input instructing an intelligent system to deploy a development product, the intelligent system being associated with a plug-in, the plug-in including at least one functional component for deploying the development product; and a first presentation module 420 configured to present first information, the first information being from the intelligent system, the first information describing the deployment status of the development product.
[0239] In some cases, the first receiving module 410 is also configured to: present an input component for interacting with the intelligent system; present a first element in the input component, the first element indicating a plug-in; and receive a first input through the input component.
[0240] In some cases, the first receiving module 410 is also configured to: receive a sixth operation on the input component, presenting a plurality of plug-in identifiers, the plug-in identifiers including a first identifier corresponding to a plug-in; receive a seventh operation, the seventh operation being used to select the first identifier; and present a first element on the input component.
[0241] In some cases, device 400 also includes a second presentation module configured to: present second information indicating that the smart system lacks a plugin; and receive a first operation for associating the plugin with the smart system.
[0242] In some cases, the second presentation module is also configured to receive a second input, which is in natural language form, and is used to instruct the intelligent system to retrieve the plugin.
[0243] In some cases, device 400 also includes a third presentation module configured to: present first deployment information from an intelligent system; and receive a second operation to confirm the first deployment information, based on which the intelligent system deploys development products.
[0244] In some cases, device 400 also includes a fourth presentation module configured to: present second deployment information from an intelligent system; receive a third input for adjusting the second deployment information; and present third deployment information from an intelligent system, which deploys development products based on the third deployment information.
[0245] In some cases, the first information indicates that the development product has been deployed, and the device 400 also includes a fifth presentation module configured to: present a first entry point corresponding to the development product; and receive a third operation to present a first interface including status information of the development product, the third operation being used to trigger the first entry point.
[0246] In some cases, the first information includes a first entry point and a second entry point, with the second entry point used to obtain the application corresponding to the development product.
[0247] In some cases, status information includes at least one of the following: configuration information, which includes at least one deployment parameter of the development artifact; and runtime information, which describes the runtime status of the development artifact.
[0248] In some cases, device 400 further includes a second receiving module configured to: receive a fourth input, which is in the form of natural language; and present third information, which is derived from an intelligent system based on the fourth input and state information.
[0249] In some cases, the development product is a first development product, the intelligent system is a first intelligent system, and the device 400 further includes a product display module configured to: display at least one development product; receive a fourth operation for selecting the first development product; present at least one intelligent system for processing the first development product; receive a fifth operation for selecting a second intelligent system, the second intelligent system being one of the at least one intelligent system; and present a fourth interface displaying a conversation with the second intelligent system.
[0250] In some cases, the device 400 also includes a determining module configured to: present at least one intelligent system, the at least one intelligent system being determined based on the attributes of the first development product.
[0251] In some cases, the device 400 also includes an update module configured to: receive a second development product from a second intelligent system, the second development product being generated based on the first development product; and update the deployment of the first development product based on the second development product.
[0252] In some cases, the device 400 further includes a sixth presentation module configured to present descriptive information on a first interface, the descriptive information including at least one entry, each of which describes at least one functional component.
[0253] In some cases, the first receiving module 410 is also configured to receive a first input in a session associated with the intelligent system, the session including at least one message, the at least one message being used to instruct the intelligent system to generate a development artifact.
[0254] In some cases, at least one functional component includes at least one of the following: at least one skill component, at least one tool component.
[0255] In some cases, the intelligent system deploys development artifacts based on the following process: the intelligent system generates deployment instructions based on plugins; and the deployment instructions are executed via a command-line interface to deploy the development artifacts, which is used to connect to the deployment system.
[0256] In some cases, the development artifact corresponds to the first version of the application, and the device 400 also includes a prompting module configured to display a prompt message in response to the successful deployment of the first version, the prompt message indicating that the second version of the application is in a disabled state.
[0257] The modules included in device 400 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some cases, one or more modules can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units in device 400 can be implemented at least partially by one or more hardware logic components. By way of example, and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard parts (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), and so on.
[0258] Figure 5 A block diagram of an electronic device 500 in which one or more examples may be implemented is shown. It should be understood that... Figure 5 The electronic device 500 shown is merely exemplary and should not be construed as limiting the functionality and scope of the examples described herein. Figure 5 The electronic device 500 shown can be used to implement the electronic device 110 discussed above.
[0259] like Figure 5As shown, electronic device 500 is in the form of a general-purpose electronic device. Components of electronic device 500 may include, but are not limited to, one or more processing units or processors 510, memory 520, storage devices 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. Processor 510 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 520. In a multiprocessor system, multiple processors execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 500.
[0260] Electronic device 500 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 500, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 520 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof). Storage device 530 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data and can be accessed within electronic device 500.
[0261] Electronic device 500 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 5 As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 520 may include computer program product 525 having one or more program modules configured to perform various methods or actions of various examples.
[0262] The communication unit 540 enables communication with other electronic devices via a communication medium. Additionally, the functionality of the components of the electronic device 500 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 500 can operate in a networked environment using logical connections to one or more other servers, networked personal computers, or another network node.
[0263] Input device 550 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 560 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 500 can also communicate with one or more external devices (not shown) via communication unit 540 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 500, or with any device that enables electronic device 500 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via an input / output (I / O) interface (not shown).
[0264] A computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. A computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above.
[0265] The flowcharts and / or block diagrams of the methods, apparatus, devices, and computer program products referred to herein describe various aspects. It should be understood that each block of the flowcharts and / or block diagrams, as well as combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.
[0266] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.
[0267] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.
[0268] The flowcharts and block diagrams in the accompanying figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products under various scenarios. In this respect, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the figures. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.
[0269] Various examples have been described above. The foregoing descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.
Claims
1. A method for deploying artifacts, comprising: The system receives a first input, which is in the form of natural language, and the first input instructs the intelligent system to deploy the development product. The intelligent system is associated with a plugin, and the plugin includes at least one functional component for deploying the development product. as well as The system presents first information, which comes from the intelligent system and describes the deployment status of the development product.
2. The method according to claim 1, further comprising: The system presents a second piece of information indicating that the intelligent system lacks the plugin. as well as Receive a first operation, which is used to associate the plugin with the smart system.
3. The method according to claim 2, wherein, The receiving first operation includes: The system receives a second input, which is in natural language and is used to instruct the intelligent system to obtain the plugin.
4. The method according to claim 1, further comprising: The first deployment information is presented, and the first deployment information comes from the intelligent system; as well as The system receives a second operation, which confirms the first deployment information, and the intelligent system deploys the development product based on the first deployment information.
5. The method according to claim 1, further comprising: Presenting second deployment information, which originates from the intelligent system; Receive a third input, which is used to adjust the second deployment information; as well as A third deployment information is presented, which comes from the intelligent system, and the intelligent system deploys the development product based on the third deployment information.
6. The method of claim 1, wherein the first information indicates that the development artifact has been deployed, the method further comprising: A first entry point is presented, which corresponds to the development product; as well as Upon receiving a third operation, a first interface is displayed, which includes the status information of the development product. The third operation is used to trigger the first entry point.
7. The method according to claim 6, wherein the first information includes the first entry and the second entry, the second entry being used to obtain an application corresponding to the development product.
8. The method of claim 6, wherein the status information includes at least one of the following: Configuration information, which includes at least one deployment parameter of the development artifact; Operational information, which describes the operational status of the development product.
9. The method of claim 6, further comprising: Receive a fourth input, which is in natural language form; as well as The system presents a third piece of information, which is derived from the intelligent system and is obtained based on the fourth input and the state information.
10. The method according to claim 1, wherein the development product is a first development product, the intelligent system is a first intelligent system, and the method further comprises: Show at least one development artifact; Receive a fourth operation, the fourth operation being used to select the first development product; At least one intelligent system is presented, the at least one intelligent system being used to process the first development product; A fifth operation is received, the fifth operation being used to select a second intelligent system, the second intelligent system being one of the at least one intelligent systems; as well as A fourth interface is presented, which displays the conversation with the second intelligent system.
11. The method according to claim 10, wherein, The presentation of at least one intelligent system includes: At least one intelligent system is presented, the at least one intelligent system being determined based on the attributes of the first development product.
12. The method of claim 10, further comprising: Receive a second development product, which comes from the second intelligent system and is generated based on the first development product; Based on the second development product, update the deployment of the first development product.
13. The method according to claim 1, wherein, The receiving of the first input includes: The first input is received in a session associated with the intelligent system, the session including at least one message instructing the intelligent system to generate the development artifact.
14. The method according to claim 1, wherein, The intelligent system deploys the development deliverables based on the following process: The intelligent system generates deployment instructions based on the plugin; as well as The deployment instructions are executed via a command-line interface to deploy the development artifacts. The command-line interface is used to connect to the deployment system.
15. The method according to claim 1, wherein, The development product corresponds to the first version of the application, and the method further includes: Upon successful deployment of the first version, a notification message is displayed indicating that the second version of the application is in a disabled state.
16. An apparatus for deploying a product, comprising: A first receiving module is configured to receive a first input, which is in the form of natural language. The first input instructs the intelligent system to deploy development products. The intelligent system is associated with a plugin, which includes at least one functional component for deploying development products. as well as The first presentation module is configured to present first information, which comes from the intelligent system and describes the deployment status of the development product.
17. An electronic device comprising: At least one processor; as well as At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions causing the electronic device to perform the method according to any one of claims 1 to 15 when executed by the at least one processor.
18. A computer-readable storage medium having stored thereon computer-executable instructions that can be executed by a processor to implement the method according to any one of claims 1 to 15.
19. A computer program product tangibly stored in a computer storage medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method according to any one of claims 1 to 15.
