CN114047943A

CN114047943A - Information processing method, device, equipment, storage medium and computer program product

Info

Publication number: CN114047943A
Application number: CN202111320671.2A
Authority: CN
Inventors: 廖超超; 王定鑫
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2021-11-09
Filing date: 2021-11-09
Publication date: 2022-02-15

Abstract

The disclosure provides an information processing method, an information processing device, information processing equipment, a storage medium and a computer program product, and relates to the technical field of computers, in particular to the field of software development. The specific implementation scheme is as follows: acquiring at least one item of information in the file information and the version information of a specified version in a remote version library; filing the at least one item of information to obtain a filing package of a specified version; the type of the archive packet of the designated version is a first type or a second type, the archive packet of the first type carries the file information of the designated version, and the archive packet of the second type carries the file information and the version information of the designated version; sending an archive package of a specified version to a third-party storage system; the third-party storage system is used for storing the archive package. According to the technical scheme, at least one of file information and version information of the specified version in the remote version library can be filed and stored in the third-party storage system, so that the read-write pressure of the remote version library is reduced, and the overall read-write performance and throughput are improved.

Description

Information processing method, device, equipment, storage medium and computer program product

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, a storage medium, and a computer program product for processing information.

Background

Current DevOps (collective term for processes, methods and systems) practice has been widely applied in the field of software development, and in the DevOps practice scenario, Git (distributed version control system) is the most popular code hosting tool at present, and each developer can locally copy a complete Git repository from a remote place by means of cloning (Git clone).

The existing source code distribution mode needs to acquire source codes from a remote Git warehouse, due to the particularity of Git protocols, the modes of acquiring the source codes from the remote Git warehouse mainly include cloning (Git clone) and pulling (Git pull/fetch), the two modes both need to establish the Git warehouse locally, the pulled data volume is large, and all historical versions containing designated branches are defaulted. In various DevOps practice scenes such as compiling, constructing, automatic testing, releasing and online, the read-write performance of a single Git warehouse is rapidly reduced under the condition of high concurrency, particularly for Git warehouses with large scale, the read success rate is obviously reduced, continuous failure retry causes the read-write pressure of a remote Git warehouse to be further increased, vicious circle is generated, the time for downloading source codes is further prolonged, and the performance of other pushing requests is also influenced.

Disclosure of Invention

The disclosure provides an information processing method, an information processing apparatus, a device, a storage medium and a computer program product.

According to a first aspect of the present disclosure, there is provided an information processing method including:

acquiring at least one item of information in the file information and the version information of a specified version in a remote version library;

filing the at least one item of information to obtain a filing package of a specified version; the type of the archive packet of the designated version is a first type or a second type, the archive packet of the first type carries the file information of the designated version, and the archive packet of the second type carries the file information and the version information of the designated version;

sending an archive package of a specified version to a third-party storage system; the third-party storage system is used for storing the archive package.

According to a second aspect of the present disclosure, there is provided an information processing apparatus comprising:

the information acquisition module is used for acquiring at least one item of information in the text information and the version information of the specified version in the remote version library;

the filing module is used for filing the at least one item of information to obtain a filing package of a specified version; the type of the archive packet of the designated version is a first type or a second type, the archive packet of the first type carries the file information of the designated version, and the archive packet of the second type carries the file information and the version information of the designated version;

the archive package storage module is used for sending an archive package with a specified version to a third-party storage system; the third-party storage system is used for storing the archive package.

According to a third aspect of the present disclosure, there is provided an electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the information processing method provided by any of the embodiments of the present disclosure.

According to a fourth aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the information processing method provided by any one of the embodiments of the present disclosure.

According to a fifth aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the information processing method provided by any of the embodiments of the present disclosure.

The technical scheme of the present disclosure can at least realize the following beneficial effects:

the technical scheme of the method can be used for filing at least one of file information and version information of a specified version in a remote version library, a filing package obtained after filing is stored in a third-party storage system, the third-party storage system can store the filing package, the filing package is provided for a user when needed, and then corresponding version information is provided, so that the read-write pressure of the remote version library can be reduced, and the overall read-write performance and throughput are improved; the archive package can carry the version information of the specified version or not, and is applicable to a scene needing to restore the version information of the original version or a scene needing not to restore the version information of the original version, so as to meet different use requirements.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1 is a schematic flow chart of an information processing method provided by an embodiment of the present disclosure;

FIG. 2 is a schematic diagram illustrating a principle of obtaining a specified version based on a way of a Git show bundle in the embodiment of the present disclosure;

FIG. 3 is a partial flow diagram of another information processing method provided by an embodiment of the present disclosure;

fig. 4 is a schematic diagram of an example of an information processing method provided by an embodiment of the present disclosure;

fig. 5 is a schematic structural framework diagram of an information processing apparatus provided in an embodiment of the present disclosure;

FIG. 6 is a block diagram of an architecture framework of an address generation module in an embodiment of the disclosure;

fig. 7 is a schematic structural framework diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

First, several terms involved in the present disclosure are introduced as follows:

DevOps: the term "Development" and "Operations" is a generic term for a set of processes, methods and systems used to facilitate communication, collaboration and integration between Development (applications/software engineering), technical Operations and quality assurance departments. DevOps requires the use of highly standardized, automated procedures and tools to support efficient collaboration of roles to achieve faster, rapid, frequent and reliable software delivery goals.

Git: an open source distributed version control system can effectively process the version management of projects from very small to very large at high speed.

Cloud-native: a method for constructing and operating an application program which fully utilizes the advantages of a cloud computing model is provided, and the cloud native technology is beneficial to constructing and operating elastically expandable applications in novel dynamic environments such as public clouds, private clouds, mixed clouds and the like of various organizations. Representative technologies of cloud-native include containers, Service Mesh, microservices, immutable infrastructure, and Application Programming Interfaces (API). These techniques enable the construction of a loosely coupled system that is fault tolerant, easy to manage, and easy to observe. In conjunction with reliable automation, cloud-native technology enables engineers to easily make frequent and predictable major changes to the system.

In the cloud-native era, DevOps itself also widely adopts technical architecture systems such as large-scale distributed construction, large-scale distributed continuous integration/delivery and the like under the scenes of large-scale automation processes and tools. In the cloud-native era, containerization is a very important manifestation, and the challenges brought by containerization to source code hosting are mainly from stateless and high-concurrent high-performance access.

In a traditional source code distribution mode, a Git warehouse is created locally mainly through two modes of cloning (Git clone) and pulling (Git pull/fetch), and in various DevOps practical scenes such as compiling, constructing, automatic testing, releasing and online, only a certain specified version of source codes are really needed, and transmission and downloading of a large number of irrelevant version history records occupy computing resources and reduce research and development efficiency. In addition, in a large-scale DevOps scene, a large amount of unnecessary data reading and transmission causes low efficiency of downloading source codes and waste of computing resources and network resources. Therefore, the traditional source code distribution mode cannot meet the actual requirement of large-scale DevOps practice on high concurrency and high performance.

To solve this problem, there are currently several main solutions:

in the first scheme, a reading node is added at a remote server to deal with the high concurrent access pressure of a large-scale DevOps automation task on source codes.

And in the second scheme, the source code cache is added at the local client so as to relieve the reading pressure of the remote server.

And in the third scheme, the Git protocol is upgraded at the remote server, and the pulling of a single version is realized, so that unnecessary resource waste is reduced.

However, the above solution has the following problems:

in the first scheme, the data synchronization of the main node and the read node has time delay, the data synchronization is poor, and meanwhile, the concurrency number which can be supported by a single Git service instance is very limited by the principle of Git and the characteristic that the Git needs to process a large number of small files in practice.

The second scheme is not suitable for the cloud-native era. The services running in the cloud-native age container usually mount storage services of a third party, and therefore, the characteristics that the Git workspace can only have a view corresponding to a given version at any given time are limited, the services in the container cannot simultaneously see multiple versions of views in the same workspace, and therefore, the source codes of multiple versions cannot be simultaneously used in the same space.

The third scheme cannot acquire the specified version and cannot thoroughly solve the problem of high concurrent reading of the remote Git warehouse. Firstly, the change of a remote Git warehouse is possible to happen at any time, and a client cannot know the depth of cloning or the time of a version, so that a specified version cannot be accurately obtained; secondly, in the third scheme, the source code of the remote Git warehouse must be obtained from the latest submitted information of the version, namely the submitted information (commit) pointed by the branch HEAD pointer (HEAD), and in order to obtain the source code of a certain version, all submitted information backtracking from the current latest submitted information to the specified submitted information (specified commit) must be obtained together, so that the problem of high concurrent reading of the remote Git warehouse cannot be completely solved, and a large amount of resource waste still exists.

According to an embodiment of the present disclosure, there is provided an information processing method applicable to a Git server or other servers, as shown in fig. 1, the method including:

s101, at least one item of information of file information and version information of a specified version in a remote version library is obtained.

The remote version repository in the disclosed embodiments may be a Git repository of a remote Git server, hereinafter referred to as the remote Git repository for short.

In the embodiment of the present disclosure, the file information of the specified version may include information of at least one of a text file (i.e., a source code file) and a binary file, and the version information of the specified version may include a history of the specified version.

Optionally, the operation of obtaining the file information and/or the version information of the specified version in the remote version library may be implemented by an archiving task construction service, or may be implemented by other services, and a corresponding service may be set according to an actual situation, which is not limited in the embodiment of the present disclosure.

S102, at least one item of information in the file information and the version information of the specified version is archived to obtain an archive package of the specified version.

The type of the archive package of the specified version is a first type or a second type, the archive package of the first type carries the file information of the specified version, and the archive package of the second type carries the file information and the version information of the specified version.

In a scenario of filing based on the first type, the file information of the specified version can be filed to obtain a first type filing package of the specified version, and in a scenario of filing based on the second type, the file information and the version information of the specified version can be filed to obtain a second type filing package of the specified version. The archive package of the first type and the archive package of the second type can both be used to restore (via file information) the file of the specified version, and the archive package of the second type can also be used to restore (via version information) the version record of the specified version.

Optionally, the operation of archiving the file information and/or the version information of the specified version may be implemented by an archiving task processing service, or may be implemented by other services, and a corresponding service may be set according to an actual situation, which is not limited in this embodiment of the present disclosure.

S103, sending the archive package with the specified version to a third-party storage system.

The third-party storage system is used for storing the archive package.

Optionally, the operation of sending the archive package of the designated version to the third-party storage system may be implemented by an archive storage and distribution service, or may be implemented by other services, and a corresponding service may be set according to an actual situation, which is not limited in this embodiment of the present disclosure.

The third-party storage system in the embodiment of the disclosure can be arranged in a remote Git server or other servers, and the filing package is stored and issued by adopting the third-party storage system, so that the reading and writing pressure of a remote version library in a high concurrency scene can be relieved, and the problem of single-point dependence on the remote version library is solved.

In an optional implementation manner, obtaining at least one of file information and version information of a specified version in a remote version library includes: and under the condition that the version is changed in the remote version library, acquiring at least one item of information of file information and version information of the changed version as at least one item of information of file information and version information of the specified version.

Optionally, whether the version in the remote version library has been changed may be determined by monitoring the version in the remote version library or polling, or may be implemented by other methods, and it may be determined whether the version in the remote version library has been changed.

In one example, the archiving task construction service may monitor the remote version library, determine whether a source code signal of each version in the remote version library has changed, consider that one or more versions have changed when the archiving task construction service monitors that file information of one or more versions in the remote version library has changed, acquire basic information of the one or more changed versions (as designated versions), create an archiving task based on the basic information, and send the archiving task to a next service, such as an archiving task processing service; the filing task processing service can acquire at least one item of information of file information and version information of the changed version from a remote version library, and the acquired information can be determined according to the type of actual filing required. Wherein, the basic information of the changed version may include submission information of the changed version.

In one example, the archive task construction service may poll the remote version repository, periodically checking the change log of the remote version repository to determine whether the file information of each version in the remote version repository has changed; when determining that the file information of one or more versions in the remote version library is changed, considering that the one or more versions are changed, the archiving task construction service can acquire basic information of one or more changed versions (as designated versions) in the remote version library, create an archiving task based on the basic information, and send the archiving task to a next service, such as an archiving task processing service; the filing task processing service can acquire at least one item of information of file information and version information of the changed version from a remote version library, and the acquired information can be determined according to the type of actual filing required. Wherein, the basic information of the changed version may include submission information of the changed version. In one example, the changed version has specified commit information.

The implementation mode of determining the version change through monitoring or polling and then creating the filing task is an active filing mode, can acquire the change information of the version in real time, and when the change of the local client is sent to the remote version library, the filing task construction service can quickly monitor the change, so as to quickly respond, create the filing task and contribute to improving the filing efficiency of the source code.

In another optional implementation, the obtaining at least one of file information and version information of a specified version in a remote version library includes: and responding to the filing instruction sent by the client, and acquiring at least one item of information of file information and version information of the version in the remote version library specified by the filing instruction as at least one item of information of file information and version information of the specified version.

Optionally, the archive instruction carries specific commit information, which may be used to determine one or more versions in the remote version store specified by the archive instruction.

In one example, after receiving an archive instruction sent by a client, an archive task construction service obtains specified submission information carried by the archive instruction, obtains basic information of one or more versions (as specified versions) specified by the archive instruction from a remote version library according to the specified submission information, creates an archive task based on the basic information, and sends the archive task to a next service, such as an archive task processing service, where the archive task processing service may obtain at least one of file information and version information of a version that has been changed from the remote version library, and the obtained information may be determined according to a type that actually needs to be archived. Wherein the base information of the version specified by the archive instruction may include commit information.

The method for creating the archiving task based on the archiving instruction sent by the client is a passive archiving method, and the source code can be archived in a targeted manner based on the actual requirements of the user.

Based on the above contents, the method for acquiring at least one of the file information and the version information of the specified version in the remote version library in the embodiment of the present disclosure is applicable to both an application scenario of active archiving and an application scenario of passive archiving, has strong flexibility, and can meet different archiving requirements.

Optionally, the first type may be a Git archive, which is used to archive file information, and the archive package of the Git archive only corresponds to a complete file content of a specified version and does not have any information for restoring the specified version.

In an alternative embodiment, the second type does not support the Git shallow clone (show clone) protocol, which may be referred to as Git show clone for short. For example, the second type may be a Git bundle, which is used to enable archiving of file information and version information. The Git bundle archive package carries necessary information for restoring a native file of a specified version, specifically carries a Git object (object) required for adding a new history record on the basis of the existing history record of a local Git warehouse (or a Git version library), and can add new submission information on the existing submission information history of the local Git warehouse in an incremental manner through the Git bundle archive package, thereby reducing the requirement for completely submitting an information history request of a remote Git warehouse.

In another alternative embodiment, the second type supports the shallow clone protocol of Git. For example, the second type may be a Git show bundle, a special binary file format, which is used to implement shallow clone compatible archive of file information and version information. The archive package of the Git show bundle carries necessary information for restoring the native file of the specified version, and the archive package of the Git show bundle contains the content of the version to be archived, including the reference (ref) of the version, the submission information, the tree (tree), the object (object), and the like.

The embodiment of the present disclosure provides several types of archive packages (e.g., Git archive, Git bundle, and Git show bundle) to implement one-time computation and permanent storage, so that a large amount of unnecessary repeated computation caused by frequent reading and writing of a remote version library can be reduced, resource waste of a Central Processing Unit (CPU), a memory, a network, and the like can be reduced, and more user read and write volume support can be provided under the same server resource, so as to relieve the read and write pressure of the remote version library in a high-concurrency scenario.

The several types of archive packets provided by the embodiment of the present disclosure may be adapted to various storage services, and further, the archive packets may be stored in various read-optimized storage services, and read acceleration may be performed through a CDN (Content Delivery Network) or other means, so that access speed of a user to read file information and/or version information may be effectively increased, and a read success rate of the user may be ensured. Under the actual DevOps scene, the flow has the obvious characteristics of reading more and writing less, the scheme can be adapted to various read optimization storage services, the success rate of the DevOps in the file information and/or version information acquisition stage can be effectively guaranteed, and the time consumption of the DevOps in the file information and/or version information acquisition stage is reduced.

The second type in the embodiment of the present disclosure may be a type of a shallow clone protocol supporting Git, for example, a Git show bundle, and the type may provide one or more specified versions in a remote version library, thereby well meeting the requirement that a user reads any sub-version library in the remote version library at high speed and accurately.

In a large number of research and development scenarios, particularly in a CI (Continuous Integration)/CD (Continuous Delivery) process, a large amount of history commit information (history commit) of a remote version library has no practical role in executing an actual task, and a user only wants to acquire file information and/or version information of a specified version in the remote version library and perform processes such as checking, scanning, building, compiling, releasing, deploying and the like on the file information and/or version information. These common processes are usually only related to specific versions of file information and/or version information, and reading and transmitting a large amount of history records is a huge waste for computing and network resources, and also restricts the development of large-scale DevOps practice. The Git show bundle supports the native property of Git show clone, and the user can obtain the latest submission information from the remote by executing a pull (Git pull/fetch) command.

In addition, the conventional scheme usually accelerates to obtain the commit information of the remote version library directly based on the Git show clone, and the scheme can only obtain < depth > +1 historical commit information of the latest commit information on the specified branch through a-depth < depth > parameter, or obtain the commit information after a certain time through-show-location < date >, but can not accurately obtain the defects of depth and version time through-depth < depth > and-show-location < date >. Based on the solution of the Git window bundle in the embodiment of the present disclosure, a user can obtain a Git window clone local version library file containing specified submission information (which may be composed of any plurality of submission information required by the user) in a remote version library in a native manner, that is, any sub-version of the remote version library, so that the defect of the native Git window clone is overcome, the flexibility of Git in reading the history of the sub-version is enhanced, and the Git window clone is more suitable for large-scale DevOps.

The scheme for obtaining the specified version by way of the Git show bundle in the embodiment of the present disclosure is further described below with reference to fig. 2.

The first row of fig. 2 shows the version of the remote version store at a branch, including the version of the head pointer of the branch, the version containing commit information 1(commit 1), and the version containing commit information 2(commit 2). The second row of fig. 2 shows a schematic diagram of locally obtaining the version containing commit 2 by means of a Git show block, the third row of fig. 2 shows a schematic diagram of locally obtaining the version containing commit 2 and commit 1 by means of a Git show block, and as can be seen from the schematic diagrams of the second row and the third row, when locally obtaining the file information and/or version information of the specified version by means of a Git show block, it is necessary to trace back all the commit information of the specified commit information (commit 2 and/or commit 1) from the latest commit information of the branch, i.e., the commit information pointed by the HEAD pointer (HEAD), and there is unnecessary trace back.

The fourth row of fig. 2 shows a schematic diagram of locally obtaining the version containing commit 2 by means of the Git bundle in the embodiment of the present disclosure, the fifth row of fig. 2 shows a schematic diagram of locally obtaining the version containing commit 2 and commit 1 by means of the Git bundle in the embodiment of the present disclosure, as can be seen from the schematic diagrams of the fourth row and the fifth row, when locally obtaining the file information and/or the version information of the specified version by means of the Git bundle, it is also necessary to trace back all the submission information carried by the Git bundle itself from the latest submission information of the branch, i.e. the submission information pointed by the HEAD pointer (HEAD), and when locally using the archived version of the specified submission information (commit 2 and/or commit 1), there must be a prerequisite condition for normal use of the Git bundle of the version of the historical submission information of the specified submission information (commit 2 and/or commit 1), otherwise, the Git bundle archive package cannot be used normally.

The sixth row of figure 2 shows a schematic diagram of locally obtaining a version containing commit 2 by way of a Git show bundle in an embodiment of the disclosure, the seventh row of fig. 2 shows a schematic diagram of locally obtaining the version containing commit 2 and commit 1 by means of the Git show bundle in the embodiment of the present disclosure, and as can be seen from the schematic diagrams of the sixth row and the seventh row, the file information and/or version information of the specified version can be directly obtained by means of the Git show bundle in the embodiment of the present disclosure, without backtracking from the latest submitted information of the branches one by one, thereby greatly reducing unnecessary backtracking and reducing waste of resources, meanwhile, the version of the specific commit information (commit 2 and/or commit 1) may be used locally, not to have the version of the historical commit information of the specific commit information (commit 2 and/or commit 1) in the local version library.

In an alternative embodiment, as shown in fig. 3, archiving at least one of file information and version information of a specified version includes the following steps S301 to S303:

s301, adding second type initial information in a first file to be archived, wherein the first file to be archived is formed by file information of a specified version.

The second type of initial information includes format information, such as bundle format information, which archives file information and version information.

In one example, the first file to be archived may be a pack file containing a specified version of file information, the second type of initial information may be information in a bundle format, and the information in the bundle format may be introduced into a header of the pack file.

S302, if the specified version has the specified submission information, adding the specified submission information of the specified version into a second file to be archived of the shallow clone protocol supporting Git.

In one example, the second file to be archived may be a Git/show file, i.e., a file named show in a remote Git repository, which supports Git's shallow clone protocol, such as SHA1(Secure Hash Algorithm 1) Hash value, MD5(Message-Digest Algorithm 5) Hash value, etc., and may be other types of key information, and the embodiments of the present disclosure are not to be enumerated.

In one example, SHA1 hash values (as specified commit information) may be written to the Git/show file, enabling the locally restored Git repository to allow the root node of the local version library to have no parent commit, with only one or more specified commit information.

S303, archiving the first file to be archived and the second file to be archived after the information is added.

Alternatively, the steps S301 to S303 may be implemented by an archive task processing service, and the archive task processing service may perform archive through the steps S301 to S303, and send the obtained archive package to a next service, for example, an archive storage and distribution service.

The archive package obtained by archiving in the above manner can be transmitted to the receiving party by a file transmission manner such as network transmission, storage medium transmission, etc., and is locally restored by the receiving party to a local shallow clone version file containing specified submission information (the specified submission information may be composed of information composed of any plurality of submission information required by the user).

In an optional implementation manner, the information processing method provided in the embodiment of the present disclosure further includes:

responding to an archive package access request sent by a client, and generating an archive package access address according to a storage address of an archive package requested to be accessed by the archive package access request in a third-party storage system; and feeding back the access address of the archive package to the client.

Optionally, the archive package access request sent by the client carries specified submission information, where the specified submission information specifies one or more versions, and the archive package of the one or more versions is the archive package requested to be accessed by the archive package access request.

The mode of generating and feeding back the access address of the filing package based on the access request of the client-side can be realized by filing storage and distribution service, after the filing storage and distribution service generates the access address of the filing package in the mode, the access address of the filing package is fed back to the client-side, and the client-side can download the corresponding filing package from a third-party storage system through the access address of the filing package. The third-party storage system can send corresponding archive packages to the client through the CDN, so that the speed and the success rate of reading the archive packages by a user are improved.

The archive packet access address in the embodiment of the present disclosure may be a temporary access address or a permanent access address, and when the archive packet access address is a temporary access address, the validity period of the access address may be set according to actual requirements.

Based on the mode, the user can obtain the filing package stored in the third-party storage system through the filing package access address to obtain the file information and/or the version information of the corresponding version, and does not need to rely on the remote version library to perform read-write operation to obtain the file information and/or the version information of the version, so that the read-write pressure of the remote version library can be reduced, and the read-write performance and efficiency can be improved.

In an optional implementation manner, in the process of generating an archive access address in response to an archive package access request sent by a client, the method specifically includes:

performing authority authentication on the access request of the archive package; and under the condition that the authority authentication of the archive packet access request passes, sending the storage address of the archive packet requested to be accessed by the archive packet access request in the third-party storage system to the client to generate an archive packet access address.

The operation of performing authority authentication on the access request of the archive package can be realized through authentication and audit services, or through other services, and corresponding services can be set according to actual conditions, which is not limited in the embodiment of the disclosure.

Optionally, the archive packet access request sent by the client carries user information, and the user information may be used to implement authority authentication on the archive packet access request.

In one example, after receiving an access request of a filing package sent by a client, a filing storage and distribution service sends the access request of the filing package to an authentication and audit service, the authentication and audit service authenticates whether user information carried by the access request of the filing package has a right to access the filing package in a third-party storage system and whether the right is consistent with a right to access a version in a remote version library, if the user information carried by the access request of the filing package is authenticated to have the right to access the filing package in the third-party storage system and the right is consistent with the right to access the version in the remote version library, the right authentication of the access request of the filing package is passed, otherwise, the right authentication of the access request of the filing package is not passed.

Optionally, in the case that the authority authentication for the archive package access request fails, information of authentication failure may be fed back to the client. In one example, in the event that the authorization authentication for the archive package access request fails, the authentication and auditing service feeds back information of the authentication failure to the archive storage and distribution service, which feeds back the information of the authentication failure to the client. In one example, each time the rights authentication is completed, the authentication and auditing service may store a record of that rights authentication for subsequent use.

Based on the above embodiment, the technical scheme of the embodiment of the disclosure can perform authority control on the archive package access request of the client, and ensure that the sending user has access authority to the archive package in the third-party storage system, so as to improve the access security; meanwhile, the access authority of the user to the archive package in the third-party storage system can be ensured to be consistent with the access authority to the version in the remote version library, so that the access effectiveness is improved.

The authentication and audit service of the embodiment of the disclosure can be set by a bypass, the read-write and access control of the filing package are decoupled, the authentication and audit service can be accessed into various Git hosting services in a low-cost mode on the basis of not changing the original access control design framework, the practicability and the compatibility are high, the read request of a user cannot be influenced even if the authentication and audit service fails, and the stability of the read operation of the user is improved.

In an optional embodiment, the authority authentication for the archive package access request includes:

and performing authority authentication on the access request of the archive package through any effective authority authentication channel in the plurality of authority authentication channels.

In one example, the authentication and audit service may be disposed in multiple rooms or network segments, where the authentication and audit service in each room or network segment serves as a permission authentication channel, and when the authentication and audit service in a certain room or network segment fails (i.e., the permission authentication channel fails), the permission authentication traffic may be quickly switched to the authentication and audit service in other rooms or network segments that do not fail (i.e., the permission authentication channel is valid).

Based on the above embodiment, the multiple right authentication channels are provided to facilitate disaster recovery switching, and when a certain right authentication channel fails, the right authentication channels are quickly switched to other effective right authentication channels, so that the stability of right authentication can be improved, and the right authentication cannot be interrupted due to the failure of the certain right authentication channel, thereby ensuring that the normal read request of a user is not influenced.

Fig. 4 is a schematic diagram illustrating an information processing method provided by the present disclosure implemented by each service, and one example of the information processing method provided by the present disclosure is described below with reference to fig. 4.

Referring to an example shown in fig. 4, the information processing method provided by the present disclosure may be implemented by a filing task construction service, a filing task processing service, a filing storage and distribution service, an authentication and audit service, and the like, and specifically relates to the following processes;

and when the file information of the software version is changed, the local client sends the change to the remote Git warehouse through Git writing operation.

The archive task construction service acquires basic information of a specified version (the version specified by the archive instruction or the version in which the remote Git warehouse is changed) when determining the version specified by the archive instruction sent by the client or the version in which the remote Git warehouse is changed, creates an archive task based on the basic information, and sends the created archive task to the archive task processing service.

The archiving task processing service acquires at least one item of information of file information and version information of one or more specified versions based on an archiving task, wherein the file information of the specified versions can be acquired for an archiving task based on a first type, and the file information and the version information of the specified versions are acquired for an archiving task based on a second type; and packaging at least one item of information in the file information and the version information of each designated version to generate a corresponding binary file, taking the binary file as a filing package or taking a binary compressed file obtained by compressing the binary file as the filing package, creating a filing package uploading task, and sending the filing package and the filing package uploading task to a filing storage and distribution service.

And the archiving storage and distribution service writes the archiving package into a third-party storage system for storage based on the archiving package uploading task.

When a user needs to acquire a filing package in a third-party storage system, a client sends a filing package access request (Git read operation), the filing storage and distribution service sends the filing package access request to an authentication and audit service, the authentication and audit service carries out authority authentication on the filing package access request, an authentication result is fed back to the filing storage and distribution service, and the filing storage and distribution service feeds back the authentication result to the client; in the case that the authority authentication passes, the fed-back authentication result includes the archive package access address, in the case that the authority authentication fails, the fed-back authentication result may include a reason of authentication failure, a suggestion of re-authentication, and the like, and only the archive package access address is fed back in the case that the authority authentication passes is shown in fig. 4 as an example.

And the client reads the corresponding archive package in the third-party storage system through the access address of the archive package.

The process described above in FIG. 4 may be processed asynchronously with the remote Git warehouse to reduce the impact of the process on the read and write performance of the remote Git warehouse.

In fig. 4, the read-write request of the client can be realized through client extension, and the client extension is mainly responsible for request operations such as encapsulation construction, downloading, restoration and the like, so that the learning and use costs of a user can be reduced. When the method is applied to a scenario of the Git hosting service, the client extension is the Git client extension, the Git client extension mainly comprises the steps that when a user executes a Git clone (clone) or pull (fetch/pull) command, the client extension firstly converts the information provided by the command into a request for acquiring a filing package (namely a filing package access request) to access filing storage and distribution service, and after authority authentication is completed and a filing package access address is fed back, the Git client extension downloads the filing package according to the filing package access address; if the download is successful, decompressing and restoring the archive package into a native local Git warehouse and checking out (checkout) a workspace (workspace); if the download fails, the native Git client is automatically forwarded to execute the native Git clone (clone) or pull (fetch/pull) commands. The mode can make the use of the client more convenient and transparent.

According to an embodiment of the present disclosure, there is also provided an information processing apparatus, as shown in fig. 5, including: an information acquisition module 501, an archive module 502, and an archive package storage module 503.

The information obtaining module 501 is configured to obtain at least one of file information and version information of a specified version in the remote version library.

The archiving module 502 is configured to archive at least one of the file information and the version information of the specified version to obtain an archive package of the specified version; the type of the archive packet of the specified version is a first type or a second type, the archive packet of the first type carries the file information of the specified version, and the archive packet of the second type carries the file information of the specified version and the version information.

An archive package storage module 503, which sends an archive package of a specified version to the third-party storage system; the third-party storage system is used for storing the archive package.

In an alternative embodiment, the second type supports a shallow clone protocol for a distributed version control system.

In an optional implementation manner, the information obtaining module 501 is specifically configured to: under the condition that the version is changed in the remote version library, acquiring at least one item of information in the file information and the version information of the changed version as at least one item of information in the file information and the version information of the specified version; or, in response to the filing instruction sent by the client, acquiring at least one of file information and version information of the version in the remote version library specified by the filing instruction as the at least one of file information and version information of the specified version.

In an alternative embodiment, the archive module 502 is specifically configured to: adding initial information of a second type in a first file to be archived, which is formed by file information of a specified version; under the condition that the specified version has the specified submission information, adding the specified submission information of the specified version into a second file to be archived, which supports the shallow clone protocol; filing the first file to be filed and the second file to be filed after the information is added; wherein the second type of initial information includes format information for archiving file information and version information.

In an optional implementation manner, an information processing apparatus provided in an embodiment of the present disclosure further includes: the device comprises an address generating module and an address feedback module.

And the address generation module is used for responding to the archive package access request sent by the client and generating an archive package access address according to the storage address of the archive package requested to be accessed by the archive package access request in the third-party storage system.

And the address feedback module is used for feeding back the access address of the archive package to the client.

In an alternative embodiment, as shown in fig. 6, the address generation module includes: a right authentication unit 601 and an address generation unit 602.

And an authority authentication unit 601, configured to perform authority authentication on the archive package access request.

And an address generating unit 602, configured to, when the authority authentication on the archive package access request passes, send, to the client, a storage address of the archive package requested to be accessed by the archive package access request in the third-party storage system, and generate an archive package access address.

In an optional implementation manner, the authority authentication unit 601 is specifically configured to: and performing authority authentication on the access request of the archive package through any effective authority authentication channel in the plurality of authority authentication channels.

The functions of each unit or module in each apparatus in the embodiments of the present disclosure may refer to the corresponding description in the above method embodiments, and are not described herein again.

In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.

The present disclosure also provides an electronic device, a non-transitory computer readable storage medium, and a computer program product according to embodiments of the present disclosure.

The electronic equipment that this disclosed embodiment provided includes: at least one processor, and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute any one of the information processing methods provided by the embodiments of the disclosure.

A non-transitory computer-readable storage medium provided by an embodiment of the present disclosure has stored thereon computer instructions for causing the computer to execute any one of the information processing methods provided by the embodiments of the present disclosure.

The computer program product provided by the embodiment of the present disclosure includes a computer program, and the computer program realizes any one of the information processing methods provided by the embodiment of the present disclosure when being executed by a processor.

FIG. 7 illustrates a schematic block diagram of an example electronic device 700 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 7, the device 700 comprises a computing unit 701, which may perform various suitable actions and processes according to a computer program stored in a Read Only Memory (ROM)702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data required for the operation of the device 700 can also be stored. The computing unit 701, the ROM 702, and the RAM703 are connected to each other by a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.

Various components in the device 700 are connected to the I/O interface 705, including: an input unit 706 such as a keyboard, a mouse, or the like; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

Computing unit 701 may be a variety of general purpose and/or special purpose processing components with processing and computing capabilities. Some examples of the computing unit 701 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 701 executes the respective methods and processes described above, such as an information processing method. For example, in some embodiments, the information processing method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 708. In some embodiments, part or all of a computer program may be loaded onto and/or installed onto device 700 via ROM 702 and/or communications unit 709. When the computer program is loaded into the RAM703 and executed by the computing unit 701, one or more steps of the information processing method described above may be performed. Alternatively, in other embodiments, the computing unit 701 may be configured to perform the information processing method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server with a combined blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. An information processing method comprising:

archiving the at least one item of information to obtain an archiving package of the specified version; the type of the archive packet of the specified version is a first type or a second type, the archive packet of the first type carries the file information of the specified version, and the archive packet of the second type carries the file information and the version information of the specified version;

sending the archive package of the specified version to a third-party storage system; the third-party storage system is used for storing the archive package.

2. The information processing method according to claim 1, wherein the second type supports a shallow clone protocol of a distributed version control system.

3. The information processing method of claim 2, wherein the archiving the at least one item of information comprises:

adding the initial information of the second type in a first file to be archived, which is formed by the file information of the specified version; the second type of initial information includes format information for archiving file information and version information;

under the condition that the specified version has specified submission information, adding the specified submission information of the specified version in a second file to be archived, which supports the shallow clone protocol;

and archiving the first file to be archived and the second file to be archived after the information is added.

4. The information processing method according to any one of claims 1 to 3, wherein the acquiring at least one of version information and file information of a specified version in a remote version repository includes:

acquiring at least one item of information of file information and version information of a version which is changed under the condition that the version is changed in the remote version library, wherein the at least one item of information is used as at least one item of information of the file information and the version information of the specified version;

or, in response to an archive instruction sent by a client, acquiring at least one of file information and version information of a version in the remote version library specified by the archive instruction as the at least one of file information and version information of the specified version.

5. The information processing method according to any one of claims 1 to 3, further comprising:

responding to an archive package access request sent by a client, and generating an archive package access address according to a storage address of an archive package requested to be accessed by the archive package access request in the third-party storage system;

and feeding back the access address of the archive package to the client.

6. The information processing method according to claim 5, wherein the generating an archive package access address according to a storage address of the archive package requested to be accessed by the archive package access request in the third-party storage system comprises:

performing authority authentication on the archive package access request;

and under the condition that the authority authentication of the archive package access request passes, sending the storage address of the archive package requested to be accessed by the archive package access request in the third-party storage system to the client to generate an archive package access address.

7. The information processing method of claim 6, wherein the performing rights authentication on the archive package access request comprises:

and performing authority authentication on the access request of the archive package through any effective authority authentication channel in a plurality of authority authentication channels.

8. An information processing apparatus comprising:

the filing module is used for filing the at least one item of information to obtain a filing package of the specified version; the type of the archive packet of the specified version is a first type or a second type, the archive packet of the first type carries the file information of the specified version, and the archive packet of the second type carries the file information and the version information of the specified version;

the archive package storage module is used for sending the archive package of the specified version to a third-party storage system; the third-party storage system is used for storing the archive package.

9. The information processing apparatus according to claim 8, wherein the second type supports a shallow clone protocol of a distributed version control system.

10. The information processing apparatus according to claim 9, wherein the archive module is specifically configured to:

adding the initial information of the second type in a first file to be archived, which is formed by the file information of the specified version; under the condition that the specified version has specified submission information, adding the specified submission information of the specified version in a second file to be archived, which supports the shallow clone protocol; archiving the first file to be archived and the second file to be archived after information is added;

the second type of initial information includes format information that archives file information and version information.

11. The information processing apparatus according to any one of claims 8 to 10, wherein the information acquisition module is specifically configured to:

acquiring at least one item of information of file information and version information of a version which is changed under the condition that the version is changed in the remote version library, wherein the at least one item of information is used as at least one item of information of the file information and the version information of the specified version; or, in response to an archive instruction sent by a client, acquiring at least one of file information and version information of a version in the remote version library specified by the archive instruction as the at least one of file information and version information of the specified version.

12. The information processing apparatus according to any one of claims 8 to 10, further comprising:

the address generation module is used for responding to an archive package access request sent by a client and generating an archive package access address according to the storage address of an archive package requested to be accessed by the archive package access request in the third-party storage system;

13. The information processing apparatus according to claim 12, wherein the address generation module includes:

the authority authentication unit is used for carrying out authority authentication on the access request of the filing package;

and the address generating unit is used for sending the storage address of the archive package requested to be accessed by the archive package access request in the third-party storage system to the client side to generate the archive package access address under the condition that the authority authentication of the archive package access request passes.

14. The information processing apparatus according to claim 13, wherein the authority authentication unit is specifically configured to:

15. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the information processing method of any one of claims 1 to 7.

16. A non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the information processing method according to any one of claims 1 to 7.

17. A computer program product comprising a computer program which, when executed by a processor, implements an information processing method according to any one of claims 1 to 7.