Application and parameter association publishing method and device and storage medium

Abstract

The invention discloses an application and parameter associated publishing method and device and a storage medium, and relates to the technical field of electronic digital data processing.The method comprises the steps that a parameter publishing list and an application publishing list are obtained, the parameter publishing list comprises to-be-published parameters, and the application publishing list comprises to-be-published applications; performing source code analysis on the application to determine parameter use scene information corresponding to the parameter, and determining a dependency relationship between the parameter and the application according to the parameter use scene information; and determining the publishing sequence of the parameters in the parameter publishing list and the applications in the application publishing list according to the dependency relationship, and publishing the parameters and the applications according to the publishing sequence. According to the method and the device, configuration missing or function abnormity caused by an error issuing sequence is avoided, the reliability of parameter and application collaborative issuing is improved, and the efficiency of parameter and application collaborative issuing is also improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of electronic digital data processing, and particularly relates to an application and parameter association publishing method and device and a storage medium. BACKGROUND

[0002] A parameter management scheme usually adopts a manner of separating parameter configuration from software application, and independently manages the application and the parameter. However, in a collaborative development process, this management manner needs to explicitly define the dependency relationship between the application and the parameter in advance, so as to avoid production accidents caused by improper publishing sequence.

[0003] At present, the main means for analyzing the application and parameter dependency relationship in the industry still relies on manual operation. The current manual operation compares the application list and the parameter list item by item to check the dependency relationship. With the rapid growth of the number of applications and the scale of parameters, the analysis process is more and more complicated, which leads to low efficiency of publishing the application and the parameter. SUMMARY

[0004] The main purpose of the present application is to provide an application and parameter association publishing method, device and storage medium, which aims to solve the technical problem of low efficiency of publishing the application and the parameter.

[0005] To achieve the above purpose, the present application provides an application and parameter association publishing method, which comprises the following steps:

[0006] Obtaining a parameter publishing list and an application publishing list, wherein the parameter publishing list comprises parameters to be published, and the application publishing list comprises applications to be published;

[0007] Performing source code analysis on the application to determine parameter use scenario information corresponding to the parameters, and determining a dependency relationship between the parameters and the applications according to the parameter use scenario information;

[0008] Determining a publishing sequence of the parameters in the parameter publishing list and the applications in the application publishing list according to the dependency relationship, and publishing the parameters and the applications according to the publishing sequence.

[0009] In an embodiment, the step of determining the publishing sequence of the parameters in the parameter publishing list and the applications in the application publishing list according to the dependency relationship comprises:

[0010] According to the dependency relationship, determining a publishing relationship between the parameters and the applications;

[0011] According to the publishing relationship, generating the publishing sequence of the parameters in the parameter publishing list and the applications in the application publishing list.

[0012] In an embodiment, the determining the release relationship between the parameter and the application according to the dependency relationship comprises:

[0013] When the dependency relationship comprises that the application depends on the parameter, the determining the release relationship comprises that the parameter is released before the application.

[0014] When the dependency relationship comprises that the parameter depends on the application, the determining the release relationship comprises that the application is released before the parameter.

[0015] In an embodiment, the parameter usage scenario information comprises a function involving parameter usage in the application and a scenario type; and the determining the dependency relationship between the parameter and the application according to the parameter usage scenario information comprises:

[0016] determining the dependency relationship between the parameter and the application according to the function involving parameter usage in the application and the scenario type.

[0017] In an embodiment, the determining the dependency relationship between the parameter and the application according to the function involving parameter usage in the application and the scenario type comprises:

[0018] determining the application and the parameter having the dependency relationship according to the function involving parameter usage in the application and the scenario type.

[0019] When the application and the parameter have the dependency relationship, when the scenario type comprises a scenario of adding parameter usage, determining that the dependency relationship comprises that the application depends on the parameter; and / or when the scenario type comprises a scenario of offline parameter usage, determining that the dependency relationship comprises that the parameter depends on the application.

[0020] In an embodiment, the determining the parameter usage scenario information corresponding to the parameter by source code parsing of the application comprises:

[0021] performing source code parsing according to a current version of the application to obtain a current usage of the parameter;

[0022] performing source code parsing according to a historical version of the application to obtain a historical usage of the parameter;

[0023] determining the parameter usage scenario information according to the current usage and the historical usage of the parameter.

[0024] In an embodiment, the determining the parameter usage scenario information according to the current usage and the historical usage of the parameter comprises:

[0025] When the parameter is used in the current version but not in previous versions, the parameter usage scenario information is determined to include scenarios where the parameter is newly added.

[0026] If the parameter is not used in the current version but has been used in a previous version, the parameter usage scenario information is determined to include scenarios where the parameter was used offline.

[0027] In one embodiment, the step of parsing the application's source code to determine the parameter usage scenario information corresponding to the parameter includes:

[0028] Determine the target application list corresponding to the parameter, wherein the target application list includes the target application corresponding to the parameter;

[0029] When an application in the application release list is in the target application list, the step of parsing the source code of the application to determine the parameter usage scenario information corresponding to the parameter is executed.

[0030] Furthermore, to achieve the above objectives, this application also proposes an application and parameter association publishing device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the application and parameter association publishing method as described above.

[0031] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the application and parameter association publishing method described above.

[0032] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the application and parameter association publishing method described above.

[0033] One or more technical solutions proposed in this application have at least the following technical effects:

[0034] By analyzing the source code of the application to be released to determine the usage scenario information of the parameters, and then determining the dependency relationship between the parameters and the application based on the usage scenario information, and finally determining the release order of the parameters and the application based on the dependency relationship, configuration loss or functional abnormality caused by incorrect release order is avoided, which improves the reliability and efficiency of parameter and application co-release. Attached Figure Description

[0035] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

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

[0037] Figure 1 This is a flowchart illustrating the method for associating and publishing parameters in this application, as provided in Embodiment 1.

[0038] Figure 2 A simplified flowchart illustrating an embodiment of the method for associating and publishing parameters in this application;

[0039] Figure 3 A simplified flowchart illustrating an embodiment of the method for associating and publishing parameters in this application;

[0040] Figure 4 A simplified flowchart illustrating an embodiment of the method for associating and publishing parameters in this application;

[0041] Figure 5 This is a flowchart illustrating the second embodiment of the method for associating and publishing parameters in this application.

[0042] Figure 6 This is a flowchart illustrating the method for associating and publishing parameters in this application, as provided in Embodiment 3.

[0043] Figure 7 This is a flowchart illustrating the fourth embodiment of the method for associating and publishing parameters in this application.

[0044] Figure 8 This is a schematic diagram of the device structure of the hardware operating environment involved in the application and parameter association publishing method in the embodiments of this application.

[0045] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0046] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0047] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0048] In the current industry, a common architecture is the separation of application and configuration, where software packages and business parameters are hosted in image repositories and configuration centers respectively, and parallel deployments are achieved through independent pipelines. However, during collaborative development, it is necessary to clearly define the dependencies between applications and parameters in advance to avoid production incidents caused by improper deployment order.

[0049] Currently, the main method for analyzing application and parameter dependencies in the industry still relies on manual operation. This involves manually checking dependencies item by item against application and parameter lists. With the rapid growth in the number of applications and the scale of parameters, the analysis process is cumbersome, and the efficiency of application and parameter release is low.

[0050] The main solution of this application embodiment is: to obtain a parameter release list and an application release list, wherein the parameter release list includes parameters to be released and the application release list includes applications to be released; to perform source code parsing on the applications to determine the parameter usage scenario information corresponding to the parameters, and to determine the dependency relationship between the parameters and the applications based on the parameter usage scenario information; to determine the release order of the parameters in the parameter release list and the applications in the application release list based on the dependency relationship, and to release the parameters and applications according to the release order.

[0051] In this embodiment, for ease of description, the following description will focus on the application and parameter association publishing device as the execution subject.

[0052] This application provides a solution that determines the usage scenario information of parameters by parsing the source code of the application to be released, determines the dependency relationship between parameters and the application based on the usage scenario information, and determines the release order of parameters and the application based on the dependency relationship. This avoids configuration loss or functional abnormality caused by incorrect release order, improves the reliability of parameter and application co-release, and also improves the efficiency of parameter and application co-release.

[0053] It should be noted that the executing entity in this embodiment can be an application and parameter association publishing device. This device can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device capable of performing the aforementioned functions. The following description uses an application and parameter association publishing device as an example to illustrate this embodiment and the subsequent embodiments.

[0054] Based on this, embodiments of this application provide a method for associating and publishing applications and parameters, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the method for associating and publishing parameters in this application.

[0055] In this embodiment, the method for associating and publishing applications and parameters includes steps S10 to S30:

[0056] Step S10: Obtain the parameter release list and the application release list. The parameter release list includes parameters to be released, and the application release list includes applications to be released.

[0057] In this embodiment, an application is a software program running on a computer, designed to perform a specific function or task. Application release is the process of formally deploying a completed software product into a production environment for user use. The application release list includes at least one application to be released; optionally, the application release list includes application A, application B, ..., application M, etc.

[0058] In this embodiment, parameters are elements within the parameter space, and are data variables with certain rules and control capabilities compiled according to system operation requirements and business processing regulations. Parameter release is the process of formally deploying the configured parameters into the production environment for application use. The parameter release list includes at least one parameter to be released; optionally, the parameter release list includes parameter 1, parameter 2, ..., parameter N, etc.

[0059] Parameters can be managed by a parameter management platform. This platform is a configuration management tool for centrally managing and dynamically adjusting system operating parameters, supporting parameter version control, release management, and management of applications using the parameters.

[0060] Step S20: Perform source code parsing on the application to determine the parameter usage scenario information corresponding to the parameter, and determine the dependency relationship between the parameter and the application based on the parameter usage scenario information.

[0061] Before parameter and software release, an application source code analysis function is introduced to automatically build a list of parameters and application dependencies before release. Combined with source code-level compatibility analysis, this reduces production incidents caused by dependency mismatches. Through automated and intelligent analysis methods, the efficiency and accuracy of dependency analysis are significantly improved, human error is reduced, and the reliability of analysis results is ensured.

[0062] Optionally, parameter usage scenario information is stored in the application's parameter usage scenario list. This list not only includes the functions in the application that involve parameter usage but also explicitly indicates the scenario type for parameter usage. Optionally, the scenario type includes scenarios where new parameters are used, scenarios where parameter usage scenarios remain unchanged, and scenarios where parameters are no longer used.

[0063] Optionally, a parameter can correspond to multiple scenario types. For example, parameter 1 involves scenarios where new parameters are used, scenarios where parameter usage remains unchanged, and scenarios where offline parameters are used.

[0064] A dependency is a condition where the operation of one thing or system depends on the existence or functionality of another thing or system. In this embodiment, a dependency can be defined as which applications a parameter must be released before or after to ensure that the application can correctly read the value of the required parameter during startup or runtime.

[0065] Optionally, the dependency includes the application depending on the parameter, meaning the application's operation depends on the parameter's existence. Alternatively, the dependency includes the parameter depending on the application, meaning the parameter's operation depends on the application's existence.

[0066] In an optional embodiment, step S20 includes: determining a list of target applications corresponding to the parameter, the list of target applications including the target applications corresponding to the parameter; when an application in the application release list is in the target application list, performing source code parsing on the application to determine the parameter usage scenario information corresponding to the parameter. When an application in the application release list is not in the target application list, it is determined that the parameter and the application have no dependency relationship. If it is determined that the application to be released and the parameter to be released have a dependency relationship, and then step S20 is performed, and the application to be released and the parameter to be released have no dependency relationship, it is determined that there is no release order requirement, and there is no need to determine the dependency relationship, thus saving computing resources.

[0067] Reference Figure 2 Based on the parameter release list P, the system queries the parameter management platform to identify which applications are involved in the parameters to be released, thus obtaining a target application list L. It then checks whether application A in the application release list is also in the target application list L. If the application to be released is not in the target application list L, then that application and the parameter to be released are independent. If the application to be released is in the target application list L, the system analyzes the parameter usage of that application one by one based on the differences between the current version and historical versions, generating parameter usage scenario information.

[0068] Step S30: Determine the release order of the parameters in the parameter release list and the applications in the application release list according to the dependency relationship, and release the parameters and the applications according to the release order.

[0069] In this embodiment, the release order is the sequential order in which parameters in the parameter release list and applications in the application release list are released. Releasing parameters and applications in association according to the release order improves release efficiency. Applications or parameters without dependencies can be placed anywhere in the release order, for example, first in the release order.

[0070] In one embodiment, reference is made to Figure 3After submitting the parameter release list, the parameter management platform queries and analyzes the list of target applications involved in the parameter release list. Combining the target application list with the application release list, this invention automatically parses the source code of each involved application to output a parameter usage scenario list. The application's parameter usage scenario list not only includes the functions in the application that use the parameters but also clearly marks the scenario type of the parameters, including scenarios where new parameters are used, scenarios where the parameter usage scenario remains unchanged, and scenarios where decommissioned parameters are used. The parameter usage list and the parameter release list are combined for correlation analysis to ultimately generate a dependency relationship list. Specifically, for scenarios where new parameters are used, the application's dependency on the parameter is established; while for scenarios where decommissioned parameters are used, the parameter's dependency on the application is established. Based on the dependency relationship list, the optimal release order of applications and parameters is automatically generated to ensure the smooth progress of the release process.

[0071] By pulling two release lists—parameters and applications—and using static source code analysis to accurately capture the real-world usage scenarios of each parameter in the application, a parameter-application dependency graph is built in real time, completely replacing manual comparison. The release order generated accordingly ensures that parameters are deployed before the applications that depend on them, eliminating startup failures and online outages caused by missing configurations or version mismatches. Even when scaling up, it maintains minute-level decision-making and zero misjudgments, significantly improving the security and efficiency of continuous delivery.

[0072] When a parameter depends on an application, the application is released before the parameter; when an application depends on a parameter, the parameter is released before the application. For example, if parameter 1 depends on application A, parameter 2 depends on application A, and application A depends on parameter 3, then application A is released before parameter 1, application A is released before parameter 2, and parameter 3 is released before application A. Finally, the release order is parameter 3, application A, parameter 2, or parameter 1.

[0073] In one embodiment, dependency analysis is exemplified as follows: Figure 4 As shown, the parameter release list includes parameter 1 (add), parameter 2 (modify), parameter 3 (delete), parameter 4 (add), parameter 5 (modify), parameter 6 (delete), and parameter 7 (modify). Parameter 1 relates to scenarios where the new parameter is used; parameter 2 relates to scenarios where the new parameter is used and scenarios where the parameter usage remains unchanged; parameter 3 relates to scenarios where the parameter is decommissioned; parameter 4 relates to scenarios where the new parameter is used; parameter 5 relates to scenarios where the new parameter is used, scenarios where the parameter usage remains unchanged, and scenarios where the parameter is decommissioned; parameter 6 relates to scenarios where the parameter is decommissioned; and parameter 7 relates to scenarios where the parameter to be released is not currently in use.

[0074] The application release list includes three applications: A, B, C, and D. Application A contains three parameter-related functions: A1, A2, and A3. Scenario A1, where the parameter is newly added, involves parameter 1; scenario A2, where the parameter remains unchanged, involves parameter 2; and scenario A3, where the parameter is decommissioned, involves parameter 3. The dependency relationships are: Application A depends on parameter 1, Application A has no dependency on parameter 2, and parameter 3 depends on Application A. Application B contains two parameter-related functions: B1 and B2. Scenario B1, where the parameter is newly added, involves parameter 2; and scenario B2, where the parameter is decommissioned, involves parameter 5. The dependency relationships are: Application B depends on parameter 2, and parameter 5 depends on Application B. Application C contains four parameter-related functions: C1, C2, C3, and C4. Scenario C1, where the parameter is newly added, involves parameter 4; scenario C2, where the parameter is newly added, involves parameter 5; scenario C3, where the parameter remains unchanged, involves parameter 5; and scenario C4, where the parameter is decommissioned, involves parameter 6. The analysis reveals the following dependencies: Application C depends on parameters 4 and 5, and parameter 6 depends on application C. Application D is not in the list of applications involved in the parameter release and has no dependency on parameter release. Parameter 7 corresponds to a scenario in the list of applications to be released that has no usage and has no dependency on application release.

[0075] Based on the above dependencies, the release order can be determined as follows: Application D, Parameter 1, Parameter 2, Parameter 7 → Application A → Application B → Parameter 3, Parameter 4, Parameter 5 → Application C → Parameter 6.

[0076] In the technical solution of this embodiment, the parameter usage scenario information is determined by parsing the source code of the application to be released, and the dependency relationship between the parameter and the application is determined based on the parameter usage scenario information. The release order of the parameter and the application is determined based on the dependency relationship. This avoids configuration loss or functional abnormality caused by incorrect release order, improves the reliability of parameter and application co-release, and also improves the efficiency of parameter and application co-release.

[0077] Based on the first embodiment of this application, in the second embodiment of this application, the same or similar content as the above embodiment can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 5 Step S30 includes:

[0078] Step S31: Determine the publishing relationship between the parameters and the application based on the dependency relationship;

[0079] Step S32: Based on the release relationship, generate the release order of the parameters in the parameter release list and the applications in the application release list.

[0080] In this embodiment, the publishing relationship is the order relationship between parameters and applications, such as the order relationship between parameter 1 and application A.

[0081] In an optional embodiment, when the dependency relationship includes an application depending on a parameter, the release relationship is determined to include that the parameter is released before the application; when the dependency relationship includes a parameter depending on an application, the release relationship is determined to include that the application is released before the parameter. Based on the release relationships between each application and each parameter, the release order of the applications and parameters can be integrated and output.

[0082] Reference Figure 4 The parameter release list includes parameter 1, parameter 2, parameter 3, parameter 4, parameter 5, parameter 6, and parameter 7. The application release list includes three applications: A, B, C, and D. Application A depends on parameter 1, application A has no dependency on parameter 2, and parameter 3 depends on application A. Application B depends on parameter 2, and parameter 5 depends on application B. Application C depends on parameters 4 and 5, and parameter 6 depends on application C. Application D is not in the application list involved in parameter release and has no dependency on parameter release. Parameter 7 has no dependency on application release. Based on the above dependencies, the recommended release order is: application D, parameter 1, parameter 2, parameter 7 → application A → application B → parameter 3, parameter 4, parameter 5 → application C → parameter 6.

[0083] In the technical solution of this embodiment, by transforming the dependency relationship into a release relationship between parameters and applications, and generating a global release order based on the release relationship, the risk of omissions and conflicts caused by manual sorting is eliminated, while improving the release efficiency of parameters and applications.

[0084] Based on the first or second embodiment of this application, in the third embodiment of this application, the content that is the same as or similar to the above embodiments can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 6 Step S20, which determines the dependency relationship between the parameter and the application based on the parameter usage scenario information, includes:

[0085] Step S21: Determine the dependency relationship between the parameter and the application based on the function involving parameter usage in the application and the scenario type.

[0086] In this embodiment, the parameter usage scenario information includes the functions and / or scenario types involved in the parameter usage in the application.

[0087] In an optional embodiment, applications and parameters with dependencies are determined based on the functions and scenario types involved in the use of parameters in the application; when applications and parameters have dependencies, if the scenario type includes scenarios where new parameters are used, the dependency is determined to include applications depending on parameters; and / or, if the scenario type includes scenarios where offline parameters are used, the dependency is determined to include parameters depending on applications.

[0088] Optionally, when the scenario type includes scenarios where the parameters remain unchanged, it is determined that there is no dependency between the parameters and the application. When the scenario type includes scenarios where the parameters to be published are not used, it is determined that there is no dependency between the parameters and the application.

[0089] It's important to note that adding parameters is used when the application needs to be ready before it can be released, meaning the application depends on the parameters. During release, parameters should be released first, followed by the application. Parameters whose usage remains unchanged mean the application's usage scenario remains the same before and after using the parameters; changes to the parameters are irrelevant to the application's release, and the two are independent. There is no specific order requirement for application release and parameter release during release. Decommissioning parameters is used when the application needs to be decommissioned before the parameters can be decommissioned, meaning the parameters depend on the application. During release, the application should be released first, followed by the parameters. Parameters that are not used mean the application does not use any parameters from the parameter release list; the two are independent. There is no specific order requirement for application release and parameter release during release.

[0090] The application release list includes three applications: A, B, C, and D. Application A contains three parameter-related functions: A1, A2, and A3. Scenario A1, where the parameter is newly added, involves parameter 1; scenario A2, where the parameter remains unchanged, involves parameter 2; and scenario A3, where the parameter is decommissioned, involves parameter 3. The dependency relationships are: Application A depends on parameter 1, Application A has no dependency on parameter 2, and parameter 3 depends on Application A. Application B contains two parameter-related functions: B1 and B2. Scenario B1, where the parameter is newly added, involves parameter 2; and scenario B2, where the parameter is decommissioned, involves parameter 5. The dependency relationships are: Application B depends on parameter 2, and parameter 5 depends on Application B. Application C contains four parameter-related functions: C1, C2, C3, and C4. Scenario C1, where the parameter is newly added, involves parameter 4; scenario C2, where the parameter is newly added, involves parameter 5; scenario C3, where the parameter remains unchanged, involves parameter 5; and scenario C4, where the parameter is decommissioned, involves parameter 6. The analysis reveals the following dependencies: Application C depends on parameters 4 and 5, and parameter 6 depends on application C. Application D is not in the list of applications involved in the parameter release and has no dependency on parameter release. Parameter 7 corresponds to a scenario in the list of applications to be released that has no usage and has no dependency on application release.

[0091] In the technical solution of this embodiment, the parameter usage scenario information is determined by parsing the source code of the application to be released. Based on the function and scenario type of the application involving parameter usage in the parameter usage scenario information, the dependency relationship between the parameter and the application is determined, which improves the accuracy of dependency determination. Furthermore, the release order of the parameter and the application is determined based on the dependency relationship, which avoids configuration loss or functional abnormality caused by incorrect release order. This improves the reliability of parameter and application co-release and also increases the efficiency of parameter and application co-release.

[0092] Based on any of the first to third embodiments of this application, in the fourth embodiment of this application, the content that is the same as or similar to the above embodiments can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 7 The content of determining the parameter usage scenario information corresponding to the parameter by parsing the source code of the application in step S20 includes:

[0093] Step S22: Parse the source code according to the current version of the application to obtain the current usage of the parameter;

[0094] Step S23: Parse the source code based on the historical versions of the application to obtain the historical usage of the parameters;

[0095] Step S24: Determine the parameter usage scenario information based on the current usage and historical usage of the parameter.

[0096] In this embodiment, for parameter 1, the current version of the application's source code is parsed to obtain the usage of parameter 1. Based on historical versions, the source code is parsed to obtain the historical usage of parameter 1. Here, the current version is the version of the application released this time, and historical versions are existing versions of the application, which could be the version released last time. Based on the current usage of parameter 1 in the current version and the historical usage in historical versions, the parameter usage scenario information for parameter 1 is determined.

[0097] In an optional embodiment, when a parameter is used in the current version but not in previous versions, the parameter usage scenario information includes scenarios where the parameter is newly added; when a parameter is not used in the current version but has been used in previous versions, the parameter usage scenario information includes scenarios where the parameter is decommissioned. When a parameter has been used in both the current and previous versions, the parameter usage scenario information includes scenarios where the parameter usage has not changed. See the table below:

[0098]

[0099]

[0100] Based on the table above, we can analyze that there are four types of parameter usage scenarios: scenarios where new parameters are used, scenarios where parameter usage remains unchanged, scenarios where offline parameters are used, and scenarios where parameters are not used. Scenarios where new parameters are used include cases where this application is being released for the first time.

[0101] In the technical solution of this embodiment, the parameter usage scenario information is determined by parsing the source code of the application to be released, so as to facilitate the subsequent analysis of the dependency relationship between the parameter and the application. Different scenario types correspond to different dependency relationships. Based on the function of the application involving parameter usage in the parameter usage scenario information and the scenario type, the dependency relationship between the parameter and the application is determined, which improves the accuracy of dependency relationship determination. Furthermore, the release order of the parameter and the application is determined based on the dependency relationship, avoiding configuration loss or functional abnormalities caused by incorrect release order. This improves the reliability and efficiency of parameter and application collaborative release.

[0102] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the application and parameter association publishing method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0103] This application provides an application and parameter association publishing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the application and parameter association publishing method in the first embodiment described above.

[0104] The following is for reference. Figure 8 This illustration shows a structural diagram of an application and parameter association publishing device suitable for implementing the embodiments of this application. The application and parameter association publishing device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable media players (PMPs), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The application and parameter association publishing device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0105] like Figure 8As shown, the application and parameter association publishing device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from storage device 1003 into random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the application and parameter association publishing device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the application and parameter association publishing device to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows application and parameter association publishing devices with various systems, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems can be implemented alternatively.

[0106] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0107] The application and parameter association publishing device provided in this application, employing the application and parameter association publishing method described in the above embodiments, can solve the technical problem of low efficiency in application and parameter publishing. Compared with the prior art, the beneficial effects of the application and parameter association publishing device provided in this application are the same as those of the application and parameter association publishing method described in the above embodiments, and other technical features in this application and parameter association publishing device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0108] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0109] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0110] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the application and parameter association publishing method in the above embodiments.

[0111] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), etc., or any suitable combination thereof.

[0112] The aforementioned computer-readable storage medium may be included in the application and parameter association publishing device; or it may exist independently and not assembled into the application and parameter association publishing device.

[0113] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by the application and parameter associated publishing device, the application and parameter associated publishing device: determines the parameter usage scenario information by parsing the source code of the application to be published, determines the dependency relationship between the parameter and the application based on the parameter usage scenario information, and determines the publishing order of the parameter and the application based on the dependency relationship. This avoids configuration loss or functional abnormality caused by incorrect publishing order, improves the reliability of parameter and application collaborative publishing, and also improves the efficiency of parameter and application collaborative publishing.

[0114] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0115] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0116] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0117] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described application and parameter association publishing method, thereby solving the technical problem of low efficiency in application and parameter publishing. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the application and parameter association publishing method provided in the above embodiments, and will not be repeated here.

[0118] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the application and parameter association publishing method described above.

[0119] The computer program product provided in this application can solve the technical problem of low efficiency in the release of applications and parameters. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the application and parameter association release method provided in the above embodiments, and will not be repeated here.

[0120] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for associating and publishing applications and parameters, characterized in that, The method for associating applications with parameters includes: Obtain a parameter release list and an application release list, wherein the parameter release list includes parameters to be released and the application release list includes applications to be released; The application's source code is parsed to determine the parameter usage scenario information corresponding to the parameter, and the dependency relationship between the parameter and the application is determined based on the parameter usage scenario information; The release order of the parameters in the parameter release list and the applications in the application release list is determined based on the dependency relationship, and the parameters and applications are released according to the release order.

2. The application and parameter association publishing method as described in claim 1, characterized in that, The step of determining the release order of the parameters in the parameter release list and the applications in the application release list based on the dependency relationship includes: Based on the dependencies, determine the publishing relationship between the parameters and the application; Based on the release relationship, the release order of the parameters in the parameter release list and the applications in the application release list is generated.

3. The application and parameter association publishing method as described in claim 2, characterized in that, The step of determining the publishing relationship between the parameters and the application based on the dependency relationship includes: When the dependency relationship includes the application depending on the parameter, it is determined that the release relationship includes the parameter being released before the application; When the dependency relationship includes the parameter depending on the application, the publication relationship is determined to include the application being published before the parameter.

4. The application and parameter association publishing method as described in claim 1, characterized in that, The parameter usage scenario information includes the functions and scenario types involved in the use of the parameters in the application. The step of determining the dependency relationship between the parameter and the application based on the usage scenario information of the parameter includes: Based on the functions involving parameter usage in the application and the scenario type, determine the dependency relationship between the parameter and the application.

5. The application and parameter association publishing method as described in claim 4, characterized in that, The step of determining the dependency relationship between the parameter and the application based on the functions involving parameter usage in the application and the scenario type includes: Based on the functions involving parameter usage in the application and the scenario type, determine the applications and parameters that have a dependency relationship; When there is a dependency between the application and the parameter, if the scenario type includes a scenario where the new parameter is used, the dependency is determined to include the application depending on the parameter; and / or, if the scenario type includes a scenario where the offline parameter is used, the dependency is determined to include the parameter depending on the application.

6. The application and parameter association publishing method as described in claim 1, characterized in that, The step of parsing the application source code to determine the parameter usage scenario information corresponding to the parameter includes: The current usage of the parameter is obtained by parsing the source code based on the current version of the application. The historical usage of the parameter is obtained by parsing the source code of the application's historical versions. Based on the current usage and historical usage of the parameter, the usage scenario information of the parameter is determined.

7. The application and parameter association publishing method as described in claim 6, characterized in that, The step of determining the usage scenario information of the parameter based on the current usage and the historical usage of the parameter includes: When the parameter is used in the current version but not in previous versions, the parameter usage scenario information is determined to include scenarios where the parameter is newly added. If the parameter is not used in the current version but has been used in a previous version, the parameter usage scenario information is determined to include scenarios where the parameter was used offline.

8. The method for associating and publishing applications and parameters as described in any one of claims 1 to 7, characterized in that, The step of parsing the application source code to determine the parameter usage scenario information corresponding to the parameter includes: Determine the target application list corresponding to the parameter, wherein the target application list includes the target application corresponding to the parameter; When an application in the application release list is in the target application list, the step of parsing the source code of the application to determine the parameter usage scenario information corresponding to the parameter is executed.

9. An application and parameter association publishing device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the application and parameter association publishing method as described in any one of claims 1 to 8.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the application and parameter association publishing method as described in any one of claims 1 to 8.

Images