Distributed task scheduling framework project code deployment method, equipment and medium

Abstract

The invention relates to the technical field of computers, and provides a distributed task scheduling framework project code deployment method and device and a medium, which can associate a distributed task scheduling framework project code with a preset code hosting website so as to facilitate centralized management of the project code and avoid data loss. When an operation request of at least one target user for the target project code in the preset code hosting website is received, each target user is authenticated, and the target user passing the authentication is allowed to change the target project code, so that the security is improved; the change data of the target project code is monitored based on the real-time data pushing mechanism, and the target project code is deployed according to the change data and the branch management mechanism, so that automatic deployment without manual intervention is realized, mistransmission can be effectively avoided, the branch management mechanism ensures the code coverage problem during multi-person collaborative development, and the development efficiency is improved. And the development efficiency and the system stability are improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a distributed task scheduling framework project code deployment method, device and medium. Background Art

[0002] In the existing technology, the project code management and deployment solutions for distributed task scheduling frameworks (such as Azkaban) mainly have the following problems:

[0003] (1) When multiple people collaborate, the uploaded zip file may overwrite other people's modifications, affecting the correctness of task scheduling.

[0004] (2) Manual operations carry the risk of miscommunication. Uploading files from one project to another can cause huge problems.

[0005] (3) When the local disk or the server of the distributed task scheduling framework fails, code data may be lost, affecting task operation.

[0006] (4) It is difficult to trace back the historical status during code debugging, which affects problem investigation and tracing. Summary of the Invention

[0007] In view of the above, it is necessary to provide a distributed task scheduling framework project code deployment method, device and medium, aiming to solve the problems of abnormal overwriting, miscommunication and data loss in the distributed task scheduling framework project code deployment process.

[0008] A distributed task scheduling framework project code deployment method, the distributed task scheduling framework project code deployment method comprising:

[0009] Obtaining a distributed task scheduling framework project code, and associating the distributed task scheduling framework project code with a preset code hosting website;

[0010] When receiving an operation request from at least one target user for the target project code in the preset code hosting website, authenticating each target user and allowing the authenticated target user to change the target project code;

[0011] The target project code is monitored for change data based on a real-time data push mechanism, and the target project code is deployed according to the change data and a branch management mechanism.

[0012] According to a preferred embodiment of the present invention, associating the distributed task scheduling framework project code with a preset code hosting website includes:

[0013] Query the distributed task scheduling framework database to obtain project information of all distributed task scheduling framework projects;

[0014] Calling the distributed task scheduling framework interface to obtain the compressed files of all the distributed task scheduling framework projects, and decompressing the compressed files to obtain decompressed files;

[0015] Creating a local repository for storing the project information and the decompressed files, and creating a remote repository through the corresponding interface of the preset code hosting website;

[0016] Associating the local warehouse with the remote warehouse, and pushing the project information and the decompressed file from the local warehouse to the remote warehouse;

[0017] Wherein, in the remote warehouse, each distributed task scheduling framework project corresponds to a folder.

[0018] According to a preferred embodiment of the present invention, before authenticating each target user, the method further includes:

[0019] Associating the preset code hosting website with single sign-on and assigning each user a unique code hosting website login account; and

[0020] Through the preset code hosting website, members are added to the member list of each distributed task scheduling framework project according to user needs, and permissions are configured for each member; wherein, when a change to a first member is detected, the permissions of the first member are updated according to the type of change; when a second member is detected to have left the corresponding distributed task scheduling framework project, the second member is removed from the member list of the corresponding distributed task scheduling framework project, so that the second member does not have the operation permission for the corresponding distributed task scheduling framework project.

[0021] According to a preferred embodiment of the present invention, deploying the target project code according to the change data and branch management mechanism includes:

[0022] Calling the login interface of the preset code hosting website to log in to the preset code hosting website;

[0023] Creating an interface access token required by the real-time data push mechanism through the preset code hosting website, and calling a corresponding interface based on the interface access token to configure the real-time data push mechanism; wherein the real-time data push mechanism includes the items to be monitored, the monitoring time, and the events to be monitored;

[0024] Monitor the change requests and change types pushed by the real-time data push mechanism through a designated program;

[0025] When a change in the target project code is detected, a target folder is created locally and / or in the cloud, and the historical project code corresponding to the target project code in the distributed task scheduling framework is backed up to the target folder;

[0026] The target project code is deployed according to the change type.

[0027] According to a preferred embodiment of the present invention, deploying the target project code according to the change type includes:

[0028] When the change type is deletion, deleting the target project code in the distributed task scheduling framework according to the change request; or

[0029] When the change type is modification and / or merging, download the latest code after modifying and / or merging the target project code from the preset code hosting website; package the latest code in the corresponding code download directory to obtain a file to be uploaded; upload the file to be uploaded to the distributed task scheduling framework for deployment; or

[0030] When the change type is new addition, the new code is downloaded from the preset code hosting website; the new code is packaged in the corresponding code download directory to obtain the file to be uploaded; a folder with the same name as the file to be uploaded is created in the distributed task scheduling framework, and the file to be uploaded is uploaded to the folder with the same name for deployment.

[0031] According to a preferred embodiment of the present invention, deploying the target project code according to the change data and branch management mechanism further includes:

[0032] When receiving operation requests for the target project code in the preset code hosting website from multiple target users, allowing the target project code to be deployed if it is detected that there is no conflict in the remote repository; and

[0033] When operation requests for the target project code in the preset code hosting website are received from multiple target users, the login interface of the preset code hosting website is called to log in to the preset code hosting website; the interface access token required by the real-time data push mechanism is created through the preset code hosting website, and the corresponding interface is called based on the interface access token to configure the real-time data push mechanism, wherein the real-time data push mechanism includes branches to be collaborated, projects to be monitored, monitoring time, and events to be monitored; and the change requests and change types of the branches pushed by the real-time data push mechanism are monitored through a specified program.

[0034] According to a preferred embodiment of the present invention, after deploying the target project code according to the change data and branch management mechanism, the method further includes:

[0035] When a rollback request for the target project code is received, querying the initial version code in the preset code hosting website according to the initial code identifier of the target project code;

[0036] Roll back the initial version code.

[0037] A distributed task scheduling framework project code deployment device, the distributed task scheduling framework project code deployment device comprising:

[0038] An associating unit, configured to obtain a distributed task scheduling framework project code and associate the distributed task scheduling framework project code with a preset code hosting website;

[0039] an authentication unit, configured to, upon receiving an operation request from at least one target user for a target project code in the preset code hosting website, authenticate each target user and allow the authenticated target user to modify the target project code;

[0040] The deployment unit is used to monitor the change data of the target project code based on a real-time data push mechanism, and deploy the target project code according to the change data and a branch management mechanism.

[0041] A computer device, comprising:

[0042] a memory storing at least one instruction; and

[0043] The processor executes the instructions stored in the memory to implement the distributed task scheduling framework project code deployment method.

[0044] A computer-readable storage medium stores at least one instruction, and the at least one instruction is executed by a processor in a computer device to implement the distributed task scheduling framework project code deployment method.

[0045] It can be seen from the above technical solutions that the present invention can obtain the distributed task scheduling framework project code and associate the distributed task scheduling framework project code with the preset code hosting website, so as to centrally manage the project code and avoid data loss; when receiving an operation request from at least one target user for the target project code in the preset code hosting website, each target user is authenticated, and the authenticated target user is allowed to change the target project code, thereby improving security; based on the real-time data push mechanism, the change data of the target project code is monitored, and the target project code is deployed according to the change data and the branch management mechanism, thereby realizing automatic deployment without human intervention, which can effectively avoid miscommunication. The branch management mechanism also ensures code coverage during collaborative development by multiple people, and improves development efficiency and system stability. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 It is a flowchart of a preferred embodiment of the distributed task scheduling framework project code deployment method of the present invention.

[0047] Figure 2 It is a functional module diagram of a preferred embodiment of the distributed task scheduling framework project code deployment device of the present invention.

[0048] Figure 3 It is a structural diagram of a computer device of a preferred embodiment of the present invention for implementing a distributed task scheduling framework project code deployment method. DETAILED DESCRIPTION

[0049] In order to make the objectives, technical solutions and advantages of the present invention more clear, the present invention is described in detail below with reference to the accompanying drawings and specific embodiments.

[0050] like Figure 1 FIG. 1 is a flow chart of a preferred embodiment of a distributed task scheduling framework project code deployment method of the present invention. The order of the steps in the flow chart may be changed and some steps may be omitted according to different requirements.

[0051] The distributed task scheduling framework project code deployment method is applied to one or more computer devices, which are devices that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions. Their hardware includes but is not limited to microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0052] The computer device can be any electronic product that can interact with a user, such as a personal computer, a tablet computer, a smart phone, a personal digital assistant (PDA), a game console, an interactive network television (IPTV), a smart wearable device, etc.

[0053] The computer device may also include a network device and / or a user device, wherein the network device includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of hosts or network servers.

[0054] The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0055] Among them, artificial intelligence (AI) is the theory, method, technology and application system that uses digital computers or machines controlled by digital computers to simulate, extend and expand human intelligence, perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0056] Fundamental AI technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interaction systems, and mechatronics. AI software technologies primarily encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0057] The network where the computer device is located includes but is not limited to the Internet, wide area network, metropolitan area network, local area network, virtual private network (VPN), etc.

[0058] S10: Obtain a distributed task scheduling framework project code, and associate the distributed task scheduling framework project code with a preset code hosting website.

[0059] In this embodiment, the distributed task scheduling framework may be Azkaban.

[0060] In this embodiment, associating the distributed task scheduling framework project code with a preset code hosting website includes:

[0061] Query the distributed task scheduling framework database to obtain project information of all distributed task scheduling framework projects;

[0062] Calling the distributed task scheduling framework interface to obtain the compressed files of all the distributed task scheduling framework projects, and decompressing the compressed files to obtain decompressed files;

[0063] Creating a local repository for storing the project information and the decompressed files, and creating a remote repository through the corresponding interface of the preset code hosting website;

[0064] Associating the local warehouse with the remote warehouse, and pushing the project information and the decompressed file from the local warehouse to the remote warehouse;

[0065] Wherein, in the remote warehouse, each distributed task scheduling framework project corresponds to a folder.

[0066] The project information may include, but is not limited to, one or a combination of the following:

[0067] Project identification information, code hosting repository address, instance link, dependent external systems, etc.

[0068] The compressed file may be a zip file.

[0069] Through the above embodiment, a dedicated warehouse for the distributed task scheduling framework project can be created in the code hosting website, ensuring centralized management of the code while avoiding code loss.

[0070] S11, when receiving an operation request from at least one target user for the target project code in the preset code hosting website, authenticate each target user and allow the authenticated target user to change the target project code.

[0071] In this embodiment, the operation request may include, but is not limited to: adding, deleting, modifying, merging and other operations.

[0072] In this embodiment, before authenticating each target user, the method further includes:

[0073] Associating the preset code hosting website with Single Sign On (SSO) and assigning each user a unique code hosting website login account; and

[0074] Through the preset code hosting website, members are added to the member list of each distributed task scheduling framework project according to user needs, and permissions are configured for each member; wherein, when a change to a first member is detected, the permissions of the first member are updated according to the type of change; when a second member is detected to have left the corresponding distributed task scheduling framework project, the second member is removed from the member list of the corresponding distributed task scheduling framework project, so that the second member does not have the operation permission for the corresponding distributed task scheduling framework project.

[0075] Among them, login security can be improved by associating single sign-on.

[0076] The existing distributed task scheduling framework's built-in permission model doesn't meet the requirements of actual project management. For example, one or more teams often log in using the same Azkaban account. This can lead to significant security risks when team members change, as members who have left the team can still perform dangerous operations such as modifying or deleting projects simply by knowing the account password.

[0077] To address the above issues, this embodiment configures user permissions through the preset code hosting website so that ordinary users do not have the permission to modify or delete projects. In addition, each team member has his or her own account. When he or she leaves the team, he or she only needs to be removed from the project's member management, which effectively improves the security of the project code.

[0078] Moreover, since each team member has his or her own account, it is clear at a glance which codes were developed and modified by whom. The responsible person can be traced through the code submission record, and the code can be reviewed, which improves code quality and project stability.

[0079] S12: Monitor the change data of the target project code based on a real-time data push mechanism, and deploy the target project code according to the change data and a branch management mechanism.

[0080] In this embodiment, the real-time data push mechanism (i.e., Webhook) is a lightweight communication mechanism based on HTTP (Hypertext Transfer Protocol) callback. Its core function is to allow one system to actively send data to another system when a specific event occurs, thereby realizing "event-driven real-time notification", which can be understood as a "real-time messenger between systems."

[0081] The real-time data push mechanism can transform passive data into active data sending, which is particularly suitable for scenarios that require automation and high real-time performance.

[0082] In this embodiment, deploying the target project code according to the change data and branch management mechanism includes:

[0083] Calling the login interface of the preset code hosting website to log in to the preset code hosting website;

[0084] Creating an interface access token required by the real-time data push mechanism through the preset code hosting website, and calling a corresponding interface based on the interface access token to configure the real-time data push mechanism; wherein the real-time data push mechanism includes the items to be monitored, the monitoring time, and the events to be monitored;

[0085] Monitor the change requests and change types pushed by the real-time data push mechanism through a designated program;

[0086] When a change in the target project code is detected, a target folder is created locally and / or in the cloud, and the historical project code corresponding to the target project code in the distributed task scheduling framework is backed up to the target folder;

[0087] The target project code is deployed according to the change type.

[0088] Through the above embodiments, automatic backup and deployment of project codes can be achieved, deployment without manual intervention can be achieved, deployment efficiency is improved, and data upload errors can be avoided.

[0089] In this embodiment, deploying the target project code according to the change type includes:

[0090] When the change type is deletion, deleting the target project code in the distributed task scheduling framework according to the change request; or

[0091] When the change type is modification and / or merging, download the latest code after modifying and / or merging the target project code from the preset code hosting website; package the latest code in the corresponding code download directory to obtain a file to be uploaded; upload the file to be uploaded to the distributed task scheduling framework for deployment; or

[0092] When the change type is new addition, the new code is downloaded from the preset code hosting website; the new code is packaged in the corresponding code download directory to obtain the file to be uploaded; a folder with the same name as the file to be uploaded is created in the distributed task scheduling framework, and the file to be uploaded is uploaded to the folder with the same name for deployment.

[0093] Through the above embodiments, different processing solutions can be executed according to different change types.

[0094] This embodiment can trigger an automated script based on the code hosting website Webhook, parse code changes, package and back up the project, and upload the corresponding code module to a distributed task scheduling framework such as Azkaban, thereby realizing automated project code deployment without manual intervention.

[0095] In this embodiment, deploying the target project code according to the change data and branch management mechanism further includes:

[0096] When receiving operation requests for the target project code in the preset code hosting website from multiple target users, allowing the target project code to be deployed if it is detected that there is no conflict in the remote repository; and

[0097] When operation requests for the target project code in the preset code hosting website are received from multiple target users, the login interface of the preset code hosting website is called to log in to the preset code hosting website; the interface access token required by the real-time data push mechanism is created through the preset code hosting website, and the corresponding interface is called based on the interface access token to configure the real-time data push mechanism, wherein the real-time data push mechanism includes branches to be collaborated, projects to be monitored, monitoring time, and events to be monitored; and the change requests and change types of the branches pushed by the real-time data push mechanism are monitored through a specified program.

[0098] For example, when multiple people collaborate on the same project, using the code hosting website mechanism, multiple developers must first resolve conflicts in remote repositories before they can successfully submit the code, which normally triggers the automatic packaging and deployment of the project mentioned in this embodiment to the distributed task scheduling framework, thereby effectively avoiding the problem of code overwriting each other during collaborative development by multiple people.

[0099] Through the above embodiments, multi-person collaborative development can be supported based on the branch management mechanism of the code hosting website, effectively avoiding the code coverage problem.

[0100] Currently, achieving goals on the first try during project development is difficult, often requiring multiple revisions and debugging, or even rollbacks. However, traditional project deployment methods for distributed task scheduling frameworks like Azkaban don't reflect historical updates and modification status. Furthermore, the debugging phase involves a large amount of repetitive tasks like decompression, downloading, and packaging and uploading, which is labor-intensive and prone to errors. This is especially true when modifications encounter anomalies and require rolling back to a stable historical version and re-development.

[0101] Therefore, in this embodiment, after deploying the target project code according to the change data and branch management mechanism, the method further includes:

[0102] When a rollback request for the target project code is received, querying the initial version code in the preset code hosting website according to the initial code identifier of the target project code;

[0103] Roll back the initial version code.

[0104] Through the above embodiment, when a rollback is required, the original code version can be directly queried from the preset code hosting website and rolled back, which effectively reduces the workload and is less likely to cause exceptions, thereby improving code quality and project stability.

[0105] In this embodiment, based on the submission record and labeling mechanism of the preset code hosting website, information such as the operator, operation record, and operation time can be recorded for each code change, thereby supporting problem backtracking, improving debugging efficiency, and being able to clarify responsibility and locate problems during code review, thereby improving code quality and project stability.

[0106] This embodiment is based on the CI / CD (Continuous Delivery / Continuous Deployment) function of the extensible code hosting website, and realizes the automated deployment of the distributed task scheduling framework project code. Developers can focus on modifying the code, that is, they only need to submit the code, and the rest of the actions can be automatically executed according to this embodiment. It effectively solves the collaboration, version tracking and data security issues in traditional code management such as Azkaban, and improves development efficiency and system stability.

[0107] It can be seen from the above technical solutions that the present invention can obtain the distributed task scheduling framework project code and associate the distributed task scheduling framework project code with the preset code hosting website, so as to centrally manage the project code and avoid data loss; when receiving an operation request from at least one target user for the target project code in the preset code hosting website, each target user is authenticated, and the authenticated target user is allowed to change the target project code, thereby improving security; based on the real-time data push mechanism, the change data of the target project code is monitored, and the target project code is deployed according to the change data and the branch management mechanism, thereby realizing automatic deployment without human intervention, which can effectively avoid miscommunication. The branch management mechanism also ensures code coverage during collaborative development by multiple people, and improves development efficiency and system stability.

[0108] like Figure 2, which is a functional module diagram of a preferred embodiment of the distributed task scheduling framework project code deployment device of the present invention. The distributed task scheduling framework project code deployment device 11 includes an association unit 110, an authentication unit 111, and a deployment unit 112. The module / unit referred to in the present invention refers to a series of computer program segments that can be executed by a processor and can perform fixed functions, which are stored in a memory. In this embodiment, the functions of each module / unit will be described in detail in subsequent embodiments.

[0109] The associating unit 110 is configured to obtain a distributed task scheduling framework project code and associate the distributed task scheduling framework project code with a preset code hosting website;

[0110] The authentication unit 111 is configured to authenticate each target user upon receiving an operation request from at least one target user for the target project code in the preset code hosting website, and allow the authenticated target user to change the target project code;

[0111] The deployment unit 112 is configured to monitor the target project code's change data based on a real-time data push mechanism, and deploy the target project code according to the change data and a branch management mechanism.

[0112] It can be seen from the above technical solutions that the present invention can obtain the distributed task scheduling framework project code and associate the distributed task scheduling framework project code with the preset code hosting website, so as to centrally manage the project code and avoid data loss; when receiving an operation request from at least one target user for the target project code in the preset code hosting website, each target user is authenticated, and the authenticated target user is allowed to change the target project code, thereby improving security; based on the real-time data push mechanism, the change data of the target project code is monitored, and the target project code is deployed according to the change data and the branch management mechanism, thereby realizing automatic deployment without human intervention, which can effectively avoid miscommunication. The branch management mechanism also ensures code coverage during collaborative development by multiple people, and improves development efficiency and system stability.

[0113] like Figure 3 , which is a structural diagram of a computer device according to a preferred embodiment of the present invention for implementing a distributed task scheduling framework project code deployment method.

[0114] The computer device 1 may include a memory 12, a processor 13 and a bus (the arrow in the figure represents the bus), and may also include a computer program stored in the memory 12 and executable on the processor 13, such as a distributed task scheduling framework project code deployment program.

[0115] Those skilled in the art will understand that the schematic diagram is merely an example of the computer device 1 and does not constitute a limitation on the computer device 1. The computer device 1 may have either a bus structure or a star structure. The computer device 1 may also include more or less other hardware or software than shown in the figure, or a different arrangement of components. For example, the computer device 1 may also include input and output devices, network access devices, etc.

[0116] It should be noted that the computer device 1 is only an example. Other existing or future electronic products that are suitable for the present invention should also be included in the scope of protection of the present invention and included here by reference.

[0117] Among them, the memory 12 includes at least one type of readable storage medium, and the readable storage medium includes a flash memory, a mobile hard disk, a multimedia card, a card-type memory (for example, SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 12 can be an internal storage unit of the computer device 1, such as a mobile hard disk of the computer device 1. In other embodiments, the memory 12 can also be an external storage device of the computer device 1, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the computer device 1. Furthermore, the memory 12 can also include both an internal storage unit of the computer device 1 and an external storage device. The memory 12 can not only be used to store application software and various types of data installed on the computer device 1, such as the code of the distributed task scheduling framework project code deployment program, but can also be used to temporarily store data that has been output or is to be output.

[0118] In some embodiments, the processor 13 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and a combination of various control chips. The processor 13 is the control core (Control Unit) of the computer device 1, connecting the various components of the entire computer device 1 using various interfaces and lines. It executes the various functions of the computer device 1 and processes data by running or executing programs or modules stored in the memory 12 (for example, executing the distributed task scheduling framework project code deployment program, etc.), and calling data stored in the memory 12.

[0119] The processor 13 executes the operating system of the computer device 1 and various installed applications. The processor 13 executes the applications to implement the steps in the above-mentioned embodiments of the distributed task scheduling framework project code deployment method, for example Figure 1 Steps shown.

[0120] Exemplarily, the computer program may be divided into one or more modules / units, which are stored in the memory 12 and executed by the processor 13 to implement the present invention. The one or more modules / units may be a series of computer-readable instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the computer device 1. For example, the computer program may be divided into an association unit 110, an authentication unit 111, and a deployment unit 112.

[0121] The above-mentioned integrated unit implemented in the form of a software functional module can be stored in a computer-readable storage medium. The above-mentioned software functional module stored in a storage medium includes a number of instructions for causing a computer device (which can be a personal computer, computer equipment, or network equipment, etc.) or a processor to execute the portion of the distributed task scheduling framework project code deployment method described in various embodiments of the present invention.

[0122] If the modules / units integrated in the computer device 1 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the present invention can also implement all or part of the processes in the above-mentioned method embodiments by instructing relevant hardware devices through a computer program. The computer program can be stored in a computer-readable storage medium. When executed by a processor, the computer program can implement the steps of each of the above-mentioned method embodiments.

[0123] The computer program includes computer program code, which may be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium may include any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a mobile hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory, etc.

[0124] Furthermore, the computer-readable storage medium may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function, etc.; the data storage area may store data created according to the use of the blockchain node, etc.

[0125] Blockchain, as used in this article, refers to a novel application model for computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Blockchain is essentially a decentralized database, a series of data blocks generated using cryptographic methods. Each block contains information about a batch of online transactions, used to verify the validity of this information (to prevent counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, the platform product service layer, and the application service layer.

[0126] The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 The figure shows that only one straight line is used, but it does not mean that there is only one bus or one type of bus. The bus is configured to realize the connection and communication between the memory 12 and at least one processor 13.

[0127] Although not shown, the computer device 1 may also include a power supply (such as a battery) to power various components. Preferably, the power supply can be logically connected to the at least one processor 13 via a power management device, thereby implementing functions such as charging management, discharging management, and power consumption management through the power management device. The power supply may also include one or more DC or AC power supplies, a recharging device, a power failure detection circuit, a power converter or inverter, a power status indicator, and other arbitrary components. The computer device 1 may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be detailed here.

[0128] Furthermore, the computer device 1 may also include a network interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is usually used to establish a communication connection between the computer device 1 and other computer devices.

[0129] Optionally, the computer device 1 may further include a user interface, which may be a display or an input unit (such as a keyboard). Optionally, the user interface may also be a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. The display may also be appropriately referred to as a display screen or a display unit, and is used to display information processed in the computer device 1 and to display a visual user interface.

[0130] It should be understood that the embodiment is for illustration only and the scope of the patent application is not limited to this structure.

[0131] It will be understood by those skilled in the art that Figure 3 The structure shown does not constitute a limitation on the computer device 1 , and may include fewer or more components than shown in the figure, or combine certain components, or arrange the components differently.

[0132] Combine Figure 1 The memory 12 in the computer device 1 stores a plurality of instructions to implement a distributed task scheduling framework project code deployment method, and the processor 13 can execute the plurality of instructions to implement:

[0133] Obtaining a distributed task scheduling framework project code, and associating the distributed task scheduling framework project code with a preset code hosting website;

[0134] When receiving an operation request from at least one target user for the target project code in the preset code hosting website, authenticating each target user and allowing the authenticated target user to change the target project code;

[0135] The target project code is monitored for change data based on a real-time data push mechanism, and the target project code is deployed according to the change data and a branch management mechanism.

[0136] Specifically, the specific implementation method of the processor 13 for the above instructions can refer to Figure 1 The description of the relevant steps in the corresponding embodiments will not be repeated here.

[0137] It should be noted that the data involved in this case were all obtained legally. The software tools or components not produced by our company that appear in the embodiments of this application are merely examples and do not represent actual use.

[0138] In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the module division is merely a logical functional division, and actual implementation may employ other division methods.

[0139] The present invention can be used in a wide variety of general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like. The present invention can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present invention can also be practiced in distributed computing environments in which tasks are performed by remote processing devices connected via a communications network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

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

[0141] In addition, the functional modules in various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or hardware plus software functional modules.

[0142] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0143] Therefore, the embodiments should be considered in all respects as illustrative and non-restrictive, and the scope of the invention is defined by the appended claims rather than the foregoing description, and all changes that come within the meaning and range of equivalents of the claims are intended to be embraced therein. Any reference to a figure in a claim should not be construed as limiting the claim to which it relates.

[0144] Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices described in the present invention may also be implemented by a single unit or device through software or hardware. Terms such as first and second are used to indicate names and do not imply any particular order.

[0145] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not limiting. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solutions of the present invention may be modified or replaced by equivalents without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A distributed task scheduling framework project code deployment method, characterized in that: The distributed task scheduling framework project code deployment method includes: Obtaining a distributed task scheduling framework project code, and associating the distributed task scheduling framework project code with a preset code hosting website; When receiving an operation request from at least one target user for the target project code in the preset code hosting website, authenticating each target user and allowing the authenticated target user to change the target project code; The target project code is monitored for change data based on a real-time data push mechanism, and the target project code is deployed according to the change data and a branch management mechanism.

2. The distributed task scheduling framework project code deployment method according to claim 1, characterized in that: The associating the distributed task scheduling framework project code with a preset code hosting website includes: Query the distributed task scheduling framework database to obtain project information of all distributed task scheduling framework projects; Calling the distributed task scheduling framework interface to obtain the compressed files of all the distributed task scheduling framework projects, and decompressing the compressed files to obtain decompressed files; Creating a local repository for storing the project information and the decompressed files, and creating a remote repository through the corresponding interface of the preset code hosting website; Associating the local warehouse with the remote warehouse, and pushing the project information and the decompressed file from the local warehouse to the remote warehouse; Wherein, in the remote warehouse, each distributed task scheduling framework project corresponds to a folder.

3. The distributed task scheduling framework project code deployment method according to claim 1, characterized in that: Before authenticating each target user, the method further includes: Associating the preset code hosting website with single sign-on and assigning each user a unique code hosting website login account; and Through the preset code hosting website, members are added to the member list of each distributed task scheduling framework project according to user needs, and permissions are configured for each member; wherein, when a change to a first member is detected, the permissions of the first member are updated according to the type of change; when a second member is detected to have left the corresponding distributed task scheduling framework project, the second member is removed from the member list of the corresponding distributed task scheduling framework project, so that the second member does not have the operation permission for the corresponding distributed task scheduling framework project.

4. The distributed task scheduling framework project code deployment method according to claim 1, characterized in that: The deploying the target project code according to the change data and the branch management mechanism includes: Calling the login interface of the preset code hosting website to log in to the preset code hosting website; Creating an interface access token required by the real-time data push mechanism through the preset code hosting website, and calling a corresponding interface based on the interface access token to configure the real-time data push mechanism; wherein the real-time data push mechanism includes the items to be monitored, the monitoring time, and the events to be monitored; Monitor the change requests and change types pushed by the real-time data push mechanism through a designated program; When a change in the target project code is detected, a target folder is created locally and / or in the cloud, and the historical project code corresponding to the target project code in the distributed task scheduling framework is backed up to the target folder; The target project code is deployed according to the change type.

5. The distributed task scheduling framework project code deployment method according to claim 4, characterized in that: The deploying the target project code according to the change type includes: When the change type is deletion, deleting the target project code in the distributed task scheduling framework according to the change request; or When the change type is modification and / or merging, download the latest code after modifying and / or merging the target project code from the preset code hosting website; package the latest code in the corresponding code download directory to obtain a file to be uploaded; upload the file to be uploaded to the distributed task scheduling framework for deployment; or When the change type is new addition, the new code is downloaded from the preset code hosting website; the new code is packaged in the corresponding code download directory to obtain the file to be uploaded; a folder with the same name as the file to be uploaded is created in the distributed task scheduling framework, and the file to be uploaded is uploaded to the folder with the same name for deployment.

6. The distributed task scheduling framework project code deployment method according to claim 2, characterized in that: The deploying the target project code according to the change data and the branch management mechanism further includes: When receiving operation requests for the target project code in the preset code hosting website from multiple target users, allowing the target project code to be deployed if it is detected that there is no conflict in the remote repository; and When operation requests for the target project code in the preset code hosting website are received from multiple target users, the login interface of the preset code hosting website is called to log in to the preset code hosting website; the interface access token required by the real-time data push mechanism is created through the preset code hosting website, and the corresponding interface is called based on the interface access token to configure the real-time data push mechanism, wherein the real-time data push mechanism includes branches to be collaborated, projects to be monitored, monitoring time, and events to be monitored; and the change requests and change types of the branches pushed by the real-time data push mechanism are monitored through a specified program.

7. The distributed task scheduling framework project code deployment method according to claim 1, characterized in that: After deploying the target project code according to the change data and the branch management mechanism, the method further includes: When a rollback request for the target project code is received, querying the initial version code in the preset code hosting website according to the initial code identifier of the target project code; Roll back the initial version code.

8. A distributed task scheduling framework project code deployment device, characterized in that: The distributed task scheduling framework project code deployment device includes: An associating unit, configured to obtain a distributed task scheduling framework project code and associate the distributed task scheduling framework project code with a preset code hosting website; an authentication unit, configured to, upon receiving an operation request from at least one target user for a target project code in the preset code hosting website, authenticate each target user and allow the authenticated target user to modify the target project code; The deployment unit is used to monitor the change data of the target project code based on a real-time data push mechanism, and deploy the target project code according to the change data and a branch management mechanism.

9. A computer device, characterized in that: The computer device comprises: a memory storing at least one instruction; and A processor executes instructions stored in the memory to implement the distributed task scheduling framework project code deployment method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one instruction, and the at least one instruction is executed by a processor in a computer device to implement the distributed task scheduling framework project code deployment method as described in any one of claims 1 to 7.

Images