Cooperative project management continuous integration delivery method and related equipment

By determining development projects, creating functional tags, initializing source code warehouses and establishing associations between application frameworks and functional applications in the continuous integration delivery platform, the problem that traditional platforms cannot achieve full-process support and poor flexibility is solved, and the project requirements are achieved Effective delivery and rapid iteration.

CN119002976APending Publication Date: 2024-11-22JIALIAN PAYMENTS CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202410991787.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-23
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The traditional continuous integration delivery platform ignores the full process support in the integrated environment of production, research and operation in terms of integration and collaboration capabilities, and cannot achieve global connectivity. In the face of complex and changing project needs, the flexibility and scalability are poor. , cannot meet the needs of rapid iteration and flexible adjustment.

Method used

By determining the development project and creating function tags, initializing the source code warehouse, establishing the relationship between the application framework and the functional application, integrating the functional application into the application framework pipeline, automatically configuring the target application through the application framework pipeline, and realizing the target application Delivery online.

Benefits of technology

It realizes the global connection of source code warehouses, applications, pipelines and project requirements, meets complex and changeable project needs, improves flexibility and scalability, and supports rapid iteration and flexible adjustment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119002976A_ABST
    Figure CN119002976A_ABST
Patent Text Reader

Abstract

The invention discloses a collaborative project management continuous integration delivery method and related equipment, which can be used for connecting source code warehouses, applications, assembly lines and project requirements in series, realizing global connection, meeting the requirements of rapid iteration and flexible adjustment and improving the flexibility and expandability. The method comprises the steps that a development project is determined, and a function label is created according to the development project; determining a plurality of function applications according to the function labels; a source code warehouse is initialized, the source code warehouse comprises an application framework and an application framework assembly line, and the application framework assembly line is used for automatically deploying, configuring and testing functions of the application framework; establishing an association relationship between the application framework and the plurality of function applications, and integrating the plurality of function applications into the application framework assembly line; automatically configuring the application framework through the application framework assembly line to generate a target application; and integrating and delivering the target application online.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of software operation and maintenance technology, and in particular to a method and related equipment for collaborative project management continuous integration delivery. Background Art

[0002] In the field of software development and operation and maintenance, continuous integration and delivery have become a key practice to improve software development efficiency and quality. Although traditional continuous integration and delivery platforms, such as systems built on open source software such as Jenkins and Gitlab CI, have achieved automation of construction, testing and deployment to a certain extent, they still expose several obvious defects and shortcomings in actual applications.

[0003] In terms of integration and collaboration capabilities, traditional solutions mainly focus on automated processes, but ignore the need for full-process support in an integrated production, research and operation environment. Some existing products can only connect some nodes in the source code warehouse, application, assembly line, demand and other links, but cannot achieve global connectivity. In the face of complex and changing project requirements, traditional platforms cannot meet the needs of rapid iteration and flexible adjustment, and have poor flexibility and scalability. Summary of the invention

[0004] In order to solve the above technical problems, the present application provides a method and related equipment for collaborative project management continuous integration delivery.

[0005] The technical solution provided in this application is described below:

[0006] The first aspect of the present application provides a method for collaborative project management continuous integration delivery, the method comprising:

[0007] identifying development projects and creating functional labels based on said development projects;

[0008] Determine multiple functional applications according to the functional labels;

[0009] Initializing a source code repository, wherein the source code repository includes an application framework and an application framework pipeline, wherein the application framework pipeline is used to automatically deploy, configure, and test functions of the application framework;

[0010] Establishing an association relationship between the application framework and the plurality of functional applications, and integrating the plurality of functional applications into the application framework pipeline;

[0011] Automatically configuring the application framework through the application framework pipeline to generate a target application;

[0012] The target application is integrated and delivered online.

[0013] Optionally, before initializing the source code repository, the method further includes:

[0014] A source code repository is created by a self-service provider, wherein the source code repository contains technology stacks of various applications.

[0015] Optionally, automatically create application frameworks and application framework pipelines based on source code repositories and target templates, including:

[0016] Initializing the source code repository according to the technology stack and the original product template, the source code repository including an application framework and an application framework pipeline;

[0017] or,

[0018] The source code repository is initialized according to the technology stack and the cloud native resource template, and the source code repository includes an application framework and an application framework pipeline.

[0019] Optionally, multiple functional applications are determined according to the functional label, including:

[0020] Obtain key function fields of the function tag;

[0021] A plurality of the functional applications are determined according to the key functional field.

[0022] Optionally, multiple functional applications are integrated into the application framework pipeline, including:

[0023] Respectively obtaining application pipeline copies of a plurality of the functional applications;

[0024] Multiple application pipeline copies are automatically integrated into the application pipeline.

[0025] Optionally, after automatically configuring the application framework through the application framework pipeline to generate a target application, the method further includes:

[0026] Detect the development progress of the target application and upload the development progress in real time.

[0027] Optionally, the target application is integrated and delivered online, including:

[0028] Detecting whether the target application includes the function tag;

[0029] If yes, the target application is integrated and delivered online;

[0030] If not, continue to execute the step of automatically configuring the application framework through the application framework pipeline to generate the target application.

[0031] A second aspect of the present application provides a system for collaborative project management continuous integration delivery, the system comprising:

[0032] A first determining unit, configured to determine a development project and create a function tag according to the development project;

[0033] A second determining unit, configured to determine a plurality of functional applications according to the function labels;

[0034] An initialization unit, used to initialize a source code repository, wherein the source code repository includes an application framework and an application framework pipeline, wherein the application framework pipeline is used to automatically deploy, configure and test functions of the application framework;

[0035] An establishing unit, used to establish an association relationship between the application framework and the plurality of functional applications, and integrate the plurality of functional applications into the application framework pipeline;

[0036] An automatic configuration unit, configured to automatically configure the application framework through the application framework pipeline to generate a target application;

[0037] The delivery unit is used to deliver the target application integration online.

[0038] A third aspect of the present application provides a device for collaborative project management continuous integration delivery, the device comprising:

[0039] Processor, memory, input-output unit, and bus;

[0040] The processor is connected to the memory, the input and output unit, and the bus;

[0041] The memory stores a program, and the processor calls the program to execute the method as described in the first aspect and any one of the first aspects.

[0042] A fourth aspect of the present application provides a computer-readable storage medium, on which a program is stored. When the program is executed on a computer, the method described in the first aspect and any one of the first aspects is performed.

[0043] It can be seen from the above technical solutions that this application has the following advantages:

[0044] In the method of collaborative project management and continuous integration delivery of the present application, a development project is first determined, and a function label is created according to the development project. Then, multiple function applications are determined according to the function label, and then a source code repository is initialized. The initialized source code repository includes an application framework and an application framework pipeline. The application framework pipeline is a function for automatically deploying, configuring and testing the application framework; and an association relationship between the application framework and multiple function applications is established, and multiple function applications are integrated into the application framework pipeline; finally, after the application framework is automatically configured through the application framework pipeline to generate a target application, the target application is integrated and delivered online.

[0045] It can be further seen that this application can connect source code repositories, applications, pipelines and project requirements in series to achieve global connectivity. After determining the development project, function tags are created for the development requirements of the development project, and ultimately the delivery and launch process of the project requirements is realized. The application is implemented in the project, and when faced with complex and changing project requirements, it can also meet the needs of rapid iteration and flexible adjustment, thereby improving flexibility and scalability. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solution in the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0047] Figure 1 A schematic diagram of an embodiment of the method for collaborative project management and continuous integration delivery of the present application;

[0048] Figure 2 A schematic diagram of another embodiment of the method for collaborative project management and continuous integration delivery of the present application;

[0049] Figure 3 A schematic diagram of another embodiment of the method for collaborative project management and continuous integration delivery of the present application;

[0050] Figure 4 A schematic diagram of another embodiment of the method for collaborative project management and continuous integration delivery of the present application;

[0051] Figure 5 A schematic diagram of an embodiment of a system for collaborative project management and continuous integration delivery of this application;

[0052] Figure 6 A schematic diagram of an embodiment of an apparatus for collaborative project management continuous integration delivery of the present application. DETAILED DESCRIPTION

[0053] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0054] In the description of the present invention, "several" means one or more, "more" means more than two, "greater than", "less than", "exceed" etc. are understood as not including the number itself, and "above", "below", "within" etc. are understood as including the number itself. If there is a description of "first" or "second", it is only used for the purpose of distinguishing the technical features, and cannot be understood as indicating or implying the relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0055] In the description of the present invention, it should be understood that descriptions involving orientation, such as up, down, left, right, front, back, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.

[0056] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0057] In the description of the present invention, it should be noted that, unless otherwise clearly defined, terms such as setting, installing, connecting, etc. should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in the present invention in combination with the specific content of the technical solution. In addition, the identification of specific steps below does not represent a limitation on the order of steps and execution logic, and the execution order and execution logic between each step should be understood and inferred with reference to the contents described in the embodiment.

[0058] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, the present invention proposes a method and related equipment for collaborative project management continuous integration delivery.

[0059] See also Figure 1The present application provides an embodiment of a method for collaborative project management continuous integration delivery, the embodiment comprising:

[0060] Step S101, determining a development project, and creating a function tag according to the development project;

[0061] Step S102, determining multiple function applications according to the function labels;

[0062] Step S103: Initialize a source code repository, wherein the source code repository includes an application framework and an application framework pipeline, wherein the application framework pipeline is used to automatically deploy, configure, and test functions of the application framework;

[0063] Step S104: establishing an association relationship between the application framework and the plurality of functional applications, and integrating the plurality of functional applications into the application framework pipeline;

[0064] Step S105: automatically configuring the application framework through the application framework pipeline to generate a target application;

[0065] Step S106: Deliver the target application integration online.

[0066] The method of collaborative project management continuous integration delivery of the present invention first determines the development project. After the development project is determined, a function label is created according to the function to be implemented by the development project. The function label is created based on the function to be implemented. For example, if the function of calling a component is to be implemented, the function label is a "call" function label. Then, the function application is determined according to the function label. The determined function application can realize the "call" function. It should be noted that in a development project, there are many functions to be implemented, so there are many function labels to be created, and there are many function applications determined based on the association of the function labels. The number of function applications to be associated is not specifically limited in this application and can be set according to actual conditions.

[0067] After determining the functional application according to the functional label, initialize the source code repository. The source code repository contains the application framework and the corresponding application framework pipeline. The application framework pipeline corresponds to the application framework and can be used to automatically deploy, configure and test the functions of the application framework. Since there is only one basic function of an application in the application framework, it cannot meet the needs of the development project. Therefore, it is necessary to establish an association relationship between the determined functional application and the application framework. The purpose of this step is to establish an association relationship between the functions implemented in the functional application and the application framework, so as to facilitate the subsequent call of the functional application. After establishing the association relationship, the associated multiple functional applications are integrated into the application framework pipeline, and then the application framework is automatically configured and tested through the application framework pipeline to generate the target application. The generated target application contains the functions to be implemented by the development project. After the target application is tested and all the implemented functions can be implemented normally, the generated functional application can be delivered online.

[0068] Therefore, in the method of collaborative project management continuous integration delivery of the present invention, after proposing a development project, development requirements are proposed based on the development project at the same time, and the development requirements can be associated with the corresponding functional applications, and then the source code warehouse is initialized. The source code warehouse contains an application framework and a corresponding application framework pipeline, and then the association is performed. After debugging and deployment, the functions of the functional application can be integrated into the application framework to generate a target application. The present invention can connect the source code warehouse, application, pipeline and project requirements in series to achieve global connection. After determining the development project, a function label is created for the development requirements of the development project, and finally the delivery and launch process of the project requirements is realized, and the application is realized in the project. When facing complex and changeable project requirements, it can also meet the needs of rapid iteration and flexible adjustment, and improve flexibility and scalability.

[0069] In step S101, the goals, scope and expected results of the development project are first clarified, and preliminary project planning is carried out based on the above information, including determining the functions, critical paths and resource requirements of the project, and then evaluating the technology stack, tools and environment required to achieve the project requirements. In this process, the programming languages, frameworks, databases and servers required for the project are considered, and technical pre-research or prototype development is carried out.

[0070] After the development project is determined, the requirements are organized into detailed documents, including functional requirements, non-functional requirements, and user interface requirements. These documents contain graphical representations such as UML diagrams and flow charts, and define the conditions that the software must meet, including specific requirements for input, processing, output, and user interface.

[0071] Determining the functions to be implemented in a development project is the first step. Functional labels are created based on the functions to be implemented in the development project. In this process, clear and traceable demand basis is provided for the subsequent development stages of software design, coding, and testing, ensuring that the software product meets the established goals and requirements, laying a solid foundation for the subsequent development stages.

[0072] In step S102, the function label is first parsed to understand its meaning and context. In this process, the label library or dictionary can be accessed, which defines the meaning, synonyms and related labels of the label. The parsing process involves natural language processing (NLP) technology, because some function labels are provided in natural language form. According to the parsed function labels, the function application library is queried, and the function applications matching these labels are found using a matching algorithm. According to the results of the matching algorithm, the system presents the selected function applications to the user or the subsequent processing flow in a list or other form.

[0073] By automatically parsing function tags and querying the function application library, the system can quickly and accurately match the function applications required by users or projects. Developers do not need to manually search and filter function applications, thus saving time and energy and improving development efficiency.

[0074] In step S103, the source code repository is initialized: ensure that the source code repository, such as GitHub, GitLab, etc., has been set up in the source code repository and contains the basic code, libraries and frameworks required for the project. The repository should be properly configured so that the automation tool can access and pull the code.

[0075] Target template selection: Select a suitable application framework template based on project requirements and technology stack. The application framework template is a predefined code structure, a set of configuration files, or a complete project framework containing automation scripts and deployment instructions. There are application frameworks and application framework pipelines in the source code repository. Specifically:

[0076] Automatically create an application framework:

[0077] Code pulling: Automation tools (such as CI / CD pipelines and scripts) first pull the selected target template code from the source code repository.

[0078] Environment configuration: Based on the requirements of the template, the automated tool configures the development environment, including installing necessary dependencies and setting environment variables.

[0079] Template customization: Automation tools can customize templates according to the specific needs of the project, such as modifying configuration files or adding specific code snippets.

[0080] Create an application framework pipeline:

[0081] Pipeline definition: Define the automated pipelines for the development, testing, and deployment phases of the application framework. The created pipelines include multiple steps: code checking, unit testing, integration testing, building and packaging, deployment to the test environment, performance testing, and deployment to the production environment.

[0082] Tool integration: Integrate necessary tools and services into the pipeline, such as code repositories, continuous integration servers (such as Jenkins, GitLab CI / CD), automated testing frameworks (such as JUnit, Selenium), and deployment tools (such as Ansible, Docker, Kubernetes).

[0083] Configure the pipeline: Configure each step of the pipeline according to the specific needs of the project, including setting triggers such as code submission, scheduled tasks, specifying the execution environment, and configuring input and output parameters.

[0084] Automated testing: Automated testing is performed in the pipeline to ensure the quality and stability of the application framework. The tests may include unit testing, integration testing, and performance testing.

[0085] Deployment verification: Deploy the application framework to the test environment to verify its functionality and performance. Depending on the verification results, you may need to adjust the code or pipeline configuration.

[0086] Production deployment: After the test passes, the automation tool deploys the application framework to the production environment for users to call and use.

[0087] Through predefined application framework templates, project infrastructure can be quickly built, reducing the time and effort required to build a project from scratch. The introduction of automated pipelines enables automated execution of repetitive tasks such as code checking, testing, and deployment. By integrating automated testing into the pipeline, it is ensured that each code submission undergoes rigorous testing, thereby improving the quality and stability of the code.

[0088] In step S104, an association relationship between the application framework and multiple functional applications is established, and multiple functional applications are integrated into the application framework pipeline. First, a comprehensive demand analysis is performed on the goals, functional requirements, and functional applications to be integrated of the application framework. Based on the demand analysis results, an association relationship between the functional applications and the application framework is established through a configuration file or a database. The configuration file includes the startup parameters, operating environment settings, and permission control of the functional applications.

[0089] Furthermore, in step S103, a corresponding application framework pipeline has been designed according to the application framework, and the key steps of code submission, construction, testing and deployment are included in the application framework pipeline. Among them, since multiple functional applications need to be integrated into the application framework pipeline, corresponding automation scripts are needed in the pipeline to realize the automatic compilation, testing, packaging and deployment functions of the code. This part of the automation script can identify and process the functional applications associated with the application framework. In the integrated testing link in the pipeline, the integrated functional applications will be tested to ensure that the integrated functional applications can run in the application framework. The test may include unit testing, integration testing and performance testing. During the testing process, the running status of the application framework will be monitored in real time, including performance monitoring, anomaly detection and log management.

[0090] The application framework allows the flexible addition or removal of functional applications to meet changing business needs. At the same time, through standardized interfaces and configuration management, the functions of the application framework can be easily expanded, and the quality of the integrated functional applications can be ensured through the integration test link. At the same time, the monitoring system can detect and handle potential problems in a timely manner, further ensuring the stability and reliability of the application framework.

[0091] This embodiment establishes an association relationship between an application framework and multiple functional applications, and integrates multiple functional applications into an automated pipeline, thereby achieving automated integration and deployment of functional applications, improving flexibility and scalability, optimizing resource usage, and providing unified management.

[0092] In step S105, the application framework is automatically configured through the application framework pipeline to generate the target application. In step S104, multiple functional applications have been integrated into the application framework pipeline. The integrated functional applications are deployed to the application framework, and necessary configuration and optimization are performed. Among them, various automation tools and scripts are integrated in the application framework pipeline to perform configuration generation and build packaging tasks. There is a configuration template in the application framework, and the configuration template contains various configuration information required to generate the target application. The configuration template can be a static file (such as a configuration file in XML or JSON format) or a dynamically generated script or code snippet. The key information in the configuration template is parameterized so that it can be filled in according to actual needs when the pipeline is running. This part of the parameters includes database connection information, service port number, and third-party service API key.

[0093] When the application framework pipeline is running, a complete configuration file or configuration code is automatically generated based on the obtained configuration parameters and configuration templates. The build tool is used to build and package the generated configuration file and source code to generate a deployable target application. The built target application is automatically deployed to the specified environment. After the deployment is completed, a series of verification tests are automatically performed, such as functional testing, performance testing, and security testing, to ensure that the target application works as expected. The test results of the target application are fed back to relevant personnel through the pipeline so that problems can be discovered and repaired in a timely manner.

[0094] Multiple functional applications are integrated into the application framework pipeline, and the application framework is automatically configured through the application framework pipeline to generate a target application, so that the application framework can adapt to different configuration requirements and environmental changes. At the same time, the scalability of the application framework pipeline also supports the integration of more custom tasks and plug-ins. This embodiment realizes the automatic configuration of the application framework and the generation of the target application through the application framework pipeline, thereby improving the automation of software development.

[0095] See also Figure 2 The present application provides another embodiment of a method for collaborative project management continuous integration delivery, the embodiment comprising:

[0096] Step S201, determining a development project, and creating a function tag according to the development project;

[0097] Step S202, determining multiple function applications according to the function labels;

[0098] Step S203: self-create a source code repository, wherein the source code repository contains technology stacks of multiple applications.

[0099] Step S204: Initialize a source code repository according to the technology stack and the original product template, the source code repository including an application framework and an application framework pipeline, or initialize a source code repository according to the technology stack and the cloud native resource template, the source code repository including an application framework and an application framework pipeline, the application framework pipeline is used to automatically deploy, configure and test the functions of the application framework;

[0100] Step S205: establishing an association relationship between the application framework and the plurality of functional applications, and integrating the plurality of functional applications into the application framework pipeline;

[0101] Step S206: automatically configuring the application framework through the application framework pipeline to generate a target application;

[0102] Step S207, detecting the development progress of the target application, and uploading the development progress in real time. Step S208, integrating and delivering the target application online.

[0103] In step S203, a source code repository is created by self-service, and the source code repository includes a variety of application technology stacks. First, according to the needs of the development project, a suitable source code repository tool is selected, such as Git, SVN, etc. These tools can provide version control, branch management and code review functions. A new repository is created in the selected source code repository tool, and necessary repository parameters are set, such as repository name, description and access permissions.

[0104] Based on the project requirements and expected functionality, analyze and select a suitable technology stack, which includes programming languages, frameworks, libraries, and tools. Integrate the selected technology stack into the source code repository, which may involve adding specific frameworks or libraries as dependencies to the project, or configuring the project to use specific tools or environments. The source code repository can also be optimized regularly, such as cleaning up useless branches, merging duplicate code, and optimizing dependency management.

[0105] By integrating the technology stacks of multiple applications into the source code repository, it is convenient for developers to use and manage these technology stacks, improving development efficiency and quality. By configuring the CI / CD pipeline, the project's automated construction, testing, and deployment are realized, improving development speed and project stability.

[0106] By self-creating source code repositories and including technology stacks for multiple applications, efficient source code management, technology stack integration and dependency management, continuous integration and deployment, and warehouse optimization and maintenance functions are achieved, providing strong support and guarantee for software development projects.

[0107] In step S204, the source code repository is initialized according to the technology stack and the original product template or the source code repository is initialized according to the technology stack and the cloud-native resource template. The source code repository contains the application framework and the application framework pipeline. The entire initialization process relies on the predefined technology stack, original product template or cloud-native resource template, as well as automated tools and processes.

[0108] Specifically, according to the needs of the development project, analyze and select the appropriate technology stack, including programming languages, frameworks, middleware, and databases. Use these technology stacks in conjunction with original product templates or cloud-native resource templates to initialize the source code repository, which includes the application framework and application framework pipeline.

[0109] The original product template or cloud-native resource template usually includes the infrastructure configuration, code structure and dependencies required to build the application framework. After selecting the technology stack and the corresponding template, use CI / CD (continuous integration / continuous deployment) tools, automation scripts, containerization technology and orchestration tools to automatically initialize the source code repository. In the initialized source code repository, the application framework and application framework pipeline will be automatically created and generated.

[0110] Creation of application framework:

[0111] Infrastructure configuration: Automatically configure the computing resources, storage resources, and network resources required by the application framework based on the infrastructure configuration information in the template.

[0112] Code structure generation: Generate the basic code structure of the application framework based on the code structure information in the template, including directory structure, file naming conventions and initial code.

[0113] Dependency management: Automatically parse dependency information in templates, install and configure third-party libraries, frameworks, and services required by the application framework.

[0114] Creation of application framework pipeline:

[0115] Pipeline definition: Based on the project's deployment requirements and release process, define the application framework pipeline, including the build phase, test phase, and deployment phase.

[0116] Automated task configuration: Configure automated tasks for each stage, such as code compilation, unit test execution, integration test execution, deployment package packaging, and deployment execution. These tasks will be automatically triggered and executed according to the definition of the pipeline.

[0117] Monitoring and feedback: Configure monitoring and feedback mechanisms to monitor the execution of the pipeline in real time and notify relevant personnel in a timely manner when problems arise. At the same time, collect the execution data of the pipeline to provide a basis for subsequent optimization and improvement.

[0118] By automating the creation of application frameworks and application framework pipelines, the efficiency and quality of software development and operation and maintenance can be significantly improved, providing strong support for business development.

[0119] In step S207, the development progress of the target application will be notified in real time by configuring the CR / MR robot notification, and the development progress will be uploaded in real time to save the development progress of the target application and the information generated during the development process. If other problems are encountered during the development process, the information in the development process can be traced back from the saved information and used as the basis for query.

[0120] In step 208, before the target application is integrated and delivered online, it is first detected whether the target application contains the functional tag. This process is to detect whether the developed target application can be used in the development project and whether it matches the requirements of the development project. If it is determined that the target application matches the requirements of the development project, the target application is integrated and delivered online. If it is determined that the target application does not match the requirements of the development project, the application framework will continue to be automatically configured through the application framework pipeline to generate the target application until the functions of the target application meet the requirements of the development project.

[0121] See also Figure 3 According to some embodiments of the present invention, determining the multiple functional applications according to the functional labels in S102 may specifically include, but is not limited to, the following:

[0122] Step S301, obtaining the key function field of the function tag;

[0123] Step S302: Determine a plurality of functional applications according to the key function field.

[0124] In step S301, the terminal will conduct an in-depth analysis of the given function tag to identify and extract the key function fields therein. These key function fields are important information that describes the core characteristics of the function tag, including function name, function type, function description, and input and output parameters. Valuable information is extracted from the function tag to provide basic data for subsequent steps.

[0125] In step S302, the terminal uses the key function fields extracted in step S301 to match and find applications with these key functions. This process involves searching and querying one or more application databases or application repositories. By comparing the key function fields with the functional description of the application, the terminal can identify functional applications that meet the requirements.

[0126] In summary, the two processes of step S301 and step S302 together constitute a mapping and determination process from function labels to function applications, which provide strong technical support for software development, system integration or function expansion scenarios by extracting key information, matching applications and providing decision support methods.

[0127] See also Figure 4 According to some embodiments of the present invention, integrating multiple functional applications into the application framework pipeline in S104 may specifically include, but is not limited to, the following:

[0128] Step S401, respectively obtaining application pipeline copies of a plurality of the functional applications;

[0129] Step S402: Automatically integrate multiple application pipeline copies into the application pipeline.

[0130] In step S401, the terminal will obtain the corresponding application pipeline copy for each determined functional application. Application pipeline usually refers to a series of automated processing processes, including code compilation, construction, testing and deployment, which are used to support continuous integration and continuous deployment (CI / CD) of software applications. Obtaining an application pipeline copy is to copy or clone the configuration and definition of the automated processing process for subsequent integration.

[0131] In step S402, the terminal will automatically integrate the multiple application pipeline copies obtained in step S401 into the application pipeline. This process involves merging, adjusting and optimizing the configurations, tasks, and dependencies in each copy to ensure that they can work together in a unified application pipeline to achieve an overall automated processing flow.

[0132] In summary, the two processes of step S401 and step S402 together constitute the automatic integration process of the application pipeline, which provides powerful automation support for software development and deployment by replicating configurations, integrating processes, improving efficiency and quality assurance.

[0133] See also Figure 5 The present application also provides a system for collaborative project management and continuous integration delivery, the system comprising:

[0134] A first determining unit 501 is used to determine a development project and create a function tag according to the development project;

[0135] A second determining unit 502, configured to determine a plurality of function applications according to the function label;

[0136] An initialization unit 503 is used to initialize a source code repository, wherein the source code repository includes an application framework and an application framework pipeline, wherein the application framework pipeline is used to automatically deploy, configure and test functions of the application framework;

[0137] An establishing unit 504, configured to establish an association relationship between the application framework and the plurality of functional applications, and integrate the plurality of functional applications into the application framework pipeline;

[0138] An automatic configuration unit 505, configured to automatically configure the application framework through the application framework pipeline to generate a target application;

[0139] The delivery unit 506 is used to deliver the target application integration online.

[0140] Optionally, the system further includes: a creating unit 507, wherein the creating unit 507 is specifically configured to:

[0141] A source code repository is created by a self-service provider, wherein the source code repository contains technology stacks of various applications.

[0142] Optionally, the initialization unit 503 is specifically used for:

[0143] Initializing the source code repository according to the technology stack and the original product template, the source code repository including an application framework and an application framework pipeline;

[0144] or,

[0145] The source code repository is initialized according to the technology stack and the cloud native resource template, and the source code repository includes an application framework and an application framework pipeline.

[0146] Optionally, the second determining unit 502 is specifically configured to:

[0147] Obtain key function fields of the function tag;

[0148] A plurality of the functional applications are determined according to the key functional field.

[0149] Optionally, the establishing unit 504 is specifically configured to:

[0150] Respectively obtaining application pipeline copies of a plurality of the functional applications;

[0151] Multiple application pipeline copies are automatically integrated into the application pipeline.

[0152] Optionally, the system further includes: a detection unit 508, wherein the detection unit 508 is specifically configured to:

[0153] Detect the development progress of the target application and upload the development progress in real time.

[0154] Optionally, the delivery unit 506 is specifically configured to:

[0155] Detecting whether the target application includes the function tag;

[0156] If yes, the target application is integrated and delivered online;

[0157] If not, the automatic configuration unit 505 continues to be executed.

[0158] See also Figure 6 , the present application also provides a collaborative project management continuous integration delivery device, including:

[0159] Processor 601, memory 602, input and output unit 603, bus 604;

[0160] The processor 601 is connected to the memory 602, the input and output unit 603 and the bus 604;

[0161] The memory 602 stores a program, and the processor 601 calls the program to execute any of the above methods.

[0162] The present application also relates to a computer-readable storage medium on which a program is stored, wherein when the program is run on a computer, the computer is caused to execute any of the above methods.

[0163] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0164] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0165] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0166] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0167] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A method for collaborative project management and continuous integration delivery, characterized in that: The method comprises: identifying development projects and creating functional labels based on said development projects; Determine multiple functional applications according to the functional labels; Initializing a source code repository, wherein the source code repository includes an application framework and an application framework pipeline, wherein the application framework pipeline is used to automatically deploy, configure, and test functions of the application framework; Establishing an association relationship between the application framework and the plurality of functional applications, and integrating the plurality of functional applications into the application framework pipeline; Automatically configuring the application framework through the application framework pipeline to generate a target application; The target application is integrated and delivered online.

2. The method for collaborative project management and continuous integration delivery according to claim 1, characterized in that: Before initializing the source code repository, the method further includes: A source code repository is created by a self-service provider, wherein the source code repository contains technology stacks of various applications.

3. The method for collaborative project management and continuous integration delivery according to claim 2, characterized in that: Initialize a source code repository, the source code repository including the application framework and the application framework pipeline including: Initializing the source code repository according to the technology stack and the original product template, the source code repository including an application framework and an application framework pipeline; or, The source code repository is initialized according to the technology stack and the cloud native resource template, and the source code repository includes an application framework and an application framework pipeline.

4. The method for collaborative project management and continuous integration delivery according to claim 1, characterized in that: Determine multiple functional applications according to the functional label, including: Obtain key function fields of the function tag; A plurality of functional applications are determined according to the key function field.

5. The method for collaborative project management and continuous integration delivery according to claim 1, characterized in that: Integrate multiple functional applications into the application framework pipeline, including: Respectively obtaining application pipeline copies of a plurality of the functional applications; Multiple application pipeline copies are automatically integrated into the application pipeline.

6. The method for collaborative project management and continuous integration delivery according to claim 2, characterized in that: After automatically configuring the application framework through the application framework pipeline to generate the target application, the method further includes: Detect the development progress of the target application and upload the development progress in real time.

7. The method for collaborative project management and continuous integration delivery according to claim 6, characterized in that: Deliver the target application integration to the online platform, including: Detecting whether the target application includes the function tag; If yes, the target application is integrated and delivered online; If not, continue to execute the step of automatically configuring the application framework through the application framework pipeline to generate the target application.

8. A collaborative project management and continuous integration delivery system, characterized in that: The system comprises: A first determining unit, configured to determine a development project and create a function tag according to the development project; A second determining unit, configured to determine a plurality of functional applications according to the function labels; An initialization unit, used to initialize a source code repository, wherein the source code repository includes an application framework and an application framework pipeline, wherein the application framework pipeline is used to automatically deploy, configure and test functions of the application framework; An establishing unit, used to establish an association relationship between the application framework and the plurality of functional applications, and integrate the plurality of functional applications into the application framework pipeline; An automatic configuration unit, configured to automatically configure the application framework through the application framework pipeline to generate a target application; The delivery unit is used to deliver the target application integration online.

9. A collaborative project management and continuous integration delivery device, characterized in that: The device comprises: Processor, memory, input-output unit, and bus; The processor is connected to the memory, the input and output unit, and the bus; The memory stores a program, and the processor calls the program to execute the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a program stored thereon, wherein the program, when executed on a computer, performs the method according to any one of claims 1 to 7.

Citation Information

Cited By

  • Assembly line flow adaptive configuration method and system

    CN121143859A