CN109086071A - A kind of method and server of management software version information - Google Patents
A kind of method and server of management software version information Download PDFInfo
- Publication number
- CN109086071A CN109086071A CN201810962897.4A CN201810962897A CN109086071A CN 109086071 A CN109086071 A CN 109086071A CN 201810962897 A CN201810962897 A CN 201810962897A CN 109086071 A CN109086071 A CN 109086071A
- Authority
- CN
- China
- Prior art keywords
- code file
- sound code
- version
- project
- target sound
- 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
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 present invention is suitable for field of computer technology, provides the method and server of a kind of management software version information, this method comprises: the script file that operation is preset；When the source code for detecting that terminal is sent merges instruction, the target sound code file that terminal uploads is obtained；Source code in source code and code storage in target sound code file is merged, and is the sound code file distribution version number after merging according to the project information that target sound code file carries；The version information of sound code file after project information and merging that submission explanation based on target sound code file, target sound code file carry, build version change record.The version change record that the present invention generates includes the old version information of project and the submission explanation of each old version information, explanation is submitted to have recorded the content that each version is updated, therefore the old version information of project and the content of each version updating can be learned by version change record, it can be improved the integrality and accuracy of version change record.
Description
Technical field
The invention belongs to field of computer technology more particularly to a kind of methods and server of management software version information.
Background technique
Project of today, scale is increasing, and function is more and more, it is often necessary to multiple developer's joint developments one
Project.Constantly there are the versions such as version iteration, such as 1.1.0,1.1.2,1.2.5 in team project, for developer, project manager
The roles such as member, user can not know the content of the version updating by these version numerical value.
In the prior art, although some projects can arrange the content of special messenger's recording version information and update, work as item
Mesh is larger, when multiple project team co-development same projects, not can guarantee the integrality of version change record and accurate
Property.
Summary of the invention
In view of this, the embodiment of the invention provides the method and server of a kind of management software version information, to solve
In the prior art, when scale of the project is larger, when multiple project team co-development same projects, version change record is not can guarantee
Integrality and accuracy the problem of.
The first aspect of the embodiment of the present invention provides a kind of method of management software version information, comprising:
Run preset script file；Wherein, the script file submits explanation for managing；
When the source code for detecting that terminal is sent merges instruction, the target sound code file that the terminal uploads is obtained；Wherein,
The target sound code file is sound code file to be combined, and the target sound code file includes submitting explanation, source code and project
Information；
Source code in source code and code storage in the target sound code file is merged, and according to the target source
The project information that code file carries is the sound code file distribution version number after merging；
Based on the source code text after the project information and the merging for submitting explanation, the target sound code file to carry
The version information of part generates the version change record of project belonging to the target sound code file；Wherein, the version change note
Record includes that the unique identification, the old version information of the project and each old version information of the project are corresponding
Submit explanation.
The second aspect of the embodiment of the present invention provides a kind of server, including memory, processor and is stored in institute
The computer program that can be run in memory and on the processor is stated, the processor executes real when the computer program
Existing following steps:
Run preset script file；Wherein, the script file submits explanation for managing；
When the source code for detecting that terminal is sent merges instruction, the target sound code file that the terminal uploads is obtained；Wherein,
The target sound code file is sound code file to be combined, and the target sound code file includes submitting explanation, source code and project
Information；
Source code in source code and code storage in the target sound code file is merged, and according to the target source
The project information that code file carries is the sound code file distribution version number after merging；
Based on the source code text after the project information and the merging for submitting explanation, the target sound code file to carry
The version information of part generates the version change record of project belonging to the target sound code file；Wherein, the version change note
Record includes that the unique identification, the old version information of the project and each old version information of the project are corresponding
Submit explanation.
The third aspect of the embodiment of the present invention provides a kind of computer readable storage medium, the computer-readable storage
Media storage has computer program, and the computer program performs the steps of when being executed by processor
Run preset script file；Wherein, the script file submits explanation for managing；
When the source code for detecting that terminal is sent merges instruction, obtains the target sound code file submission that the terminal uploads and say
It is bright；Wherein, the target sound code file is sound code file to be combined, and the target sound code file includes submitting explanation, source code
And project information；
Source code in source code and code storage in the target sound code file is merged, and according to the target source
The project information that code file carries is the sound code file distribution version number after merging；
Based on the source code text after the project information and the merging for submitting explanation, the target sound code file to carry
The version information of part generates the version change record of project belonging to the target sound code file；Wherein, the version change note
Record includes that the unique identification, the old version information of the project and each old version information of the project are corresponding
Submit explanation.
The method and server for implementing a kind of management software version information provided in an embodiment of the present invention have following
The utility model has the advantages that
The embodiment of the present invention passes through the submission explanation for obtaining sound code file to be combined, and based on target source code to be combined
The version letter of sound code file after the project information of project belonging to file, the submission explanation of target sound code file and merging
Breath, build version change record.Due to version change record include the unique identification of the project, the old version information of project with
And the corresponding submission explanation of each old version information, the content for submitting the source code for having recorded this submission in explanation to be updated,
Therefore, the old version information of the project and the content of each version updating can be learned by the version change record of project,
It can be improved the integrality and accuracy of version change record.
Detailed description of the invention
It to describe the technical solutions in the embodiments of the present invention more clearly, below will be to embodiment or description of the prior art
Needed in attached drawing be briefly described, it should be apparent that, the accompanying drawings in the following description is only of the invention some
Embodiment for those of ordinary skill in the art without any creative labor, can also be according to these
Attached drawing obtains other attached drawings.
Fig. 1 is a kind of implementation flow chart of the method for management software version information that one embodiment of the invention provides；
Fig. 2 be another embodiment of the present invention provides a kind of management software version information method implementation flow chart；
Fig. 3 is a kind of schematic diagram for server that one embodiment of the invention provides；
Fig. 4 be another embodiment of the present invention provides a kind of server schematic diagram.
Specific embodiment
In order to make the objectives, technical solutions, and advantages of the present invention clearer, with reference to the accompanying drawings and embodiments, right
The present invention is further elaborated.It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, and
It is not used in the restriction present invention.
Referring to Figure 1, Fig. 1 is a kind of implementation process of the method for management software version information provided in an embodiment of the present invention
Figure.The executing subject of the method for management software version information is server in the present embodiment.Management software version as shown in the figure
The method of information can include:
S101: preset script file is run；Wherein, the script file submits explanation for managing.
Server can run preset script file, when detecting the instruction of one software project of creation to pass through
The script file manages the submission explanation of newly created software project.Alternatively, server can detect terminal request from generation
The instruction of code warehouse downloading source code, when developing to software project belonging to the source code, runs preset script file.Or
Person's server is when detecting that user runs the control instruction of preset script file by the interactive interface triggering of terminal, response
The control instruction runs preset script file.
Preset script file submits explanation (commit message) for managing, and has recorded this in submission explanation and mentions
The content that the source code of friendship updates.Submitting explanation includes three parts: header (header), main body (body), footer (footer).
Wherein, header is required, and main body and footer can be omitted, either which part, and any a line just must not exceed 72 or 100
A character influences beautiful to avoid automatic line feed.
Header only has a line, including three fields: type type (required), range scope (optional) and theme in part
Subject (required).
Type is used to illustrate the type of commit；Scope is used to illustrate the range that commit influences, such as data Layer, control
Preparative layer, view layer etc.；Subject is the Short Description of commit purpose, is no more than 50 characters.
Type only allows to identify using following 7:
Feat: new function (feature)；
Fix: patching fault (bug)；
Docs: document (documentation)；
Style: format (variation for not influencing code operation)；
Refactor: reconstruct (neither what's new, nor the code variations of modification failure)；
Test: increase test；
Chore: the variation of building process or auxiliary tool.
Software project is developed with source code trunk branch, is had in code storage and only one trunk.Source code master
Dry branch's development mode include: the more Stable Branchs of pioneer's trunk, guard the more pioneer branches of trunk, trunk without branch, guard trunk
Single branch.More Stable Branchs of pioneer's trunk and to guard the more pioneer branches of trunk be common development mode.
Wherein, the 1) development mode of the more Stable Branchs of pioneer's trunk specifically: after obtaining a stable release, this is stablized
As soon as version is put into Ge Xin branch, the patch up for this stable release carries out in this branch, and new function is not herein
It is developed in branch, and carries out the exploitation of new function on trunk.This is industry using more mode.
Some modifications on Stable Branch, such as defect (bug) are repaired, and need to be merged into trunk, but some specific modifications,
It does not need to be merged into trunk.At this moment it should be noted that merging accurate file to trunk.
2) development mode of the more pioneer branches of trunk is guarded specifically: after obtaining a stable release, pioneer branch is pulled out,
New function is developed in branch, is patched up on trunk.After pioneer branch is by certain test, it is merged into master
It is dry.Can have multiple pioneer branches simultaneously, different functions can draw different branches, different issuing time points and again simultaneously
The content of exploitation must be in different branches.
Said from the angle of publication, more recommend will certainly issue together in be received in identical pioneer branch.
It is stable release forever on trunk, can issues at any time.The modification of bug and the increase of new function, all in branch
Upper progress.And each bug and new function have different exploitation branches, are kept completely separate.And to the publication each time on trunk
All make a label rather than branch.Exploitation in branch and trunk is just merged into after being completed.This dissemination method
Benefit is that the content adjustment issued every time gets up to be easier.If some new function or the bug nothing before issue next time
Method is completed, it is then not possible to is merged into trunk, would not also be influenced the publication of other changes.In addition, the lifetime ratio of each branch
It is shorter, it is unique it is long-standing is exactly trunk, merge that there is very little risk every time in this way.Every time before publication, as long as comparing trunk
On latest edition and the version of last publication be just able to know that the file extent specifically issued.
3) the branchiess development mode of trunk specifically: only trunk, without branch, all urgent normal modifications exist entirely
On trunk, the thing of half is developed if wanting online, cleverly to be concealed.Height is proposed to the structure of program to want
It asks, on and off to facilitate, switchgear distribution can't do without.Single to say from efficiency, this is most efficient mode.Have many
Supplementary measures just can be with.Common supplementary measures: daily integrated (compiling deployment test), static code inspection, test is not only
There is unit testing, there are also interface testings, and there are also interface automation tests.
4) development mode of trunk list branch is guarded specifically: only one branch, urgent modification carry out on trunk, just
Normally opened hair carries out in branch, trunk and branch bi-directional synchronization as needed.It needs using identical mating without branch with trunk
Means, and the daily integrated or even continuous integrating of construction is required on trunk and branch.
S102: when the source code for detecting that terminal is sent merges instruction, the target sound code file that the terminal uploads is obtained；
Wherein, the target sound code file be sound code file to be combined, the target sound code file include submit explanation, source code and
Project information.
When the same software project of multiple developer's co-developments, by terminal from the code storage of server loading source
Code file is developed, and the sound code file of downloading carries the project information of its affiliated project.Project information includes the unique of project
Mark and version information.The title that unique identification can be project is also possible to the uniform resource locator (Uniform of project
Resource Locator, URL) address.Version information in project information entrained by the sound code file of downloading includes version
Number, version number refers to the version number of the sound code file stored in code storage.When project information can also include version change
Between, the version change time refers to the version change time of the sound code file stored in code storage.
Developer is after the sound code file based on downloading completes exploitation, and developer is by terminal login service device, later, leads to
It crosses terminal updated target sound code file is uploaded onto the server, at this point, developer can pass through interaction circle of click terminal
Sound code file synthesis option triggering terminal in face generates source code and merges instruction, and the source code of generation is merged instruction to server
It sends.
Developer includes submitting explanation by the target sound code file that terminal to server uploads, and submitting explanation includes uploading
Sound code file information, the submission illustrate for describe this upload sound code file and downloading sound code file between difference
It is different, for example, newly-increased function or the bug of reparation etc..Its affiliated item is carried in the target sound code file for the update that developer uploads
Purpose project information, project information include version number, and version number refers to the version number of the sound code file before the update, i.e. code storehouse
The version number of the sound code file stored in library.
It is understood that developer can be when each sound code file for uploading and updating, by clicking interaction circle
Sound code file synthesis option triggering terminal in face generates source code and merges instruction；It can also be in the sound code file for uploading more parts of updates
Afterwards, option triggering terminal is synthesized by the sound code file clicked in interactive interface and generates sound code file merging instruction, at this point, exploitation
Person can be uploaded a for describing the sound code file of more parts of sound code files and downloading of this upload by terminal to server
Between difference submission explanation.Alternatively, terminal get developer by interactive interface to server upload it is updated
When sound code file, terminal automatically generates source code and merges instruction, and sends it to server.Source code synthetic instruction is used to indicate clothes
Business device merges the sound code file in sound code file and server that developer uploads.
If terminal is when uploading a sound code file and uploading the submission of the sound code file and illustrate, triggering source code synthesis refers to
It enables, then, source code merges the code of the source code that instruction is used to indicate in this sound code file for uploading terminal and server
Trunk in warehouse merges.
If terminal upload more parts of sound code files and upload it is a for describe more parts of sound code files of this upload with
When the submission of difference between the sound code file of downloading illustrates, source code synthetic instruction is triggered, then, source code merges instruction for referring to
Show and merges the trunk in the code storage of source code and server in more parts of sound code files of terminal upload.
Server obtains the target sound code file that terminal uploads when the source code for getting terminal transmission merges instruction, and
Obtain submission explanation, project information and the source code in target sound code file.
Wherein, when source code merges the source code and server that instruction is used to indicate in this sound code file for uploading terminal
Code storage in source code when merging, the quantity of target sound code file is portion, the submission explanation that server is got
This corresponding submission explanation of portion target source code file uploaded for terminal.
When source code merges the code of the source code that instruction is used to indicate in more parts of sound code files for uploading terminal and server
When source code in warehouse merges, the quantity of target sound code file is more parts, and the submission explanation that server is got can be
The common corresponding submission explanation of the more parts of target sound code files that terminal uploads.
S103: the source code in the source code and code storage in the target sound code file is merged, and according to described
The project information that target sound code file carries is the sound code file distribution version number after merging.
For server when detecting that source code merges instruction, response source code merges instruction, the source code text submitted according to developer
The unique identification and version information for including in the project information that part carries, obtain matched with unique identification and version information
All sound code files, by the source in the code storage of source code and server in the target sound code file to be combined of terminal upload
Code merges, the sound code file after being merged.
Sound code file after merging includes the source code in source code and code storage in target sound code file.After merging
Sound code file in, the source code of target sound code file can be used as one of branch on the trunk of code storage, Huo Zhezuo
For the trunk of code storage.
The source code and code storage being illustrated for needing to merge a version scope in target sound code file below
In source code merge implementation:
It, can be by the source code of target sound code file if the source code of target sound code file belongs to the trunk of code storage
It is merged into the branch of code storage, (source code modified in trunk is by the source in target sound code file by the source code modified in trunk
Code and the determination of the source code of the trunk in code storage) it is synchronized in branch, the trunk belonged in code storage at this time is merged into point
The case where branch；If the source code of target sound code file belongs to the branch of code storage, the source code of target sound code file is closed
And the trunk of code storage is arrived, the source code modified in branch is synchronized to trunk, the branch belonged in code storage at this time merges
The case where to trunk.
Server also obtains the project information that the target sound code file of terminal upload carries, due to containing in project information
The version information of the unique identification and target source code of project belonging to target sound code file before the update, therefore, server exists
When getting the project information of target sound code file carrying, it can be got according to the unique identification determination for including in project information
Target sound code file belonging to software project；Each software item purpose mark and each software in code storage based on server
The version information of project determines the current version number of software project belonging to target sound code file；Server is believed also according to project
Version information in breath determines the version number of target sound code file before the update；Later, it is being updated based on target sound code file
The current version number of software project belonging to preceding version number, target sound code file is to merge by preset version allocation strategy
Sound code file afterwards distributes version number.The version number of sound code file after merging is higher than software project belonging to target sound code file
Current version number.Version allocation strategy can be configured according to actual needs, herein without limitation.
It is understood that S102 may be performed simultaneously with S103.
S104: after the project information and the merging for submitting explanation, the target sound code file to carry
The version information of sound code file generates the version change record of project belonging to the target sound code file；Wherein, the version
Change record includes the unique identification of the project, the old version information of the project and each old version information
Corresponding submission explanation.
The unique identification for the project for including in the project information that server can be carried according to target sound code file, from data
It searches in library and is recorded with the matched version change of the unique identification of the project.
Server is when finding version change record matched with the unique identification of the project, in version change record
It has recorded before target sound code file is synthesized with the trunk source code in code storage, the institute of project belonging to target sound code file
There are old version information and the corresponding submission explanation of each old version；Server is based on that target sound code file is corresponding mentions
The version information of sound code file after handing over explanation and merging, update gets version change record, to generate target source code
The newest version change of project belonging to file records.It is had recorded in the newest version change record, unique mark of project
Knowledge, the old version information of project and the corresponding submission explanation of each old version information.At this point, in target sound code file
Source code merge with the source code in code storage after sound code file version information be target sound code file belonging to project most
New old version information.
Server determines in database not when not finding version change record matched with the unique identification of the project
There are the version change of project records, and the project did not updated before this.Server is corresponding according to target sound code file
The version information of sound code file after submitting explanation and merging creates the version change note of project belonging to target sound code file
Record.After version change record includes the unique identification of the project, the corresponding submission explanation of target sound code file and merges
The version information of sound code file.
Further, when the version information in version change record may include each version number corresponding version change
Between.
It is understood that the code storage in server in embodiments of the present invention can be the warehouse Git, code storehouse
It include source code and version information in library, Git is the distributed version control system (Version Control of open source code of an open source
Software), can effectively, the processing of high speed is from very little to very big Item version management.
The embodiment of the present invention, by obtaining the submission explanation of sound code file to be combined, and based on source code text to be combined
The version information of sound code file after the project information of project belonging to part, the submission explanation got and merging, generates version
This change record.Since version change record includes the unique identification of the project, the old version information of project and is each gone through
Therefore the corresponding submission explanation of history version information, the content for submitting the source code for having recorded this submission in explanation to be updated pass through
The version change record of project can learn the old version information of the project and the content of each version updating, can be improved version
The integrality and accuracy of this change record.
Refer to Fig. 2, Fig. 2 be another embodiment of the present invention provides a kind of management software version information method realization
Flow chart.The executing subject of the method for management software version information is server in the present embodiment.Management software as shown in the figure
The method of version information can include:
S201: preset script file is run；Wherein, the script file submits explanation for managing.
S201 is identical as the S101 in a upper embodiment in the present embodiment, referring specifically to the phase of S101 in a upper embodiment
Description is closed, details are not described herein again.
S202: when the source code for detecting that terminal is sent merges instruction, obtaining the target sound code file that the terminal uploads,
Hook program is called to obtain the submission explanation in the target sound code file；Wherein, the target sound code file is to be combined
Sound code file, the target sound code file include submitting explanation, source code and project information.
When the same software project of multiple developer's co-developments, by terminal from the code storage of server loading source
Code file is developed, and the sound code file of downloading carries the project information of its affiliated project.Project information includes the unique of project
Mark and version information.The title that unique identification can be project is also possible to the uniform resource locator (Uniform of project
Resource Locator, URL) address.Version information in project information entrained by the sound code file of downloading includes version
Number, version number refers to the version number of the sound code file stored in code storage.When project information can also include version change
Between, the version change time refers to the version change time of the sound code file stored in code storage.
Developer is after the sound code file based on downloading completes exploitation, and developer is by terminal login service device, later, leads to
It crosses terminal updated target sound code file is uploaded onto the server, at this point, developer can pass through interaction circle of click terminal
Sound code file synthesis option triggering terminal in face generates source code and merges instruction, and the source code of generation is merged instruction to server
It sends.
Developer includes submitting explanation by the target sound code file that terminal to server uploads, and submitting explanation includes uploading
Sound code file information, the submission illustrate for describe this upload sound code file and downloading sound code file between difference
It is different, for example, newly-increased function or the bug of reparation etc..Its affiliated item is carried in the target sound code file for the update that developer uploads
Purpose project information, project information include version number, and version number refers to the version number of the sound code file before the update, i.e. code storehouse
The version number of the sound code file stored in library.
It is understood that developer can be when each sound code file for uploading and updating, by clicking interaction circle
Sound code file synthesis option triggering terminal in face generates source code and merges instruction；It can also be in the sound code file for uploading more parts of updates
Afterwards, option triggering terminal is synthesized by the sound code file clicked in interactive interface and generates sound code file merging instruction, at this point, exploitation
Person can be uploaded a for describing the sound code file of more parts of sound code files and downloading of this upload by terminal to server
Between difference submission explanation.Alternatively, terminal get developer by interactive interface to server upload it is updated
When sound code file, terminal automatically generates source code and merges instruction, and sends it to server.Source code synthetic instruction is used to indicate clothes
Business device merges the sound code file in sound code file and server that developer uploads.
If terminal is when uploading a sound code file and uploading the submission of the sound code file and illustrate, triggering source code synthesis refers to
It enables, then, source code merges the code of the source code that instruction is used to indicate in this sound code file for uploading terminal and server
Trunk in warehouse merges.
If terminal upload more parts of sound code files and upload it is a for describe more parts of sound code files of this upload with
When the submission of difference between the sound code file of downloading illustrates, source code synthetic instruction is triggered, then, source code merges instruction for referring to
Show and merges the trunk in the code storage of source code and server in more parts of sound code files of terminal upload.
Server obtains the target sound code file that terminal uploads, root when the source code for getting terminal transmission merges instruction
According to the information (for example, the unique identification for the target sound code file that terminal uploads) of target sound code file, hook program is called to pass through
The hook (hook) of explanation is submitted to obtain the corresponding submission explanation of target sound code file for obtaining.It is stored in advance in server
The trigger action of hook hook.In the present embodiment, the trigger event of the hook for obtaining submission explanation is to get source code
Merge instruction.
Wherein, when source code merges the source code and server that instruction is used to indicate in this sound code file for uploading terminal
Code storage in source code when merging, the quantity of target sound code file is portion, the submission explanation that server is got
This corresponding submission explanation of portion target source code file uploaded for terminal.
When source code merges the code of the source code that instruction is used to indicate in more parts of sound code files for uploading terminal and server
When source code in warehouse merges, the quantity of target sound code file is more parts, and the submission explanation that server is got is terminal
The common corresponding submission explanation of the more parts of target sound code files uploaded.
Further, for the ease of user by submitting the content for illustrating to understand target source code file and being updated, in S202
Later, it can also include S203: the submission is illustrated to carry out the processing that labels.
Server get target sound code file it is corresponding submission illustrate when, according to submit explanation include content determine
The label that the submission illustrates, and (tag) processing that labelled is illustrated to the submission based on determining label.Tag is alternatively
It is a kind of keyword tag, more conducively search is searched；But tag is also different from general keyword, with general keyword into
When row search, the keyword submitted and illustrate that the inside refers to can only be searched, but make good use of tag can to submit root in explanation
This no keyword is marked as tag.
Further, for the ease of user by submitting the accurate content learning target sound code file and being updated of explanation,
S203 can be with specifically: obtain the header information for submitting explanation, according to include in the header information type field, master
The information of autograph section instruction is determining and the label for submitting explanation is arranged.
Due to submitting the page Header of explanation, including three fields: type type (required), range scope (optional)
With theme subject (required)；Type is used to illustrate the type of commit (for example, new function, patching fault, increase test
Deng), subject is short description between commit purpose, therefore, server can according in header the type field and
Information that both subject fields respectively indicate determines the label for submitting explanation, and according to determining label to submission illustrate into
The capable processing that labels, the label for submitting explanation is arranged.
S204: the source code in the source code and code storage in the target sound code file is merged, and according to described
The project information that target sound code file carries is the sound code file distribution version number after merging.
S204 is identical as the S103 in a upper embodiment in the present embodiment, referring specifically to the phase of S103 in a upper embodiment
Description is closed, details are not described herein again.
Wherein, S204 and S202 can be performed simultaneously.
S205: after the project information and the merging for submitting explanation, the target sound code file to carry
The version information of sound code file generates the version change record of project belonging to the target sound code file；Wherein, the version
Change record includes the unique identification of the project, the old version information of the project and each old version information
Corresponding submission explanation.
S205 is identical as the S104 in a upper embodiment in the present embodiment, referring specifically to the phase of S104 in a upper embodiment
Description is closed, details are not described herein again.
Further, the version information of sound code file after merging include merge after sound code file version number and
The version change time (the version change time by the source code in the source code and code storage in target sound code file merge when
Between determine) when, S205 specifically: based on it is described submit explanation, the target sound code file carry project information, the merging
The version change time of sound code file after the version number of sound code file afterwards and the merging generates the target sound code file
The version change of affiliated project records.
The unique identification for the project for including in the project information that server can be carried according to target sound code file, from data
It searches in library and is recorded with the matched version change of the unique identification of the project.
Server is when finding version change record matched with the unique identification of the project, in version change record
It has recorded before target sound code file is synthesized with the trunk source code in code storage, the institute of project belonging to target sound code file
Have old version information and an each old version corresponding submission explanation, old version information include old version number and
The each old version number corresponding version change time.
Server is based on the corresponding version information for submitting the sound code file after illustrating and merging of target sound code file, more
Version change record is newly got, to generate the newest version change record of project belonging to target sound code file.This is most
It is had recorded in new version change record, the corresponding version of the unique identification of project, the old version number of project, old version number
Change time and the corresponding submission explanation of each old version number.At this point, source code and code storage in target sound code file
In source code merge after sound code file version information be target sound code file belonging to project newest old version letter
Breath.
Server determines in database not when not finding version change record matched with the unique identification of the project
There are the version change of project records, and the project did not updated before this.Server is corresponding according to target sound code file
The version number of sound code file after submitting explanation, merging and version change time, create project belonging to target sound code file
Version change record.Version change record includes the unique identification of the project, the corresponding submission explanation of target sound code file, closes
The version number of sound code file after and and version change time.
It is understood that when submission explanation of method after executing S203, in S205 of management software version information
For by labelling, treated submits explanation.
It should be understood that the size of the serial number of each step is not meant that the order of the execution order in above-described embodiment, each process
Execution sequence should be determined by its function and internal logic, the implementation process without coping with the embodiment of the present invention constitutes any limit
It is fixed.
Referring to Fig. 3, Fig. 3 is a kind of schematic diagram for server that one embodiment of the invention provides.Server includes each
Unit is used to execute each step in the corresponding embodiment of FIG. 1 to FIG. 2.Referring specifically to the corresponding embodiment of FIG. 1 to FIG. 2
In associated description.For ease of description, only the parts related to this embodiment are shown.Referring to Fig. 3, server 3 includes:
Script running unit 310, for running preset script file；Wherein, the script file is submitted for managing
Explanation；
Acquiring unit 320, for obtaining the mesh that the terminal uploads when the source code for detecting that terminal is sent merges instruction
Mark sound code file；Wherein, the target sound code file is sound code file to be combined, and the target sound code file includes submitting to say
Bright, source code and project information；
Combining unit 330, for the source code in the source code and code storage in the target sound code file to be merged,
And according to the target sound code file carry project information be merge after sound code file distribution version number；
Generation unit 340, for based on the project information for submitting explanation, the target sound code file to carry and institute
The version information for stating the sound code file after merging generates the version change record of project belonging to the target sound code file；Its
In, version change record includes the unique identification of the project, the old version information of the project and each described
The corresponding submission explanation of old version information.
Further, acquiring unit 320 is specifically used for: when the source code for detecting that terminal is sent merges instruction, obtaining institute
The target sound code file of terminal upload is stated, hook program is called to obtain the submission explanation of the sound code file uploaded.
Further, server further include:
Marking unit, for illustrating to carry out the processing that labels to the submission.
Further, marking unit is specifically used for: the header information for submitting explanation is obtained, according to the header information
In the type field that includes, the information of subject field instruction it is determining and the label for submitting explanation is set.
Further, the version information of the sound code file after the merging includes the version of the sound code file after the merging
Number and the version change time；Generation unit 340 is specifically used for: being carried based on submission explanation, the target sound code file
Project information, the version number of sound code file after the merging and the version change time of the sound code file after the merging,
Generate the version change record of project belonging to the target sound code file.
Fig. 4 be another embodiment of the present invention provides a kind of server schematic diagram.As shown in figure 4, the clothes of the embodiment
Business device 4 includes: processor 40, memory 41 and is stored in the memory 41 and can run on the processor 40
Computer program 42, such as the control program of server.The processor 40 is realized above-mentioned when executing the computer program 42
Step in the embodiment of the method for the management software version information of each server, such as S101 shown in FIG. 1 to S104.Or
Person, the processor 40 realize the function of each unit in above-mentioned each Installation practice when executing the computer program 42, such as
The function of unit 310 to 340 shown in Fig. 3.
Illustratively, the computer program 42 can be divided into one or more units, one or more of
Unit is stored in the memory 41, and is executed by the processor 40, to complete the present invention.One or more of lists
Member can be the series of computation machine program instruction section that can complete specific function, and the instruction segment is for describing the computer journey
Implementation procedure of the sequence 42 in the server 4.For example, the computer program 42 can be divided into script running unit,
Acquiring unit, combining unit and generation unit, each unit concrete function are as described above.
The server may include, but be not limited only to, processor 40, memory 41.It will be understood by those skilled in the art that
Fig. 4 is only the example of server 4, does not constitute the restriction to server 4, may include than illustrating more or fewer portions
Part perhaps combines certain components or different components, such as the server can also include input and output server, net
Network access server, bus etc..
Alleged processor 40 can be central processing unit (Central Processing Unit, CPU), can also be
Other general processors, digital signal processor (Digital Signal Processor, DSP), specific integrated circuit
(Application Specific Integrated Circuit, ASIC), ready-made programmable gate array (Field-
Programmable Gate Array, FPGA) either other programmable logic device, discrete gate or transistor logic,
Discrete hardware components etc..General processor can be microprocessor or the processor is also possible to any conventional processor
Deng.
The memory 41 can be the internal storage unit of the server 4, such as the hard disk or memory of server 4.
The memory 41 is also possible to the external storage servers of the server 4, such as the plug-in type being equipped on the server 4
Hard disk, intelligent memory card (Smart Media Card, SMC), secure digital (Secure Digital, SD) card, flash card
(Flash Card) etc..Further, the memory 41 can also both include the internal storage unit of the server 4 or wrap
Include external storage servers.The memory 41 is for other journeys needed for storing the computer program and the server
Sequence and data.The memory 41 can be also used for temporarily storing the data that has exported or will export.
Embodiment described above is merely illustrative of the technical solution of the present invention, rather than its limitations；Although referring to aforementioned reality
Applying example, invention is explained in detail, those skilled in the art should understand that: it still can be to aforementioned each
Technical solution documented by embodiment is modified or equivalent replacement of some of the technical features；And these are modified
Or replacement, the spirit and scope for technical solution of various embodiments of the present invention that it does not separate the essence of the corresponding technical solution should all
It is included within protection scope of the present invention.
Claims (10)
1. a kind of method of management software version information characterized by comprising
Run preset script file；Wherein, the script file submits explanation for managing；
When the source code for detecting that terminal is sent merges instruction, the target sound code file that the terminal uploads is obtained；Wherein, described
Target sound code file is sound code file to be combined, and the target sound code file includes submitting explanation, source code and project information；
Source code in source code and code storage in the target sound code file is merged, and according to the target source code text
The project information that part carries is the sound code file distribution version number after merging；
Based on the sound code file after the project information and the merging for submitting explanation, the target sound code file to carry
Version information generates the version change record of project belonging to the target sound code file；Wherein, the version change record packet
Include the unique identification of the project, the old version information of the project and the corresponding submission of each old version information
Explanation.
2. the method according to claim 1, wherein described when the source code merging instruction for detecting that terminal is sent
When, obtain the target sound code file that the terminal uploads, comprising:
When the source code for detecting that terminal is sent merges instruction, the target sound code file that the terminal uploads is obtained, calls hook
Program obtains the submission explanation in the target sound code file.
3. according to the method described in claim 2, it is characterized in that, described when the source code merging instruction for detecting that terminal is sent
When, after calling hook program to obtain the submission explanation of the target sound code file uploaded, further includes:
The submission is illustrated to carry out the processing that labels.
4. according to the method described in claim 3, it is characterized in that, described illustrate label to handle packet to the submission
It includes:
Obtain it is described submit explanation header information, according to include in the header information type field, subject field indicate
Information it is determining and the label for submitting explanation is set.
5. method according to any one of claims 1 to 4, which is characterized in that the version of the sound code file after the merging
Information includes version number and the version change time of the sound code file after the merging；It is described to be based on submission explanation, institute
The version information of sound code file after stating the project information and the merging of target sound code file carrying, generates the target source
The version change record of project belonging to code file, comprising:
Version based on the sound code file after the project information for submitting explanation, the target sound code file to carry, the merging
The version change time of sound code file after this number and the merging, generate the version of project belonging to the target sound code file
Change record.
6. a kind of server, which is characterized in that the server includes memory, processor and stores in the memory
And the computer program that can be run on the processor, the processor realize following step when executing the computer program
It is rapid:
Run preset script file；Wherein, the script file submits explanation for managing；
When the source code for detecting that terminal is sent merges instruction, the target sound code file that the terminal uploads is obtained；Wherein, described
Target sound code file is sound code file to be combined, and the target sound code file includes submitting explanation, source code and project information；
Source code in source code and code storage in the target sound code file is merged, and according to the target source code text
The project information that part carries is the sound code file distribution version number after merging；
Based on the sound code file after the project information and the merging for submitting explanation, the target sound code file to carry
Version information generates the version change record of project belonging to the target sound code file；Wherein, the version change record packet
Include the unique identification of the project, the old version information of the project and the corresponding submission of each old version information
Explanation.
7. server according to claim 6, which is characterized in that described when the source code merging instruction for detecting that terminal is sent
When, obtain the target sound code file that the terminal uploads, comprising:
When the source code for detecting that terminal is sent merges instruction, the target sound code file that the terminal uploads is obtained, calls hook
Program obtains the submission explanation in the target sound code file.
8. server according to claim 7, which is characterized in that described when the source code merging instruction for detecting that terminal is sent
When, after calling hook program to obtain the submission explanation in the target sound code file uploaded, the processor executes the calculating
Following steps are also realized when machine program: the submission is illustrated to carry out the processing that labels.
9. server according to claim 8, which is characterized in that described to illustrate label to the submission to handle packet
It includes:
Obtain it is described submit explanation header information, according to include in the header information type field, subject field indicate
Information it is determining and the label for submitting explanation is set.
10. a kind of computer readable storage medium, the computer-readable recording medium storage has computer program, and feature exists
In when the computer program is executed by processor the step of any one of such as claim 1 to 5 of realization the method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810962897.4A CN109086071A (en) | 2018-08-22 | 2018-08-22 | A kind of method and server of management software version information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810962897.4A CN109086071A (en) | 2018-08-22 | 2018-08-22 | A kind of method and server of management software version information |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109086071A true CN109086071A (en) | 2018-12-25 |
Family
ID=64794416
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810962897.4A Pending CN109086071A (en) | 2018-08-22 | 2018-08-22 | A kind of method and server of management software version information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109086071A (en) |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109683955A (en) * | 2018-12-29 | 2019-04-26 | 北京奇艺世纪科技有限公司 | Version repository clone method and system |
| CN109947657A (en) * | 2019-04-03 | 2019-06-28 | 广东电网有限责任公司 | A kind of the mobility scale analysis method and system of enterprise-level information management system |
| CN110134431A (en) * | 2019-04-16 | 2019-08-16 | 深圳壹账通智能科技有限公司 | Code data management method and system |
| CN110162334A (en) * | 2019-05-29 | 2019-08-23 | 上海摩软通讯技术有限公司 | A kind of code administration method, apparatus, storage medium and computer program product |
| CN110750243A (en) * | 2019-09-20 | 2020-02-04 | 中国联合网络通信集团有限公司 | Project code development method and system |
| CN110751797A (en) * | 2019-09-30 | 2020-02-04 | 南京紫津融畅信息科技服务有限公司 | ATM system fault processing method, system and storage medium |
| CN110990055A (en) * | 2019-12-19 | 2020-04-10 | 南京邮电大学 | Pull Request function classification method based on program analysis |
| CN111399841A (en) * | 2020-03-10 | 2020-07-10 | Oppo广东移动通信有限公司 | Block chain-based code processing method and device, storage medium and electronic equipment |
| CN111459535A (en) * | 2020-03-19 | 2020-07-28 | 深圳木成林科技有限公司 | Branch merging method, device, equipment and computer storage medium |
| CN111506339A (en) * | 2020-05-29 | 2020-08-07 | 北京奇艺世纪科技有限公司 | Method and device for processing change information of Software Development Kit (SDK) |
| CN111552778A (en) * | 2020-04-26 | 2020-08-18 | 北京达佳互联信息技术有限公司 | Audio resource management method, device, computer readable storage medium and equipment |
| CN111638903A (en) * | 2020-05-08 | 2020-09-08 | 北京达佳互联信息技术有限公司 | Method and device for generating difference information of different software versions |
| CN111666081A (en) * | 2020-04-30 | 2020-09-15 | 平安科技（深圳）有限公司 | Project version release method, device, equipment and medium based on Git |
| CN111708747A (en) * | 2020-06-15 | 2020-09-25 | 中国航空工业集团公司西安飞行自动控制研究所 | Method for generating version tree of distributed version management document |
| CN111767075A (en) * | 2020-06-23 | 2020-10-13 | 北京思特奇信息技术股份有限公司 | Method and device for synchronizing application program versions |
| CN111782239A (en) * | 2020-06-03 | 2020-10-16 | 中移（杭州）信息技术有限公司 | Software packaging and source code version information acquisition method, device and storage medium |
| CN111796855A (en) * | 2020-07-22 | 2020-10-20 | 大箴(杭州)科技有限公司 | Incremental version updating method and device, storage medium and computer equipment |
| CN111966353A (en) * | 2020-08-13 | 2020-11-20 | 北京金山云网络技术有限公司 | Job development method and device, electronic equipment and storage medium |
| CN112114859A (en) * | 2020-09-17 | 2020-12-22 | 云账户技术(天津)有限公司 | File processing method and device and storage medium |
| CN112148350A (en) * | 2020-09-04 | 2020-12-29 | 深圳市大富网络技术有限公司 | Remote version management method for works, electronic device and computer storage medium |
| CN112256320A (en) * | 2020-11-04 | 2021-01-22 | 广州繁星互娱信息科技有限公司 | Version number generation method, device, terminal and storage medium |
| CN112650724A (en) * | 2020-12-25 | 2021-04-13 | 中国工商银行股份有限公司 | Document file processing method, system, computing device and medium |
| WO2021068740A1 (en) * | 2019-10-10 | 2021-04-15 | 深圳前海微众银行股份有限公司 | File management method and device |
| CN112783533A (en) * | 2021-02-03 | 2021-05-11 | 北京达佳互联信息技术有限公司 | Version information updating method, version information updating device, terminal and storage medium |
| CN112835614A (en) * | 2021-01-29 | 2021-05-25 | 宝宝巴士股份有限公司 | Method for optimizing generation of curriculum packets |
| CN112947986A (en) * | 2020-09-29 | 2021-06-11 | 深圳市明源云科技有限公司 | Multi-version code sign-in control method and device, client and storage medium |
| CN112948734A (en) * | 2021-02-25 | 2021-06-11 | 平安普惠企业管理有限公司 | Project style integration and adaptation method, device, equipment and storage medium |
| CN113127027A (en) * | 2019-12-31 | 2021-07-16 | 深圳云天励飞技术有限公司 | Version updating method and device based on distributed version control system |
| CN113448614A (en) * | 2021-06-29 | 2021-09-28 | 北京金山云网络技术有限公司 | Software project code management method and device, storage medium and electronic equipment |
| CN113703417A (en) * | 2021-07-13 | 2021-11-26 | 交控科技股份有限公司 | Method and device for determining test cases of full-automatic scene of train operation |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461578A (en) * | 2014-12-26 | 2015-03-25 | 广州唯品会信息科技有限公司 | Automatic code merging method and system |
| CN105404519A (en) * | 2015-12-07 | 2016-03-16 | 青岛海信电器股份有限公司 | Version control method, code testing method and system |
| CN108170469A (en) * | 2017-12-20 | 2018-06-15 | 南京邮电大学 | A kind of Git warehouses similarity detection method that history is submitted based on code |
-
2018
- 2018-08-22 CN CN201810962897.4A patent/CN109086071A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461578A (en) * | 2014-12-26 | 2015-03-25 | 广州唯品会信息科技有限公司 | Automatic code merging method and system |
| CN105404519A (en) * | 2015-12-07 | 2016-03-16 | 青岛海信电器股份有限公司 | Version control method, code testing method and system |
| CN108170469A (en) * | 2017-12-20 | 2018-06-15 | 南京邮电大学 | A kind of Git warehouses similarity detection method that history is submitted based on code |
Cited By (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109683955A (en) * | 2018-12-29 | 2019-04-26 | 北京奇艺世纪科技有限公司 | Version repository clone method and system |
| CN109683955B (en) * | 2018-12-29 | 2022-07-05 | 北京奇艺世纪科技有限公司 | Version library copying method and system |
| CN109947657A (en) * | 2019-04-03 | 2019-06-28 | 广东电网有限责任公司 | A kind of the mobility scale analysis method and system of enterprise-level information management system |
| CN110134431A (en) * | 2019-04-16 | 2019-08-16 | 深圳壹账通智能科技有限公司 | Code data management method and system |
| CN110162334A (en) * | 2019-05-29 | 2019-08-23 | 上海摩软通讯技术有限公司 | A kind of code administration method, apparatus, storage medium and computer program product |
| CN110750243A (en) * | 2019-09-20 | 2020-02-04 | 中国联合网络通信集团有限公司 | Project code development method and system |
| CN110751797A (en) * | 2019-09-30 | 2020-02-04 | 南京紫津融畅信息科技服务有限公司 | ATM system fault processing method, system and storage medium |
| WO2021068740A1 (en) * | 2019-10-10 | 2021-04-15 | 深圳前海微众银行股份有限公司 | File management method and device |
| CN110990055A (en) * | 2019-12-19 | 2020-04-10 | 南京邮电大学 | Pull Request function classification method based on program analysis |
| CN110990055B (en) * | 2019-12-19 | 2022-07-01 | 南京邮电大学 | Pull Request function classification method based on program analysis |
| CN113127027A (en) * | 2019-12-31 | 2021-07-16 | 深圳云天励飞技术有限公司 | Version updating method and device based on distributed version control system |
| CN111399841A (en) * | 2020-03-10 | 2020-07-10 | Oppo广东移动通信有限公司 | Block chain-based code processing method and device, storage medium and electronic equipment |
| CN111399841B (en) * | 2020-03-10 | 2024-02-23 | Oppo广东移动通信有限公司 | Code processing method and device based on blockchain, storage medium and electronic equipment |
| CN111459535A (en) * | 2020-03-19 | 2020-07-28 | 深圳木成林科技有限公司 | Branch merging method, device, equipment and computer storage medium |
| CN111552778A (en) * | 2020-04-26 | 2020-08-18 | 北京达佳互联信息技术有限公司 | Audio resource management method, device, computer readable storage medium and equipment |
| CN111666081B (en) * | 2020-04-30 | 2024-04-05 | 平安科技（深圳）有限公司 | Git-based project version release method, device, equipment and medium |
| CN111666081A (en) * | 2020-04-30 | 2020-09-15 | 平安科技（深圳）有限公司 | Project version release method, device, equipment and medium based on Git |
| CN111638903B (en) * | 2020-05-08 | 2023-05-30 | 北京达佳互联信息技术有限公司 | Method and device for generating difference information of different software versions |
| CN111638903A (en) * | 2020-05-08 | 2020-09-08 | 北京达佳互联信息技术有限公司 | Method and device for generating difference information of different software versions |
| CN111506339A (en) * | 2020-05-29 | 2020-08-07 | 北京奇艺世纪科技有限公司 | Method and device for processing change information of Software Development Kit (SDK) |
| CN111782239A (en) * | 2020-06-03 | 2020-10-16 | 中移（杭州）信息技术有限公司 | Software packaging and source code version information acquisition method, device and storage medium |
| CN111708747A (en) * | 2020-06-15 | 2020-09-25 | 中国航空工业集团公司西安飞行自动控制研究所 | Method for generating version tree of distributed version management document |
| CN111767075A (en) * | 2020-06-23 | 2020-10-13 | 北京思特奇信息技术股份有限公司 | Method and device for synchronizing application program versions |
| CN111796855A (en) * | 2020-07-22 | 2020-10-20 | 大箴(杭州)科技有限公司 | Incremental version updating method and device, storage medium and computer equipment |
| CN111796855B (en) * | 2020-07-22 | 2023-06-09 | 大箴(杭州)科技有限公司 | Incremental version updating method and device, storage medium and computer equipment |
| CN111966353A (en) * | 2020-08-13 | 2020-11-20 | 北京金山云网络技术有限公司 | Job development method and device, electronic equipment and storage medium |
| CN112148350A (en) * | 2020-09-04 | 2020-12-29 | 深圳市大富网络技术有限公司 | Remote version management method for works, electronic device and computer storage medium |
| CN112114859A (en) * | 2020-09-17 | 2020-12-22 | 云账户技术(天津)有限公司 | File processing method and device and storage medium |
| CN112947986A (en) * | 2020-09-29 | 2021-06-11 | 深圳市明源云科技有限公司 | Multi-version code sign-in control method and device, client and storage medium |
| CN112256320A (en) * | 2020-11-04 | 2021-01-22 | 广州繁星互娱信息科技有限公司 | Version number generation method, device, terminal and storage medium |
| CN112650724A (en) * | 2020-12-25 | 2021-04-13 | 中国工商银行股份有限公司 | Document file processing method, system, computing device and medium |
| CN112835614A (en) * | 2021-01-29 | 2021-05-25 | 宝宝巴士股份有限公司 | Method for optimizing generation of curriculum packets |
| CN112783533A (en) * | 2021-02-03 | 2021-05-11 | 北京达佳互联信息技术有限公司 | Version information updating method, version information updating device, terminal and storage medium |
| CN112948734A (en) * | 2021-02-25 | 2021-06-11 | 平安普惠企业管理有限公司 | Project style integration and adaptation method, device, equipment and storage medium |
| CN113448614A (en) * | 2021-06-29 | 2021-09-28 | 北京金山云网络技术有限公司 | Software project code management method and device, storage medium and electronic equipment |
| CN113703417A (en) * | 2021-07-13 | 2021-11-26 | 交控科技股份有限公司 | Method and device for determining test cases of full-automatic scene of train operation |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109086071A (en) | A kind of method and server of management software version information | |
| US10740093B2 (en) | Advanced packaging techniques for improving work flows | |
| US11314698B2 (en) | Dynamically performing data processing in a data pipeline system | |
| CN111352651B (en) | Code branch management method and device | |
| US9588752B2 (en) | Performing unattended software installation | |
| US20200326988A1 (en) | Integrated system to distribute and execute complex applications | |
| US8769494B2 (en) | Globally sound and consistent configuration management for distributed datacenter components | |
| US20160306612A1 (en) | Determining errors and warnings corresponding to a source code revision | |
| CN105893259B (en) | Code detection system, method and device | |
| CN106708740B (en) | Script testing method and device | |
| CN108776643B (en) | Target code merging control method and system based on version control process | |
| US9639350B2 (en) | Tagging non-upstream source code | |
| CN114780138B (en) | Flow field simulation software code version management method and device and storage medium | |
| CN106033388A (en) | A test use case library management method and system | |
| US20200104107A1 (en) | Systems and methods for deploying software products to environments | |
| CN117693734A (en) | Front-end item processing method, device, equipment, management system and storage medium | |
| CN101753619A (en) | Method and system for extending service model | |
| US11099837B2 (en) | Providing build avoidance without requiring local source code | |
| Ormenisan et al. | Implicit provenance for machine learning artifacts | |
| CN109582347B (en) | Method and device for acquiring front-end codes | |
| US20200356885A1 (en) | Service management in a dbms | |
| US20220413843A1 (en) | Combining model-driven applications and canvas-type applications with application lifecycle management | |
| KR20190143228A (en) | Method for object management using trace identifier, apparatus for the same, computer program for the same, and recording medium storing computer program thereof | |
| JP2003242313A (en) | Business progress controller and method thereof, business progress control program, and recording medium recorded with the program | |
| US11068468B2 (en) | Extensible validation framework |
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 |