Intangible asset whole life cycle automatic management method and system

Abstract

This invention provides an automated management method and system for the entire lifecycle of intangible assets, relating to the field of enterprise digital asset management technology. It involves acquiring a spreadsheet configuration file, wherein the spreadsheet configuration file includes management task information corresponding to multiple projects, including configuration library management information, baseline management information, integration management information, and archive management information; parsing the spreadsheet configuration file to extract the management task information corresponding to each of the multiple projects; and using an automated execution tool on a host computer to perform configuration library establishment, baseline establishment, integration construction tasks, and archive operations for each of the multiple projects, and automatically sending notifications. This addresses the problem of low management efficiency and high error rate caused by reliance on manual labor in the full lifecycle management of intangible assets.

Description

Technical Field

[0001] This application relates to the fields of enterprise digital asset management and software development engineering technology, and in particular to an automated management method and system for the entire lifecycle of intangible assets. Background Technology

[0002] As enterprises deepen their digital transformation, the number of software development projects is exploding, with a single company often initiating hundreds of projects a year. Each project generates a large number of intangible assets, including but not limited to source code, executable programs, requirements documents, design documents, test cases, configuration files, and installation and deployment packages. These intangible assets have significant value in the company's production and operation and require strict full lifecycle management, covering multiple management stages such as project configuration library establishment, baseline establishment, integration and construction, archiving, and notification.

[0003] Currently, the industry primarily relies on multiple heterogeneous management platforms, such as source code configuration management platforms, continuous integration platforms, and deliverable management platforms, for the full lifecycle management of intangible assets. Administrators manually log into each platform and sequentially execute various management operations, including configuration repository creation, baseline establishment, integration build, and archiving notifications. For example, after project initiation, the administrator needs to log into the source code configuration management platform, manually create project configuration repositories, and configure repository permissions and project descriptions. Before project integration, the administrator needs to manually establish baselines in each project configuration repository to identify stable, releasable versions. During project integration, the administrator needs to log into the continuous integration platform, manually select integration tasks, fill in build parameters, and trigger the build. After the build is complete, the administrator also needs to manually obtain the deliverable download link from the deliverable management platform. Finally, the administrator manually sends the deliverable link to relevant personnel via email and logs into the deliverable platform to manually complete project archiving.

[0004] However, in the existing technology, the full life cycle management of intangible assets relies on manual execution of various management operations on multiple heterogeneous management platforms. There is a lack of a unified automated management mechanism across platforms and the entire process, resulting in low management efficiency and a high error rate. Summary of the Invention

[0005] This application provides an automated management method and system for the entire lifecycle of intangible assets, in order to solve the problems of low management efficiency and high error rate caused by the reliance on manual management of the entire lifecycle of intangible assets.

[0006] The first aspect of this application provides a method for automated management of the entire lifecycle of intangible assets, the method comprising: Obtain the spreadsheet configuration file; wherein, the spreadsheet configuration file includes management task information corresponding to multiple projects, and the management task information includes configuration library management information, baseline management information, integration management information and archive management information; Parse the spreadsheet configuration file to extract the management task information corresponding to each of the multiple projects; Using an automated execution tool on a host computer, perform the following operations for each of the multiple projects, based on the management task information corresponding to that project: Based on the configuration library management information, the configuration library management function of the first management platform is invoked to establish a configuration library for the project; Based on the baseline management information, the baseline management function of the first management platform is invoked to establish a baseline for the project; Based on the integrated management information, the integration build function of the second management platform is invoked to trigger the integration build task of the project; Based on the archive management information, the archive function of the second management platform is invoked to perform the archive operation for this project and a notification is automatically sent.

[0007] By acquiring spreadsheet configuration files containing management task information for multiple projects, parsing and extracting the management task information for each project, and then using an automated execution tool on a host computer to perform operations such as configuration library establishment, baseline establishment, integration construction, and archiving notifications based on the management task information, management operations scattered across multiple heterogeneous management platforms can be unified and orchestrated into an automated process. This significantly improves the efficiency of intangible asset lifecycle management and effectively reduces the error rate caused by manual operations.

[0008] Optionally, the configuration library management information includes a repository name, repository administrator information, and project description information; the step of calling the configuration library management function of the first management platform to create a configuration library for the project based on the configuration library management information includes: logging into the first management platform; creating a new repository in the first management platform based on the repository name; configuring administrator permissions for the new repository based on the repository administrator information; and filling in the project description of the new repository based on the project description information.

[0009] By refining configuration repository management information into repository name, repository administrator information, and project description information, and sequentially performing operations such as login, creating a new repository, configuring permissions, and filling in descriptions, configuration repositories can be automatically created in batches. This avoids the tedious process of manually logging into the platform one by one, thereby improving the efficiency and accuracy of configuration repository creation.

[0010] Optionally, the baseline management information includes a configuration repository identifier, a baseline version identifier, and a commit identifier; the step of calling the baseline management function of the first management platform to establish a baseline for the project based on the baseline management information includes: logging into the first management platform; searching for the corresponding configuration repository based on the configuration repository identifier; entering the baseline configuration interface of the configuration repository; and establishing the baseline corresponding to the baseline version identifier based on the commit identifier and using the code commit version corresponding to the commit identifier as a benchmark.

[0011] By refining baseline management information into configuration repository identifier, baseline version identifier, and commit identifier, and establishing baselines based on the code commit version corresponding to the commit identifier, it is possible to automatically establish baselines based on specific code versions, avoiding manual operation of entering the configuration repository one by one, thereby improving the efficiency of baseline establishment and the accuracy of version traceability.

[0012] Optionally, the integration management information includes an integration task identifier, integration task parameters, and deliverable path information; the step of invoking the integration build function of the second management platform based on the integration management information to trigger the integration build task of the project includes: logging into the second management platform; searching for the corresponding integration task based on the integration task identifier; filling in the build parameters of the integration task based on the integration task parameters; triggering the build execution of the integration task; and after the integration task is built, obtaining the download address of the deliverable corresponding to the deliverable path information from the deliverable management platform.

[0013] By refining the integration management information into integration task identifiers, integration task parameters, and deliverable path information, and sequentially executing operations such as logging in, searching for integration tasks, filling in build parameters, triggering the build, and obtaining the deliverable download address, the entire process of integration build tasks can be automated, avoiding multiple manual operations across platforms, thereby improving the efficiency of integration builds and the accuracy of deliverable acquisition.

[0014] Optionally, the automatic notification sending includes: automatically generating a notification email, the body of which includes integration result information indicating the completion of the integration task and the download address of the deliverable; and sending the notification email to a preset recipient.

[0015] By automatically generating notification emails containing integration result information and deliverable download links and sending them to preset recipients, a closed-loop notification of integration build results can be achieved, avoiding the need for manually writing emails and copying deliverable links, thereby improving the efficiency and completeness of notifications.

[0016] Optionally, the archive management information includes an archive task identifier and archive task parameters; the step of automatically invoking the archive function of the second management platform and performing the archive operation of the project based on the archive management information includes: automatically logging into the second management platform; searching for the corresponding archive task based on the archive task identifier; filling in the execution parameters of the archive task based on the archive task parameters; and triggering the construction and execution of the archive task.

[0017] By refining archive management information into archive task identifiers and archive task parameters, and sequentially executing operations such as logging in, searching for archive tasks, filling in execution parameters, and triggering build execution, project archiving can be automated, avoiding manual login to the platform and manual execution of archiving operations one by one, thereby improving the efficiency and standardization of archiving operations.

[0018] Optionally, the method further includes: after parsing the spreadsheet configuration file, performing field integrity verification and / or field validity verification on the extracted management task information; if the verification fails, an error message is output and the operation on the corresponding item of the management task information is suspended.

[0019] By performing field integrity and / or field validity checks on the management task information after parsing the spreadsheet configuration file, configuration errors can be detected before execution, avoiding execution anomalies caused by incomplete or invalid configuration information, thereby improving the system's fault tolerance and operational reliability.

[0020] Optionally, the method further includes: recording execution log information during the process of the host computer automated execution tool performing the operation on each project; and generating an execution result report after completing the operation of all projects, the execution result report including the number of projects that were successfully executed and / or the number of projects that failed and the corresponding reasons for failure.

[0021] By recording execution log information during the execution process and generating an execution result report upon completion, it is possible to achieve comprehensive recording of the operation process and summary of results, which facilitates subsequent auditing and version traceability, thereby improving the traceability and standardization of intangible asset management.

[0022] Optionally, the spreadsheet configuration file is an Excel file; the host computer automation execution tool simulates user operations through a browser automation framework to automatically invoke the management functions of the first management platform and the second management platform.

[0023] By using Excel files as the configuration data source and leveraging a browser automation framework to simulate user operations and invoke management functions of various management platforms, cross-platform automation can be achieved in a non-intrusive manner without modifying the original interfaces of each management platform, thereby improving system compatibility and scalability.

[0024] The second aspect of this application provides an automated management system for the entire lifecycle of intangible assets, applicable to the automated management method for the entire lifecycle of intangible assets described in the first aspect, comprising: The configuration parsing module is configured to: obtain a spreadsheet configuration file; wherein, the spreadsheet configuration file includes management task information corresponding to multiple projects, and the management task information includes configuration library management information, baseline management information, integration management information, and archive management information; parse the spreadsheet configuration file to extract the management task information corresponding to the multiple projects; The automated execution module is configured to perform the following operations for each of the multiple projects, based on the management task information corresponding to that project: Based on the configuration library management information, invoke the configuration library management function of the first management platform to establish a configuration library for that project; based on the baseline management information, invoke the baseline management function of the first management platform to establish a baseline for that project; based on the integration management information, invoke the integration build function of the second management platform to trigger the integration build task for that project; and based on the archive management information, invoke the archive function of the second management platform to perform the archive operation for that project. The notification module is configured to automatically send a notification after the archiving operation is completed.

[0025] By acquiring and parsing spreadsheet configuration files through the configuration parsing module, the automated execution module performs configuration library establishment, baseline establishment, integration construction and archiving operations based on management task information, and the notification module automatically sends notifications after the archiving operation is completed. This can unify management operations scattered across multiple heterogeneous management platforms into automated processes, thereby significantly improving the efficiency of intangible asset lifecycle management and effectively reducing the error rate caused by manual operations.

[0026] As can be seen from the above technical solutions, this application provides an automated management method and system for the entire lifecycle of intangible assets. The method includes: obtaining a spreadsheet configuration file; parsing the spreadsheet configuration file to extract management task information corresponding to each of multiple projects; and using an automated execution tool on a host computer to perform configuration library establishment, baseline establishment, integration construction tasks, and archiving operations for each project, and automatically sending notifications, so as to solve the problem of low management efficiency and high error rate caused by the reliance on manual labor in the lifecycle management of intangible assets. Attached Figure Description

[0027] To more clearly illustrate the technical solution of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 A flowchart illustrating the automated management method for the entire lifecycle of intangible assets provided in this application embodiment; Figure 2 A schematic diagram of the automatic batch configuration library creation tool and configuration files provided in the embodiments of this application; Figure 3 A schematic diagram of the automatic batch creation tool and configuration file provided in this application embodiment; Figure 4 A schematic diagram of the automatic project integration tool and configuration file provided in the embodiments of this application; Figure 5 A schematic diagram of the automatic project archiving tool and configuration file provided in the embodiments of this application. Detailed Implementation

[0029] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application.

[0030] It should be understood that, in this application, intangible assets specifically refer to digital R&D deliverables generated during the software development process, including but not limited to source code, executable programs, requirements documents, design documents, test cases, configuration files, and installation / deployment packages. Although these assets have no physical form, they possess significant commercial value and require standardized management throughout their entire lifecycle.

[0031] A spreadsheet configuration file is a task configuration data file stored in a structured spreadsheet format (such as an Excel file with the extension .xlsx or .xls). This file acts as the data source for the entire automation system, recording management task information for each project row by row and defining various task parameter fields column by column, enabling a data-driven model of one-time configuration and batch execution. In one example, the file uses a multi-sheet structure: Sheet1 corresponds to configuration library management information, Sheet2 to baseline management information, Sheet3 to integration management information, and Sheet4 to archive management information. The first row of each sheet defines the header row.

[0032] A host computer automation execution tool refers to an automated software program running on the administrator's computer (host computer) to replace manual operations on various heterogeneous management platforms. In one example, the host computer automation execution tool is written in Python and uses browser automation frameworks such as Selenium to simulate user behavior in a browser, enabling automatic login, automatic parameter filling, and automatic clicking on web platforms, thus completing various management tasks without human intervention.

[0033] The primary management platform refers to a configuration repository management platform used for source code version control, such as GitLab and SVN. The primary management platform provides functions such as configuration repository (repository) creation, permission management, and baseline (Tag / Branch) management.

[0034] The second management platform refers to a continuous integration and delivery management platform used for project integration and archiving, such as Jenkins or GitLab CI. The second management platform provides functions such as CI task triggering, build parameter input, deliverable management, and archiving operations.

[0035] To address the issues of low management efficiency and high error rates resulting from reliance on manual labor in the full lifecycle management of intangible assets, see [reference needed]. Figure 1 This application provides a method for automated management of the entire lifecycle of intangible assets, comprising the following embodiments: S10: Get the spreadsheet configuration file.

[0036] The spreadsheet configuration file includes management task information for each of the multiple projects. This management task information includes configuration library management information, baseline management information, integration management information, and archive management information.

[0037] It should be understood that the spreadsheet configuration file serves as the unified data entry point for this application's automated management solution. When using this solution, administrators only need to fill in the information of the multiple projects to be processed into the corresponding worksheets in the spreadsheet configuration file. Without modifying any code, they can start fully automated management, achieving one-time configuration and batch execution.

[0038] Configuration library management information refers to all the parameter information required to establish a project configuration library, including: the library name, which is used to uniquely identify the configuration library in the first management platform; the library administrator information, which is used to configure an account with management permissions for the library; and the project description information, which is used to fill in the project description for the library, so as to facilitate subsequent retrieval and management.

[0039] In some embodiments, the warehouse administrator information field supports multiple administrator accounts, separated by semicolons or commas.

[0040] Baseline management information refers to all the parameter information required to establish a project baseline, including: configuration repository identifier (used to uniquely locate the target configuration repository, usually a repository path, such as namespace / repository name), baseline version identifier (used to mark the version name of this baseline, such as v1.0.0), and commit identifier (i.e., Commit ID, used to specify which code commit is used as the base version of the baseline).

[0041] Integration management information refers to all the parameter information required to trigger project integration build, including: integration task identifier (used to uniquely identify the target CI task in the second management platform, such as the job name in Jenkins), integration task parameters (used to fill in the build parameters of the CI task, such as version number, branch name, build type, etc.), and deliverable path information (used to obtain the storage path of the corresponding deliverable from the deliverable management platform after integration is completed).

[0042] Archive management information refers to all the parameter information required to perform project archive operations, including: archive task identifier (used to uniquely identify the target archive CI task in the second management platform) and archive task parameters (used to fill in the execution parameters of the archive task, such as archive path, version description, etc.).

[0043] S20: Parse the spreadsheet configuration file to extract the management task information corresponding to each of the multiple projects.

[0044] It should be understood that the parsing process is handled by the host computer's automated execution tool. In one example, the host computer's automated execution tool uses Python's openpyxl or pandas library to read the Excel file, parses the data records in each worksheet line by line, converts each row of data into a structured task object, extracts various field information, and provides structured input data for subsequent automated operations.

[0045] In some embodiments, after parsing the spreadsheet configuration file, the extracted management task information is subjected to field integrity verification and / or field validity verification; if the verification fails, an error message is output and the operation on the corresponding item of the management task information is suspended.

[0046] Specifically, field integrity verification checks whether all required fields are filled in, disallowing critical fields (such as repository name, integration task identifier, etc.) from being empty; field validity verification checks whether field values ​​conform to preset rules, such as: repository names must not contain special characters, commit identifiers must be in valid Git Commit ID format (40-digit hexadecimal string), and email addresses must conform to standard formats. If a record fails verification, the system will output a clear error message (including the line number and error reason) and skip that record to continue processing the next one, thus avoiding the interruption of the entire batch of operations due to a single error.

[0047] S30: Through the host computer automated execution tool, perform the following operations for each of multiple projects, based on the management task information corresponding to the project.

[0048] It should be understood that the automated execution tool on the host computer traverses and parses all project records. For each project, it automatically calls the corresponding functions of each management platform in sequence, following the order of configuration library creation → baseline creation → integration build → archive notification, to achieve a fully sequential execution process. There are logical dependencies between each step: the configuration library is the carrier of the baseline, the baseline is the benchmark for integration, and the integration result is the content of the archive.

[0049] S31: Based on the configuration library management information, call the configuration library management function of the first management platform to create a configuration library for the project.

[0050] It should be understood that a configuration repository refers to a structured storage space used to store and manage project source code, version information, and other R&D assets. Establishing a configuration repository in the first management platform means creating a dedicated code repository for the project, allowing project members to perform operations such as code submission, branch management, and version control within that repository.

[0051] In some embodiments, the configuration repository management information includes the repository name, repository administrator information, and project description information; based on the configuration repository management information, the configuration repository management function of the first management platform is invoked to create a configuration repository for the project, including: Step S311: Log in to the first management platform.

[0052] It should be understood that the host computer automation tool launches a web browser through a browser automation framework such as Selenium WebDriver, automatically navigates to the login page of the primary management platform, and enters the pre-configured administrator username and password to complete the automatic login. In one example, if the primary management platform is GitLab, the tool will automatically open the GitLab login URL, enter the account information in the username and password input boxes, click the login button, and wait for the page to load before confirming successful login.

[0053] Step S312: Create a new warehouse in the first management platform based on the warehouse name.

[0054] It should be understood that the tool reads the warehouse name field from the current record row of the spreadsheet configuration file, automatically fills in the warehouse name on the new warehouse page of the first management platform, and performs a confirmation operation to complete the warehouse creation. In some embodiments, the tool can also simultaneously set attributes such as the warehouse's visibility (public / private), which can be configured through extended fields in the spreadsheet configuration file.

[0055] Step S313: Configure administrator permissions for the newly created warehouse based on the warehouse administrator information.

[0056] It should be understood that the tool reads the warehouse administrator information field from the spreadsheet configuration file, searches for and adds the corresponding administrator account on the member management page of the newly created warehouse, and sets its permission level to maintainer or owner to ensure that the administrator has full operational permissions for the warehouse. In some embodiments, when the warehouse administrator information field contains multiple accounts, the tool will perform the add operation in a loop, configuring permissions for each account one by one.

[0057] Step S314: Based on the project description information, fill in the project description for the new warehouse.

[0058] It should be understood that the tool reads the project description information field from the spreadsheet configuration file, automatically fills in the description content in the project description input box on the repository settings page, and saves the settings. The project description information usually includes descriptive content such as the business project name corresponding to the repository, the responsible team, and the applicable version, which facilitates subsequent asset retrieval and management.

[0059] In some embodiments, after completing steps S311 to S314 above, the tool will continue to read the next configuration library management record in the spreadsheet configuration file, repeat steps S311 to S314 until all configuration library management information records are processed, and output a batch library creation result log, recording the creation status of each library (success / failure and the reason for failure).

[0060] See Figure 2From an underlying implementation perspective, the aforementioned automated batch configuration repository creation function is implemented by an automated batch configuration repository creation tool. This tool is a Python-based host computer software that uses the Selenium browser automation framework to simulate all administrator operations on the web interface of the source code configuration management platform (the first management platform). These operations include: automatically logging into the configuration repository platform, automatically creating repositories, automatically configuring repository administrator permissions, and automatically filling in project descriptions. After reading the repository creation information Excel configuration table, the tool iterates through each repository creation record and executes the commands sequentially. Upon completion, it outputs a batch repository creation result log, fully recording the operation status of each repository for easy administrator verification and auditing.

[0061] S32: Based on the baseline management information, invoke the baseline management function of the first management platform to establish a baseline for the project, specifically including the following steps: Step S321: Log in to the first management platform.

[0062] Step S322: Search for the corresponding configuration repository based on the configuration repository identifier.

[0063] It should be understood that a configuration repository identifier is an identifier that can uniquely locate the target configuration repository within the primary management platform. It is typically a repository name or repository path (namespace / repository name). The tool navigates to the target configuration repository's main page by invoking the primary management platform's search function or by directly concatenating the URL path. In one example, if the repository identifier is projectA / backend, the tool will automatically navigate to the corresponding repository page in GitLab.

[0064] Step S323: Enter the baseline configuration interface of the configuration library.

[0065] It should be understood that the baseline configuration interface is the page in the primary management platform used to create and manage baselines (tags). In one example, in GitLab, a baseline corresponds to the tag function. The tool will automatically navigate to the Repository > Tags page of the repository, and clicking the New Tag button will take you to the baseline creation page.

[0066] Step S324: Based on the commit identifier, establish a baseline corresponding to the baseline version identifier, using the code commit version corresponding to the commit identifier as the benchmark.

[0067] It should be understood that a commit ID is a hash value (usually a 40-digit hexadecimal string, but in practice, the first 7 digits of a shorter hash can also be used) used to uniquely identify a code commit in the Git version control system. On the baseline creation page, enter the baseline version identifier (e.g., v2.0.0) in the Tag name input box and the commit ID in the Create from input box, then click the confirm button to complete the baseline creation. Using the commit ID as the baseline benchmark accurately identifies the code version corresponding to that baseline, ensuring version traceability.

[0068] In some embodiments, after the baseline of a project is established, the tool will continue to read the next baseline management record and repeat the above steps until all baseline management information records are processed and a batch baseline establishment result log is output, recording the creation status of each baseline.

[0069] See Figure 3 From an underlying implementation perspective, the aforementioned automated batch creation of baselines is handled by an automated batch project baseline creation tool. This tool is a Python-based host computer software that uses the Selenium browser automation framework to simulate administrator operations on the source code configuration management platform's web interface. It achieves the following: automatic login to the configuration repository platform, automatic search for the configuration repository where baselines need to be created, automatic access to the baseline configuration interface, and automatic creation of baselines based on the submission ID. After reading the baseline information Excel configuration table, the automated batch project baseline creation tool module iterates through each baseline record and executes the commands sequentially, thus achieving automated batch creation of project baselines.

[0070] S33: Based on the integration management information, invoke the integration build function of the second management platform to trigger the integration build task of this project, specifically including the following steps: Step S331: Log in to the second management platform.

[0071] It should be understood that the tool launches a web browser through a browser automation framework, automatically navigates to the login page of a second management platform (such as the Jenkins platform), fills in the pre-configured administrator account and password, and completes the automatic login.

[0072] Step S332: Search for the corresponding integration task based on the integration task identifier.

[0073] It should be understood that an integration task identifier refers to the name or number used to uniquely identify a target CI (Continuous Integration) task in the second management platform. In one example, in the Jenkins platform, an integration task corresponds to a Job. The tool will search for a Job that matches the integration task identifier in the Jenkins task list page, or directly navigate to the details page of the target Job via URL concatenation.

[0074] Step S333: Based on the integration task parameters, fill in the construction parameters of the integration task.

[0075] It should be understood that integration task parameters refer to the build parameters required when triggering a CI task, typically including the target branch name, version number, build type (Debug / Release), and target environment. The tool uses the Buildwith Parameters page of the integration task to input the corresponding parameter values ​​from the spreadsheet configuration file into each parameter input box, ensuring the build is executed with the correct parameters.

[0076] Step S334: Trigger the build execution of the integration task.

[0077] It should be understood that after the parameters are filled in, the tool automatically clicks the build button to trigger the CI task to execute the build, and continuously polls the build status until the build is completed (success or failure) and records the build result.

[0078] Step S335: After the integration task is built, obtain the download address of the deliverable corresponding to the deliverable path information from the deliverable management platform.

[0079] It should be understood that the deliverable management platform is an independent artifact repository platform used to store deliverables (such as installation packages, image files, etc.) produced by CI builds. After the integration task is completed, the tool obtains the accessible download address (URL) of the deliverable based on the deliverable path information recorded in the spreadsheet configuration file (such as the Nexus repository path or Artifactory path), by calling the deliverable management platform's interface or navigating to the corresponding page.

[0080] In some embodiments, automatically sending a notification includes: automatically generating a notification email, the body of which includes integration result information indicating that the integration task has been completed and the download address of the deliverables; and sending the notification email to a preset recipient.

[0081] Specifically, after obtaining the deliverable download address, the tool automatically builds a notification email. The email subject is typically "[Project Name] Integration Build Complete Notification," and the email body includes the project name, integration task name, build version number, build time, build result (success / failure), and the download link for the deliverable. Email recipients are read from preset recipient fields in the spreadsheet configuration file, supporting multiple recipients. The tool automatically sends emails using Python's smtplib library or an enterprise email service API, achieving closed-loop notification for integration tasks.

[0082] See Figure 4 From a low-level implementation perspective, the aforementioned automated integration and build functionality is handled by the project's automated integration tool. This tool is a Python-based host computer software that uses the Selenium browser automation framework to simulate administrator operations on the Jenkins platform's web interface. It automatically logs into the Jenkins platform, searches for and locates integration CI tasks, fills in integration parameters, triggers build execution, and, upon integration completion, automatically retrieves the deliverables download address from the deliverables platform and notifies relevant personnel via email. After reading the integration information Excel configuration table, the tool iterates through each integration record and executes them sequentially, achieving full automation of the project integration and build process.

[0083] Step S34: Based on the archive management information, invoke the archive function of the second management platform to perform the archive operation for this project, specifically including the following steps: Step S341: Automatically log in to the second management platform.

[0084] Step S342: Search for the corresponding archive task based on the archive task identifier.

[0085] It should be understood that the archive task identifier is the name used to uniquely identify the target archive CI task in the second management platform. Archive CI tasks are similar to integration CI tasks, but their purpose is to formally archive the integrated deliverables to a designated storage location, achieving long-term preservation and version management of the deliverables. In one example, in the Jenkins platform, archive tasks are typically named with the prefix "archive" or "release" to easily distinguish them from integration tasks.

[0086] Step S343: Based on the archive task parameters, fill in the execution parameters of the archive task.

[0087] It should be understood that archive task parameters refer to the parameters required when performing an archive operation, typically including the archive target path, archive version number, and archive description text. The tool uses the parameter input page for the archive task to fill in the corresponding parameter values ​​from the spreadsheet configuration file into each parameter input box.

[0088] Step S344: Trigger the build execution of the archive task.

[0089] It should be understood that the tool automatically clicks the build button, triggering the execution of the archiving task, and waits for the archiving operation to complete. Once archiving is complete, the tool automatically generates and sends an archiving result notification email to inform relevant administrators that the project archiving is complete. The notification email includes information such as the project name, archiving task name, archiving time, and archiving result (success / failure).

[0090] See Figure 5 From an underlying implementation perspective, the aforementioned automated archiving functionality is handled by the project auto-archiving tool. This tool is a Python-based host computer software that uses the Selenium browser automation framework to simulate administrator operations on the Jenkins platform's web interface. It automatically logs into the Jenkins platform, searches for and locates the archive CI task, fills in archive parameters, triggers archive execution, and sends email notifications to relevant administrators upon completion. The project auto-archiving tool reads the archive information Excel configuration table and iterates through each archive record sequentially, achieving full automation of the project archiving process.

[0091] In other embodiments, the method further includes: recording execution log information during the execution of operations on each project by the host computer automated execution tool; and generating an execution result report after all project operations are completed, the execution result report including the number of projects that were successfully executed and / or the number of projects that failed and the corresponding reasons for failure.

[0092] Specifically, the host computer-based automated execution tool outputs execution logs to the console and log files in real time for each operation. The log content includes: operation type (database creation / baseline creation / integration / archiving), operation time (accurate to the second), operation target (project name / repository name / task name), operation result (success / failure), and reason for failure (if failure). After all project records have been processed, the tool automatically generates an execution result report, presenting a tabular summary of the operation status statistics for all projects, including: total number of processed projects, number of successful projects, number of failed projects, and detailed reasons for each failure. The execution result report can be output to the console or saved as a text file or Excel file for administrator review.

[0093] In other embodiments, the spreadsheet configuration file is an Excel file; the host computer automation execution tool simulates user operations through a browser automation framework to automatically invoke the management functions of the first and second management platforms.

[0094] Specifically, a browser automation framework is a technical framework that controls a web browser to perform automated operations through programmatic control. In one example, the host computer automation execution tool uses Selenium WebDriver as the browser automation framework. Its working principle is as follows: the Selenium driver (such as ChromeDriver, GeckoDriver, etc.) acts as a communication bridge between the browser and the Python script. The Python script sends operation instructions to the driver by calling the Selenium API, and the driver then converts the instructions into native browser operations (such as clicking, filling, scrolling, etc.), thus completely simulating human operation behavior on the browser interface. Selenium supports mainstream browsers including Chrome, Firefox, and Edge, and has good compatibility and adaptability.

[0095] In other embodiments, the host computer automation execution tool can also use other browser automation frameworks such as Playwright and Puppeteer to achieve the same functionality. Playwright offers higher execution stability and richer waiting mechanisms compared to Selenium; Puppeteer focuses on Chromium-based browsers and offers faster execution speeds. The specific framework chosen can be flexibly selected based on the actual deployment environment and the web technology characteristics of the target platform.

[0096] This application embodiment also provides an automated management system for the entire lifecycle of intangible assets, applicable to the automated management method for the entire lifecycle of intangible assets provided in the above embodiments. The system includes: The configuration parsing module is configured to: obtain a spreadsheet configuration file; wherein the spreadsheet configuration file includes management task information corresponding to multiple projects, and the management task information includes configuration library management information, baseline management information, integration management information and archive management information; and parse the spreadsheet configuration file to extract the management task information corresponding to multiple projects.

[0097] It should be understood that the configuration parsing module corresponds to steps S10 and S20 in the above method embodiments. It is responsible for reading the Excel file and parsing each row of records into structured task data objects for use by subsequent modules. In one example, the configuration parsing module opens the Excel file using the openpyxl library, reads the data from the specified sheet, and maps each field value to its corresponding data structure. Simultaneously, the configuration parsing module also undertakes the responsibility of verifying field integrity and validity, ensuring that the data in each record is compliant before being passed to downstream modules for execution.

[0098] The automated execution module is configured to perform the following operations for each project across multiple projects, based on the management task information corresponding to that project: Based on the configuration library management information, call the configuration library management function of the first management platform to create a configuration library for that project; based on the baseline management information, call the baseline management function of the first management platform to create a baseline for that project; based on the integration management information, call the integration build function of the second management platform to trigger the integration build task for that project; and based on the archive management information, call the archive function of the second management platform to perform the archive operation for that project.

[0099] The notification module is configured to automatically send a notification after the archiving operation is completed.

[0100] It should be understood that the notification module is responsible for automatically generating and sending result notification emails after the integration build and archiving operations are completed. The notification module obtains operation result information (including integration results, deliverable download addresses, archiving results, etc.) from the automation execution module, constructs the email content according to a predefined email template, and sends the notification to the recipient list specified in the spreadsheet configuration file via the enterprise email service.

[0101] In some embodiments, the system further includes: a log recording module configured to record execution log information in real time during the execution of operations on each project by the automated execution module; and a report generation module configured to generate an execution result report after all project operations are completed, the report including the number of successful operations, the number of failed operations and the corresponding reasons for failure.

[0102] As can be seen from the above technical solutions, the embodiments of this application provide an automated management method and system for the entire lifecycle of intangible assets. The method includes: obtaining a spreadsheet configuration file; parsing the spreadsheet configuration file to extract management task information corresponding to each of the multiple projects; and using an automated execution tool on a host computer to perform configuration library establishment, baseline establishment, integration construction tasks and archiving operations for each project, and automatically sending notifications, so as to solve the problem of low management efficiency and high operation error rate caused by the reliance on manual management of the entire lifecycle of intangible assets.

[0103] Similar parts between the embodiments provided in this application can be referred to mutually. The specific implementation methods provided above are only a few examples under the overall concept of this application and do not constitute a limitation on the scope of protection of this application. For those skilled in the art, any other implementation methods extended from the solution of this application without creative effort shall fall within the scope of protection of this application.

Claims

1. A method for automated management of the entire lifecycle of intangible assets, characterized in that, include: Obtain the spreadsheet configuration file; wherein, the spreadsheet configuration file includes management task information corresponding to multiple projects, and the management task information includes configuration library management information, baseline management information, integration management information and archive management information; Parse the spreadsheet configuration file to extract the management task information corresponding to each of the multiple projects; Using an automated execution tool on a host computer, perform the following operations for each of the multiple projects, based on the management task information corresponding to that project: Based on the configuration library management information, the configuration library management function of the first management platform is invoked to establish a configuration library for the project; Based on the baseline management information, the baseline management function of the first management platform is invoked to establish a baseline for the project; Based on the integrated management information, the integration build function of the second management platform is invoked to trigger the integration build task of the project; Based on the archive management information, the archive function of the second management platform is invoked to perform the archive operation of the project and automatically send a notification.

2. The method for automated management of the entire lifecycle of intangible assets according to claim 1, characterized in that, The configuration repository management information includes the repository name, repository administrator information, and project description information; The step of calling the configuration library management function of the first management platform to establish a configuration library for the project based on the configuration library management information includes: Log in to the first management platform; Based on the warehouse name, create a new warehouse in the first management platform; Based on the warehouse administrator information, configure administrator permissions for the newly created warehouse; Based on the project description information, fill in the project description for the newly created warehouse.

3. The method for automated management of the entire lifecycle of intangible assets according to claim 1, characterized in that, The baseline management information includes the configuration repository identifier, baseline version identifier, and commit identifier; The step of invoking the baseline management function of the first management platform to establish a baseline for the project based on the baseline management information includes: Log in to the first management platform; Search for the corresponding configuration repository based on the configuration repository identifier; Access the baseline configuration interface of the configuration library; Based on the commit identifier, and using the code commit version corresponding to the commit identifier as a benchmark, a baseline corresponding to the baseline version identifier is established.

4. The method for automated management of the entire lifecycle of intangible assets according to claim 1, characterized in that, The integrated management information includes the integrated task identifier, integrated task parameters, and deliverable path information; The step of invoking the integration build function of the second management platform based on the integration management information to trigger the integration build task of the project includes: Log in to the second management platform; Based on the integrated task identifier, search for the corresponding integrated task; Based on the integrated task parameters, fill in the construction parameters of the integrated task; Trigger the build execution of the integrated task; After the integration task is completed, the download address of the deliverable corresponding to the deliverable path information is obtained from the deliverable management platform.

5. The method for automated management of the entire lifecycle of intangible assets according to claim 4, characterized in that, The automatic notification sending includes: Automatically generate a notification email, the body of which includes integration result information indicating the completion of the integration task and the download address of the deliverable; The notification email is sent to a pre-defined recipient.

6. The method for automated management of the entire lifecycle of intangible assets according to claim 1, characterized in that, The archive management information includes the archive task identifier and archive task parameters; The step of invoking the archiving function of the second management platform based on the archiving management information to perform the archiving operation of the project includes: Log in to the second management platform; Search for the corresponding archive task based on the archive task identifier; Based on the archive task parameters, fill in the execution parameters of the archive task; This triggers the build and execution of the archive task.

7. The method for automated management of the entire lifecycle of intangible assets according to claim 1, characterized in that, The method further includes: After parsing the spreadsheet configuration file, the extracted management task information is subjected to field integrity verification and / or field validity verification. If the verification fails, an error message will be output and the operation on the item corresponding to the management task information will be suspended.

8. The method for automated management of the entire lifecycle of intangible assets according to claim 1, characterized in that, The method further includes: During the process of the host computer automated execution tool performing the operations on each project, execution log information is recorded; After all project operations are completed, an execution result report is generated, which includes the number of projects that were successfully executed and / or the number of projects that failed and the corresponding reasons for the failures.

9. The method for automated management of the entire lifecycle of intangible assets according to claim 1, characterized in that, The spreadsheet configuration file is in Excel format; the host computer automation execution tool simulates user operations through a browser automation framework to automatically invoke the management functions of the first management platform and the second management platform.

10. An automated management system for the entire lifecycle of intangible assets, characterized in that, The method for automated management of the entire lifecycle of intangible assets applicable to any one of claims 1-9 includes: The configuration parsing module is configured to: obtain a spreadsheet configuration file; wherein, the spreadsheet configuration file includes management task information corresponding to multiple projects, and the management task information includes configuration library management information, baseline management information, integration management information and archive management information; Parse the spreadsheet configuration file to extract the management task information corresponding to each of the multiple projects; The automated execution module is configured to perform the following operations for each of the plurality of projects, based on the management task information corresponding to that project: Based on the configuration library management information, the configuration library management function of the first management platform is invoked to establish a configuration library for the project; Based on the baseline management information, the baseline management function of the first management platform is invoked to establish a baseline for the project; Based on the integrated management information, the integration build function of the second management platform is invoked to trigger the integration build task of the project; Based on the archive management information, the archive function of the second management platform is invoked to perform the archive operation of the project; The notification module is configured to automatically send a notification after the archiving operation is completed.

Images