CN110795125A - Software updating method, system, device and readable storage medium based on DevOps framework - Google Patents
Software updating method, system, device and readable storage medium based on DevOps framework Download PDFInfo
- Publication number
- CN110795125A CN110795125A CN201910998853.1A CN201910998853A CN110795125A CN 110795125 A CN110795125 A CN 110795125A CN 201910998853 A CN201910998853 A CN 201910998853A CN 110795125 A CN110795125 A CN 110795125A
- Authority
- CN
- China
- Prior art keywords
- automatic deployment
- project
- script
- server
- source code
- 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
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000013515 script Methods 0.000 claims abstract description 339
- 238000012986 modification Methods 0.000 claims abstract description 121
- 230000004048 modification Effects 0.000 claims abstract description 121
- 238000011161 development Methods 0.000 claims abstract description 95
- 238000004891 communication Methods 0.000 claims abstract description 55
- 238000012544 monitoring process Methods 0.000 claims abstract description 14
- 238000010276 construction Methods 0.000 claims description 29
- 238000012545 processing Methods 0.000 claims description 6
- 230000003252 repetitive effect Effects 0.000 abstract description 16
- 230000008569 process Effects 0.000 description 23
- 238000012360 testing method Methods 0.000 description 18
- 238000009434 installation Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000002085 persistent effect Effects 0.000 description 8
- 238000013024 troubleshooting Methods 0.000 description 8
- 238000012423 maintenance Methods 0.000 description 7
- 238000012384 transportation and delivery Methods 0.000 description 7
- 230000008878 coupling Effects 0.000 description 5
- 238000010168 coupling process Methods 0.000 description 5
- 238000005859 coupling reaction Methods 0.000 description 5
- 230000010354 integration Effects 0.000 description 5
- 230000004888 barrier function Effects 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- KXLUWEYBZBGJRZ-POEOZHCLSA-N Canin Chemical compound O([C@H]12)[C@]1([C@](CC[C@H]1C(=C)C(=O)O[C@@H]11)(C)O)[C@@H]1[C@@]1(C)[C@@H]2O1 KXLUWEYBZBGJRZ-POEOZHCLSA-N 0.000 description 1
- GPFVKTQSZOQXLY-UHFFFAOYSA-N Chrysartemin A Natural products CC1(O)C2OC2C34OC3(C)CC5C(CC14)OC(=O)C5=C GPFVKTQSZOQXLY-UHFFFAOYSA-N 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011981 development test Methods 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
A software updating method, a system, a device and a readable storage medium based on a DevOps framework are provided, the method comprises the following steps: acquiring automatic deployment scripts respectively corresponding to a plurality of created projects, wherein the automatic deployment scripts corresponding to the projects comprise: configuring parameters, task codes and communication interface calling codes; monitoring whether modification operation exists in each project; when the fact that the item with the modification operation exists is monitored, the automatic deployment script corresponding to the item with the modification operation is operated, and the automatic deployment script of other items called by the item with the modification operation is operated. By the scheme, repetitive work can be reduced, and development efficiency is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computer software, in particular to a software updating method, a system, equipment and a readable storage medium based on a DevOps framework.
Background
With the popularization and rapid development of the internet, the requirements of users on software products are higher and higher. In the complex and variable multi-set environment, the traditional waterfall type (development-test-release) project development mode often cannot find problems in time due to lack of communication in each link, the source cannot be accurately positioned due to reaction lag, the processing efficiency is not high, and the delivery progress is delayed. The Development and operation and maintenance frame breaks the barrier between Development and operation and maintenance, and tightly connects links such as Development, test, system operation and maintenance and the like.
An existing DevOps framework-based project development mode is generally to create a development project according to a plan, and CI/CD (Continuous Integration/Continuous Deployment) flows of all codes are concentrated in the development project, and as long as one of the flows is modified, all the flows need to be started again, so that more repetitive work is required, time and labor are wasted, the development efficiency is low, and the high-frequency release requirement of a new project development mode (for example, an agile development mode) is difficult to meet.
Disclosure of Invention
In view of this, embodiments of the present invention provide a software updating method, system, device and readable storage medium based on a DevOps framework, which reduce repetitive work and improve development efficiency.
The embodiment of the invention provides a software updating method based on a DevOps framework, which comprises the following steps:
acquiring automatic deployment scripts respectively corresponding to a plurality of created projects, wherein the automatic deployment scripts corresponding to the projects comprise: configuring parameters, task codes and communication interface calling codes; monitoring whether modification operation exists in each project; when the fact that the item with the modification operation exists is monitored, the automatic deployment script corresponding to the item with the modification operation is operated, and the automatic deployment script of other items called by the item with the modification operation is operated.
Optionally, the created plurality of items include: a first source code development project and a first server deployment project; the acquiring of the automatic deployment scripts corresponding to the created multiple projects respectively includes: and acquiring a first source code automatic deployment script corresponding to the first source code development project and a first server automatic deployment script corresponding to the first server deployment project.
Optionally, when it is monitored that there is a project with a modification operation, the automatic deployment script corresponding to the project with the modification operation is run, and the automatic deployment scripts of other projects called by the project with the modification operation are run, where the automatic deployment scripts include at least one of the following: when it is monitored that the first source code development project has modification operation, running the first source code automatic deployment script and running the first server automatic deployment script called by the first source code automatic deployment script; and running the first server automatic deployment script when the first server deployment project is monitored to have modification operation.
Optionally, the created plurality of items include: a second source code development project, a mirror image construction project and a second server deployment project; the acquiring of the automatic deployment scripts corresponding to the created multiple projects respectively includes: and acquiring a second source code automatic deployment script corresponding to the second source code development project, a mirror image automatic deployment script corresponding to the mirror image construction project and a second server automatic deployment script corresponding to the second server deployment project.
Optionally, when it is monitored that there is a project with a modification operation, the automatic deployment script corresponding to the project with the modification operation is run, and the automatic deployment scripts of other projects called by the project with the modification operation are run, where the automatic deployment scripts include at least one of the following: when it is monitored that the second source code development project has modification operation, running the second source code automatic deployment script, running the mirror image automatic deployment script called by the second source code automatic deployment script, and running the second server automatic deployment script called by the mirror image automatic deployment script; when the mirror image construction project is monitored to have modification operation, running the mirror image automatic deployment script and running the second server automatic deployment script called by the mirror image automatic deployment script; and when the second server deployment project is monitored to have modification operation, running the second server automatic deployment script.
The embodiment of the invention also provides a software updating system based on the DevOps framework, which comprises the following steps:
the script obtaining unit is adapted to obtain automatic deployment scripts corresponding to the created multiple projects, respectively, where the automatic deployment scripts corresponding to the projects include: configuring parameters, task codes and communication interface calling codes; the modification operation monitoring unit is suitable for monitoring whether modification operation exists in each project; and the script running unit is suitable for running the automatic deployment script corresponding to the project with the modification operation and running the automatic deployment script of other projects called by the project with the modification operation when the project with the modification operation is monitored to exist.
Optionally, the created plurality of items include: a first source code development project and a first server deployment project; the script obtaining unit is suitable for obtaining a first source code automatic deployment script corresponding to the first source code development project and a first server automatic deployment script corresponding to the first server deployment project.
Optionally, the created plurality of items include: a second source code development project, a mirror image construction project and a second server deployment project; the script obtaining unit is adapted to obtain a second source code automatic deployment script corresponding to the second source code development project, and a mirror image automatic deployment script corresponding to the mirror image construction project and a second server automatic deployment script corresponding to the second server deployment project.
The embodiment of the invention also provides data processing equipment, which comprises a memory and a processor; wherein the memory is adapted to store one or more computer instructions which, when executed by the processor, perform the steps of the method of any of the above embodiments.
The embodiment of the present invention further provides a computer-readable storage medium, on which computer instructions are stored, and when the computer instructions are executed, the steps of the method described in any of the above embodiments are performed.
By adopting the software updating scheme based on the DevOps framework, the automatic deployment scripts respectively corresponding to the created multiple projects can be obtained, wherein the automatic deployment scripts corresponding to the projects comprise: the method comprises the steps of configuring parameters, task codes and communication interface calling codes, then monitoring whether modification operation exists in each project, and when the fact that the modification operation exists is monitored, running automatic deployment scripts corresponding to the project in which the modification operation exists and running automatic deployment scripts of other projects called by the project in which the modification operation exists. By adopting the scheme, the development process based on the DevOps can be divided into a plurality of projects and corresponding automatic deployment scripts, so that loose coupling of the process is realized; when the project with the modification operation is monitored, the automatic deployment script corresponding to the project with the modification operation and the automatic deployment scripts of other subsequent projects can be directly operated without operating the automatic deployment scripts corresponding to all the projects, so that automatic delivery and automatic deployment are realized, unnecessary repetitive work is reduced, time is saved, and development efficiency is improved.
Further, the created projects include a first source code development project and a first server deployment project, and a corresponding first source code automatic deployment script and a corresponding first server automatic deployment script are respectively obtained, so that when it is monitored that the first source code development project has modification operation, the first source code automatic deployment script can be run, and the first server automatic deployment script called by the first source code automatic deployment script can be run; and when the first server deployment project is monitored to have modification operation, the first server automatic deployment script can be run. Therefore, if only the first server deployment project has modification operation, the first source code automatic deployment script does not need to be run first, but the first server automatic deployment script can be directly run, so that unnecessary repetitive work is reduced, time is saved, and development efficiency is improved. Meanwhile, the first source code automatic deployment script and the first source code automatic deployment script are respectively operated, so that if a fault occurs in the operation process, the corresponding automatic deployment script can be checked immediately, the checking range is reduced, and the troubleshooting time is saved.
Further, the created plurality of projects may include a second source code development project, a mirror image construction project, and a second server deployment project, and obtain a corresponding second source code automatic deployment script, a mirror image automatic deployment script, and a second server automatic deployment script, respectively, so that when it is monitored that the second source code development project has a modification operation, the second source code automatic deployment script may be run, the mirror image automatic deployment script called by the second source code automatic deployment script may be run, and the second server automatic deployment script called by the mirror image automatic deployment script may be run; when the condition that the mirror image construction project has modification operation is monitored, the mirror image automatic deployment script can be operated, and the second server automatic deployment script called by the mirror image automatic deployment script is operated; and when the second server deployment project is monitored to have modification operation, running the second server automatic deployment script. Therefore, when the mirror image construction project has modification operation, the second source code automatic deployment script does not need to be executed first, and when the second server deployment project has modification operation, the second source code automatic deployment script and the mirror image automatic deployment script do not need to be executed first, and the source codes can be compatible with various different running environments after being packaged into the mirror images, so that unnecessary repetitive work is reduced, the time is saved, and the development efficiency is improved. Meanwhile, the second source code automatic deployment script, the mirror image automatic deployment script and the second source code automatic deployment script are respectively operated, so that if a fault occurs in the operation process, the corresponding automatic deployment script can be checked immediately, the checking range is reduced, and the troubleshooting time is saved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present specification, the drawings needed to be used in the embodiments of the present specification or in the description of the prior art will be briefly described below, it is obvious that the drawings described below are only some embodiments of the present specification, and it is also possible for a person skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a software updating method based on a DevOps framework in an embodiment of the present invention.
Fig. 2 is a diagram of a software update architecture based on a DevOps framework in an embodiment of the present invention.
Fig. 3 is another software update architecture diagram based on the DevOps framework in an embodiment of the invention.
Fig. 4 is a schematic structural diagram of a software update system based on a DevOps framework in an embodiment of the present invention.
Fig. 5 is a schematic structural diagram of a script execution unit according to an embodiment of the present invention.
Fig. 6 is a schematic structural diagram of another script execution unit in the embodiment of the present invention.
Detailed Description
As mentioned above, in the conventional software development, a developer generally manages and controls a unified version, an operation and maintenance person feeds back software development requirements to the developer, the developer develops and tests the version, and then sends the version to the operation and maintenance person in the form of an installation package or an upgrade package for distribution, and the conventional mode strictly follows the flow sequence of planned requirements, analysis, design, coding and testing in advance, so that the traditional mode is also called a waterfall type project development mode, the strict classification of the traditional mode results in low freedom, and the change of requirements in the later period is difficult to adjust due to commitment made in the early stage of the project, or the adjustment cost is high. And each link lacks communication in the development process, often can not find the problem immediately, and the reaction lags and leads to unable accurate positioning root cause, and processing efficiency is not high, delays the delivery progress. As the frequency of software release iterations becomes higher and higher, the traditional "waterfall" project development model has been unable to meet the demand for rapid delivery.
The generated DevOps (combination words of Development and Operations) breaks the barrier between Development and operation and maintenance, and links such as Development, test, system operation and maintenance and the like are closely connected. However, the conventional DevOps framework-based project development model usually creates a development project according to a plan, and integrates CI/CD (Continuous integration/Continuous Deployment) flows of all codes into the development project, and once one of the flows is modified, all the flows need to be started to run again, so that the conventional DevOps framework-based project development model has the disadvantages of more repetitive work, time and labor consuming, low development efficiency, and difficulty in meeting the high-frequency release requirement of a new project development model (e.g., agile development model).
In view of the foregoing problem, an embodiment of the present specification provides a software update scheme based on a DevOps framework, which may acquire automatic deployment scripts corresponding to a plurality of created projects, where the automatic deployment scripts corresponding to the projects may include: the method comprises the steps of configuring parameters, task codes and communication interface calling codes, then monitoring whether modification operation exists in each project, and when the fact that the modification operation exists is monitored, running automatic deployment scripts corresponding to the project in which the modification operation exists and running automatic deployment scripts of other projects called by the project in which the modification operation exists.
By adopting the embodiment of the specification, the development process based on the DevOps can be divided into a plurality of projects and corresponding automatic deployment scripts, so that loose coupling of the process is realized; when the project with the modification operation is monitored, the automatic deployment script corresponding to the project with the modification operation and the automatic deployment scripts of other subsequent projects can be directly operated without operating the automatic deployment scripts corresponding to all the projects, so that automatic delivery and automatic deployment are realized, unnecessary repetitive work is reduced, time is saved, and development efficiency is improved.
In order to make the embodiments of the present disclosure more clearly understood and implemented by those skilled in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort shall fall within the protection scope of the present specification.
Referring to a flowchart of a software updating method based on a DevOps framework shown in fig. 1, in an embodiment of the present invention, the software updating method based on the DevOps framework may adopt the following steps:
s11, acquiring automatic deployment scripts corresponding to the created multiple projects, where the automatic deployment scripts corresponding to the projects may include: configuration parameters, task code, and communication interface call code.
In a specific implementation, a plurality of projects may be created according to a specific scenario, and a corresponding automatic deployment script may be generated according to work content of each project, and each automatic deployment script may include configuration parameters for initializing each project, task codes for executing work content of each project, and communication interface calling codes for calling a communication interface to continue other processes.
For example, a plurality of corresponding projects can be created according to the development stage of the development project, such as a project of a software code development stage, a project of a software version management stage, a project of a software delivery stage, and the like; for another example, the software development model can be disassembled according to the flow of the project development model to create a plurality of corresponding projects, such as a software development project, a software test project, a software release project, and the like.
In particular implementations, the items created may be relatively independent of one another, and the loose coupling between the items may reduce the impact between the items, e.g., modify the configuration of one of the items, with the configuration of the other items being modified less, or even not required.
And S12, monitoring whether the modification operation exists in each project.
In specific implementation, the existing monitoring tool can be adopted, and monitoring points can be set by self for monitoring.
And S13, when the existence of the project of the modification operation is monitored, running the automatic deployment script corresponding to the project of the modification operation, and running the automatic deployment script of other projects called by the project of the modification operation.
The corresponding communication interface is called to run the automatic deployment script corresponding to the project with the modification operation, and the automatic deployment script corresponding to the project with the modification operation can also be run by other triggering means.
In a specific implementation, assume that n items A are created1-AnGet item A1-AnCorresponding auto-deploy script B1-BnWhen one item A is detectediWhen the modification operation is performed, canIn the item AiAfter the modification operation is finished, automatically running the project AiCorresponding auto-deploy script BiAnd, when the automatic deployment script BiWhen the automatic deployment scripts of other projects are called, the automatic deployment scripts of other projects can be continuously run, and the automatic deployment scripts of other projects can also be called until all the called automatic deployment scripts of other projects are finished. Wherein i and n are both natural numbers, and i is less than or equal to n.
By the software updating method based on the DevOps framework, the development process based on the DevOps can be divided into a plurality of projects and corresponding automatic deployment scripts, and loose coupling of the process is realized; when the project with the modification operation is monitored, the automatic deployment script corresponding to the project with the modification operation and the automatic deployment scripts of other subsequent projects can be directly operated without operating the automatic deployment scripts corresponding to all the projects, so that automatic delivery and automatic deployment are realized, unnecessary repetitive work is reduced, time is saved, and development efficiency is improved.
In a specific implementation, based on the DevOps framework, the created plurality of items may include: the method includes the steps of obtaining a first source code development project and a first server deployment project, and obtaining a first source code automatic deployment script corresponding to the first source code development project and a first server automatic deployment script corresponding to the first server deployment project.
Then, the first source code development project and the first server deployment project may be monitored for the presence of modification operations. And when the first source code development project is monitored to have modification operation, running the first source code automatic deployment script, and running the first server automatic deployment script of the first server deployment project called by the first source code automatic deployment script. And running the first server automatic deployment script when the first server deployment project is monitored to have modification operation.
Wherein the first source code auto-deployment script may include: a first configuration parameter, a first task code and a first communication interface calling code; the first server auto-deployment script may include: a second configuration parameter and a second task code and a second communication interface call code.
Specifically, when the first source code automatic deployment script is run, the first task code may be executed based on the first configuration parameter, and after the first task code is completely executed, the first communication interface calling code is executed to call the corresponding first communication interface, so that the first server automatic deployment script of the first server deployment item corresponding to the first communication interface may be automatically run.
When the first server automatic deployment script is operated, the second task code can be executed on the server to be deployed based on the second configuration parameter, and after the second task code is executed, the second communication interface calling code is executed to call the corresponding second communication interface, so that the execution result of the second task code can be automatically returned, and whether software updating is successful or not can be displayed.
It may be understood that, in the specific implementation process, the automatic deployment script corresponding to each project may call the corresponding communication interface by executing the configured communication interface call code, and automatically return the execution result of the task code in each automatic deployment script, or may call the corresponding communication interface by executing the configured communication interface call code, and automatically run the automatic deployment scripts of other subsequent projects, and the automatic deployment scripts of other subsequent projects may not be unique.
In an embodiment of the present invention, the content of the first task code may include a test source code and is uploaded to a cloud server, and the content of the second task code may include a source code document running on a server to be deployed. When there is a modification operation in the first source code development project and the first server deployment project, a corresponding automatic deployment script may be run.
For example, after a first source code document is uploaded in the first source code development project, it is monitored that a modification operation exists in the first source code development project, the first source code automatic deployment script may be run for automatic testing, and after the test is passed, the first source code document is uploaded to the cloud server. Then, a first server automatic deployment script of a first server deployment item corresponding to the first communication interface can be automatically operated by executing the first communication interface calling code to call the corresponding first communication interface, a server to be deployed is logged in through an Internet Protocol (IP) address, the first source code document is downloaded from the cloud server according to the name of the first source code document, then the first source code document is operated in the server to be deployed, and software updating is performed on the server to be deployed.
For another example, after the IP address of the server to be deployed is modified in the first server deployment project, it is monitored that the modification operation exists in the first server deployment project, the first server automatic deployment script of the first server deployment project may be automatically run, the corresponding server to be deployed is logged in through the modified IP address, the first source code document is downloaded and run from the cloud server, and software update is performed on the server to be deployed.
It is to be understood that the foregoing embodiments are merely examples, and are not limiting to the specific implementation, in the specific implementation process, the content of the first task code and the content of the first task code may be set according to an actual situation, and the modification operation may be a modification of any content in the first source code development project and the first server deployment project.
Therefore, if only the first server deployment project has modification operation, the first source code automatic deployment script does not need to be run first, but the first server automatic deployment script can be directly run, so that unnecessary repetitive work is reduced, time is saved, and development efficiency is improved. Meanwhile, the first source code automatic deployment script and the first source code automatic deployment script are respectively operated, so that if a fault occurs in the operation process, the corresponding automatic deployment script can be checked immediately, the checking range is reduced, and the troubleshooting time is saved.
In specific implementation, software is often required to be updated in different operating systems, and software updating is usually performed by using installation packages, because the operating environments of the software installation packages are different, only installation packages composed of corresponding compiling languages can be installed for each operating environment, for example, the installation modes of two operating systems, i.e., Windows and Linux, are different, corresponding compiling languages are required to be used for writing and testing, and source code documents passing the testing are packaged into the software installation packages for updating. If there are many designated objects for which software needs to be updated, for example, when software is updated on several servers with different operating systems, software installation packages corresponding to compiled languages need to be run on these servers, respectively, and the software updating process is complicated.
For the above problem, in the specific implementation, the source code may be packaged as a mirror image, so that the source code in the software installation package may be run by running the mirror image without independently arranging the running environment of the software installation package according to the operating system, which may avoid the difference between the operating systems, reduce the usage space, and facilitate the subsequent software update.
For example, the created plurality of items may include: a second source code development project, a mirror image construction project and a second server deployment project, and a second source code automatic deployment script corresponding to the second source code development project, a mirror image automatic deployment script corresponding to the mirror image construction project and a second server automatic deployment script corresponding to the second server deployment project may be obtained.
Then, a second source code development project, a mirror build project, and a second server deployment project may be monitored for the presence of modification operations.
When it is monitored that the second source code development project has modification operation, running the second source code automatic deployment script, running a mirror image automatic deployment script of the mirror image construction project called by the second source code automatic deployment script, and running a second server automatic deployment script of the second server deployment project called by the mirror image automatic deployment script.
And when the condition that the mirror image construction project has modification operation is monitored, running the mirror image automatic deployment script, and running the mirror image automatic deployment script of the mirror image construction project called by the second source code automatic deployment script.
And when the second server deployment project is monitored to have modification operation, running the second server automatic deployment script.
Wherein the second source code auto-deployment script may include: a third configuration parameter, a third task code and a third communication interface calling code; the mirror image auto deployment script may include: a fourth configuration parameter, a fourth task code and a fourth communication interface calling code; the second server auto-deployment script may include: a fifth configuration parameter, a fifth task code and a fifth communication interface calling code;
specifically, when the second source code automatic deployment script is run, the third task code may be executed based on the third configuration parameter, and after the third task code is executed, the third communication interface calling code is executed to call the corresponding third communication interface, so that the mirror image automatic deployment script of the mirror image construction project corresponding to the third communication interface may be automatically run.
When the mirror image automatic deployment script is operated, the fourth task code may be executed based on the fourth configuration parameter, and after the fourth task code is executed, the second server automatic deployment script of the second server deployment project may be automatically operated by executing the fourth communication interface calling code to call the corresponding fourth communication interface.
When the second server automatic deployment script is operated, the fifth task code may be executed on the server to be deployed based on the fifth configuration parameter, and after the fifth task code is executed, the corresponding fifth communication interface is called by executing the fifth communication interface calling code, and an execution result of the fifth task code may be automatically returned, so as to display whether software update is successful.
The server is deployed in a mirror image mode, so that source codes of different assembly languages can be operated in the server to be deployed, the difference of operating systems formed by different assembly languages is further reduced, and the compatibility of the source codes is improved.
It is to be understood that the above embodiments are merely illustrative and not restrictive of the specific implementations, and that the mirror image may be applied to other items in the specific implementations.
In an embodiment of the present invention, the content of the third task code may include a test source code and is uploaded to a cloud server, the content of the fourth task code may include a build image and is uploaded to a cloud image library, and the content of the fifth task code may include a run image on a server to be deployed. When modification operations exist in the second source code development project, the mirror image construction project and the first server deployment project, corresponding automatic deployment scripts can be run.
For example, after uploading a second source code document in the second source code development project, it is monitored that the second source code development project has a modification operation, the second source code automatic deployment script may be run for automatic testing, and after the test is passed, the second source code document is uploaded to the cloud server.
Then, the third communication interface is executed to call the corresponding third communication interface through calling the code, the automatic mirror image deployment script of the mirror image construction project corresponding to the third communication interface can be automatically operated, the second source code document is downloaded from the cloud server according to the name of the second source code document, and then a new mirror image can be constructed on the corresponding basic mirror image formed by the same assembly language based on the second source code document and is uploaded to a cloud mirror image library. The base image can be stored in a file or a folder corresponding to the specified path.
And then, the second server automatic deployment script of the second server deployment project can be automatically operated by executing the fourth communication interface calling code to call the corresponding fourth communication interface. And then, logging in a server to be deployed through an IP address, downloading the second source code document from the cloud server according to the name of the new image, running the second source code document in the server to be deployed, and updating software of the server to be deployed.
For another example, after replacing the basic mirror image in the mirror image construction project, it is monitored that the mirror image construction project has operation modification, the mirror image automatic deployment script of the mirror image construction project can be automatically run, the second source code document is downloaded from the cloud server according to the name of the second source code document, and based on the second source code document, a new mirror image can be constructed on the replaced basic mirror image, and the new mirror image is uploaded to the cloud mirror image library.
Then, the second server automatic deployment script of the second server deployment project can be automatically run by executing the fourth communication interface calling code to call the corresponding fourth communication interface. And then, logging in a server to be deployed through an IP address, downloading the second source code document from the cloud server according to the name of the new image, running the second source code document in the server to be deployed, and updating software of the server to be deployed.
For example, after the IP address of the server to be deployed is modified in the second server deployment project, it is monitored that the second server deployment project has a modification operation, the second server automatic deployment script of the second server deployment project can be automatically run, the corresponding server to be deployed is logged in through the modified IP address, the second source code document is downloaded from the cloud server according to the name of the new image, the second source code document is run in the server to be deployed, and software update is performed on the server to be deployed.
It should be understood that the foregoing embodiments are merely illustrative, and are not limiting to the specific implementation, in the specific implementation process, the content of the third task code, the content of the fourth task code, and the content of the fifth task code may be set according to an actual situation, and the modification operation may be a modification of any content in the second source code development project, the image construction project, and the first server deployment project.
Therefore, when the mirror image construction project has modification operation, the second source code automatic deployment script does not need to be executed first, and when the second server deployment project has modification operation, the second source code automatic deployment script and the mirror image automatic deployment script do not need to be executed first, and the source codes can be compatible with various different running environments after being packaged into the mirror images, so that unnecessary repetitive work is reduced, the time is saved, and the development efficiency is improved. Meanwhile, the second source code automatic deployment script, the mirror image automatic deployment script and the second source code automatic deployment script are respectively operated, so that if a fault occurs in the operation process, the corresponding automatic deployment script can be checked immediately, the checking range is reduced, and the troubleshooting time is saved.
In particular implementations, a code hosting platform may be employed for versioning and collaborative development of software, such as code hosting platforms like GitHub, GitLab, BitBucket, SubVersion, Coding, Bazaar, and the like. Persistent integrated execution platforms may also be employed for persistent integration and persistent deployment of software, such as, for example, GitLab, Jenkins, Capistrano, BuildPot, Fabric, Tinderbox, Travis CI, flow. CI Continum, LuntBuild, CruiseControl, Integrity, Gump, Go, and the like persistent integrated execution platforms. A container platform may also be used to construct a corresponding image of the software, for example, a container platform such as Docker, socket, Ubuntu (LXC), a third party vendor (e.g., AWS/arrhizus), and the like.
In order to make the embodiments of the present disclosure more clearly understood and implemented by those skilled in the art, the following description will clearly and completely describe the technical solutions in the embodiments of the present disclosure with reference to the drawings in the embodiments of the present disclosure in a specific application scenario.
In an embodiment of the present invention, referring to a software update architecture diagram based on a DevOps framework shown in fig. 2, a GitLab platform can be adopted for version control, collaborative development, persistent integration and persistent deployment of software.
Based on the DevOps framework, a first project 21 and a second project 22 are created, the first project 21 is named "src" and the second project is named "deployment", and the first project 21 and the second project 22 are configured with corresponding first automatic deployment script 211 and second automatic deployment script 221, respectively. The first project 21 and the second project 22 may run respective first automated deployment scripts 211 and second automated deployment scripts 221 through associated first and second GitLab execution tools (GitLab-runner)23 and 25, respectively.
After the first automatic deployment script 211 runs all the work contents, the corresponding first GitLab communication interface (GitLab api)24 can be called by executing the communication interface calling code, so that the second automatic deployment script 221 of the second item 22 can be run automatically, and after the second automatic deployment script 221 runs all the work contents, the software update of the specified object is completed.
The first GitLab executing tool 23 and the second GitLab executing tool 25 can be installed on different running carriers, so that the bearing pressure is reduced, and the operation efficiency is improved.
Also, the autodeployment scripts may be in YAML (Another Markup Language) syntax format, and thus have ". yml" as suffix, respectively, and since the first autodeployment script 211 and the second autodeployment script 221 are located in different first project 21 and second project 22, respectively, the first autodeployment script 211 and the second autodeployment script 221 may both be named "gitlab-ci.yml".
The first automatic deployment script 211 comprises 3 job jobs 1-jobs 3, wherein the content of jobs 1 is as follows: test source code (test); the contents of joba 2 are: packaging the source code into an installation package (package); the contents of joba 3 are: uploading to a secure File Transfer Protocol (SSH File Transfer Protocol, sftp) server.
The second automatic deployment script 221 includes 2 job jobs 4 and jobs 5, and the content of jobs 4 is: acquiring a corresponding installation package (pull package from sftp server to the server) from the sftp server; the contents of joba 5 are: and running an installation package (run package on the server) on the server to be deployed.
In implementation, different job content may be associated with corresponding task code, and the task code may be distributed in different sub-scripts. When the first automatic deployment script 211 or the second automatic deployment script 221 runs the work therein, it may jump to the corresponding folder through a designated path, and then, a sub-script of the corresponding work content in the folder may be executed. For example, when the first automatic deployment script 211 runs the job1, it can enter a folder written with a test script through a specified path, and then run a sub-script containing the work content of the job 1.
When it is monitored that a modification operation exists on the first project 21, for example, source code modification and the like, a first gitlab-runner 23 associated with the first project 21 may be started, and a corresponding first automatic deployment script 211 may be automatically executed, and after the first automatic deployment script 211 has executed all the work content, a corresponding first gitlab api 24 may be called by executing a communication interface call code, so that a second gitlab-runner 25 may be started to automatically execute a second automatic deployment script 221 of the second project 22, and when the second automatic deployment script 221 has executed all the work content, software update on a server to be deployed is completed.
When it is monitored that a modification operation, for example, a modification of deployment configuration, exists in the second project 22, the second gitlab-runner 25 associated with the second project 22 may run a corresponding second automatic deployment script 221, and when the second automatic deployment script 221 runs all the work contents, software update on the server to be deployed is completed.
As can be seen from the above, if only the second item 22 has modification operation, the corresponding second automatic deployment script 221 can be directly run without first running the first automatic deployment script 211 of the first item 21, which reduces unnecessary repetitive work, saves time, and improves development efficiency. Meanwhile, as the corresponding first automatic deployment script 211 and the second automatic deployment script 221 can be respectively run, if a fault occurs in the running process, for example, the source code fails to be tested or fails to be deployed, the corresponding automatic deployment script can be immediately checked, the checking range is reduced, and the troubleshooting time is saved.
In another embodiment of the present invention, referring to a software update architecture diagram based on a DevOps framework shown in fig. 3, a GitLab platform and a Docker platform may be adopted, the GitLab platform is used for version control, collaborative development, persistent integration and persistent deployment of software, and the Docker platform is used for constructing a corresponding mirror image of the software.
Based on the DevOps framework, a third project 31, a fourth project 32 and a fifth project 33 are created, the third project 31, the fourth project 32 and the fifth project 33 are named as "src", "built _ dockcr _ image" and "deploy", respectively, and are configured with a corresponding third automatic deployment script 311, a fourth automatic deployment script 321 and a fifth automatic deployment script 331 for the third project 31, the fourth project 32 and the fifth project 33, respectively. The third project 31, the fourth project 32, and the fifth project 33 may run respective third automated deployment scripts 311, fourth automated deployment scripts 321, and fifth automated deployment scripts 331 through associated third, fourth, and fifth GitLab execution tools 34, 36, and 38, respectively.
After the third automatic deployment script 311 runs all the work content, it may call the corresponding second GitLab communication interface (GitLab api)35 by executing the communication interface calling code, so that the fourth automatic deployment script 321 of the fourth project 32 may be run automatically; after the fourth automatic deployment script 321 runs all the work contents, the corresponding third GitLab communication interface (GitLab api)37 may be called by executing the communication interface calling code, so that the fifth automatic deployment script 331 of the fifth project 33 may be automatically run, and after the fifth automatic deployment script 331 runs all the work contents, the software update of the specified object is completed.
The third, fourth and fifth GitLab execution tools 34, 36, 38 can be mounted on different operation carriers, so as to reduce the load bearing pressure and improve the operation efficiency.
Also, the auto deployment scripts may be in YAML (Another Markup Language) syntax format, and thus are respectively prefixed with ". yml", and since the third auto deployment script 311, the fourth auto deployment script 321, and the fifth auto deployment script 331 are respectively located in different third project 31, fourth project 32, and fifth project 33, the third auto deployment script 311, the fourth auto deployment script 321, and the fifth auto deployment script 331 may all be named "tlgiab-ci.
The third automatic deployment script 311 contains 3 job jobs 6-jobs 8, and the content of jobs 6 is as follows: test source code (test); the contents of joba 7 are: packaging the source code into an installation package (package); the contents of joba 8 are: uploading to the sftp server (upload to sftp server).
The fourth automatic deployment script 321 includes 2 job jobs 9 and jobs 10, and the contents of jobs 9 are as follows: constructing a corresponding mirror image (build image) of the installation package; the contents of joba 10 are: the image is uploaded to the image library (run package on the server).
The fifth automatic deployment script 331 includes 2 job jobs 11 and jobs 12, and the contents of jobs 11 are as follows: acquiring a corresponding mirror image from the sftp server; the contents of joba 12 are: and running a mirror image (run package on the server) on the server to be deployed.
In implementation, different job content may be associated with corresponding task code, and the task code may be distributed in different sub-scripts. When at least one of the third automatic deployment script 311, the fourth automatic deployment script 321, and the fifth automatic deployment script 331 runs a work therein, it may jump to a corresponding folder through a specified path, and then, a sub-script of a corresponding work content in the folder may be executed. For example, when the third automatic deployment script 311 runs the job6, it can enter the folder written with the test script through a specified path, and then run the sub-script containing the work content of the job 6.
When it is monitored that a modification operation exists on the third project 31, for example, a source code is modified, a third gitlab-runner 34 associated with the third project 31 may be started, a corresponding third automatic deployment script 311 is automatically run, and after the third automatic deployment script 311 runs all work contents, a corresponding second gitlab api 35 may be called by executing a communication interface call code, so that a fourth gitlab-runner 36 may be started to automatically run a fourth automatic deployment script 321 of the fourth project 32; after the fourth automatic deployment script 321 runs and finishes all the work contents, the corresponding third gitlab api 37 can be called by executing a communication interface calling code, so that the fifth gitlab-runner 38 can be started to automatically run the fifth automatic deployment script 331 of the fifth item 33; when the fifth automatic deployment script 331 runs to complete all the work contents, the software update on the server to be deployed is completed.
When it is detected that a modification operation exists on the fourth item 32, for example, a mirror image configuration is modified, a fourth gitlab-runner 36 associated with the fourth item 32 may be started, a fourth auto-deployment script 321 of the fourth item 32 is automatically run, and after all work contents are completed in the running of the fourth auto-deployment script 321, a corresponding third gitlab api 37 may be called by executing a communication interface calling code, so that a fifth gitlab-runner 38 may be started to automatically run a fifth auto-deployment script 331 of the fifth item 33; when the fifth automatic deployment script 331 runs to complete all the work contents, the software update on the server to be deployed is completed.
When it is detected that a modification operation exists in the fifth project 33, for example, a deployment configuration is modified, a fifth gitlab-runner 38 associated with the fifth project 33 may be started, a fifth automatic deployment script 331 of the fifth project 33 is automatically executed, and after all the work contents are executed by the fifth automatic deployment script 331, software update on the server to be deployed is completed.
As can be seen from the above, when there is a modification operation in the fourth project 32, it is not necessary to execute the third automatic deployment script 311 of the third project 31 first, and when there is a modification operation in the fifth project 33, it is also not necessary to execute the third automatic deployment script 311 of the third project 31 and the fourth automatic deployment script 321 of the fourth project 32 first, and after the source code is encapsulated into the mirror image, it is compatible with various different operating environments, thereby reducing unnecessary repetitive work, saving time, and improving development efficiency. Meanwhile, as the corresponding third automatic deployment script 311, the fourth automatic deployment script 321 and the fifth automatic deployment script 331 are respectively operated, if a fault occurs in the operation process, the corresponding automatic deployment scripts can be checked immediately, the checking range is reduced, and the troubleshooting time is saved.
It is understood that the above embodiments are only examples, and are not limited to the specific implementation, and in the specific implementation process, the automatic deployment script may adopt other syntax formats, for example, XML (eXtensible markup language) format or JSON (JavaScript Object Notation). In addition, the name and the working content of the automatic deployment script can be set according to specific situations, and different platforms or custom platforms can be selected according to the specific situations.
Embodiments of the present invention further provide a system capable of implementing the above-mentioned software updating method based on the DevOps framework, so that those skilled in the art can better understand and implement the embodiments of the present invention, which will be described in detail below with specific embodiments by referring to the drawings.
Referring to the schematic structural diagram of the software updating system based on the DevOps framework shown in fig. 4, in the embodiment of the present invention, the software updating system 40 based on the DevOps framework may specifically include:
a script obtaining unit 41, adapted to obtain automatic deployment scripts corresponding to the created multiple projects, where the automatic deployment scripts corresponding to the projects may include: configuring parameters, task codes and communication interface calling codes;
a modification operation monitoring unit 42 adapted to monitor whether a modification operation exists for each item;
and the script running unit 43 is adapted to run, when it is monitored that the item with the modification operation exists, the automatic deployment script corresponding to the item with the modification operation exists, and run the automatic deployment script of another item called by the item with the modification operation.
By adopting the scheme, the development process based on the DevOps can be divided into a plurality of projects and corresponding automatic deployment scripts, so that loose coupling of the process is realized; when the project with the modification operation is monitored, the automatic deployment script corresponding to the project with the modification operation and the automatic deployment scripts of other subsequent projects can be directly operated without operating the automatic deployment scripts corresponding to all the projects, so that automatic delivery and automatic deployment are realized, unnecessary repetitive work is reduced, time is saved, and development efficiency is improved.
In a specific implementation, the acquired created plurality of items may include: a first source code development project and a first server deployment project. Therefore, the script obtaining unit 41 is adapted to obtain a first source code automatic deployment script corresponding to the first source code development project and a first server automatic deployment script corresponding to the first server deployment project.
As shown in fig. 5, in an embodiment of the present specification, the script execution unit 43 may include the following execution sub-units:
the first running subunit 431 is adapted to run the first source code automatic deployment script and run the first server automatic deployment script called by the first source code automatic deployment script when it is monitored that the first source code development project has a modification operation.
A second running subunit 432, adapted to run the first server automatic deployment script when it is monitored that there is a modification operation for the first server deployment project.
Therefore, if only the first server deployment project has modification operation, the first source code automatic deployment script does not need to be run first, but the first server automatic deployment script can be directly run, so that unnecessary repetitive work is reduced, time is saved, and development efficiency is improved. Meanwhile, the first source code automatic deployment script and the first source code automatic deployment script are respectively operated, so that if a fault occurs in the operation process, the corresponding automatic deployment script can be checked immediately, the checking range is reduced, and the troubleshooting time is saved.
In a specific implementation, the created plurality of items may include: a second source code development project, a mirror build project, and a second server deployment project. Therefore, the script obtaining unit is adapted to obtain a second source code automatic deployment script corresponding to the second source code development project, a mirror image automatic deployment script corresponding to the mirror image construction project, and a second server automatic deployment script corresponding to the second server deployment project.
As shown in fig. 6, in an embodiment of the present specification, the script execution unit 43 may include the following execution sub-units:
a third running subunit 433, adapted to run, when it is monitored that there is a modification operation in the second source code development project, the second source code automatic deployment script, the mirror image automatic deployment script called by the second source code automatic deployment script, and the second server automatic deployment script called by the mirror image automatic deployment script;
a fourth running subunit 434, adapted to run the image automatic deployment script and run the second server automatic deployment script called by the image automatic deployment script when it is monitored that the image construction project has a modification operation;
a fifth running subunit 435, adapted to run the second server automatic deployment script when it is monitored that there is a modification operation in the second server deployment project.
Therefore, when the mirror image construction project has modification operation, the second source code automatic deployment script does not need to be executed first, and when the second server deployment project has modification operation, the second source code automatic deployment script and the mirror image automatic deployment script do not need to be executed first, and the source codes can be compatible with various different running environments after being packaged into the mirror images, so that unnecessary repetitive work is reduced, the time is saved, and the development efficiency is improved. Meanwhile, the second source code automatic deployment script, the mirror image automatic deployment script and the second source code automatic deployment script are respectively operated, so that if a fault occurs in the operation process, the corresponding automatic deployment script can be checked immediately, the checking range is reduced, and the troubleshooting time is saved.
It should be noted that the prefix of the nouns such as "first", "second", "third" and "fourth" and the suffix of the nouns such as "1", "2", "3" and "4" are only used to distinguish nouns with different functions, and do not represent order, size or importance.
The embodiment of the present invention further provides a data processing device, which may include a memory and a processor, where the memory stores computer instructions executable on the processor, and the processor may execute the steps of the method according to any one of the above embodiments of the present invention when executing the computer instructions. The specific implementation of the method executed when the computer instruction runs may refer to the steps of the above method, and is not described in detail. The data processing device can be a handheld terminal such as a mobile phone, a tablet computer, a personal desktop computer and the like.
The embodiment of the present invention further provides a computer-readable storage medium, on which computer instructions are stored, and when the computer instructions are executed, the steps of the method according to any of the above embodiments of the present invention may be executed. The computer readable storage medium may be various suitable readable storage media such as an optical disc, a mechanical hard disc, a solid state hard disc, and the like. The instructions stored in the computer-readable storage medium may be used to execute the method according to any of the embodiments, which may specifically refer to the embodiments described above and will not be described again.
Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected therein by one skilled in the art without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. A software updating method based on a DevOps framework is characterized by comprising the following steps:
acquiring automatic deployment scripts respectively corresponding to a plurality of created projects, wherein the automatic deployment scripts corresponding to the projects comprise: configuring parameters, task codes and communication interface calling codes;
monitoring whether modification operation exists in each project;
when the fact that the item with the modification operation exists is monitored, the automatic deployment script corresponding to the item with the modification operation is operated, and the automatic deployment script of other items called by the item with the modification operation is operated.
2. The DevOps framework-based software update method as claimed in claim 1, wherein the created plurality of items comprises: a first source code development project and a first server deployment project;
the acquiring of the automatic deployment scripts corresponding to the created multiple projects respectively includes:
and acquiring a first source code automatic deployment script corresponding to the first source code development project and a first server automatic deployment script corresponding to the first server deployment project.
3. The DevOps framework-based software update method according to claim 2, wherein when it is detected that there is an item of modification operation, running an automatic deployment script corresponding to the item of modification operation and running an automatic deployment script of other items called by the item of modification operation comprises at least one of:
when it is monitored that the first source code development project has modification operation, running the first source code automatic deployment script and running the first server automatic deployment script called by the first source code automatic deployment script;
and running the first server automatic deployment script when the first server deployment project is monitored to have modification operation.
4. The DevOps framework-based software update method as claimed in claim 1, wherein the created plurality of items comprises: a second source code development project, a mirror image construction project and a second server deployment project;
the acquiring of the automatic deployment scripts corresponding to the created multiple projects respectively includes:
and acquiring a second source code automatic deployment script corresponding to the second source code development project, a mirror image automatic deployment script corresponding to the mirror image construction project and a second server automatic deployment script corresponding to the second server deployment project.
5. The DevOps framework based software update method of claim 4, wherein when it is detected that there is an item of modification operation, the method runs an automatic deployment script corresponding to the item of modification operation and runs an automatic deployment script of other items called by the item of modification operation, and comprises at least one of:
when it is monitored that the second source code development project has modification operation, running the second source code automatic deployment script, running the mirror image automatic deployment script called by the second source code automatic deployment script, and running the second server automatic deployment script called by the mirror image automatic deployment script;
when the mirror image construction project is monitored to have modification operation, running the mirror image automatic deployment script and running the second server automatic deployment script called by the mirror image automatic deployment script;
and when the second server deployment project is monitored to have modification operation, running the second server automatic deployment script.
6. A DevOps framework based software update system, comprising:
the script obtaining unit is adapted to obtain automatic deployment scripts corresponding to the created multiple projects, respectively, where the automatic deployment scripts corresponding to the projects include: configuring parameters, task codes and communication interface calling codes;
the modification operation monitoring unit is suitable for monitoring whether modification operation exists in each project;
and the script running unit is suitable for running the automatic deployment script corresponding to the project with the modification operation and running the automatic deployment script of other projects called by the project with the modification operation when the project with the modification operation is monitored to exist.
7. The DevOps framework based software update system of claim 6, wherein the created plurality of items comprises: a first source code development project and a first server deployment project;
the script obtaining unit is suitable for obtaining a first source code automatic deployment script corresponding to the first source code development project and a first server automatic deployment script corresponding to the first server deployment project.
8. The DevOps framework based software update system of claim 6, wherein the created plurality of items comprises: a second source code development project, a mirror image construction project and a second server deployment project;
the script obtaining unit is adapted to obtain a second source code automatic deployment script corresponding to the second source code development project, and a mirror image automatic deployment script corresponding to the mirror image construction project and a second server automatic deployment script corresponding to the second server deployment project.
9. A data processing apparatus comprising a memory and a processor, the memory having stored thereon computer instructions executable on the processor, wherein the processor, when executing the computer instructions, performs the steps of the method of any one of claims 1 to 5.
10. A computer readable storage medium having computer instructions stored thereon, wherein the computer instructions when executed perform the steps of the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910998853.1A CN110795125A (en) | 2019-10-21 | 2019-10-21 | Software updating method, system, device and readable storage medium based on DevOps framework |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910998853.1A CN110795125A (en) | 2019-10-21 | 2019-10-21 | Software updating method, system, device and readable storage medium based on DevOps framework |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110795125A true CN110795125A (en) | 2020-02-14 |
Family
ID=69440484
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910998853.1A Pending CN110795125A (en) | 2019-10-21 | 2019-10-21 | Software updating method, system, device and readable storage medium based on DevOps framework |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110795125A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112947990A (en) * | 2021-03-23 | 2021-06-11 | 四川虹美智能科技有限公司 | Development library creating method and device and computer readable medium |
| CN114553930A (en) * | 2022-01-26 | 2022-05-27 | 石化盈科信息技术有限责任公司 | System integration method and device, computer equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101384995A (en) * | 2006-02-13 | 2009-03-11 | 国际商业机器公司 | Administration automation in application servers |
| CN101667115A (en) * | 2008-09-02 | 2010-03-10 | 中国移动通信集团公司 | Terminal, system and method for deploying client application |
| CN105743680A (en) * | 2014-12-11 | 2016-07-06 | 深圳云之家网络有限公司 | Cluster disposition method and disposition device |
| CN107066292A (en) * | 2017-03-06 | 2017-08-18 | 北京百度网讯科技有限公司 | Server environment dispositions method and device |
| CN108073400A (en) * | 2017-12-07 | 2018-05-25 | 湖北三新文化传媒有限公司 | Software automation construction method, server and storage medium |
| CN108255509A (en) * | 2018-02-07 | 2018-07-06 | 平安好房（上海）电子商务有限公司 | Using dispositions method, device, equipment and readable storage medium storing program for executing |
-
2019
- 2019-10-21 CN CN201910998853.1A patent/CN110795125A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101384995A (en) * | 2006-02-13 | 2009-03-11 | 国际商业机器公司 | Administration automation in application servers |
| CN101667115A (en) * | 2008-09-02 | 2010-03-10 | 中国移动通信集团公司 | Terminal, system and method for deploying client application |
| CN105743680A (en) * | 2014-12-11 | 2016-07-06 | 深圳云之家网络有限公司 | Cluster disposition method and disposition device |
| CN107066292A (en) * | 2017-03-06 | 2017-08-18 | 北京百度网讯科技有限公司 | Server environment dispositions method and device |
| CN108073400A (en) * | 2017-12-07 | 2018-05-25 | 湖北三新文化传媒有限公司 | Software automation construction method, server and storage medium |
| CN108255509A (en) * | 2018-02-07 | 2018-07-06 | 平安好房（上海）电子商务有限公司 | Using dispositions method, device, equipment and readable storage medium storing program for executing |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112947990A (en) * | 2021-03-23 | 2021-06-11 | 四川虹美智能科技有限公司 | Development library creating method and device and computer readable medium |
| CN112947990B (en) * | 2021-03-23 | 2023-04-07 | 四川虹美智能科技有限公司 | Development library creating method, device and computer readable medium |
| CN114553930A (en) * | 2022-01-26 | 2022-05-27 | 石化盈科信息技术有限责任公司 | System integration method and device, computer equipment and storage medium |
| CN114553930B (en) * | 2022-01-26 | 2024-04-16 | 石化盈科信息技术有限责任公司 | System integration method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9760343B2 (en) | Application builder based on metadata | |
| WO2022170801A1 (en) | Ios application program construction method and apparatus, electronic device, and storage medium | |
| US8745585B2 (en) | Meta-data for single development test environment | |
| US20200097390A1 (en) | Platform-integrated ide | |
| US20150100832A1 (en) | Method and system for selecting and executing test scripts | |
| US20190303187A1 (en) | Methods, devices, and systems for distributing software to and deploying software in a target environment | |
| US8464246B2 (en) | Automation of mainframe software deployment | |
| US20150278074A1 (en) | Logging code generation and distribution | |
| US20150100830A1 (en) | Method and system for selecting and executing test scripts | |
| US20210373870A1 (en) | Method and device for building images | |
| CN113626036A (en) | Code integrated management method and system based on Jenkins | |
| US11288176B2 (en) | Executing integration scenario regression tests in customer landscapes | |
| CN111324522A (en) | Automatic test system and method | |
| CN115454869A (en) | Interface automation test method, device, equipment and storage medium | |
| CN110795125A (en) | Software updating method, system, device and readable storage medium based on DevOps framework | |
| EP2503449A2 (en) | Single development test environment | |
| CN113296787A (en) | Online development and code hosting system based on cloud platform and using method | |
| CN113722204A (en) | Application debugging method, system, device and medium | |
| US20100153913A1 (en) | Systems and Methods for Executing Object-Oriented Programming Code Invoking Pre-Existing Objects | |
| US8473943B2 (en) | Using ecoprint for cloning of applications | |
| CN110647349A (en) | Method for realizing continuous delivery of iOS APP | |
| CN115686462A (en) | React-Native based engineering architecture method and system | |
| CN115061746A (en) | Jenkins-based vehicle-mounted network controller product development method and system | |
| CN111813659A (en) | UI and interface based automatic test method, device, equipment and readable medium | |
| CN114726848B (en) | Client automatic packaging and exe distribution method and device for Windows platform |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200214 |
|
| WD01 | Invention patent application deemed withdrawn after publication |