CN116204219A - Processing method for software version update, electronic equipment and storage medium - Google Patents
Processing method for software version update, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116204219A CN116204219A CN202111445575.0A CN202111445575A CN116204219A CN 116204219 A CN116204219 A CN 116204219A CN 202111445575 A CN202111445575 A CN 202111445575A CN 116204219 A CN116204219 A CN 116204219A
- Authority
- CN
- China
- Prior art keywords
- software version
- code
- tool
- software
- gerit
- 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
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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/73—Program documentation
Abstract
The invention discloses a processing method for software version update, electronic equipment and a storage medium, wherein the processing method is realized in a Jenkins tool and comprises the following steps: acquiring codes corresponding to the updated software versions; acquiring an altered code of the updated software version relative to the pre-updated software version; the remark theme corresponding to the change code is obtained, and the remark theme is used for updating the content of the remark change code; and generating a hypertext document based on the remark theme for display. According to the processing method, the electronic equipment and the storage medium for the software version update, the remark theme after the software version development content update is obtained through the Jenkins tool and displayed, so that a user can intuitively, conveniently and accurately know the update progress and the gist of the software version; meanwhile, data exposure caused by exposure of specific code content is avoided, so that the development efficiency of the software project is ensured, and meanwhile, the development safety of the software project is maintained.
Description
Technical Field
The present invention relates to the field of development version management technologies, and in particular, to a software version update processing method, an electronic device, and a storage medium.
Background
The development workload of the existing software project is large, the personnel involved in development are more and less, the software project relates to the fact that related personnel mostly need to know the development progress in time, but at the same time, the source code of the software development belongs to core business data and is not easy to see by unrelated personnel, so that contradiction between the two is caused, and the development efficiency of the software project is easily affected. Jenkins is an open source software project and is a continuous integration tool for monitoring continuous repeated software development work, and aims to provide an open and easy-to-use software platform so that the software project can be continuously integrated.
Disclosure of Invention
The invention aims to overcome the defect that the safety of codes and the transparency of the software development progress cannot be considered in the development process in the prior art, and provides a processing method for updating a software version, electronic equipment and a storage medium.
The invention solves the technical problems by the following technical scheme:
the invention provides a processing method for software version update, which is realized in a Jenkins tool and comprises the following steps:
acquiring codes corresponding to the updated software versions;
acquiring an altered code of the updated software version relative to the pre-updated software version;
acquiring remark subjects corresponding to the change codes, wherein the remark subjects are used for remarking updated contents of the change codes;
and generating a hypertext document based on the remark theme for display.
The invention also provides an electronic device, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the processing method of the software version update when executing the computer program.
The invention also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the above-described software version update processing method.
The invention has the positive progress effects that: according to the processing method, the electronic equipment and the storage medium for the software version update, the remark theme after the software version development content update is obtained through the Jenkins tool and displayed, so that a user can intuitively, conveniently and accurately know the update progress and the gist of the software version; meanwhile, data exposure caused by exposure of specific code content is avoided, so that the development efficiency of the software project is ensured, and meanwhile, the development safety of the software project is maintained.
Drawings
Fig. 1 is a flowchart of a processing method of a software version update according to embodiment 1 of the present invention.
Fig. 2 is an application scenario schematic diagram of a processing method of software version update in embodiment 1 of the present invention.
Fig. 3 is a block diagram of an electronic device according to embodiment 2 of the present invention.
Detailed Description
The invention is further illustrated by means of the following examples, which are not intended to limit the scope of the invention.
Example 1
Referring to fig. 1, the embodiment specifically provides a method for processing software version update, where the processing method is implemented in a Jenkins tool, and the processing method includes:
s1, acquiring codes corresponding to updated software versions;
s2, acquiring an altered code of the updated software version relative to the software version before updating;
s3, obtaining remark subjects corresponding to the change codes, wherein the remark subjects are used for updating contents of the remark change codes;
s4, generating a hypertext document based on the remark theme for display.
The continuous integration is a process of team development member integration work in software development, usually, development members are integrated regularly, verification is carried out through automatic project construction, links such as compiling, publishing and automatic testing are included, and therefore integration errors are found as soon as possible, and development efficiency of software projects is improved. The Jenkins tool in the embodiment is a continuous integration tool for software development, and supports continuous integration, automatic test and continuous deployment; the method can continuously and periodically compile according to the configuration, run corresponding codes, and send the running results to mails or display the running results as reports and the like.
The step S1 of obtaining the code corresponding to the updated software version may be implemented based on the Jenkins tool, and the manner includes, but is not limited to, pulling the plug-in through the code of the plug-in Jenkins tool, specifically, selecting a corresponding plug-in submenu in the setting menu of the Jenkins tool, uploading and submitting the plug-in to be loaded, for example, a git plug-in, to obtain the code in the code library, where the obtained plug-in is to be matched with the version of the Jenkins tool, and installing and updating the plug-in may be used to obtain the code corresponding to the updated software version from the code library.
As a preferred embodiment, step S1 is preceded by:
s5, submitting the software source code to a gerit auditing tool for auditing through a git version control system;
s6, if the auditing is passed, triggering the Jenkins tool through a gerit auditing tool so that the Jenkins tool executes the step of acquiring the code corresponding to the updated software version;
wherein, the gerit auditor, the git version control system and the Jenkins tool are configured in a correlated manner.
git is a distributed version control system, and compared with a centralized version control system, git can record all change records of a file, and can enable a software development member to submit development contents to the local and locally copy a complete code warehouse through a code cloning function. That is, the computer of the development members is used as a complete version library without a central server, and the development members can see the modification of each other by pushing the respective modification to each other, so that the development synchronization is realized. The gerit is a code auditor based on a webpage and established on a git version control system, and software programmers of a development team can mutually review the program codes after being modified to determine whether the program codes can be submitted, returned or continuously modified, so that the complete execution of a software development quality assurance mechanism is ensured.
The software project in this embodiment is to manage code such as version control of specific code related to development content based on the git version control system, and those skilled in the art will recognize that the code generally refers to source code of software development, and specifically, the code may be divided into several code libraries according to development content.
gerit is a code auditor and is particularly used in android software projects. As described above, although the Jenkins tool can pull the code replacing content from the git version control system by calling the related interfaces and the like, in the embodiment, the git version control system adopts the gerrit auditing tool to conduct code auditing, and the gerrit auditing tool is a webpage-based code auditing tool built on the git version control system and is used as a very important ring in a software development quality assurance mechanism, and the code auditing mechanism is forcedly introduced in the traditional source code management cooperation flow, and codes which do not meet requirements are shielded outside a code library through the manual code auditing and automatic code verification process, so that multi-user verification, multi-user mutual preparation and automatic construction verification of core codes are ensured.
In the embodiment, step S5 submits the software source code to the gerit auditing tool for auditing through the git version control system, so that members of the development team can mutually review the program codes after modification based on a certain authority to determine whether the modification can be submitted, returned or continued. Usually, a developer can not directly submit the project to a code center server after cloning the project to the local and modifying the code, but can submit the project to a gerit auditing tool for auditing, and the auditing member judges whether the project passes after seeing the information to be audited, and submits the project to a jenkins tool. Specifically, the project created by the user on the git version control system can be forcedly audited, namely, the relevant user is appointed to have only 'report' authority, so that the user does not have authority to directly pull codes by the Jenkins tool through the 'git push' function, and only source codes can be submitted to a gerrit auditor for audit.
And S6, triggering the Jenkins tool when the gerit auditor passes the audit of the submitted source code, so that the Jenkins tool obtains the code corresponding to the updated software version. Specifically, under the premise that the Jenkins tool and the gerit auditor are connected in a configuration mode, the Jenkins tool monitors project events of the gerit auditor, triggers a construction task to test codes, takes a test result in a form of a mark of success or failure of information verification as a return value, and informs relevant auditors of the gerit auditor. Referring to fig. 2, an application scenario diagram of linking a git version control system and a gerit auditing tool through the Jenkins tool is shown, a developer A, B submits codes of a code library a and b to a git server respectively, and after the codes are sent to the gerit server for relevant auditing, version compiling is performed in the Jenkins tool; meanwhile, the hypertext document is generated and output through pulling and changing the remark theme.
Step S2, obtaining the change codes of the updated software version relative to the software version before updating, and determining the change codes by obtaining the marking information of the source codes of the new version and the old version. Preferably, step S2 calls an application interface of the gerit auditor to obtain a modified code of the updated software version relative to the pre-updated software version. When the development process is that the git version control system carries out code management and the related gerit auditors carry out code audit submission, the content states before and after the code audit submission can be compared by the gerit, so that the changed codes of the updated software version can be rapidly and accurately obtained. Specifically, the modified content of the current version of the software item in this development period relative to the previous version, that is, the modified content of each code library, can be obtained by calling the REST API application interface, and the content is summarized and saved.
Preferably, step S6 includes: triggering the Jenkins tool through a triggering plug-in corresponding to the gerit auditing tool; the trigger plug-in is integrated with the Jenkins tool. Specifically, the method can be realized by installing a Trigger plug-in unit "Gerrit Trigger" of a gerit auditing tool in a Jenkins tool, and setting a corresponding gerit auditing tool website in a configuration option of the Jenkins tool after the Trigger plug-in unit is installed and adding required Trigger conditions. Because each code audit in the gerit audit tool has a unique channel number, the return value is stored in the global variable corresponding to the jenkins tool after the trigger plug-in is triggered, so that the trigger task is completed. For example, after configuring trigger docking of a gerit auditor and a jenkins tool, when audit commands in the gerit auditor are executed, the corresponding test tasks of the jenkins tool are automatically triggered. If the task execution is successful automatically, the jenkins tool test is passed.
The remark theme in step S3 is remark information of the updated content of the modified code, for example, "vehicle condition text update", "first page english, spanish text change", etc., and by reading the remark information, the development member can intuitively know the development progress of the software project without corresponding source code reading permission. The mode of obtaining remark subjects corresponding to the changed codes includes, but is not limited to, obtaining remark information of the changed codes from the updated codes, or carrying out remark according to a preset format when the source codes are submitted to the gerit auditor through the Git version control system, or reading remark information of the codes to be audited through calling an application program interface of the gerit auditor.
And step S4, generating a hypertext document based on the remark theme for display. The hypertext document may be presented in a variety of ways including, but not limited to, links, menus, or pop-up boxes, it being understood that the remark theme is presented in the hypertext document. Preferably, the hypertext document further includes at least one of developer information, version identification, and hypertext links corresponding to the altered code. Such as developer information "Zhao Yupeng", version identification "E0009S", and a hypertext link to source code specific information.
As a preferred embodiment, the hypertext links are used to jump to the code corresponding to the updated software version; the jump authority of the hypertext links is correspondingly set according to the auditing authority of the gerit auditing tool on the software source code.
In this embodiment, the hypertext link is set to jump to the code corresponding to the updated software version, so that after the relevant member initially knows the development progress according to the remark theme, the relevant member can jump to the relevant source code further for viewing through the hypertext link; in order to ensure the information security of the source code, the hypertext links are provided with jump authorities, specifically, the corresponding setting can be carried out according to the auditing authorities of the gerit auditing tool to the software source code, for example, an auditing personnel A in the gerit auditing tool has auditing authorities to the code libraries c and d, and an auditing personnel B has auditing authorities to the code libraries c and e; the corresponding authority of the hypertext link is set as the source code of the code library c and d which can be accessed by the auditor A by clicking the hypertext link, and the code library c and e which can be accessed by the auditor B by clicking the hypertext link. For related personnel without access rights, rights error prompt can be presented, or related information such as a catalog of source code files can be provided only. For whether the related authority exists, the judgment can be made according to the login account of the jenkins tool of the related person.
As a preferred embodiment, the processing method further includes: based on the Jenkins tool, compiling the code corresponding to the updated software version. According to the embodiment, the Jenkins tool compiles codes corresponding to the updated software version to generate the program package, and deploys the program package to produce a software product, so that continuous integration of the software project version is realized.
The processing method for updating the software version of the embodiment obtains and displays remark subjects after updating the development content of the software version through the Jenkins tool, so that a user can intuitively, conveniently and accurately know the updating progress and the key points of the software version; meanwhile, data exposure caused by exposure of specific code content is avoided, so that the development efficiency of the software project is ensured, and meanwhile, the development safety of the software project is maintained.
Example 2
Referring to fig. 3, the present embodiment provides an electronic device 30 including a processor 31 and a memory 32 connected thereto, the processor 31 implementing a processing method of software version update as in embodiment 1 when executing a computer program stored on the memory 32. The electronic device 30 shown in fig. 3 is only an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
The electronic device 30 may be in the form of a general purpose computing device, which may be a server device, for example. Components of electronic device 30 may include, but are not limited to: the at least one processor 31, the at least one memory 32, a bus 33 connecting the different system components, including the memory 32 and the processor 31.
The bus 33 includes a data bus, an address bus, and a control bus.
The processor 31 executes various functional applications and data processing such as a processing method of software version update in embodiment 1 of the present invention by running a computer program stored in the memory 32.
The electronic device 30 may also communicate with one or more external devices 34 (e.g., keyboard, pointing device, etc.). Such communication may be through an input/output (I/O) interface 35. Also, model-generating device 30 may also communicate with one or more networks, such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet, via network adapter 36. Network adapter 36 communicates with the other modules of model-generating device 30 via bus 33. Other hardware and/or software modules may be used in connection with the model-generating device 30, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, data backup storage systems, and the like.
It should be noted that although several units/modules or sub-units/modules of an electronic device are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more units/modules described above may be embodied in one unit/module in accordance with embodiments of the present invention. Conversely, the features and functions of one unit/module described above may be further divided into ones that are embodied by a plurality of units/modules.
Example 3
The present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the processing method of the software version update in embodiment 1.
More specifically, among others, readable storage media may be employed including, but not limited to: portable disk, hard disk, random access memory, read only memory, erasable programmable read only memory, optical storage device, magnetic storage device, or any suitable combination of the foregoing.
In a possible implementation, the disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the processing method of implementing the software version update in embodiment 1, when the program product is run on the terminal device.
Wherein the program code for carrying out the present disclosure may be written in any combination of one or more programming languages, and the program code may execute entirely on the user device, partly on the user device, as a stand-alone software package, partly on the user device, partly on a remote device or entirely on the remote device.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that this is by way of example only, and the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the principles and spirit of the invention, but such changes and modifications fall within the scope of the invention.
Claims (9)
1. A method for processing a software version update, the method implemented in a Jenkins tool, the method comprising:
acquiring codes corresponding to the updated software versions;
acquiring an altered code of the updated software version relative to the pre-updated software version;
acquiring remark subjects corresponding to the change codes, wherein the remark subjects are used for remarking updated contents of the change codes;
and generating a hypertext document based on the remark theme for display.
2. The method for processing a software version update according to claim 1, wherein the step of acquiring the code corresponding to the updated software version comprises:
submitting a software source code to a gerit auditing tool for auditing through a git version control system;
if the verification is passed, triggering the Jenkins tool through the gerit verification tool so that the Jenkins tool executes the step of acquiring the code corresponding to the updated software version;
wherein the gerit auditor, the git version control system, and the Jenkins tool are configured in association.
3. The method for processing a software version update according to claim 2, the step of triggering the Jenkins tool by the gerit auditor comprising:
triggering the Jenkins tool through a triggering plug-in corresponding to the gerit auditing tool; the trigger plug-in is integrated with the Jenkins tool.
4. The method for processing a software version update according to claim 2, wherein the step of acquiring the change code of the updated software version with respect to the pre-update software version comprises:
and calling an application interface of the gerit auditor to acquire the changed code of the updated software version relative to the software version before updating.
5. The method for processing a software version update according to claim 1, wherein the hypertext document further comprises at least one of developer information, version identification and hypertext links corresponding to the modification code.
6. The method for processing a software version update according to claim 5, wherein the hypertext link is used for jumping to a code corresponding to the updated software version; and the skip authority of the hypertext link is correspondingly set according to the auditing authority of the gerit auditing tool on the software source code.
7. The method of processing a software version update according to claim 1, the method of processing further comprising:
and compiling codes corresponding to the updated software version based on the Jenkins tool.
8. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of processing a software version update according to any of claims 1-7 when executing the computer program.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of processing a software version update according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111445575.0A CN116204219A (en) | 2021-11-30 | 2021-11-30 | Processing method for software version update, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111445575.0A CN116204219A (en) | 2021-11-30 | 2021-11-30 | Processing method for software version update, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116204219A true CN116204219A (en) | 2023-06-02 |
Family
ID=86508188
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111445575.0A Pending CN116204219A (en) | 2021-11-30 | 2021-11-30 | Processing method for software version update, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116204219A (en) |
-
2021
- 2021-11-30 CN CN202111445575.0A patent/CN116204219A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3769223B1 (en) | Unified test automation system | |
| US5960196A (en) | Software release metric reporting system and method | |
| CN101876943B (en) | Systems and methods for identifying a relationship between multiple interrelated applications in a mainframe environment | |
| US8893106B2 (en) | Change analysis on enterprise systems prior to deployment | |
| US20170372247A1 (en) | Methods, systems, and articles of manufacture for implementing software application development and releases | |
| US11907107B2 (en) | Auto test generator | |
| CN101384995A (en) | Administration automation in application servers | |
| CN112527382B (en) | Method for deploying pipeline engine system, and method and device for continuous integration | |
| US9311077B2 (en) | Identification of code changes using language syntax and changeset data | |
| US10572247B2 (en) | Prototype management system | |
| US20200242559A1 (en) | Dynamically controlling case model structure using case fragments | |
| CN117112060A (en) | Component library construction method and device, electronic equipment and storage medium | |
| CN116204219A (en) | Processing method for software version update, electronic equipment and storage medium | |
| WO2023277802A2 (en) | Device and method for identifying errors in a software application | |
| Ben Charrada et al. | An automated hint generation approach for supporting the evolution of requirements specifications | |
| Colnel et al. | Software quality management approach for WEST CODAC | |
| CN109669868A (en) | The method and system of software test | |
| CN116932414B (en) | Method and equipment for generating interface test case and computer readable storage medium | |
| Whitener et al. | The ERSDT Software Quality Assurance Plan Practices and Development Environment Setup for RASCAL 5 | |
| US11894976B1 (en) | Automated predictive change analytics | |
| WO1998027487A1 (en) | Software release media download system and method | |
| CN115543807A (en) | Automatic regression testing method and device, computer equipment and storage medium | |
| Chaffin et al. | Cross-database searching: the implementation of Metalib | |
| CN114090419A (en) | Program testing method, system, device, electronic equipment and storage medium | |
| Vlasceanu et al. | A study concerning the bug tracking applications |
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 |