CN112416422A - Development version file submitting method, device, equipment and storage medium - Google Patents
Development version file submitting method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112416422A CN112416422A CN202011286902.8A CN202011286902A CN112416422A CN 112416422 A CN112416422 A CN 112416422A CN 202011286902 A CN202011286902 A CN 202011286902A CN 112416422 A CN112416422 A CN 112416422A
- Authority
- CN
- China
- Prior art keywords
- file
- version
- submitted
- submission
- version file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000011161 development Methods 0.000 title claims abstract description 45
- 238000000034 method Methods 0.000 title claims abstract description 36
- 230000004044 response Effects 0.000 claims abstract description 7
- 238000012790 confirmation Methods 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 7
- 230000003287 optical effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The embodiment of the invention discloses a development version file submission method, a development version file submission device, development version file submission equipment and a storage medium, wherein the method comprises the following steps: in response to the detected version file submission request, determining a to-be-submitted version file associated with the version file submission request; acquiring file attribute information of a version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information; and submitting the version file to be submitted based on the target submission branch. According to the method provided by the embodiment of the invention, the target submission branch is determined according to the file attribute information of the version file to be submitted to submit the file, so that the automatic submission of the version file is realized, and the efficiency of the version file is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a development version file submission method, a development version file submission device, development version file submission equipment and a storage medium.
Background
With the development of computer software, there are cases where a plurality of versions such as a development version, an online version, and a past version are used in the daily development of software. When the developed version needs to be submitted, the developed version needs to be submitted to different resource catalogs so as to avoid resource leakage of the new version or unnecessary increase of the bag body. At present, the version submission is manual submission, and the submission efficiency is low.
Disclosure of Invention
The embodiment of the invention provides a development version file submission method, a development version file submission device, development version file submission equipment and a storage medium, and aims to improve the submission efficiency of development version files.
In a first aspect, an embodiment of the present invention provides a development version file submission method, including:
in response to the detected version file submission request, determining a to-be-submitted version file associated with the version file submission request;
acquiring file attribute information of a version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information;
and submitting the version file to be submitted based on the target submission branch.
Optionally, further, obtaining file attribute information of the version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information, includes:
acquiring file attribute information of a version file to be submitted, and determining a version identifier of the version file to be submitted according to the file attribute information;
and taking the submission branch corresponding to the version identification as a target submission branch.
Optionally, further, obtaining file attribute information of the version file to be submitted, and determining the version identifier of the version file to be submitted according to the file attribute information, includes:
and acquiring the file name of the file of the version to be submitted, and determining the version identification according to the file name.
Optionally, further, obtaining file attribute information of the version file to be submitted, and determining the version identifier of the version file to be submitted according to the file attribute information, includes:
obtaining form information of a version file to be submitted, and determining a version identifier according to the form information
Optionally, further, before submitting the version file to be submitted based on the target submission branch, the method further includes:
generating and displaying submission confirmation information containing the target submission branch so that a user can confirm whether the submission branch is accurate according to the submission confirmation information;
and responding to the detected submission confirmation information, and storing the version file to be submitted to a target submission branch.
Optionally, further, submitting the version file to be submitted based on the target submission branch includes:
and acquiring a target address of a target submission branch, and submitting the version file to be submitted to the target address.
In a second aspect, an embodiment of the present invention further provides a device for submitting a development version file, including:
the version file to be submitted module is used for responding to the detected version file submission request and determining the version file to be submitted associated with the version file submission request;
the target submission branch module is used for acquiring the file attribute information of the version file to be submitted and determining a target submission branch of the version file to be submitted according to the file attribute information;
and the file to be submitted submitting module is used for submitting the file of the version to be submitted based on the target submitting branch.
Optionally, the target commit branching module further includes:
the file attribute acquisition unit is used for acquiring file attribute information of the version file to be submitted and determining the version identification of the version file to be submitted according to the file attribute information;
and the target submission branch unit is used for taking the submission branch corresponding to the version identifier as a target submission branch.
Optionally, further, the file attribute obtaining unit is specifically configured to:
and acquiring the file name of the file of the version to be submitted, and determining the version identification according to the file name.
Optionally, further, the file attribute obtaining unit is specifically configured to:
and acquiring form information of the version file to be submitted, and determining the version identification according to the form information.
Optionally, the apparatus further includes a commit confirmation module, configured to:
before submitting the version file to be submitted based on the target submitting branch, generating and displaying submission confirmation information containing the target submitting branch so that a user can confirm whether the submitting branch is accurate according to the submission confirmation information;
and responding to the detected submission confirmation information, and storing the version file to be submitted to a target submission branch.
Optionally, the to-be-submitted file submitting module is specifically configured to:
and acquiring a target address of a target submission branch, and submitting the version file to be submitted to the target address.
In a third aspect, an embodiment of the present invention further provides a computer device, where the computer device includes:
one or more processors;
storage means for storing one or more programs;
when executed by one or more processors, cause the one or more processors to implement a development version file submission method as provided by any of the embodiments of the invention.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the development version file submission method provided in any embodiment of the present invention.
The embodiment of the invention determines the version file to be submitted associated with the version file submission request by responding to the detected version file submission request; acquiring file attribute information of a version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information; and submitting the version file to be submitted based on the target submitting branch, and determining the target submitting branch according to the file attribute information of the version file to be submitted to submit the file, so that the automatic submission of the version file is realized, and the efficiency of improving the version file is improved.
Drawings
Fig. 1 is a flowchart of a development version file submission method according to an embodiment of the present invention;
fig. 2 is a flowchart of a development version file submission method according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a development version file submission apparatus according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of a development version file submission method according to an embodiment of the present invention. The present embodiment is applicable to a case where file submission of a development version is performed. The method may be performed by a development version file submitting apparatus, which may be implemented in software and/or hardware, for example, and may be configured in a computer device. As shown in fig. 1, the method includes:
s110, responding to the detected version file submission request, and determining the version file to be submitted associated with the version file submission request.
In this embodiment, the version file submission request may be a request initiated by a user through a terminal and used for submitting the version file to be submitted. Optionally, the user may actively upload the version file to be submitted to the development version file submitting device, and initiate a version file submitting request, and after the development version file submitting device detects the version file submitting request initiated by the user, the to-be-submitted version file associated with the version file submitting request is determined. For example, assuming that the version file to be submitted is the file a, the user may drag the selected file a to the version submission area to initiate a version file submission request, or may directly link out the selected file a in the version file submission area to trigger the version file submission request.
S120, acquiring file attribute information of the file of the version to be submitted, and determining a target submitting branch of the file of the version to be submitted according to the file attribute information.
Optionally, after determining the version file to be submitted, obtaining file attribute information of the version file to be submitted. The file attribute information may be understood as information that uniquely identifies a file attribute of the version file to be submitted, such as information of a name, a requirement, a form, and the like of the version file to be submitted.
Considering the storage mode of the version file as follows: files of the same software version are stored under the same submission branch (namely, the resource directory), and files of different software versions are stored under different submission branches, so that the target submission branch of the file of the version to be submitted is basically determined according to the version of the file of the version to be submitted. That is to say, obtaining the file attribute information of the file of the version to be submitted, and determining the target submission branch of the file of the version to be submitted according to the file attribute information, includes: acquiring file attribute information of a version file to be submitted, and determining a version identifier of the version file to be submitted according to the file attribute information; and taking the submission branch corresponding to the version identification as a target submission branch. Basically, the version identification of the version file to be submitted is obtained, and the corresponding submission branch of the version file to be submitted can be automatically determined by taking the submission branch corresponding to the version identification as a target submission branch.
In this embodiment, the version identifier of the version file to be submitted may be obtained in different manners.
In one embodiment, obtaining file attribute information of a version file to be submitted, and determining a version identifier of the version file to be submitted according to the file attribute information includes: and acquiring the file name of the file of the version to be submitted, and determining the version identification according to the file name. Optionally, when the version file to be submitted has a fixed naming rule, the version identifier may be determined according to the file name of the version file to be submitted. For example, the naming rule of the version file to be submitted may be determined as: version identification-file content-file type. The avatar model version 3.9 may be named "v 3.9-avatar-model". Therefore, based on the fixed naming rule, the version identification contained in the file name of the version file to be submitted can be obtained.
In one embodiment, obtaining file attribute information of a version file to be submitted, and determining a version identifier of the version file to be submitted according to the file attribute information includes: and acquiring form information of the version file to be submitted, and determining the version identification according to the form information. Optionally, the version identifier of the version file to be submitted may also be determined according to the form information of the version file to be submitted. The form information of the version file to be submitted comprises information such as the requirement, the release plan and the version identification of the version file to be submitted. When a user generates a version submitting request, form files carrying information such as requirements, release plans and version identifications of the version files to be submitted are uploaded to a development version file submitting device. The development version file submitting device can determine form information managed by the version file to be submitted, and obtain the version identification of the version file to be submitted from the form information.
And S130, submitting the version file to be submitted based on the target submitting branch.
In this embodiment, after the target submission branch of the version file to be submitted is determined, the version file to be submitted is directly submitted to the target submission branch, and then the submission of the version file to be submitted can be completed.
Optionally, submitting the version file to be submitted based on the target submission branch includes: and acquiring a target address of a target submission branch, and submitting the version file to be submitted to the target address. Specifically, when the version file to be submitted is submitted, the address of the target submission branch is obtained, and the version file to be submitted is submitted to the target address.
The embodiment of the invention determines the version file to be submitted associated with the version file submission request by responding to the detected version file submission request; acquiring file attribute information of a version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information; and submitting the version file to be submitted based on the target submitting branch, and determining the target submitting branch according to the file attribute information of the version file to be submitted to submit the file, so that the automatic submission of the version file is realized, and the efficiency of improving the version file is improved.
Example two
Fig. 2 is a flowchart of a development version file submission method according to a second embodiment of the present invention. The embodiment is further optimized on the basis of the scheme. As shown in fig. 2, the method includes:
s210, in response to the detected version file submission request, determining the version file to be submitted associated with the version file submission request.
S220, acquiring file attribute information of the version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information.
And S230, generating and displaying submission confirmation information containing the target submission branch so that the user can confirm whether the submission branch is accurate according to the submission confirmation information.
In this embodiment, to ensure the accuracy of the submission branch, the submission user may be requested to confirm the target submission branch after determining the target submission branch. Specifically, the submission confirmation information including the name of the version file to be submitted and the target submission branch corresponding to the version file to be submitted may be generated and displayed, and the user confirms whether the submission branch is accurate through the displayed submission confirmation information.
S240, responding to the detected submission confirmation information, and storing the version file to be submitted to a target submission branch.
Optionally, after the user confirms that the submission information is accurate, the confirmation information is triggered, and after the development version file submission device detects the submission confirmation information initiated by the user, the version file to be submitted is submitted based on the target submission branch.
If the target submission branch is not accurate, the user can manually modify the target submission branch and initiate submission of modification information, and after the development version file submission device detects the submission modification information initiated by the user, the submission branch modified by the user is used as the target submission branch to submit the version file to be submitted.
The embodiment of the invention ensures that a user confirms whether the submission branch is accurate or not according to the submission confirmation information by generating and displaying the submission confirmation information containing the target submission branch; and responding to the detected submission confirmation information, storing the version file to be submitted to the target submission branch, further ensuring the accuracy of the target submission branch through user confirmation, and avoiding the new version resource leakage and unnecessary bag body increase caused by the submission branch error.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a development version file submission apparatus according to a third embodiment of the present invention. The development version file submitting device can be implemented in software and/or hardware, for example, the development version file submitting device can be configured in a computer device. As shown in fig. 3, the apparatus includes a pending-commit version file module 310, a target-commit branching module 320, and a pending-commit file committing module 330, wherein:
a to-be-submitted version file module 310, configured to determine, in response to the detected version file submission request, a to-be-submitted version file associated with the version file submission request;
the target submission branch module 320 is configured to obtain file attribute information of the version file to be submitted, and determine a target submission branch of the version file to be submitted according to the file attribute information;
and a to-be-submitted file submitting module 330, configured to submit the to-be-submitted version file based on the target submitting branch.
The version file to be submitted is determined by the version file to be submitted module responding to the detected version file submission request; the target submission branch module acquires file attribute information of the version file to be submitted and determines a target submission branch of the version file to be submitted according to the file attribute information; the file submitting module to be submitted submits the version file to be submitted based on the target submitting branch, and the file submitting branch is determined according to the file attribute information of the version file to be submitted so as to submit the file, so that the automatic submission of the version file is realized, and the efficiency of improving the version file is improved.
Optionally, on the basis of the above scheme, the target commit branching module 320 includes:
the file attribute acquisition unit is used for acquiring file attribute information of the version file to be submitted and determining the version identification of the version file to be submitted according to the file attribute information;
and the target submission branch unit is used for taking the submission branch corresponding to the version identifier as a target submission branch.
Optionally, on the basis of the above scheme, the file attribute obtaining unit is specifically configured to:
and acquiring the file name of the file of the version to be submitted, and determining the version identification according to the file name.
Optionally, on the basis of the above scheme, the file attribute obtaining unit is specifically configured to:
and acquiring form information of the version file to be submitted, and determining the version identification according to the form information.
Optionally, on the basis of the foregoing scheme, the apparatus further includes a commit confirmation module, configured to:
before submitting the version file to be submitted based on the target submitting branch, generating and displaying submission confirmation information containing the target submitting branch so that a user can confirm whether the submitting branch is accurate according to the submission confirmation information;
and responding to the detected submission confirmation information, and storing the version file to be submitted to a target submission branch.
Optionally, on the basis of the above scheme, the file to be submitted submitting module is specifically configured to:
and acquiring a target address of a target submission branch, and submitting the version file to be submitted to the target address.
The development version file submitting device provided by the embodiment of the invention can execute the development version file submitting method provided by any embodiment of the invention, and has the corresponding functional module and beneficial effect of the execution method.
Example four
Fig. 4 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an exemplary computer device 412 suitable for use in implementing embodiments of the present invention. The computer device 412 shown in FIG. 4 is only one example and should not impose any limitations on the functionality or scope of use of embodiments of the present invention.
As shown in FIG. 4, computer device 412 is in the form of a general purpose computing device. Components of computer device 412 may include, but are not limited to: one or more processors 416, a system memory 428, and a bus 418 that couples the various system components (including the system memory 428 and the processors 416).
The system memory 428 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)430 and/or cache memory 432. The computer device 412 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage 434 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, and commonly referred to as a "hard drive"). Although not shown in FIG. 4, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 418 by one or more data media interfaces. Memory 428 can include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 440 having a set (at least one) of program modules 442 may be stored, for instance, in memory 428, such program modules 442 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. The program modules 442 generally perform the functions and/or methodologies of the described embodiments of the invention.
The computer device 412 may also communicate with one or more external devices 414 (e.g., keyboard, pointing device, display 424, etc.), with one or more devices that enable a user to interact with the computer device 412, and/or with any devices (e.g., network card, modem, etc.) that enable the computer device 412 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 422. Also, computer device 412 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet) through network adapter 420. As shown, network adapter 420 communicates with the other modules of computer device 412 over bus 418. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the computer device 412, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processor 416 executes various functional applications and data processing by executing programs stored in the system memory 428, for example, implementing a development version file submission method provided by the embodiment of the present invention, the method including:
in response to the detected version file submission request, determining a to-be-submitted version file associated with the version file submission request;
acquiring file attribute information of a version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information;
and submitting the version file to be submitted based on the target submission branch.
Of course, those skilled in the art will understand that the processor may also implement the technical solution of the development version file submission method provided in any embodiment of the present invention.
EXAMPLE five
The fifth embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for submitting a development version file provided in the fifth embodiment of the present invention, where the method includes:
in response to the detected version file submission request, determining a to-be-submitted version file associated with the version file submission request;
acquiring file attribute information of a version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information;
and submitting the version file to be submitted based on the target submission branch.
Of course, the computer program stored on the computer-readable storage medium provided by the embodiment of the present invention is not limited to the above method operations, and may also perform the operations related to the development version file submission method provided by any embodiment of the present invention.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having 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. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments illustrated herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A development version file submission method, comprising:
in response to the detected version file submission request, determining a to-be-submitted version file associated with the version file submission request;
acquiring file attribute information of the version file to be submitted, and determining a target submission branch of the version file to be submitted according to the file attribute information;
and submitting the version file to be submitted based on the target submission branch.
2. The method according to claim 1, wherein the obtaining of the file attribute information of the version file to be submitted and the determining of the target submission branch of the version file to be submitted according to the file attribute information comprises:
acquiring file attribute information of the version file to be submitted, and determining the version identification of the version file to be submitted according to the file attribute information;
and taking the submission branch corresponding to the version identification as the target submission branch.
3. The method according to claim 2, wherein the obtaining of the file attribute information of the version file to be submitted and the determining of the version identifier of the version file to be submitted according to the file attribute information comprises:
and acquiring the file name of the file of the version to be submitted, and determining the version identification according to the file name.
4. The method according to claim 2, wherein the obtaining of the file attribute information of the version file to be submitted and the determining of the version identifier of the version file to be submitted according to the file attribute information comprises:
and acquiring form information of the file with the version to be submitted, and determining the version identification according to the form information.
5. The method of claim 1, further comprising, prior to committing the version-to-commit file based on the target commit branch:
generating and displaying submission confirmation information containing the target submission branch so that a user can confirm whether the submission branch is accurate according to the submission confirmation information;
and responding to the detected submission confirmation information, and storing the version file to be submitted to the target submission branch.
6. The method of claim 1, wherein said committing the version-to-be-committed file based on the target commit branch comprises:
and acquiring the target address of the target submission branch, and submitting the version file to be submitted to the target address.
7. A development version file submission apparatus, comprising:
the version file to be submitted module is used for responding to the detected version file submission request and determining the version file to be submitted associated with the version file submission request;
the target submission branch module is used for acquiring the file attribute information of the version file to be submitted and determining a target submission branch of the version file to be submitted according to the file attribute information;
and the file to be submitted submitting module is used for submitting the version file to be submitted based on the target submitting branch.
8. The apparatus of claim 7, wherein the target commit branching module comprises:
the file attribute acquisition unit is used for acquiring the file attribute information of the version file to be submitted and determining the version identification of the version file to be submitted according to the file attribute information;
and the target submission branch unit is used for taking the submission branch corresponding to the version identifier as the target submission branch.
9. A computer device, characterized in that the device comprises:
one or more processors;
storage means for storing one or more programs;
when executed by one or more processors, cause the one or more processors to implement the development version file submission method of any of claims 1-7.
10. A computer-readable storage medium on which a computer program is stored, the program, when executed by a processor, implementing the development version file submission method as recited in any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011286902.8A CN112416422A (en) | 2020-11-17 | 2020-11-17 | Development version file submitting method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011286902.8A CN112416422A (en) | 2020-11-17 | 2020-11-17 | Development version file submitting method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112416422A true CN112416422A (en) | 2021-02-26 |
Family
ID=74832074
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011286902.8A Pending CN112416422A (en) | 2020-11-17 | 2020-11-17 | Development version file submitting method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112416422A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117492822A (en) * | 2023-12-29 | 2024-02-02 | 杭州新中大科技股份有限公司 | Change contrast method, device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050055686A1 (en) * | 2003-09-08 | 2005-03-10 | Microsoft Corporation | Method and system for servicing software |
| US20150244827A1 (en) * | 2014-02-24 | 2015-08-27 | International Business Machines Corporation | Data Transmission |
| CN108762761A (en) * | 2018-05-17 | 2018-11-06 | 深圳市分期乐网络科技有限公司 | Generation method, device, server and the storage medium of target channel packet |
| CN110109840A (en) * | 2019-05-10 | 2019-08-09 | 重庆八戒电子商务有限公司 | Code audit method, audit device and the medium compared based on version number |
| CN111651196A (en) * | 2020-06-24 | 2020-09-11 | 腾讯科技（深圳）有限公司 | Document publishing method, device and server |
| CN111813742A (en) * | 2020-06-29 | 2020-10-23 | 北京百度网讯科技有限公司 | File management method, device, equipment and medium |
-
2020
- 2020-11-17 CN CN202011286902.8A patent/CN112416422A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050055686A1 (en) * | 2003-09-08 | 2005-03-10 | Microsoft Corporation | Method and system for servicing software |
| US20150244827A1 (en) * | 2014-02-24 | 2015-08-27 | International Business Machines Corporation | Data Transmission |
| CN108762761A (en) * | 2018-05-17 | 2018-11-06 | 深圳市分期乐网络科技有限公司 | Generation method, device, server and the storage medium of target channel packet |
| CN110109840A (en) * | 2019-05-10 | 2019-08-09 | 重庆八戒电子商务有限公司 | Code audit method, audit device and the medium compared based on version number |
| CN111651196A (en) * | 2020-06-24 | 2020-09-11 | 腾讯科技（深圳）有限公司 | Document publishing method, device and server |
| CN111813742A (en) * | 2020-06-29 | 2020-10-23 | 北京百度网讯科技有限公司 | File management method, device, equipment and medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117492822A (en) * | 2023-12-29 | 2024-02-02 | 杭州新中大科技股份有限公司 | Change contrast method, device, electronic equipment and storage medium |
| CN117492822B (en) * | 2023-12-29 | 2024-03-29 | 杭州新中大科技股份有限公司 | Change contrast method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112055064B (en) | Data synchronization method, device, equipment and storage medium | |
| CN111818145B (en) | File transmission method, device, system, equipment and storage medium | |
| CN110134869B (en) | Information pushing method, device, equipment and storage medium | |
| CN112346794A (en) | Interface calling method, device, equipment and medium | |
| CN109284108B (en) | Unmanned vehicle data storage method and device, electronic equipment and storage medium | |
| CN109033456B (en) | Condition query method and device, electronic equipment and storage medium | |
| CN112416422A (en) | Development version file submitting method, device, equipment and storage medium | |
| CN111581098B (en) | Method, device, server and storage medium for transferring and storing interface data | |
| CN112799760A (en) | Form rendering method and device | |
| CN112328272A (en) | Algorithm upgrading method, device, equipment and storage medium | |
| CN115576484A (en) | Data reading and writing method and device, electronic equipment and storage medium | |
| CN111596997B (en) | UI information request method, device, terminal and storage medium | |
| CN112364268A (en) | Resource acquisition method and device, electronic equipment and storage medium | |
| CN111026463B (en) | Page loading method, device, equipment and storage medium | |
| CN112925796A (en) | Write consistency control method, device, equipment and storage medium | |
| CN114356322A (en) | Communication mapping method, device, equipment and storage medium for equipment configuration | |
| CN110515807B (en) | Database table monitoring method, device, equipment and storage medium | |
| CN111046430B (en) | Data processing method and device, storage medium and electronic equipment | |
| CN110958243A (en) | Network vulnerability submitting method and device, storage medium and electronic equipment | |
| CN111881381A (en) | Display method, device, equipment and storage medium | |
| CN110888665B (en) | Method, device, equipment and storage medium for submitting changed content | |
| CN113535660B (en) | Android log storage method and device | |
| CN111897774B (en) | File uploading method and device, electronic equipment and storage medium | |
| CN113032650B (en) | Library book management method, library book management device, library book management server and library book management storage medium | |
| CN111506567B (en) | Cross-database cleaning method and device for data, computer equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |