CN115599437A - Software version processing method and device, electronic equipment and storage medium - Google Patents
Software version processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115599437A CN115599437A CN202211321370.6A CN202211321370A CN115599437A CN 115599437 A CN115599437 A CN 115599437A CN 202211321370 A CN202211321370 A CN 202211321370A CN 115599437 A CN115599437 A CN 115599437A
- Authority
- CN
- China
- Prior art keywords
- version number
- version
- sent
- instruction
- target software
- 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.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 20
- 238000011161 development Methods 0.000 claims abstract description 108
- 238000000034 method Methods 0.000 claims abstract description 34
- 238000012545 processing Methods 0.000 claims abstract description 31
- 230000008439 repair process Effects 0.000 claims abstract description 30
- 230000008569 process Effects 0.000 claims abstract description 16
- 230000004048 modification Effects 0.000 claims description 8
- 238000012986 modification Methods 0.000 claims description 8
- 238000004590 computer program Methods 0.000 claims description 6
- 238000001514 detection method Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 7
- 230000004044 response Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000006467 substitution reaction Methods 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a software version processing method, a software version processing device, an electronic device and a storage medium, wherein the software version processing method comprises the following steps: responding to a version management instruction of a user, and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction; if the version management instruction is a version issuing instruction, acquiring the current development version number of the target software, identifying the minor version number of the current development version number, and performing numerical updating on the minor version number to determine the newly developed version number of the target software; and if the version management instruction is a version repairing instruction, acquiring a sent version number of the target software, repairing the target code corresponding to the sent version number, and modifying the sent version number after the repair is finished to determine a new repaired version number of the target software. The generation of the newly developed version number and the newly repaired version number is automatically realized in the version sending and modifying processes of the version number, so that the generation efficiency of the version number is improved, and the error rate of the version number is reduced.
Description
Technical Field
The present application relates to the field of software version management technologies, and in particular, to a method and an apparatus for processing a software version, an electronic device, and a storage medium.
Background
The code amount of modern enterprise-level application programs is rapidly increased, and the traditional software management mode obviously cannot meet the requirements of the software industry. However, the advent of distributed version control systems has enabled efficient resolution of code versions. The distributed version control system is used as an open-source distributed version control system, can effectively process project version management at high speed, does not need the support of server-side software, and ensures that the release and the exchange of source codes are very convenient.
However, with the rise of large-scale software engineering, collaborative development becomes the mainstream, multi-version synchronous development makes code branch management difficult, and especially when the code is managed by using the current distributed version control system, the code version number needs to be managed manually, which easily causes the technical problem of version number confusion, so how to improve the processing efficiency of the software version becomes a non-trivial technical problem.
Disclosure of Invention
In view of this, an object of the present application is to provide a method and an apparatus for processing a software version, an electronic device, and a storage medium, which automatically generate a newly developed version number and a newly repaired version number in the process of version release and modification of the version number, thereby improving the efficiency of generating the version number and reducing the error rate of the version number.
The embodiment of the application provides a software version processing method, which comprises the following steps:
responding to a version management instruction sent by a user, and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction;
if the version management instruction is the version issuing instruction, acquiring a current development version number of the target software, identifying a minor version number of the current development version number, and performing numerical updating on the minor version number to determine a new development version number of the target software;
and if the version management instruction is the version repairing instruction, acquiring a sent version number of the target software, repairing a target code corresponding to the sent version number, and modifying the sent version number after the repair is finished to determine a new repaired version number of the target software.
In a possible implementation manner, the obtaining a current development version number of target software, identifying a minor version number of the current development version number, performing numerical update on the minor version number, and determining a new development version number of the target software includes:
responding to the version issuing instruction, acquiring the current development version number from a database engineering record, and determining a code address based on the current development version number;
acquiring a main branch code corresponding to the current development version number from a distributed version control database based on the code address;
determining an engineering code corresponding to the current development version number in the main branch code, and identifying a minor version number of the current development version number in the engineering code;
and updating the current numerical value corresponding to the minor version number to determine the newly developed version number of the target software.
In a possible implementation manner, after the determining of the new development version number of the target software, the processing method further includes:
and creating a first version number label in the distributed version control database based on the newly developed version number, associating the first version number label with the main branch code, and creating a publishing record in the database engineering record.
In a possible implementation manner, after the determining the new development version number of the target software, the processing method further includes:
and adding suffix identification information at the end of the newly developed version number.
In a possible implementation manner, the obtaining a sent version number of target software, repairing a target code corresponding to the sent version number, and modifying the sent version number after the repair is completed to determine a new repaired version number of the target software includes:
responding to the version repairing instruction, acquiring the sent version number from a database engineering record, and determining a second version number label corresponding to the sent version number in a distributed version control database based on the sent version number;
determining a target code corresponding to the sent version number based on the second version number label;
and after the target code is repaired, identifying the revision version number of the sent version number, updating the current value of the revision version number, and determining the number of the new revision version.
In a possible implementation manner, the new revision number includes a major version number, a minor version number, and a revision version number, and after the determination of the new revision number of the target software, the processing method further includes:
detecting whether the new repaired version number is consistent with the historical development version number;
and if so, updating the current numerical value of the revision version number in the new revision version number.
An embodiment of the present application further provides a processing apparatus for a software version, where the processing apparatus includes:
the detection module is used for responding to a version management instruction sent by a user and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction;
the version issuing module is used for acquiring the current development version number of the target software if the version management instruction is the version issuing instruction, identifying the minor version number of the current development version number, carrying out numerical updating on the minor version number and determining the newly developed version number of the target software;
and the modification module is used for acquiring the sent version number of the target software if the version management instruction is the version repair instruction, repairing the target code corresponding to the sent version number, modifying the sent version number after the repair is finished, and determining the new repaired version number of the target software.
In a possible implementation manner, when the version issuing module is configured to obtain the current development version number of the target software, identify a minor version number of the current development version number, perform numerical update on the minor version number, and determine a new development version number of the target software, the version issuing module is configured to:
responding to the version issuing instruction, acquiring the current development version number from a database engineering record, and determining a code address based on the current development version number;
acquiring a main branch code corresponding to the current development version number from a distributed version control database based on the code address;
determining an engineering code corresponding to the current development version number in the main branch code, and identifying a minor version number of the current development version number in the engineering code;
and updating the current numerical value corresponding to the minor version number to determine the newly developed version number of the target software.
An embodiment of the present application further provides an electronic device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the electronic device is running, the machine-readable instructions being executable by the processor to perform the steps of the software version processing method as described above.
Embodiments of the present application further provide a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the software version processing method as described above.
The embodiment of the application provides a software version processing method, a software version processing device, an electronic device and a storage medium, wherein the processing method comprises the following steps: responding to a version management instruction sent by a user, and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction; if the version management instruction is the version issuing instruction, acquiring a current development version number of the target software, identifying a minor version number of the current development version number, and performing numerical updating on the minor version number to determine a new development version number of the target software; and if the version management instruction is the version repairing instruction, acquiring the current development version number of the target software, repairing the target code corresponding to the current development version number, and modifying the current development version number after repairing to determine the new repaired version number of the target software. The generation of the newly developed version number and the newly repaired version number is automatically realized in the version issuing and modifying processes of the version number, so that the generation efficiency of the version number is improved, and the error rate of the version number is reduced.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a flowchart of a method for processing a software version according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a processing apparatus for a software version according to an embodiment of the present disclosure;
fig. 3 is a second schematic structural diagram of a processing apparatus of a software version according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
To make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for illustrative and descriptive purposes only and are not used to limit the scope of protection of the present application. Additionally, it should be understood that the schematic drawings are not necessarily drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be performed out of order, and that steps without logical context may be performed in reverse order or concurrently. In addition, one skilled in the art, under the guidance of the present disclosure, may add one or more other operations to the flowchart, or may remove one or more operations from the flowchart.
In addition, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
To enable those skilled in the art to utilize the present disclosure, the following embodiments are presented in conjunction with a specific application scenario "processing software versions," and it will be apparent to those skilled in the art that the general principles defined herein may be applied to other embodiments and application scenarios without departing from the spirit and scope of the present disclosure.
The method, the apparatus, the electronic device, or the computer-readable storage medium described in the embodiments of the present application may be applied to any scenario that requires processing a software version, and the embodiments of the present application do not limit a specific application scenario, and any scheme that uses the method, the apparatus, the electronic device, and the storage medium for processing a software version provided in the embodiments of the present application is within the protection scope of the present application.
First, an application scenario to which the present application is applicable will be described. The method and the device can be applied to the technical field of software version management.
Research shows that with the rise of large-scale software engineering, collaborative development becomes the mainstream, multi-version synchronous development makes code branch management difficult, and especially when a code is managed by using the current distributed version control system, the code version number needs to be managed manually, which easily causes the technical problem of version number confusion, so how to improve the processing efficiency of software versions becomes a non-trivial technical problem.
Based on this, the embodiment of the application provides a method for processing a software version, and by automatically realizing generation of a newly developed version number and a newly repaired version number in the process of version release and modification of the version number, the efficiency of generation of the version number is improved, and the error rate of the version number is reduced.
Referring to fig. 1, fig. 1 is a flowchart of a software version processing method according to an embodiment of the present disclosure. As shown in fig. 1, a processing method provided in an embodiment of the present application includes:
s101: and responding to a version management instruction sent by a user, and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction.
In this step, in response to a version management instruction sent by a user, it is detected whether the version management instruction sent by the user is any one of a version issue instruction and a version repair instruction.
Here, the version issue instruction is an instruction for implementing issue of a software version.
Here, the version repair instruction is an instruction to repair a software version.
S102: and if the version management instruction is the version issuing instruction, acquiring the current development version number of the target software, identifying the minor version number of the current development version number, carrying out numerical updating on the minor version number, and determining the newly developed version number of the target software.
In the step, if the version management instruction is detected to be a version issuing instruction, the current development version number of the target software is obtained, the minor version number of the current development version number is identified, the minor version number is updated numerically, and a new development version number is determined.
Here, the version format of the currently developed version number is: major version number, minor version number, and revision version number.
Here, the major version number is an incompatible API modification (the development management platform is temporarily reserved and used for a major change of a project in the future), the minor version number is a functional new addition (release) that is downward compatible, and the revision version number is a problem correction (repair) that is downward compatible.
In a possible implementation manner, the obtaining a current development version number of the target software, identifying a minor version number of the current development version number, performing numerical updating on the minor version number, and determining a new development version number of the target software includes:
a: and responding to the version issuing instruction, acquiring the current development version number from a database engineering record, and determining a code address based on the current development version number.
Here, in response to the version issuing instruction, the current development version number is acquired from the database engineering record, and the code address is determined according to the current development version number.
The code address is an engineering code address corresponding to the current development version number in the distributed version control database.
B: and acquiring the main branch code corresponding to the current development version number from a distributed version control database based on the code address.
Here, the main branch code corresponding to the current development version number is acquired in the distributed version control database according to the code address.
C: and determining an engineering code corresponding to the current development version number in the main branch code, and identifying a minor version number of the current development version number in the engineering code.
Here, the engineering code corresponding to the current development version number is determined in the main branch code, and the minor version number of the current development version number is identified in the engineering code.
Here, a pom.xml file is obtained from the main branch code, an engineering code corresponding to the current development version number is found in the pom.xml file, and a minor version number of the current development version number is identified in the engineering code.
D: and updating the current numerical value corresponding to the minor version number to determine the newly developed version number of the target software.
Here, the current value corresponding to the minor version number is updated, and the newly developed version number of the target software is determined.
And determining the current value corresponding to the minor version number, automatically performing updating on the current value corresponding to the minor version number by +1 or +2 on the basis of the current value, and determining the newly developed version number of the target software.
In one possible implementation, in response to a user needing to modify a currently developed version number, a version number manually input by the user may be received according to a version number specification, and the manually input version number is used as a newly developed version number of target software.
In a specific embodiment, a current development version number is read from a database engineering record, a code address of a previous development version number in a git code library is located through a project code and an engineering code, a main branch code is pulled from the git code library, a pom.xml file in the code is read, the engineering code is found, a current numerical value corresponding to the minor version number is updated, a new development version number of the target software is determined, the pom.xml file is stored, and the modified version number is submitted to the main branch code.
In a possible implementation manner, after the determining the new development version number of the target software, the processing method further includes:
and creating a first version number label in the distributed version control database based on the newly developed version number, associating the first version number label with the main branch code, and creating a version sending record in the database engineering record.
Here, a first version number tag is created for the newly developed version number in the distributed version control database, the first version number tag is associated with the main branch code, and a publishing record is created in the database engineering record.
In a particular embodiment, a tag named first version number tag is created in the distributed version control database creation to point to the primary branch code to enable the association with the primary branch code to be completed and a publishing record is created in the database project record.
In a possible implementation manner, after the determining the new development version number of the target software, the processing method further includes:
suffix identification information is added at the end of the newly developed version number.
Here, suffix identification information such as "-snap shot" is added at the end of the newly developed version number.
S103: and if the version management instruction is the version repairing instruction, acquiring a sent version number of the target software, repairing a target code corresponding to the sent version number, and modifying the sent version number after the repair is finished to determine a new repaired version number of the target software.
In the step, if the version management instruction is a version repair instruction, the sent version number of the target software is obtained, the target code corresponding to the sent version number is repaired, and the sent version number is modified after the repair is completed to determine the new repaired version number of the target software.
In a possible implementation manner, the obtaining a sent version number of the target software, repairing the target code corresponding to the sent version number, and modifying the sent version number after the repair is completed to determine a new repaired version number of the target software includes:
a: and responding to the version repairing instruction, acquiring the sent version number from the database engineering record, and determining a second version number label corresponding to the sent version number in the distributed version control database based on the sent version number.
And the distributed version control database determines a second version number label corresponding to the sent version number according to the sent version number.
Here, the second version number tag is a tag that finds the corresponding name in the distributed version control database according to the version number that has been issued.
b: and determining the target code corresponding to the sent version number based on the second version number label.
Here, the target code corresponding to the sent version number is determined according to the second version number label.
c: and after the target code is repaired, identifying the revision version number of the sent version number, updating the current value of the revision version number, and determining the number of the new revision version.
After the target code is repaired, the revision version number of the sent version number is identified, the current value of the revision version number is updated, and the new revision version number is determined.
Here, updating the current value of the revision version number is automatically performed to +1 or +2 or the like on the basis of the current value, and the new revision version number is determined.
In a possible implementation manner, the new revision number includes a major version number, a minor version number, and a revision version number, and after the determination of the new revision number of the target software, the processing method further includes:
detecting whether the new repaired version number is consistent with the historical development version number; and if so, updating the current numerical value of the revision version number in the new revision version number.
Here, whether the new revision version number is consistent with the historical development version number is detected; and if the new revision version number is consistent with the historical development version number, updating the current numerical value of the revision version number in the new revision version number.
In a specific embodiment, the system finds the current development version number (the version number to be repaired) of the target software from the database record, obtains the version number, finds a tag with a corresponding name according to the version number, and creates a repair branch with the name of "version number + patch" based on the tag. And pulling the repair branch by a developer to modify the problem, submitting the code after the modification is finished, and then constructing. And building a tag named as a repair version number, and recording the tag into a corresponding version record. In the construction process of the compiling tag corresponding system, firstly, adding one to a revision number (a third bit in the revision number) in the revision number to generate a repair revision number, revising the revision number in the code, and completing repair of the created code.
In a specific embodiment, in response to a version management instruction sent by a user, detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction; if the version management instruction is detected to be a version issuing instruction, acquiring the current development version number of the target software, identifying the minor version number of the current development version number, automatically adding one to update the current value of the minor version number, and determining the newly developed version number of the target software; and if the version management instruction is detected to be the version repairing instruction, acquiring the sent version number of the target software, repairing the target code corresponding to the sent version number, and automatically adding 1 to the current numerical value of the revised version number of the sent version number after the repair is finished to determine the new repaired version number of the target software.
The processing method for the software version provided by the embodiment of the application comprises the following steps: responding to a version management instruction sent by a user, and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction; if the version management instruction is the version issuing instruction, acquiring a current development version number of the target software, identifying a minor version number of the current development version number, and performing numerical updating on the minor version number to determine a new development version number of the target software; and if the version management instruction is the version repairing instruction, acquiring a sent version number of the target software, repairing a target code corresponding to the sent version number, and modifying the sent version number after the repair is finished to determine a new repaired version number of the target software. The generation of the newly developed version number and the newly repaired version number is automatically realized in the version sending and modifying processes of the version number, so that the generation efficiency of the version number is improved, and the error rate of the version number is reduced.
Referring to fig. 2 and fig. 3, fig. 2 is a schematic structural diagram of a processing device of a software version according to an embodiment of the present disclosure; fig. 3 is a second schematic structural diagram of a processing apparatus of a software version according to an embodiment of the present application. As shown in fig. 2, the processing device 200 of the software version includes:
the detecting module 210 is configured to detect whether a version management instruction sent by a user is any one of a version issuing instruction and a version repairing instruction;
the version issuing module 220 is configured to, if the version management instruction is the version issuing instruction, obtain a current development version number of the target software, identify a minor version number of the current development version number, perform numerical update on the minor version number, and determine a new development version number of the target software;
a modifying module 230, configured to, if the version management instruction is the version repairing instruction, obtain a sent version number of the target software, repair the target code corresponding to the sent version number, and modify the sent version number after the repair is completed, to determine a new repaired version number of the target software.
Further, when the version sending module 220 is configured to obtain the current development version number of the target software, identify a minor version number of the current development version number, perform numerical update on the minor version number, and determine a new development version number of the target software, the version sending module 220 is configured to:
responding to the version issuing instruction, acquiring the current development version number from a database engineering record, and determining a code address based on the current development version number;
acquiring a main branch code corresponding to the current development version number from a distributed version control database based on the code address;
determining an engineering code corresponding to the current development version number in the main branch code, and identifying a minor version number of the current development version number in the engineering code;
and updating the current numerical value corresponding to the minor version number to determine the newly developed version number of the target software.
Further, as shown in fig. 3, the processing apparatus 200 of the software version further includes an association module 240, where the association module 240 is configured to:
and creating a first version number label in the distributed version control database based on the newly developed version number, associating the first version number label with the main branch code, and creating a version sending record in the database engineering record.
Further, as shown in fig. 3, the processing apparatus 200 of the software version further includes a suffix identifier adding module 250, and the suffix identifier adding module 250 is configured to:
suffix identification information is added at the end of the newly developed version number.
Further, when the modifying module 230 is configured to obtain the sent version number of the target software, repair the target code corresponding to the sent version number, modify the sent version number after the repair is completed, and determine a new repaired version number of the target software, the modifying module 230 is configured to:
responding to the version repairing instruction, acquiring the sent version number from a database engineering record, and determining a second version number label corresponding to the sent version number in a distributed version control database based on the sent version number;
determining a target code corresponding to the sent version number based on the second version number label;
and after the target code is repaired, identifying the revision version number of the sent version number, updating the current value of the revision version number, and determining the number of the new revision version.
Further, as shown in fig. 3, the processing apparatus 200 of the software version further includes a detection module 260, and the detection module 260 is configured to:
detecting whether the new repaired version number is consistent with the historical development version number;
and if so, updating the current numerical value of the revision version number in the new revision version number.
An embodiment of the present application provides a processing apparatus for a software version, where the processing apparatus includes: the detection module is used for responding to a version management instruction sent by a user and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction; the version issuing module is used for acquiring the current development version number of the target software if the version management instruction is the version issuing instruction, identifying the minor version number of the current development version number, carrying out numerical updating on the minor version number and determining the newly developed version number of the target software; and the modification module is used for acquiring the sent version number of the target software if the version management instruction is the version repair instruction, repairing the target code corresponding to the sent version number, modifying the sent version number after the repair is finished, and determining the new repaired version number of the target software. The generation of the newly developed version number and the newly repaired version number is automatically realized in the version sending and modifying processes of the version number, so that the generation efficiency of the version number is improved, and the error rate of the version number is reduced.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. As shown in fig. 4, the electronic device 400 includes a processor 410, a memory 420, and a bus 430.
The memory 420 stores machine-readable instructions executable by the processor 410, when the electronic device 400 runs, the processor 410 communicates with the memory 420 through the bus 430, and when the machine-readable instructions are executed by the processor 410, the steps of the method for processing a software version in the method embodiment shown in fig. 1 may be performed.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the step of the method for processing a software version in the method embodiment shown in fig. 1 may be executed.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some communication interfaces, indirect coupling or communication connection between devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in software functional units and sold or used as a stand-alone product, may be stored in a non-transitory computer-readable storage medium executable by a processor. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present application and are intended to be covered by the appended claims. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method for processing a software version, the method comprising:
responding to a version management instruction sent by a user, and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction;
if the version management instruction is the version issuing instruction, acquiring a current development version number of the target software, identifying a minor version number of the current development version number, and performing numerical updating on the minor version number to determine a new development version number of the target software;
and if the version management instruction is the version repairing instruction, acquiring a sent version number of the target software, repairing a target code corresponding to the sent version number, and modifying the sent version number after the repair is finished to determine a new repaired version number of the target software.
2. The processing method according to claim 1, wherein the obtaining a current development version number of the target software, identifying a minor version number of the current development version number, performing numerical update on the minor version number, and determining a new development version number of the target software comprises:
responding to the version issuing instruction, acquiring the current development version number from a database engineering record, and determining a code address based on the current development version number;
acquiring a main branch code corresponding to the current development version number from a distributed version control database based on the code address;
determining an engineering code corresponding to the current development version number in the main branch code, and identifying a minor version number of the current development version number in the engineering code;
and updating the current numerical value corresponding to the minor version number to determine the newly developed version number of the target software.
3. The process of claim 2, wherein after said determining a newly developed version number of said target software, said process further comprises:
and creating a first version number label in the distributed version control database based on the newly developed version number, associating the first version number label with the main branch code, and creating a version sending record in the database engineering record.
4. The process of claim 1, wherein after said determining a newly developed version number of said target software, said process further comprises:
suffix identification information is added at the end of the newly developed version number.
5. The processing method according to claim 1, wherein the obtaining of the sent version number of the target software, repairing the target code corresponding to the sent version number, and after the repair is completed, modifying the sent version number to determine a new repaired version number of the target software comprises:
responding to the version repairing instruction, acquiring the sent version number from a database engineering record, and determining a second version number label corresponding to the sent version number in a distributed version control database based on the sent version number;
determining a target code corresponding to the sent version number based on the second version number label;
and after the target code is repaired, identifying the revision version number of the sent version number, updating the current value of the revision version number, and determining the number of the new revision version.
6. The process of claim 1, wherein the new revision number comprises a major revision number, a minor revision number, and a revision number, and after the determination of the new revision number of the target software, the process further comprises:
detecting whether the new repaired version number is consistent with the historical development version number;
and if so, updating the current numerical value of the revision version number in the new revision version number.
7. A processing apparatus of a software version, the processing apparatus comprising:
the detection module is used for responding to a version management instruction sent by a user and detecting whether the version management instruction is any one of a version issuing instruction and a version repairing instruction;
the version issuing module is used for acquiring the current development version number of the target software if the version management instruction is the version issuing instruction, identifying the minor version number of the current development version number, carrying out numerical updating on the minor version number and determining the newly developed version number of the target software;
and the modification module is used for acquiring the sent version number of the target software if the version management instruction is the version repair instruction, repairing the target code corresponding to the sent version number, modifying the sent version number after the repair is finished, and determining the new repaired version number of the target software.
8. The processing apparatus according to claim 7, wherein the version issuing module, when configured to obtain a current development version number of the target software, identify a minor version number of the current development version number, perform numerical update on the minor version number, and determine a new development version number of the target software, is configured to:
responding to the version issuing instruction, acquiring the current development version number from a database engineering record, and determining a code address based on the current development version number;
acquiring a main branch code corresponding to the current development version number from a distributed version control database based on the code address;
determining an engineering code corresponding to the current development version number in the main branch code, and identifying a minor version number of the current development version number in the engineering code;
and updating the current numerical value corresponding to the minor version number to determine the newly developed version number of the target software.
9. An electronic device, comprising: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the electronic device is running, the machine-readable instructions being executable by the processor to perform the steps of the method of processing a software version as claimed in any one of claims 1 to 6.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method of processing a software version according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211321370.6A CN115599437B (en) | 2022-10-26 | 2022-10-26 | Software version processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211321370.6A CN115599437B (en) | 2022-10-26 | 2022-10-26 | Software version processing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115599437A true CN115599437A (en) | 2023-01-13 |
| CN115599437B CN115599437B (en) | 2023-10-20 |
Family
ID=84849956
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211321370.6A Active CN115599437B (en) | 2022-10-26 | 2022-10-26 | Software version processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115599437B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115857962A (en) * | 2023-02-20 | 2023-03-28 | 爱集微咨询(厦门)有限公司 | Software project processing method and device, electronic equipment and readable storage medium |
| CN117785274A (en) * | 2024-02-23 | 2024-03-29 | 智业软件股份有限公司 | Method for disassembling version based on gitlab and microservice architecture |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8745612B1 (en) * | 2011-01-14 | 2014-06-03 | Google Inc. | Secure versioning of software packages |
| CN107766074A (en) * | 2017-09-01 | 2018-03-06 | 惠州市德赛西威汽车电子股份有限公司 | A kind of method of automatic generating software version number |
| CN109901858A (en) * | 2019-01-17 | 2019-06-18 | 平安普惠企业管理有限公司 | Application software updates detection method, device, computer equipment and storage medium |
| US20190347091A1 (en) * | 2018-05-11 | 2019-11-14 | Fujitsu Limited | Information processing apparatus and method for managing version number |
| CN112256320A (en) * | 2020-11-04 | 2021-01-22 | 广州繁星互娱信息科技有限公司 | Version number generation method, device, terminal and storage medium |
| CN112783549A (en) * | 2021-01-08 | 2021-05-11 | 东风汽车股份有限公司 | Method for upgrading data version number of automobile electric control element |
| CN113656050A (en) * | 2020-05-12 | 2021-11-16 | 北京字节跳动网络技术有限公司 | Method and device for generating version number |
| CN114780135A (en) * | 2022-03-28 | 2022-07-22 | 东莞市盟大数据科技有限公司 | Project management method and device based on git, electronic equipment and storage medium |
| CN115185821A (en) * | 2022-06-22 | 2022-10-14 | 中国平安财产保险股份有限公司 | Version labeling method, system, equipment and storage medium in program test |
-
2022
- 2022-10-26 CN CN202211321370.6A patent/CN115599437B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8745612B1 (en) * | 2011-01-14 | 2014-06-03 | Google Inc. | Secure versioning of software packages |
| CN107766074A (en) * | 2017-09-01 | 2018-03-06 | 惠州市德赛西威汽车电子股份有限公司 | A kind of method of automatic generating software version number |
| US20190347091A1 (en) * | 2018-05-11 | 2019-11-14 | Fujitsu Limited | Information processing apparatus and method for managing version number |
| CN109901858A (en) * | 2019-01-17 | 2019-06-18 | 平安普惠企业管理有限公司 | Application software updates detection method, device, computer equipment and storage medium |
| CN113656050A (en) * | 2020-05-12 | 2021-11-16 | 北京字节跳动网络技术有限公司 | Method and device for generating version number |
| CN112256320A (en) * | 2020-11-04 | 2021-01-22 | 广州繁星互娱信息科技有限公司 | Version number generation method, device, terminal and storage medium |
| CN112783549A (en) * | 2021-01-08 | 2021-05-11 | 东风汽车股份有限公司 | Method for upgrading data version number of automobile electric control element |
| CN114780135A (en) * | 2022-03-28 | 2022-07-22 | 东莞市盟大数据科技有限公司 | Project management method and device based on git, electronic equipment and storage medium |
| CN115185821A (en) * | 2022-06-22 | 2022-10-14 | 中国平安财产保险股份有限公司 | Version labeling method, system, equipment and storage medium in program test |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115857962A (en) * | 2023-02-20 | 2023-03-28 | 爱集微咨询(厦门)有限公司 | Software project processing method and device, electronic equipment and readable storage medium |
| CN117785274A (en) * | 2024-02-23 | 2024-03-29 | 智业软件股份有限公司 | Method for disassembling version based on gitlab and microservice architecture |
| CN117785274B (en) * | 2024-02-23 | 2024-04-30 | 智业软件股份有限公司 | Method for disassembling version based on gitlab and micro-service architecture |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115599437B (en) | 2023-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108415706B (en) | Method, system, equipment and storage medium for generating visual webpage | |
| CN115599437A (en) | Software version processing method and device, electronic equipment and storage medium | |
| CN109086071A (en) | A kind of method and server of management software version information | |
| CN112558980A (en) | Multi-software-package management method and device | |
| JP6090850B2 (en) | Source program analysis system, source program analysis method and program | |
| CN110442371B (en) | Method, device and medium for releasing codes and computer equipment | |
| CN105446712A (en) | Defect mending method and device for application program | |
| CN110764839A (en) | Business processing flow configuration method, business request processing method and device | |
| CN114020256A (en) | Front-end page generation method, device and equipment and readable storage medium | |
| CN104133743B (en) | A kind of by burning file to the method for EMMC chip and device | |
| WO2019026248A1 (en) | Program development assistance device, program development assistance method, and program development assistance program | |
| CN111367890A (en) | Data migration method and device, computer equipment and readable storage medium | |
| CN114090602A (en) | Configuration file updating method and device, server and storage medium | |
| CN110633258B (en) | Log insertion method, device, computer device and storage medium | |
| CN109582347B (en) | Method and device for acquiring front-end codes | |
| CN114331135B (en) | Process flow management method, device, equipment and storage medium | |
| JP2012168900A (en) | Programming device and program | |
| CN113901025A (en) | Database management method, device, equipment and storage medium | |
| JP2015162218A (en) | Software development apparatus and software development method | |
| KR101534493B1 (en) | Source code security weakness detection apparatus and method based on structure conversion | |
| CN113448614A (en) | Software project code management method and device, storage medium and electronic equipment | |
| JP2018018197A (en) | Source code evaluation program | |
| CN112925561A (en) | Software development method and device, computer equipment and storage medium | |
| CN109002287B (en) | Management method and device for software in cloud data system | |
| CN114398033B (en) | Interface and data stripping design method |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |