Method, device, equipment and storage medium for generating dependency packages compatible with dual versions

Abstract

This article provides a method, device, equipment and storage medium for generating a dependency package compatible with two versions. The method includes: obtaining the target code of the financial information system; generating a POM file set, the POM file set including a first POM file and a second POM file, the first POM file corresponds to the first version of the financial information system, and the second POM file corresponds to the second version of the financial information system; determining the target deployment environment; selecting a POM file corresponding to the target deployment environment from the POM file set; packaging the POM file corresponding to the target deployment environment and the target code to generate a dependency package corresponding to the target deployment environment; this article solves the problem of application deployment of financial information systems on different versions by generating POM files corresponding to different versions and directly calling the corresponding POM files to package the target code and generate a dependency package after determining the target deployment environment.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, equipment and storage medium for generating a dependency package compatible with dual versions. Background Art

[0002] As a national key information infrastructure, the financial information system is directly related to the normal operation of the national economy and society. At present, the business systems of financial institutions are all running on the X86 version, and have long relied on imported equipment and systems, which not only requires huge foreign exchange expenditures, but also involves the security and controllability of my country's financial industry. Therefore, it is necessary to ensure that important financial business systems can run stably on the domestic version to avoid the risk of no servers that can run financial transaction systems due to the suspension of core technology supply by foreign companies.

[0003] At the same time, since my country's financial localization is still in its infancy, it will take a long time to verify the reliability and stability of the localized financial trading platform. Therefore, at this stage, it is necessary to design a set of financial trading systems and trading operation solutions that can ensure the integration of the localized version. This is crucial to ensure the continuity of financial transactions and improve customer satisfaction. Summary of the invention

[0004] In view of the above-mentioned problems in the prior art, the purpose of this article is to provide a method, device, equipment and storage medium for generating a dependency package compatible with dual versions, so as to solve the problem in the prior art that the financial information system cannot be deployed on the domestically produced version.

[0005] In order to solve the above technical problems, the specific technical solutions of this article are as follows:

[0006] On the one hand, this article provides a method for generating a dependency package compatible with two versions, including the following steps:

[0007] Obtaining the object code of the financial information system;

[0008] Generate a POM file set, the POM file set includes a first POM file and a second POM file, the first POM file corresponds to a first version of the financial information system, and the second POM file corresponds to a second version of the financial information system;

[0009] Determine the target deployment environment;

[0010] Selecting a POM file corresponding to the target deployment environment from the POM file set;

[0011] The POM file corresponding to the target deployment environment and the target code are packaged to generate a dependency package corresponding to the target deployment environment.

[0012] Specifically, the method further includes:

[0013] The dependent package is deployed in the target deployment environment, and the dependent package is continuously integrated.

[0014] Further, the deploying the dependent package in the target deployment environment includes:

[0015] Calling a deployment script of a server that matches the target deployment environment, and deploying the dependent package in the server;

[0016] Restart the server.

[0017] Further, deploying the dependency in the target deployment environment includes:

[0018] Decompress the dependency package and copy it to a path of a server that matches the target deployment environment;

[0019] Modify the server configuration information;

[0020] Restart the server.

[0021] Specifically, the deploying the dependent package in the target deployment environment further includes:

[0022] A server matching the target deployment environment is checked to obtain a check result.

[0023] Preferably, the checking of the server matching the target deployment environment includes:

[0024] Check whether the configuration parameters of the server are correct;

[0025] Checking whether the uniform resource locator of the server is accessible;

[0026] Check whether the memory setting parameters of the server are correct.

[0027] Preferably, the method further comprises:

[0028] According to the inspection result, determining whether the dependent package is successfully deployed in the target deployment environment;

[0029] If the deployment fails, a deployment failure reminder message will be sent.

[0030] Specifically, the object code of the financial information system is obtained, including:

[0031] Get dynamic view;

[0032] Acquiring the source code of the financial information system according to the dynamic view;

[0033] The source code is compiled to obtain the target code of the financial information system.

[0034] Specifically, generating a POM file set includes:

[0035] Obtain first dependency configuration information and first database configuration information of the first version, and generate a first POM file according to the first dependency configuration information and the first database configuration information;

[0036] Obtain the second dependency configuration information and the second database configuration information of the second version, and generate a second POM file according to the second dependency configuration information and the second database configuration information

[0037] Specifically, the selecting a POM file corresponding to the target deployment environment from the POM file set includes:

[0038] Obtaining environmental parameters of the target deployment environment;

[0039] Compare the environment parameter with the first file name of the first POM file and the second file name of the second POM file respectively;

[0040] When the environment parameter corresponds to the first file name of the first POM file, selecting the first POM file;

[0041] When the environment parameter corresponds to the second file name of the second POM file, the second POM file is selected.

[0042] Furthermore, packaging the POM file corresponding to the target deployment environment and the target code to generate a dependency package corresponding to the target deployment environment also includes:

[0043] Determine whether the packaging is successful;

[0044] If packaging fails, a reminder message indicating that the dependent package generation failed will be sent.

[0045] Furthermore, before deploying the dependent package in the target deployment environment, the process further includes:

[0046] Download the dependency package to local;

[0047] Upload the dependent package from the local to the target deployment environment.

[0048] In the second aspect, based on the above-mentioned method, this article also provides a dual-version compatible dependency package generation device, including:

[0049] An acquisition module, used for acquiring the target code of the financial information system;

[0050] A generation module, configured to generate a POM file set, wherein the POM file set includes a first POM file and a second POM file, wherein the first POM file corresponds to a first version of the financial information system, and the second POM file corresponds to a second version of the financial information system;

[0051] A determination module, used to determine the target deployment environment;

[0052] A selection module, used to select a POM file corresponding to the target deployment environment from the POM file set;

[0053] The packaging module is used to package the POM file corresponding to the target deployment environment and the target code to generate a dependency package corresponding to the target deployment environment.

[0054] In a third aspect, the present invention also provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the method for generating a dependency package compatible with dual versions as described above are implemented.

[0055] In a fourth aspect, the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores an executable computer program, and when the computer program is executed by a processor, the method for generating a dependency package compatible with dual versions as described above is implemented.

[0056] By adopting the above technical scheme, a method, device, equipment and storage medium for generating a dependency package compatible with two versions described in this article generates POM files corresponding to different versions, and directly calls the POM files corresponding to the target deployment environment to package the target code after determining the target deployment environment, thereby generating a dependency package for deployment, thereby solving the problem of application deployment of the financial information system on the domestically produced version that is running on the same track.

[0057] In order to make the above and other purposes, features and advantages of this article more obvious and easy to understand, the following specifically cites preferred embodiments and describes them in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the technical solutions in the embodiments of this article or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of this article. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0059] Figure 1 A schematic diagram of the steps of a method for generating a dependency package compatible with two versions provided in an embodiment of this invention is shown;

[0060] Figure 2 A schematic diagram of the structure of a device for generating a dependency package compatible with two versions provided in an embodiment of the present invention is shown;

[0061] Figure 3 A schematic diagram of the structure of a computer device provided in the embodiments of this document is shown.

[0062] Description of the accompanying symbols:

[0063] 21. Get module;

[0064] 22. Generate module;

[0065] 23. Determine the module;

[0066] 24. Select module;

[0067] 25. Packaging module;

[0068] 302. Computer equipment;

[0069] 304. Processor;

[0070] 306. Memory;

[0071] 308, driving mechanism;

[0072] 310, input / output module;

[0073] 312. Input devices;

[0074] 314. Output devices;

[0075] 316. Presentation equipment;

[0076] 318. Graphical user interface;

[0077] 320, network interface;

[0078] 322. Communication link;

[0079] 324. Communication bus. DETAILED DESCRIPTION

[0080] The following will be combined with the drawings in the embodiments of this article to clearly and completely describe the technical solutions in the embodiments of this article. Obviously, the described embodiments are only part of the embodiments of this article, not all of the embodiments. Based on the embodiments of this article, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this article.

[0081] It should be noted that the terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0082] As a national key information infrastructure, the financial information system is directly related to the normal operation of the national economy and society. At present, most of the business systems of financial institutions run on the X86 version and rely on imported equipment and systems for a long time. This not only requires huge foreign exchange expenditures, but also involves the security and controllability of my country's financial industry. The difference between deploying financial systems in the localized version and deploying them in the X86 version lies in the different version dependencies and parameters: version dependency refers to other open sources that need to be introduced into the system, such as the X86 version needs to introduce the ojdbc database driver package; the localized version needs to introduce the GaussDriver database driver package, and because the Gauss database connection pool resources need to be customized, it is necessary to introduce Alibaba's Druid dependency package. The Druid package is an open source database connection pool project that can not only be used to create a connection pool, but also contains a series of JDBC (Java Data Base Connectivity) component libraries to support database operations; different parameters refer to the different parameter values ​​when configuring the same system on the localized version and the X86 version, such as the financial information system to be configured in this article, and the required servers are also different. In order to promote the localization of the infrastructure of the financial information system, this patent provides a method, device, computer equipment and storage medium for generating dependency packages that are compatible with dual versions of the financial system, which can meet the deployment of the financial system on the localized version and the X86 version, thereby ensuring the rapid iteration of the dual versions and accelerating the localization construction of the financial information system.

[0083] Figure 1It is a schematic diagram of the steps of the method for generating a compatible dual-version dependency package provided in the embodiments of this article. This specification provides the method operation steps described in the embodiments or flowcharts, but may include more or fewer operation steps based on conventional or non-creative labor. The order of steps listed in the embodiments is only one way of executing the steps among many orders, and does not represent the only order of execution. When the actual system or device product is executed, it can be executed in the order or in parallel according to the method shown in the embodiments or the drawings. Specifically, Figure 1 As shown, the method may include:

[0084] S100: Acquire the target code of the financial information system;

[0085] S200: Generate a POM file set, the POM file set including a first POM file and a second POM file, the first POM file corresponds to a first version of the financial information system, and the second POM file corresponds to a second version of the financial information system;

[0086] It should be noted that the above step S200 in this article is to perform mvn-profile management. The POM (Project Object Model) file is a tool for managing projects in Maven, and Maven is an open source project management tool and build automation tool written in pure Java. All project configuration information is defined in a file called POM.xml. Through this file, Maven can manage the entire life cycle of the project, including compilation, construction, testing, release, reporting, etc.

[0087] In this article, the first version of the financial information system refers to the X86 version of the financial information system, whose processor is based on the X86 architecture; the application server is based on non-open source application servers such as WebLogic, and WebLogic is a Java application server that can be used to develop, integrate, deploy and manage large-scale distributed Web applications, network applications and database applications; the operating system is based on UNIX or Linux; the database is based on Oracle, etc.

[0088] The WebLogic server compatible with the X86 version is a complex instruction set architecture that can handle big data analysis, but it has defects such as high heat generation, high power consumption, and high cost that do not meet future energy-saving and resource-saving requirements.

[0089] In this article, the second version of the financial information system refers to the localized version of the financial information system, that is, the version that can deploy the financial information system on ARM. Under this ARM version, the processor of the localized financial system can be based on the domestic CPU of the ARM architecture (for example, the 48-core Kunpeng 920 chip based on the ARM architecture); in the ARM version of the financial information system, the Tomcat open source component is mainly used. The Tomcat server is a free open source Web application server, which is a lightweight application server. Due to the advanced technology, stable performance and low power consumption of Tomcat, it is widely used in small and medium-sized systems and occasions where there are not many concurrent access users; it can use a localized operating system (for example, the Zhongbiao Kylin operating system, etc.); and it can use a localized database (for example, the Gauss database, etc.). The above-mentioned software basic environment is integrated together to form a full-stack localized environment that can support the actual application of the financial system.

[0090] S300: Determine the target deployment environment;

[0091] In this article, the target deployment environment refers to the application deployment environment of the above-mentioned financial information system on the X86 version, including the various secondary environments of the X86 version; and the application deployment environment of the financial information system on the ARM version, including the various secondary environments of the ARM version.

[0092] S400: Selecting a POM file corresponding to the target deployment environment from the POM file set;

[0093] S500: Packaging the POM file corresponding to the target deployment environment and the target code to generate a dependency package corresponding to the target deployment environment.

[0094] In this article, the dependent package refers to the war package on which the financial information system relies to be deployed on the X86 version or the ARM version.

[0095] In order to realize the continuous integration of financial information systems on X86 version and ARM version, this paper provides a method for generating dependency packages compatible with dual versions, which generates a POM file set including the first POM file and the second POM file. Therefore, after the target deployment environment is determined, the POM file that meets the corresponding deployment environment is directly selected to package the target code to generate a dependency package for deployment: when the target deployment environment is the X86 version and its secondary environment, the corresponding first POM file is selected to generate a dependency package that meets the X86 version deployment environment; when the target deployment environment is the ARM version and its secondary environment, the second POM file is selected to generate a dependency package that is compatible with the ARM version; no repeated processing is required.

[0096] In addition, the POM file collection is generated in advance, and there is no need to repeat processing according to different target deployment environments. Once the target deployment environment is determined, targeted calls are made directly from the POM file collection, which not only realizes deployment on dual versions, but also helps to improve deployment efficiency.

[0097] It should be noted that the dual-version compatible continuous integration method provided in this article also includes the following steps:

[0098] The dependent package is deployed in the target deployment environment to achieve continuous integration of the dependent package.

[0099] As the complexity of software development continues to increase, how to better collaborate among team members to ensure the quality of software development has gradually become an unavoidable issue in the development process. Especially in recent years, Agile has become increasingly popular in the field of software engineering. How to quickly adapt to and ensure the quality of software in the ever-changing needs has become particularly important. Continuous integration is a software development method that targets this type of problem.

[0100] In this article, the continuous integration mentioned above is a software development practice that is recognized and widely used in the industry. It is an essential component of agile development. It enables the work of the development team to be quickly integrated and verified, and problems that arise during the integration of the developed software are discovered in a timely manner.

[0101] In the embodiment of this article, step S100: obtaining the target code of the financial information system further includes:

[0102] S110: Acquire a dynamic view;

[0103] It should be noted that, in this article, the dynamic view is obtained by uploading the program code of the financial information system to the version control server. The program code of the financial information system refers to the program code written in a programming language and according to its rules for implementing the functions of the financial information system. In this article, the program code can be the Java code of the financial information system.

[0104] And herein, it is preferred that the program code is submitted to a CC (ClearCase) server to generate a CC dynamic view.

[0105] The CC server is a version control server that can be used for code modification. Since the system involves code changes (i.e. code modifications) when adjusting or upgrading functions, using a CC server can prevent code conflicts when modifying the code to maintain source code consistency.

[0106] S120: Acquire the source code of the financial information system according to the dynamic view;

[0107] The CC dynamic view is a path corresponding to the source code of the financial information system. Through the CC dynamic view, configuration managers, deployers or version publishers can obtain compiled codes corresponding to the source code of the financial information system.

[0108] CC dynamic view can automatically keep synchronized with the VOB library, use the MVFS (Multi-Version FileSystem) file system to transparently access the VOB library, do not occupy local space, and do not need to copy files to the local directory. It can access the versions in the VOB through the virtual file system, and provide the functions of sharing derived objects and building audits. MVFS is ClearCase's own file system, which can simulate file systems such as Window / UNIX, allowing VOB to appear as a directory or a drive letter. And it supports the use of Dynamic View. DynamicView uses MVFS to present selected local and remote files, as if these files were stored in the local file system.

[0109] It should be noted that, in this article, the source code of the financial information system obtained based on the dynamic view does not mean that the program code of the financial information system has been modified or otherwise processed. The obtained source code can be understood as a copy of the program code.

[0110] And S130: compile the source code to obtain the target code of the financial information system.

[0111] In a further embodiment, step S200: generating a POM file collection, the POM file collection including a first POM file and a second POM file, the first POM file corresponding to a first version of the financial information system, the second POM file corresponding to a second version of the financial information system, further includes:

[0112] Obtain first dependency configuration information and first database configuration information of the first version (ie, X86 version), and create a first POM file according to the first dependency configuration information and the first database configuration information;

[0113] Specifically, the first POM file generation method is as follows:

[0114] In the first POM file, use the dependencies tag to define the external open source Jar packages required in the first version;

[0115] The first database configuration information refers to the Java class required to connect to the database in the first version. For example, when generating the first POM file in this article, the first database configuration information required in the first POM file is defined through the ${DataSourceConnection} variable:

[0116] <datasourceconnection> JNDI< / datasourceconnection> ;

[0117] In addition, when generating the first POM file, this article also defines the first profile information in the first POM file.

[0118] The second POM file generation method is as follows:

[0119] Obtain second dependency configuration information and second database configuration information of the second version, and create a second POM file according to the second dependency configuration information and the second database configuration information.

[0120] The specific steps include:

[0121] In the second POM file, use the dependencies tag to define the external open source Jar package required in the second version (ie, ARM version) to define the second dependency configuration information;

[0122] The Java class required in the second POM file is also defined through the ${DataSourceConnection} variable to define the second database configuration information:

[0123] <datasourceconnection> NcisDruidI< / datasourceconnection> ;

[0124] It also includes defining the second profile information of the second POM file through the properties tag.

[0125] For example:

[0126] For the ARM version of the pl1 environment, the second profile information can be defined as follows:

[0127]

[0128] It should be noted that the above is only the definition of the second profile information in the second POM for one secondary environment in the ARM version, namely the pl1 environment. Of course, for other secondary environments of the ARM version, the definition of the second profile information in the second POM file will be different.

[0129] Moreover, in this article, the POM file collection includes a first POM file and a second POM file, which is only for the purpose of achieving compatible deployment of the financial information system on the X86 version and the ARM version, and achieving continuous integration on the above-mentioned dual systems. For deployment and continuous integration on other versions, the above-mentioned POM file collection may also include POM files that are compatible with the deployment environment of other versions.

[0130] In a further embodiment, step S400: selecting a POM file corresponding to the target deployment environment from the POM file set may further include:

[0131] S410: Acquire the environment parameters of the target deployment environment;

[0132] S420: Compare the environment parameters with the first file name of the first POM file and the second file name of the second POM file respectively; for example, the file name of the first POM file is pom.xml; the file name of the second POM file is pom-arm.xml.

[0133] S430: When the environment parameter information corresponds to the first file name of the first POM file, the first file name of the first POM file is specified by using the -f parameter, and the first POM file is selected by using the following command: mvn -fpom.xml;

[0134] Furthermore, for each level of secondary environment of X86, a -p parameter may be added to specify the first profile information defined in the first POM file, and variable replacement is performed according to the parameter value defined in the first profile information to select a POM file suitable for the corresponding X86 secondary environment; or

[0135] When the environment parameter information corresponds to the second file name of the second POM file, the -f parameter is used to select the second POM file; the following instruction: mvn-fpom-arm.xml is used to select the second POM file.

[0136] Furthermore, the -p parameter may be used to specify the profile name defined in the second POM file, and variable replacement may be performed according to the parameter value defined in the second profile information to obtain a POM file that complies with the corresponding ARM version secondary environment.

[0137] Herein, step S500: packaging the POM file corresponding to the target deployment environment and the target code to generate a dependency package corresponding to the target deployment environment, further includes:

[0138] S510: Determine whether packaging is successful;

[0139] When the corresponding dependency package (war package) is generated, the packaging is successful; otherwise, it means the packaging has failed;

[0140] S520: If packaging fails, a dependent package generation failure reminder message is sent.

[0141] For example: when the target environment parameter information obtained corresponds neither to the first file name of the first POM file nor to the second file name of the second POM file, and there is no corresponding relevant file name of other POM files, the email sending API (Application Programming Interface) is called to send a dependency package generation failure reminder message to the configuration management personnel, deployment personnel or version release personnel.

[0142] In a further embodiment, before the step of deploying the dependency package in the deployment environment to achieve continuous integration of the dependency package, uploading the dependency package is also included, specifically including:

[0143] Download the dependency package from the CC server to the local computer;

[0144] In this article, after the source code of the financial information system is submitted to the CC server, the subsequent generation of dynamic views and the compilation of the source code are all performed in the above CC server, and the server of the target deployment environment is different from the above configuration management server and needs to be transferred through the local environment.

[0145] And upload the dependent package from the local to the target deployment environment.

[0146] Further, the step of deploying the dependent package in the target deployment environment to continuously integrate the dependent package specifically includes:

[0147] Determining a server corresponding to the target deployment environment;

[0148] If the server is based on WebLogic server, then

[0149] Calling a deployment script of a server matching the target deployment environment, namely, a deployment script (WLST) of a WebLogic server, to deploy the dependency package in the currently running server;

[0150] WLST is a command-line scripting interface that system administrators and operators can use to monitor and manage WebLogic Server instances and domains. In this article, we use it to control and manage the server life cycle.

[0151] And restart the WebLogic server.

[0152] In this article, restarting the WebLogic server is achieved by calling weblogic related scripts: first calling the script that stops the server, and then calling the script that controls the startup of the server.

[0153] If the server is a Tomcat server, then

[0154] Unzip the dependency package and copy it to the path specified by the Tomcat server;

[0155] Modify the configuration information of the Tomcat server, including:

[0156] Modify Server.xml in tomcat; change Context path = "tomcat" to Context path = "URL name accessible to the application"; and change docBase = "tomcat / webapp" to docBase = "location where the application is deployed";

[0157] Restart the Tomcat server: first call the script used to stop the Tomcat server, and then call the script used to control the startup of the server. In this article, there will be no missing directories for dependencies, and only one release file needs to be managed, and it can be automatically recognized by the Tomcat server. After starting the server, you can run the project.

[0158] Furthermore, after the step of deploying the dependent package in the target deployment environment to continuously integrate the dependent package, the method further includes:

[0159] A server matching the target deployment environment is checked to obtain a check result.

[0160] For example, when it is determined that the server is a WebLogic server, it is necessary to check whether the parameter values ​​configured in config.xml are correct; verify whether the application Url (Uniform Resource Locator) is accessible; and whether the parameters of the application memory settings are correct, etc.

[0161] When it is determined that the server is a Tomcat server, the corresponding checks include: checking whether the configuration file information in server.xml is correct; verifying whether the application Url is accessible; whether the parameters of the application memory setting are correct, and other check items not included in it may also be included.

[0162] That is, the above-mentioned checking process is used to determine whether the dependent package is successfully deployed in the target deployment environment. Therefore, step: checking the server matching the target deployment environment also includes:

[0163] According to the inspection results of each inspection item in the above inspection process, determine whether the dependent package is successfully deployed in the target deployment environment;

[0164] If it fails, the email API is called to send a deployment failure reminder.

[0165] Through the above method, technical personnel in this field can obtain dependency packages of financial information systems that are compatible with and deployed on X86 and ARM versions, and thus can achieve continuous integration of financial information systems on the above dual versions. This is of great significance for verifying the reliability and stability of domestically produced financial information systems and trading platforms, so as to fully realize the localization of financial information systems.

[0166] Preferably, the Jenkins one-click deployment tool is selected in this article to complete packaging, transmission of dependent packages, application deployment in the target deployment environment, and notification of deployment results.

[0167] like Figure 2 As shown, based on the same inventive concept, on the basis of the above-mentioned method for generating a dependency package compatible with two versions, the embodiment of this invention also provides a device for generating a dependency package compatible with two versions, such as Figure 2 As shown, the device comprises:

[0168] An acquisition module 21, used for acquiring the target code of the financial information system;

[0169] A generating module 22, configured to generate a POM file set, wherein the POM file set includes a first POM file and a second POM file, wherein the first POM file corresponds to a first version of the financial information system, and the second POM file corresponds to a second version of the financial information system;

[0170] A determination module 23, used to determine a target deployment environment;

[0171] A selection module 24, configured to select a POM file corresponding to the target deployment environment from the POM file set;

[0172] The packaging module 25 is used to package the POM file corresponding to the target deployment environment and the target code to generate a dependency package corresponding to the target deployment environment.

[0173] like Figure 3As shown, a computer device provided in an embodiment of this invention is shown. The computer device 302 may include one or more processors 304, such as one or more central processing units (CPUs), and each processing unit may implement one or more hardware threads.

[0174] The computer device 302 may also include any memory 306 for storing any kind of information such as code, settings, data, etc. Without limitation, for example, the memory 306 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent a fixed or removable component of the computer device 302. In one case, when the processor 304 executes an associated instruction stored in any memory or combination of memories, the computer device 302 may perform any operation of the associated instruction. The computer device 302 also includes one or more drive mechanisms 308 for interacting with any memory, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0175] The computer device 302 may also include an input / output module 310 (I / O) for receiving various inputs (via input devices 312) and for providing various outputs (via output devices 314). A specific output mechanism may include a presentation device 316 and an associated graphical user interface (GUI) 318. In other embodiments, the input / output module 310 (I / O), the input device 312, and the output device 314 may not be included, and the computer device 302 may be used as a computer device in a network. The computer device 302 may also include one or more network interfaces 320 for exchanging data with other devices via one or more communication links 322. One or more communication buses 324 couple the components described above together.

[0176] The communication link 322 may be implemented in any manner, for example, via a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 322 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols. Figure 1 The method in this article also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

[0177] The embodiment of the present invention also provides a computer readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figure 1The method shown.

[0178] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0179] It should also be understood that in the embodiments of this article, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0180] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this article.

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

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

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

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

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

[0186] Specific embodiments are used in this article to illustrate the principles and implementation methods of this article. The description of the above embodiments is only used to help understand the methods and core ideas of this article. At the same time, for general technicians in this field, according to the ideas of this article, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on this article.

Claims

1. A method for generating a dependency package compatible with two versions, characterized in that: include: Acquiring the target code of the financial information system, including: acquiring a dynamic view; acquiring the source code of the financial information system according to the dynamic view; compiling the source code to acquire the target code of the financial information system; Obtain first dependency configuration information and first database configuration information of a first version, generate a first POM file according to the first dependency configuration information and the first database configuration information, and the first version is an X86 version; obtain second dependency configuration information and second database configuration information of a second version, generate a second POM file according to the second dependency configuration information and the second database configuration information, and the second version is an ARM version; the first POM file and the second POM file constitute a POM file set; Determine the target deployment environment; Selecting a POM file corresponding to the target deployment environment from the POM file set; The POM file corresponding to the target deployment environment and the target code are packaged to generate a dependency package corresponding to the target deployment environment.

2. According to the method for generating a dependency package compatible with two versions according to claim 1, it is characterized in that: Also includes: The dependent package is deployed in the target deployment environment to perform continuous integration on the dependent package.

3. A method for generating a dependency package compatible with two versions according to claim 2, characterized in that: The deploying the dependent package in the target deployment environment includes: Calling a deployment script of a server that matches the target deployment environment, and deploying the dependent package in the server; Restart the server.

4. A method for generating a dependency package compatible with two versions according to claim 2, characterized in that: The step of deploying the dependency package in the target deployment environment includes: Decompress the dependency package and copy it to a path of a server that matches the target deployment environment; Modifying the configuration information of the server; Restart the server.

5. A method for generating a dependency package compatible with two versions according to any one of claims 3 or 4, characterized in that: The step of deploying the dependent package in the target deployment environment to continuously integrate the dependent package further includes: A server matching the target deployment environment is checked to obtain a check result.

6. A method for generating a dependency package compatible with two versions according to claim 5, characterized in that: The checking of the server matching the target deployment environment includes: Check whether the configuration parameters of the server are correct; Check whether the uniform resource locator of the server is accessible; Check whether the memory setting parameters of the server are correct.

7. A method for generating a dependency package compatible with two versions according to claim 5, characterized in that: The method further comprises: According to the inspection result, determine whether the dependent package is successfully deployed in the target deployment environment; If it fails, a deployment failure reminder message will be sent.

8. The method for generating a dependency package compatible with two versions according to claim 1, characterized in that: The selecting a POM file corresponding to the target deployment environment from the POM file set includes: Obtaining environmental parameters of the target deployment environment; Compare the environment parameter with the first file name of the first POM file and the second file name of the second POM file respectively; When the environment parameter corresponds to the first file name of the first POM file, selecting the first POM file; When the environment parameter corresponds to the second file name of the second POM file, the second POM file is selected.

9. A method for generating a dependency package compatible with two versions according to claim 1, characterized in that: Also includes: The step of packaging the POM file corresponding to the target deployment environment and the target code to generate a dependency package corresponding to the target deployment environment further includes: Determine whether the packaging is successful; If packaging fails, a reminder message indicating that the dependent package generation failed will be sent.

10. A method for generating a dependency package compatible with two versions according to claim 2, characterized in that: Before deploying the dependent package in the target deployment environment, the method further includes: Download the dependency package to local; Upload the dependent package from the local to the target deployment environment.

11. A device for generating a dependency package compatible with two versions, characterized in that: include: An acquisition module, used to acquire the target code of the financial information system, including: acquiring a dynamic view; acquiring the source code of the financial information system according to the dynamic view; compiling the source code to acquire the target code of the financial information system; A generation module is used to obtain first dependency configuration information and first database configuration information of a first version, and generate a first POM file according to the first dependency configuration information and the first database configuration information, wherein the first version is an X86 version; obtain second dependency configuration information and second database configuration information of a second version, and generate a second POM file according to the second dependency configuration information and the second database configuration information, wherein the second version is an ARM version, and the first POM file and the second POM file constitute a POM file set; A determination module, used to determine the target deployment environment; A selection module, used to select a POM file corresponding to the target deployment environment from the POM file set; The packaging module is used to package the POM file corresponding to the target deployment environment and the target code to generate a dependency package corresponding to the target deployment environment.

12. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for generating a dependency package compatible with two versions as described in any one of claims 1 to 10 is implemented.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores an executable computer program, and when the computer program is executed by a processor, the method for generating a dependent package compatible with dual versions as described in any one of claims 1 to 10 is implemented.

Images