Data acquisition method and apparatus
By configuring a shared storage disk and declaring it as a PVC on the fat client, pipeline nodes can directly obtain the ClearCase server code from the shared storage disk, which solves the problems of instability and inefficiency in the existing technology and achieves fast and stable code acquisition and efficient continuous integration.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA CONSTRUCTION BANK
- Filing Date
- 2022-09-20
- Publication Date
- 2026-06-12
AI Technical Summary
In existing technologies, ClearCase code acquisition methods are unstable and inefficient, and are easily affected by network bandwidth, leading to reduced continuous integration efficiency and poor user experience.
Configure a shared storage disk on the fat client to store the target code synchronized from the ClearCase server, and declare the shared storage disk as a persistent volume and declare PVC through the storage middleware. The pipeline node mounts the PVC when initializing the Pod, so as to directly obtain the code from the shared storage disk and skip the secondary synchronization.
It enables fast and stable code retrieval, reduces retrieval time, improves the efficiency of continuous integration, avoids the impact of network fluctuations on the retrieval process, and ensures the value and significance of continuous integration.
Smart Images
Figure CN115480956B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of automatic programming technology, and in particular to a data acquisition method and device. Background Technology
[0002] ClearCase is a version control tool with a long history of use and is widely used in the financial industry. However, with the popularization of DevOps (a combination of Development and Operations) agile development concepts, the code in ClearCase also needs to be incorporated into continuous integration.
[0003] One current solution for adding ClearCase code to continuous integration is as follows: use Jenkins as the continuous integration tool, with the Jenkins job node being a Kubernetes pod. The fat client uses the Cleartool tool to create a view (mkview) to synchronize the code to the fat client. After the code is synchronized to the fat client's disk, a data mirroring backup tool such as rsync is used to synchronize the code to the pipeline job space. After the code synchronization is complete, the pipeline node executes subsequent job nodes according to the user-defined process.
[0004] However, the current solution has several drawbacks. For example, if network fluctuations occur during code synchronization by the data mirroring backup tool, synchronization will fail, forcing the entire pipeline to shut down. In other words, this solution for retrieving code from ClearCase is easily affected by network bandwidth, making it unstable. Furthermore, the current solution performs two synchronizations when retrieving code from ClearCase, inevitably increasing retrieval time and reducing the efficiency of continuous integration. Both this instability and low efficiency lead to a poor user experience, rendering continuous integration meaningless. Summary of the Invention
[0005] This application provides a data acquisition method and device to solve the technical problems of unstable code acquisition methods and low acquisition efficiency in the existing ClearCase technology.
[0006] Firstly, this application provides a data acquisition method, including:
[0007] The fat client synchronizes the target code from the ClearCase server based on the stream information and stores the target code to the shared storage disk;
[0008] When a pipeline node initializes a Pod, the Pod mounts a persistent volume (PVC) and the pipeline node retrieves the target code from the shared storage disk via a storage middleware.
[0009] The storage middleware is used to declare the shared storage disk as the PVC.
[0010] In one possible design, after the pipeline node obtains the target code, the following is also included:
[0011] The pipeline nodes execute pipeline operations using the target code according to the job requirements.
[0012] In one possible design, the fat client obtains the target code from the ClearCase server based on the streaming information, including:
[0013] The fat client creates associated views for the ClearCase server using binary tools;
[0014] The fat client synchronizes the target code from the ClearCase server based on the associated view and the stream information;
[0015] The flow information is used to identify the target code based on the pipeline operation.
[0016] In one possible design, when the pipeline operation is repeated, the method further includes: the fat client updating the created associated view.
[0017] In one possible design, the fat client stores the target code to the shared storage disk according to a shared directory.
[0018] In one possible design, both the fat client and the shared storage disk are configured on Linux machines, which are located in each development center.
[0019] In one possible design, the binary tool includes the Cleartool tool.
[0020] Secondly, this application provides a data acquisition device, comprising:
[0021] The first processing module is used to synchronize the target code from the ClearCase server according to the stream information and store the target code to the shared storage disk;
[0022] The second processing module is used to retrieve the target code from the shared storage disk via the storage middleware when the pipeline node initializes the Pod and the Pod mounts a persistent volume declaration PVC.
[0023] The storage middleware is used to declare the shared storage disk as the PVC.
[0024] In one possible design, the second processing module is further configured to:
[0025] Execute pipeline operations using the target code according to the job requirements.
[0026] In one possible design, the first processing module is specifically used for:
[0027] Create associated views for the ClearCase server using binary tools;
[0028] Synchronize the target code from the ClearCase server based on the associated view and the stream information;
[0029] The flow information is used to identify the target code based on the pipeline operation.
[0030] In one possible design, when the pipeline operation is repeated, the first processing module is further configured to: update the created associated view.
[0031] In one possible design, the first processing module is further configured to: store the target code to the shared storage disk according to the shared directory.
[0032] In one possible design, both the fat client and the shared storage disk are configured on Linux machines, which are located in each development center.
[0033] In one possible design, the binary tool includes the Cleartool tool.
[0034] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;
[0035] The memory stores computer-executed instructions;
[0036] The processor executes computer execution instructions stored in the memory to implement any of the possible data acquisition methods provided in the first aspect.
[0037] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement any of the possible data acquisition methods provided in the first aspect.
[0038] Fifthly, this application provides a computer program product, including computer execution instructions, which, when executed by a processor, are used to implement any of the possible data acquisition methods provided in the first aspect.
[0039] Sixthly, this application provides a data acquisition system, comprising:
[0040] A fat client, used to synchronize target code from the ClearCase server based on streaming information;
[0041] A shared storage disk is used to store the target code;
[0042] Storage middleware is used to declare the shared storage disk as a persistent volume (PVC).
[0043] Pipeline nodes are used to mount PVCs to the Pod during Pod initialization and to retrieve the target code from the shared storage disk via the storage middleware.
[0044] This application provides a data acquisition method and device. A fat client synchronizes target code from a ClearCase server based on streaming information and stores the synchronized target code on a shared storage disk. When a pipeline node initializes a Pod, the Pod mounts a PVC, allowing the pipeline node to retrieve the target code from the shared storage disk via a storage middleware, which declares the shared storage disk as a PVC. By mounting a PVC during Pod initialization and declaring the shared storage disk as a PVC through the storage middleware, the pipeline node's jobspace can directly access the target code from the ClearCase server via shared storage, eliminating the secondary synchronization required in existing technologies. This significantly reduces code retrieval time and enables fast and stable acquisition of the target code. Attached Figure Description
[0045] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0046] Figure 1 This is a schematic diagram of the structure of a data acquisition system provided in an embodiment of this application;
[0047] Figure 2 This is a schematic diagram of another data acquisition system provided in an embodiment of this application;
[0048] Figure 3 A flowchart illustrating a data acquisition method provided in an embodiment of this application;
[0049] Figure 4 A flowchart illustrating another data acquisition method provided in an embodiment of this application;
[0050] Figure 5 This is a schematic diagram of the structure of a data acquisition device provided in an embodiment of this application;
[0051] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0052] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of methods and apparatus consistent with some aspects of this application as detailed in the appended claims.
[0053] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0054] First, let me explain the terms used in this application:
[0055] ClearCase (abbreviated CC) is a software configuration management solution that provides tools for version control, workspace management, parallel development support, and build auditing.
[0056] Cleartool: A binary tool that provides views for creating, updating, ending, and deleting CCs;
[0057] Fat client: refers to a client that connects to the CC server and can create views and synchronize code in the CC server.
[0058] Continuous Integration (CI) refers to a pipeline process that can be automatically triggered based on preset conditions. This pipeline process includes nodes that retrieve code from the CC server, such as pipeline nodes.
[0059] One current solution for incorporating ClearCase code into continuous integration involves using Jenkins as the continuous integration tool, with Jenkins job nodes running as Kubernetes pods. A fat client uses the Cleartool tool to create a view (mkview) to synchronize the code to the fat client. After the code is synchronized to the fat client's disk, a data mirroring tool such as rsync is used to synchronize the code to the pipeline's job space. Once synchronization is complete, the pipeline nodes execute subsequent job nodes according to a user-defined process. However, this solution has several drawbacks. For example, if network fluctuations occur during code synchronization, the data mirroring tool may fail, forcing the entire pipeline to exit. In other words, this solution for retrieving ClearCase code is easily affected by network bandwidth, making it unstable. Furthermore, the current solution performs two synchronizations when retrieving ClearCase code, inevitably increasing retrieval time and reducing continuous integration efficiency. This instability and low efficiency lead to a poor user experience, rendering continuous integration meaningless.
[0060] To address the aforementioned problems in existing technologies, this application provides a data acquisition method and apparatus. The inventive concept of the data acquisition method and apparatus provided in this application is as follows: In a software development center configured with a fat client, a shared storage disk is configured. After the fat client obtains code from the ClearCase server, it stores it on the shared storage disk. Then, a storage middleware is used to declare the shared storage disk as a PVC. Thus, when a pipeline node in continuous integration initializes a Pod, the Pod mounts the PVC. Based on this, the code stored on the shared storage disk can be directly obtained in the pipeline workspace, i.e., the container environment, eliminating secondary synchronization, greatly reducing code acquisition time, solving the SSH protocol interruption problem, and achieving fast and stable code acquisition.
[0061] Figure 1 This is a schematic diagram of the structure of a data acquisition system provided in an embodiment of this application. Figure 1 As shown, the data acquisition system 100 provided in this application embodiment includes: a fat client 101, a shared storage disk 102, a storage middleware 103, and a pipeline node 104.
[0062] The fat client 101 communicates with the ClearCase server 200 and can synchronize code from the ClearCase server 200 according to the stream information input by the user. The synchronized code is defined as target code. Target code is a general term for the code that is to be added to continuous integration from the ClearCase server 200. The content of the target code is not limited in this embodiment of the application.
[0063] After the fat client 101 synchronizes the target code from the ClearCase server 200, it stores the target code on a shared storage disk 102, which is connected to the fat client 101. The shared storage disk 102 can be, for example, a Linux disk.
[0064] Storage middleware 103 can declare shared storage disk 102 as a persistent volume claim (PVC), and there is a communication connection between storage middleware 103 and shared storage disk 102.
[0065] Pipeline node 104 is any node in continuous integration and is communicatively connected to storage middleware 103. Pipeline node 104 is used to perform pipelined operations. When pipeline node 104 initializes a Pod, the Pod can mount a PVC. Since storage middleware 103 declares shared storage disk 102 as a PVC, pipeline node 104 can directly obtain the target code stored in shared storage disk 102 through storage middleware 103. The target code can be mounted to the container environment, realizing direct retrieval of target code from ClearCase server 200 to continuous integration.
[0066] It should be noted that, Figure 1 The solid arrows in the text represent the transmission of the target code during the acquisition process, while the dashed arrows represent the declaration of the PVC by the storage middleware 103 and the mounting of the PVC by the Pod.
[0067] As described above, the target code can be added to the continuous integration process directly from the ClearCase server using shared storage and storage middleware. During the acquisition of the target code, on the one hand, data mirroring and backup tools are not used, avoiding the impact of network bandwidth on the acquisition process and overcoming the instability of the acquisition process, thus achieving stable acquisition; on the other hand, the secondary code synchronization during the acquisition process is omitted, which can greatly reduce the acquisition time and achieve fast acquisition, thereby improving the efficiency of continuous integration and preventing continuous integration from losing its value and meaning.
[0068] The data acquisition system provided in this application embodiment synchronizes target code from the ClearCase server based on stream information and stores the synchronized target code on a shared storage disk. When a pipeline node initializes a Pod, the Pod mounts a PVC, allowing the pipeline node to obtain the target code from the shared storage disk via a storage middleware, which declares the shared storage disk as a PVC. By mounting a PVC during Pod initialization and declaring the shared storage disk as a PVC, the pipeline node's job space can directly access the target code from the ClearCase server through shared storage, eliminating the secondary synchronization required in existing technologies. This significantly reduces code acquisition time and enables fast and stable acquisition of target code.
[0069] exist Figure 1 On this basis, Figure 2 This is a schematic diagram of another data acquisition system provided in an embodiment of this application. For example... Figure 2 As shown, both the fat client 101 and the shared storage disk 102 can be configured on the Linux machine 1010. This Linux machine 1010 can be configured in each development center, such as each software development center. Development centers are usually planned according to regions, hence each development center is also called a domain development center.
[0070] Figure 3 This is a flowchart illustrating a data acquisition method provided in an embodiment of this application. The data acquisition method provided in this application can be applied to the data acquisition system described in the above embodiments. Figure 3 As shown in the embodiments of this application, the data acquisition method includes:
[0071] S101: The fat client synchronizes the target code from the ClearCase server based on the stream information and stores the target code to the shared storage disk.
[0072] Target code is a general term for code obtained from the ClearCase server and added to continuous integration. This application embodiment does not limit the content of the target code. The purpose of adding target code to continuous integration is to perform pipelined operations. Flow information is input by the user to the fat client and is used to identify the target code corresponding to the pipelined operation; that is, flow information is used to identify the target code according to the pipelined operation.
[0073] The user inputs streaming information to the fat client, which then responds to the streaming information to synchronize the target code indicated by the streaming information from the ClearCase server. The fat client communicates with the ClearCase server, and the communication connection method can be wired or wireless, which is not limited in this embodiment.
[0074] After the fat client synchronizes the target code from the ClearCase server, it stores the synchronized target code on a shared storage disk.
[0075] Optionally, in order to distinguish the target code corresponding to different stream information, the fat client can store the synchronized target code to a shared storage disk according to a shared directory, which facilitates data preservation and direct access by subsequent devices.
[0076] S102: When a pipeline node initializes a Pod, the Pod mounts a persistent volume and declares a PVC. The pipeline node then retrieves the target code from the shared storage disk via the storage middleware.
[0077] The storage middleware is used to declare shared storage disks as PVCs.
[0078] The storage middleware communicates with the shared storage disk, which is declared as a PVC. When a pipeline node initializes a Pod, the Pod directly mounts the PVC. The pipeline node can then retrieve the target code stored on the shared storage disk via the storage middleware, completing the process of adding the target code from the ClearCase server to continuous integration, i.e., completing the target code retrieval process.
[0079] A pipeline node is any node in continuous integration. The target code is added to the pipeline job space of the continuous integration, i.e., the pipeline node.
[0080] As described in the above embodiments, by using shared storage, the target code can be directly added from the ClearCase server to the continuous integration process through the storage middleware, thus completing the acquisition of the target code. In this acquisition process, firstly, no data mirroring backup tools are used, avoiding the impact of network bandwidth on the acquisition process, resolving SSH protocol interruption issues, overcoming instability, and achieving stable acquisition. Secondly, continuous integration frequently acquires the target code from the ClearCase server. To achieve rapid integration, each node in the continuous integration process, such as pipeline nodes, requires high operational efficiency. This target code acquisition process omits secondary code synchronization, greatly reducing acquisition time, improving continuous integration efficiency, and preventing continuous integration from losing its value and meaning. Furthermore, this target code acquisition process allows the target code to be quickly pulled into the pipeline's container environment for continuous integration, and it can also open up new research in ClearCase version control, providing support for the compilation and execution of programming languages.
[0081] The data acquisition method provided in this application involves a fat client synchronizing target code from a ClearCase server based on stream information and storing the synchronized target code on a shared storage disk. When a pipeline node initializes a Pod, the Pod mounts a PVC, allowing the pipeline node to obtain the target code from the shared storage disk via a storage middleware, which declares the shared storage disk as a PVC. By mounting a PVC during Pod initialization and declaring the shared storage disk as a PVC through the storage middleware, the pipeline node's job space can directly access the target code from the ClearCase server via shared storage, eliminating the secondary synchronization required in existing technologies. This significantly reduces code acquisition time and enables fast and stable acquisition of the target code.
[0082] Figure 4 This is a flowchart illustrating another data acquisition method provided in an embodiment of this application. The data acquisition method provided in this application can be applied to the data acquisition system described in the above embodiments. Figure 4 As shown in the embodiments of this application, the data acquisition method includes:
[0083] S201: The fat client creates the associated view of the ClearCase server using binary tools.
[0084] S202: The fat client synchronizes the target code from the ClearCase server based on the associated view and flow information.
[0085] Among them, flow information is used to identify target codes based on assembly line operations.
[0086] In order to synchronize target code from the ClearCase server based on streaming information, the fat client also needs to use binary tools to create an associated view of the ClearCase server, and then synchronize the target code from the ClearCase server based on the associated view.
[0087] As mentioned above Figure 3 As described in the embodiments, target code is a general term for code obtained from the ClearCase server and added to the continuous integration process. This application embodiment does not limit the content of the target code. The purpose of adding target code to continuous integration is to perform pipelined operations. Stream information is input by the user to the fat client and is used to identify the target code corresponding to the pipelined operation. The user inputs stream information to the fat client, and the fat client responds to the stream information to synchronize the target code indicated by the stream information from the ClearCase server. The fat client and the ClearCase server are connected in a communication relationship.
[0088] As can be seen from the above description, the fat client first creates an associated view of the ClearCase server using binary tools, and then can synchronize the target code from the ClearCase server based on the associated view and the flow information.
[0089] Alternatively, binary tools may include the Cleartool tool.
[0090] S203: The fat client stores the target code to a shared storage disk.
[0091] After the fat client synchronizes the target code from the ClearCase server, it stores the synchronized target code on a shared storage disk.
[0092] For example, a fat client stores the target code in a shared directory on a shared storage disk.
[0093] S204: When a pipeline node initializes a Pod, the Pod mounts a persistent volume and declares a PVC. The pipeline node then retrieves the target code from the shared storage disk via the storage middleware.
[0094] The storage middleware is used to declare shared storage disks as PVCs.
[0095] The storage middleware communicates with the shared storage disk, which is declared as a PVC. When a pipeline node initializes a Pod, the Pod directly mounts the PVC. The pipeline node can then retrieve the target code stored on the shared storage disk via the storage middleware, completing the process of adding the target code from the ClearCase server to continuous integration, i.e., completing the target code retrieval process.
[0096] A pipeline node is any node in continuous integration. The target code is added to the pipeline job space of the continuous integration, i.e., the pipeline node.
[0097] Additionally, a fat client and a shared storage disk are configured in each development center. Alternatively, both the fat client and the shared storage disk can be configured on Linux machines, thus configuring Linux machines in each development center.
[0098] S205: Pipeline nodes execute pipeline operations using target code according to job requirements.
[0099] The purpose of adding target code to continuous integration is to perform pipeline operations. Therefore, after the pipeline node obtains the target code, the pipeline operation is executed using the target code according to the operation requirements of the pipeline operation. This application embodiment does not limit the specific content of the pipeline operation.
[0100] Optionally, after the pipeline operation is completed, the pipeline node can delete the acquired target code to keep the data in the persistent volume from being contaminated.
[0101] Optionally, when the pipeline job is repeated, it means that the target code required by the pipeline job is the same. The fat client only needs to update the associated view of the created ClearCase server, without having to repeatedly obtain the same target code from the ClearCase server.
[0102] Optionally, when it is necessary to discard an already created associated view, the fat client can trigger view deletion commands in the binary tools, such as triggering endview and rmview in the Cleartool tool, to clean up discarded data on the fat client.
[0103] The data acquisition method provided in this application involves a fat client synchronizing target code from a ClearCase server based on stream information and storing the synchronized target code on a shared storage disk. When a pipeline node initializes a Pod, the Pod mounts a PVC, allowing the pipeline node to obtain the target code from the shared storage disk via a storage middleware, which declares the shared storage disk as a PVC. By mounting a PVC during Pod initialization and declaring the shared storage disk as a PVC through the storage middleware, the pipeline node's job space can directly access the target code from the ClearCase server via shared storage, eliminating the secondary synchronization required in existing technologies. This significantly reduces code acquisition time and enables fast and stable acquisition of the target code.
[0104] Figure 5 This is a schematic diagram of the structure of a data acquisition device provided in an embodiment of this application. Figure 5 As shown, the data acquisition device 400 provided in this application embodiment includes:
[0105] The first processing module 401 is used to synchronize the target code from the ClearCase server according to the stream information and store the target code to the shared storage disk;
[0106] The second processing module 402 is used to mount the PVC to the Pod when the pipeline node initializes the Pod, and to obtain the target code from the shared storage disk through the storage middleware.
[0107] The storage middleware is used to declare shared storage disks as PVCs.
[0108] In one possible design, the second processing module 402 is also used for:
[0109] Execute pipeline operations using target code according to job requirements.
[0110] In one possible design, the first processing module 401 is specifically used for:
[0111] Create associated views for the ClearCase server using binary tools;
[0112] Synchronize the target code from the ClearCase server based on the associated view and flow information;
[0113] Among them, flow information is used to identify target codes based on assembly line operations.
[0114] In one possible design, when the pipeline operation is repeated, the first processing module 401 is also used to update the created associated view.
[0115] In one possible design, the first processing module 401 is further used for:
[0116] Store the target code to a shared storage disk according to the shared directory.
[0117] In one possible design, both the fat client and the shared storage disk are configured on Linux machines, which are located in each development center.
[0118] In one possible design, binary tools include the Cleartool tool.
[0119] The data acquisition device provided in this application embodiment can execute each step of the data acquisition method in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described again here.
[0120] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 500 may include a processor 501 and a memory 502 communicatively connected to the processor 501.
[0121] Memory 502 is used to store programs. Specifically, the program may include program code, which includes computer-executable instructions.
[0122] The memory 502 may include high-speed RAM memory, and may also include non-volatile memory (MoM-volatile memory), such as at least one disk storage device.
[0123] The processor 501 is used to execute computer execution instructions stored in the memory 502 to implement the data acquisition method.
[0124] The processor 501 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.
[0125] Optionally, the memory 502 can be either standalone or integrated with the processor 501. When the memory 502 is a device independent of the processor 501, the electronic device 500 may further include:
[0126] Bus 503 is used to connect processor 501 and memory 502. The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc., but this does not mean there is only one bus or one type of bus.
[0127] Optionally, in a specific implementation, if the memory 502 and the processor 501 are integrated on a single chip, the memory 502 and the processor 501 can communicate through an internal interface.
[0128] This application also provides a computer-readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. Specifically, the computer-readable storage medium stores computer-executable instructions, which are used in the various steps of the methods in the above embodiments.
[0129] This application also provides a computer program product, including computer execution instructions that, when executed by a processor, implement the steps of the methods described above.
[0130] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the claims.
[0131] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A data acquisition method, characterized by, include: The fat client synchronizes target code from the ClearCase server based on the stream information and stores the target code to a shared storage disk; wherein, the stream information is input by the user to the fat client and is used to identify the target code corresponding to the pipeline operation; the target code is a general term for the code obtained from the ClearCase server to be added to continuous integration; When a pipeline node initializes a Pod, the Pod mounts a persistent volume and declares a PVC. The pipeline node retrieves the target code from the shared storage disk via a storage middleware. Here, the pipeline node can be any node in continuous integration, and the target code being added to the continuous integration refers to the pipeline job space of the pipeline node retrieving the target code. The storage middleware is used to declare the shared storage disk as the PVC.
2. The data acquisition method of claim 1, wherein, After the pipeline node obtains the target code, the process further includes: The pipeline nodes execute pipeline operations using the target code according to the job requirements.
3. The data acquisition method of claim 2, wherein, The fat client obtains the target code from the ClearCase server based on the stream information, including: The fat client creates associated views for the ClearCase server using binary tools; The fat client synchronizes the target code from the ClearCase server based on the associated view and the stream information; The flow information is used to identify the target code based on the pipeline operation.
4. The data acquisition method of claim 3, wherein, When the pipeline operation is repeated, the method further includes: the fat client updating the created associated view.
5. The data acquisition method of claim 1, wherein, The fat client stores the target code to the shared storage disk according to the shared directory.
6. The data acquisition method according to any one of claims 1-5, characterized in that, Both the fat client and the shared storage disk are configured on Linux machines, which are located in each development center.
7. The data acquisition method according to claim 3, characterized in that, The binary tools include the Cleartool tool.
8. A data acquisition device, characterized in that, include: The first processing module is used to synchronize target code from the ClearCase server according to the stream information and store the target code to a shared storage disk; wherein, the stream information is input by the user to the fat client and is used to identify the target code corresponding to the pipeline operation; the target code is a general term for the code obtained from the ClearCase server to be added to continuous integration; The second processing module is used to retrieve the target code from the shared storage disk when the pipeline node initializes the Pod, the Pod mounts a persistent volume declaration PVC, and the target code is retrieved from the shared storage disk via the storage middleware; wherein, the pipeline node is any node in continuous integration, and the target code is added to the pipeline job space of the pipeline node in continuous integration. The storage middleware is used to declare the shared storage disk as the PVC.
9. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the data acquisition 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 computer-executable instructions, which, when executed by a processor, are used to implement the data acquisition method as described in any one of claims 1 to 7.
11. A computer program product comprising computer-executable instructions, which, when executed by a processor, are used to implement the data acquisition method as described in any one of claims 1 to 7.
12. A data acquisition system, characterized in that, include: A fat client, used to synchronize target code from the ClearCase server based on streaming information; The stream information is input by the user into the fat client and is used to identify the target code corresponding to the pipeline operation; The target code is a collective term for the code obtained from the ClearCase server and added to continuous integration; A shared storage disk is used to store the target code; Storage middleware is used to declare the shared storage disk as a persistent volume (PVC). Pipeline nodes are used to mount PVCs to the Pod during Pod initialization and to retrieve the target code from the shared storage disk via the storage middleware; The pipeline node can be any node in continuous integration, and the target code being added to continuous integration refers to the target code being obtained from the pipeline job space of the pipeline node.