CN108509346B - Dual-system BIOS continuous integration platform and method - Google Patents
Dual-system BIOS continuous integration platform and method Download PDFInfo
- Publication number
- CN108509346B CN108509346B CN201810331794.8A CN201810331794A CN108509346B CN 108509346 B CN108509346 B CN 108509346B CN 201810331794 A CN201810331794 A CN 201810331794A CN 108509346 B CN108509346 B CN 108509346B
- Authority
- CN
- China
- Prior art keywords
- source code
- tested
- module
- jenkins
- detected
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 25
- 230000010354 integration Effects 0.000 title claims abstract description 21
- 238000012360 testing method Methods 0.000 claims abstract description 106
- 238000001514 detection method Methods 0.000 claims abstract description 20
- 230000002085 persistent effect Effects 0.000 claims description 8
- 230000003068 static effect Effects 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 6
- 230000009977 dual effect Effects 0.000 claims description 4
- 230000009471 action Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3624—Software debugging by performing operations on the source code, e.g. via a compiler
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a dual-system BIOS continuous integration platform and a method, comprising a Jenkins node and a VCS source code library; the Jenkins node comprises: the detection module is used for detecting whether the source code to be detected is stored in the VCS source code library or not; the acquisition module is used for acquiring the source code to be detected when the detection module detects that the VCS source code library stores the source code to be detected; the compiling module is used for compiling the source code to be tested under the local system to obtain a BIOS Image; the burning module is used for burning the BIOS Image to the equipment to be tested by utilizing the BMC under the local system; the virtual system creating module is used for creating a virtual system corresponding to the equipment to be tested; the test module is used for running a BIOS firmware automatic test suite by using the BAT under the virtual system, running a BIOS Image in the equipment to be tested for testing and generating a test report; according to the method and the device, the compiling and burning are carried out under the local system, the testing is carried out under the virtual system, the compiling, burning and testing can be carried out faster and more reliably by the double systems, the automatic testing is realized, and the testing efficiency is improved.
Description
Technical Field
The invention relates to the field of firmware engineering, in particular to a dual-system BIOS continuous integration platform and a method.
Background
The firmware engineering applies the concept, theory and experience of software engineering to the microprogram design, and the formalized model of the firmware is closely related to microprogram hardware for realizing the microinstruction; the firmware engineering mainly comprises the following steps: requirement definition and specification of the microprogram; designing and implementing a microprogram; testing, debugging and verifying the microprogram; maintenance of microprograms, etc.; firmware engineering requires that the microprogram hardware be structured and easily described, so as to organically integrate firmware and software into a single entity, and to have common terminology for both.
In the prior art environment, the firmware development environment is far behind the software development environment, practical micro-program high-level languages and testing and debugging tools are still lacking, the automation degree in the field of firmware engineering is low, and for a traditional integrated testing mode of a server firmware BIOS (Base Input/Output System), a research and development tester is relied on to carry out manual compiling, burning deployment, manual testing or manual execution of a testing script, so that great manpower is consumed, and the problem feedback period is long.
Therefore, it is very necessary to improve the automation degree in the field of firmware and find an efficient and timely BIOS continuous integration test system.
Disclosure of Invention
In view of this, the present invention provides a dual-system BIOS persistent integration platform and method, which implement automatic testing, increase testing efficiency, and increase testing speed. The specific scheme is as follows:
a dual-system BIOS continuous integration platform comprises a Jenkins node and a VCS source code library used for receiving and storing source codes to be detected; wherein, Jenkins node includes:
the detection module is used for detecting whether the source code to be detected is stored in the VCS source code library or not;
the acquisition module is used for acquiring the source code to be detected when the detection module detects that the source code to be detected is stored in the VCS source code library;
the compiling module is used for compiling the source code to be tested under the local system to obtain a BIOS Image;
the burning module is used for burning the BIOS Image to the equipment to be tested by utilizing the BMC;
the virtual system creating module is used for creating a virtual system corresponding to the equipment to be tested;
and the test module is used for running the BIOS firmware automatic test suite by using BAT under the virtual system, running the BIOS Image in the equipment to be tested for testing and generating a test report.
Optionally, the Jenkins node includes a Jenkins master node and a Jenkins slave node; the Jenkins master node comprises the detection module and the acquisition module, and the Jenkins slave node comprises the compiling module, the burning module, the virtual system creating module and the test module.
Optionally, the Jenkins slave node further includes:
and the source code verification module is used for performing static code scanning on the source code to be detected and detecting whether the source code to be detected has a security vulnerability.
Optionally, the method further includes:
and the feedback server is used for sending information by using the result sent by the Jenkins node and sending the test result to the user terminal, wherein the result sent information comprises the test result and a sending command in which a sending object and a sending instruction are recorded.
The invention also discloses a dual-system BIOS continuous integration method, which comprises the following steps:
detecting whether a source code to be detected is stored in a VCS source code library or not;
if yes, acquiring the source code to be detected from the VCS source code library;
compiling the source code to be tested to obtain a BIOS Image;
burning the BIOS Image to the equipment to be tested by utilizing BMC;
creating a virtual system corresponding to the equipment to be tested;
and running a BIOS firmware automation test suite by using BAT under the virtual system, running the BIOS Image in the equipment to be tested for testing, and generating a test report.
Optionally, before the compiling the source code to be tested, the method further includes:
and performing static code scanning on the source code to be detected, and detecting whether the source code to be detected has a security vulnerability.
Optionally, after generating the test report, the method further includes:
and generating result sending information, and sending the result sending information to a feedback server so that the feedback server sends the test result to the user terminal, wherein the result sending information comprises the test result and a sending command in which a sending object and a sending instruction are recorded.
The invention relates to a dual-system BIOS continuous integration platform, which comprises Jenkins nodes and a VCS source code library used for receiving and storing source codes to be detected; wherein, Jenkins node includes: the detection module is used for detecting whether the source code to be detected is stored in the VCS source code library or not; the acquisition module is used for acquiring the source code to be detected when the detection module detects that the VCS source code library stores the source code to be detected; the compiling module is used for compiling the source code to be tested under the local system to obtain a BIOS Image; the burning module is used for burning the BIOS Image to the equipment to be tested by utilizing the BMC under the local system; the virtual system creating module is used for creating a virtual system corresponding to the equipment to be tested; and the test module is used for running the BIOS firmware automatic test suite by using the BAT under the virtual system, running the BIOS Image in the equipment to be tested for testing and generating a test report.
The invention relates to a dual-system BIOS continuous integration platform which comprises Jenkins nodes and a VCS source code library, wherein a detection module automatically detects whether the VCS source code library stores a source code to be detected or not, when the source code to be detected is detected, an acquisition module acquires the source code to be detected from the VCS source code library, a compiling module and a burning module compile the source code to be detected into a BIOS Image format under a local system with good compatibility, the BIOS Image is burnt to equipment to be detected by a BMC (baseboard management controller), so that the BIOS Image can run in the equipment to be detected, a virtual system creating module runs the BIOS Image on the equipment to be detected for testing, creates a virtual system corresponding to the equipment to be detected, runs a BIOS firmware automatic testing suite by a BAT under the virtual system, runs the BIOS Image in the equipment to be detected for testing, generates a testing report, completes the testing whether the BIOS Image can normally run in the equipment to be detected, and enables the compiling to be automatically, The burning and testing can run faster and more reliably, automatic testing is realized, testing efficiency is improved, and testing speed is increased.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a schematic structural diagram of a dual-system BIOS persistent integration platform according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of another dual-system BIOS persistent integration platform configuration according to an embodiment of the present disclosure;
fig. 3 is a flow chart illustrating a method for continuously integrating a dual-system BIOS according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention discloses a dual-System BIOS continuous integration platform, which is shown in figure 1 and comprises a Jenkins node 2 and a VCS source code library 1(VCS, Version Control System) for receiving and storing a source code to be detected; wherein, Jenkins node 2 includes:
the detection module 21 is configured to detect whether a source code to be detected is stored in the VCS source code library 1;
the obtaining module 22 is configured to obtain a source code to be detected when the detecting module 21 detects that the source code to be detected is stored in the VCS source code library 1;
a compiling module 23, configured to compile the source code to be tested in the local system to obtain a BIOS Image (binary executable Image);
a burning module 24, configured to burn the BIOS Image to the device to be tested by using a BMC (Board Management Controller System, onboard out-of-band Management System) in the local System;
a virtual system creating module 25, configured to create a virtual system corresponding to the device to be tested;
the test module 26 is configured to run a BIOS firmware automation test suite by using a BAT (BIOS Automated Testing BIOS automation test service), run a BIOS Image in the device to be tested, and generate a test report.
Specifically, after the BIOS developer edits the source code to be tested, the source code to be tested is sent to the VCS source code library 1 through the user terminal, and the source code to be tested is stored for subsequent testing, and after the VCS source code library 1 receives the source code to be tested, the version of the VCS source code library 1 is updated, where the VCS source code library 1 may be an SVN source code library or a GIT source code library.
Specifically, the detection module 21 detects a version change of the VCS source code library 1, and when the version of the VCS source code library 1 changes, which indicates that the VCS source code library 1 receives a new source code to be detected, and the detection module 21 detects that the source code to be detected is stored in the VCS source code library 1, the acquisition module 22 acquires the source code to be detected from the VCS source code library 1 after detecting that the source code to be detected is stored in the VCS source code library 1 according to a detection result of the detection module 21, and the compilation module 23 compiles the acquired source code to be detected in a local system to compile the source code to be detected into a BIOS Image, and after the compilation is completed, the burning module 24 burns the BIOS Image to the device to be detected by using the BMC under the local system so that the source code to be detected runs in the device to be detected.
The local system may be a running system for facilitating running of compiling and burning, for example, a Windows system.
In particular, after the burning is finished, because the running system convenient for running compiling and burning and the running system of the device to be tested are possibly inconsistent, since the system known to the running system of the device to be tested must be used for testing, in order to accelerate the testing speed and reduce the compatibility problem, the virtual system creating module 25 is used to create the virtual system corresponding to the device to be tested in the Jenkins node 2, so that the Jenkins node 2 has a local system which is convenient for running, compiling and burning, and a virtual system corresponding to the device under test, after the virtual system is generated, the test module 26 runs the BIOS firmware automatic test suite by using BAT under the virtual system, carrying out BIOS Image operation test on the equipment to be tested, detecting whether the BIOS Image can normally operate in the equipment to be tested, and generating a test report recording a test result, wherein the test report can reflect and record BUG initiated by the BIOS Image in the operation process of the equipment to be tested; the system of the virtual system and the device to be tested may be a Linux system.
It can be understood that, the detection module 21 continues to detect if the source code to be detected is not detected in the VCS source code library 1; the functions of the VCS source code library 1 and the Jenkins node 2 are respectively realized by different servers.
It can be seen that, in the embodiment of the present invention, the dual-system BIOS persistent integration platform includes a Jenkins node 2 and a VCS source code library 1, the detection module 21 automatically detects whether the VCS source code library 1 stores a source code to be tested, when a source code to be tested is detected, the acquisition module 22 acquires the source code to be tested from the VCS source code library 1, the compiling module 23 and the burning module 24 compile the source code to be tested into a BIOS Image format under a compatible local system, and burn the BIOS Image into a device to be tested by using the BMC, so that the BIOS Image can run in the device to be tested, the virtual system creation module 25 runs the BIOS Image on the device to be tested to perform a test, creates a virtual system corresponding to the device to be tested, the test module 26 runs the BIOS firmware automation test suite under the virtual system, runs the BIOS Image in the device to be tested to perform a test, generates a test report, and completes a test on whether the BIOS Image can run normally on the device to be tested, the dual systems enable the compiling, burning and testing to run faster and more reliably, automatic testing is achieved, testing efficiency is improved, and testing speed is improved.
The embodiment of the invention discloses a specific dual-system BIOS continuous integration platform, and compared with the previous embodiment, the embodiment further describes and optimizes the technical scheme. Referring to fig. 2, specifically:
in the embodiment of the invention, in order to refine management, improve the stability and the running speed of a system and distribute different tasks to different node servers, the Jenkins node 2 can comprise a Jenkins master node 21 and a Jenkins slave node 22; the Jenkins master node comprises a detection module 211 and an acquisition module 212, and the Jenkins slave node comprises a compiling module 222, a burning module 223, a virtual system creating module 224 and a testing module 225.
Specifically, the Jenkins master node 21 and the Jenkins slave node 22 may be connected through a network, and the Jenkins slave node 22 completes compilation of the source code to be tested in the local system after receiving the source code to be tested sent by the Jenkins master node 21, and completes a test on the BIOS Image running in the device to be tested.
In an embodiment of the present invention, in order to ensure that the source code to be detected does not have a security vulnerability, the Jenkins slave node 22 may further include a source code verification module 221, which is configured to perform static code scanning on the source code to be detected and detect whether the source code to be detected has a security vulnerability.
Specifically, before the compiling module 222 compiles the source code to be detected, the source code verifying module 221 may perform static code scanning on the source code to be detected by using the verifying code to detect whether the source code to be detected has a security vulnerability, where the verifying code may be HP party or IBM AppScansrc, and the source code verifying module 221 may generate a verification report from the verification result so that the user can browse the verification result to repair the security vulnerability of the source code to be detected.
Further, in order to feed back the test result to the user in time, a feedback server 3 may be added, configured to send the test result to the user terminal by using result sending information sent by the Jenkins node 2, where the result sending information includes the test result and a sending command in which a sending object and a sending instruction are recorded.
Specifically, after the Jenkins node 2 generates a test result, result sending information including the test result and a sending command in which a sending object and a sending instruction are recorded is generated, and the result sending information is sent to the feedback server 3, after the feedback server 3 receives the result sending information, the test result is sent to the user terminal by using the sending command of the sending object and the sending instruction, so that a user can receive the test result in time; the feedback server 3 may be a mail management server, and sends the test result to the user terminal in the form of a mail.
Correspondingly, the embodiment of the invention also discloses a method for continuously integrating the dual-system BIOS, which is shown in fig. 3 and comprises the following steps:
s11: detecting whether a source code to be detected is stored in a VCS source code library or not;
s12: if yes, acquiring a source code to be detected from the VCS source code library;
s13: compiling the source code to be tested to obtain a BIOS Image;
s14: burning the BIOS Image to the equipment to be tested by utilizing the BMC;
s15: creating a virtual system corresponding to the equipment to be tested;
s16: and running the BIOS firmware automatic test suite by using the BAT under the virtual system, running the BIOS Image in the equipment to be tested for testing, and generating a test report.
It can be understood that if the source code to be detected is not detected to be stored in the VCS source code library, the detection is continued, and no action is taken.
In the embodiment of the invention, before the source code to be tested is compiled, the source code to be tested can be subjected to static code scanning to detect whether the source code to be tested has a security vulnerability.
Further, after the test report is generated, result sending information may be generated, and the result sending information is sent to the feedback server, so that the feedback server sends the test result to the user terminal, where the result sending information includes the test result and a sending command in which a sending object and a sending instruction are described.
It can be seen that, in the embodiment of the present invention, the dual-system BIOS persistent integration method automatically detects whether the VCS source code library stores the source code to be tested, when the source code to be tested is detected, obtains the source code to be tested from the VCS source code library, compiles the source code to be tested into the BIOS Image format under the compatible local system, and burns the BIOS Image into the device to be tested by using the BMC, so that the BIOS Image can run in the device to be tested, creates a virtual system corresponding to the device to be tested for running the BIOS Image on the device to be tested to perform a test, runs the BIOS firmware automation test suite under the virtual system, runs the BIOS Image in the device to be tested to perform a test, generates a test report, completes the test on whether the BIOS Image can run normally in the device to be tested, and the dual-system enables the compiling, burning and testing to run faster and more reliably, realizes an automation test, and accelerates the test efficiency, the testing speed is improved.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The above is a detailed description of a dual-system BIOS persistent integration platform and method provided by the present invention, and a specific example is applied in the present disclosure to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (4)
1. A dual-system BIOS continuous integration platform is characterized by comprising Jenkins nodes and a VCS source code library used for receiving and storing source codes to be tested; wherein, Jenkins node includes:
the detection module is used for detecting whether the source code to be detected is stored in the VCS source code library or not;
the acquisition module is used for acquiring the source code to be detected when the detection module detects that the source code to be detected is stored in the VCS source code library;
the compiling module is used for compiling the source code to be tested under the local system to obtain a BIOS Image;
the burning module is used for burning the BIOS Image to the equipment to be tested by utilizing the BMC;
the virtual system creating module is used for creating a virtual system corresponding to the equipment to be tested;
the test module is used for running a BIOS firmware automatic test suite by using BAT under the virtual system, running the BIOS Image in the equipment to be tested for testing and generating a test report;
the source code verification module is used for performing static code scanning on the source code to be detected and detecting whether the source code to be detected has a security vulnerability;
the Jenkins nodes comprise Jenkins main nodes and Jenkins slave nodes; the Jenkins master node comprises the detection module and the acquisition module, and the Jenkins slave node comprises the compiling module, the burning module, the virtual system creating module and the test module.
2. The dual system BIOS persistent integration platform of claim 1, further comprising:
and the feedback server is used for sending information by using the result sent by the Jenkins node and sending the test result to the user terminal, wherein the result sending information comprises the test result and a sending command in which a sending object and a sending instruction are recorded.
3. A dual system BIOS continuous integration method is characterized by comprising the following steps:
the Jenkins main node detects whether a source code to be detected is stored in a VCS source code library or not;
if so, the Jenkins master node acquires the source code to be detected from the VCS source code library;
compiling the source code to be tested by the Jenkins slave node under a local system to obtain a BIOS Image;
the Jenkins slave node burns the BIOS Image to the equipment to be tested by utilizing a BMC (baseboard management controller) under a local system;
the Jenkins slave node creates a virtual system corresponding to the equipment to be tested;
running a BIOS firmware automation test suite by the Jenkins slave node under the virtual system by using BAT, and running the BIOS Image in the equipment to be tested for testing to generate a test report;
before the source code to be tested is compiled, the method further includes:
and performing static code scanning on the source code to be detected, and detecting whether the source code to be detected has a security vulnerability.
4. The dual system BIOS persistent integration method of claim 3, wherein after generating the test report, further comprising:
and generating result sending information, and sending the result sending information to a feedback server so that the feedback server sends the test result to the user terminal, wherein the result sending information comprises the test result and a sending command in which a sending object and a sending instruction are recorded.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810331794.8A CN108509346B (en) | 2018-04-13 | 2018-04-13 | Dual-system BIOS continuous integration platform and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810331794.8A CN108509346B (en) | 2018-04-13 | 2018-04-13 | Dual-system BIOS continuous integration platform and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108509346A CN108509346A (en) | 2018-09-07 |
| CN108509346B true CN108509346B (en) | 2021-10-22 |
Family
ID=63381801
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810331794.8A Active CN108509346B (en) | 2018-04-13 | 2018-04-13 | Dual-system BIOS continuous integration platform and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108509346B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110633131B (en) * | 2019-09-16 | 2022-05-31 | 东软集团股份有限公司 | Method, device, equipment and system for virtualizing firmware |
| CN111611157B (en) * | 2020-05-08 | 2023-07-28 | 珠海全志科技股份有限公司 | GMS continuous integration construction automatic test method and system |
| CN111679942B (en) * | 2020-06-09 | 2024-03-22 | 深圳酷宅科技有限公司 | Burn-in test method, system and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103455350A (en) * | 2013-08-28 | 2013-12-18 | 浪潮电子信息产业股份有限公司 | Method for updating BIOS (Basic Input/Output System) |
| CN105653449A (en) * | 2015-12-28 | 2016-06-08 | 湖南蚁坊软件有限公司 | Continuous integration method based on container virtualization |
| CN106708716A (en) * | 2015-07-17 | 2017-05-24 | 中兴通讯股份有限公司 | Software testing method, device and system |
| CN106776270A (en) * | 2016-11-11 | 2017-05-31 | 努比亚技术有限公司 | A kind of code detection method, device and terminal |
| CN107741908A (en) * | 2017-10-12 | 2018-02-27 | 郑州云海信息技术有限公司 | A kind of continuous integrating method and device based on automatic test |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10171593B2 (en) * | 2014-06-30 | 2019-01-01 | Verizon Patent And Licensing Inc. | Validating web services for compatibility with a client device by emulating the client device by populating a template associated with the web services |
-
2018
- 2018-04-13 CN CN201810331794.8A patent/CN108509346B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103455350A (en) * | 2013-08-28 | 2013-12-18 | 浪潮电子信息产业股份有限公司 | Method for updating BIOS (Basic Input/Output System) |
| CN106708716A (en) * | 2015-07-17 | 2017-05-24 | 中兴通讯股份有限公司 | Software testing method, device and system |
| CN105653449A (en) * | 2015-12-28 | 2016-06-08 | 湖南蚁坊软件有限公司 | Continuous integration method based on container virtualization |
| CN106776270A (en) * | 2016-11-11 | 2017-05-31 | 努比亚技术有限公司 | A kind of code detection method, device and terminal |
| CN107741908A (en) * | 2017-10-12 | 2018-02-27 | 郑州云海信息技术有限公司 | A kind of continuous integrating method and device based on automatic test |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108509346A (en) | 2018-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8352916B2 (en) | Facilitating the automated testing of daily builds of software | |
| KR101038965B1 (en) | How to Configure Test Systems, Computer-readable Media, and Computing Systems | |
| US8140905B2 (en) | Incremental problem determination and resolution in cloud environments | |
| KR102341154B1 (en) | High-speed application for installation on mobile devices for permitting remote configuration of such mobile devices | |
| CN108509346B (en) | Dual-system BIOS continuous integration platform and method | |
| CN111259406B (en) | Automatic construction method and system for cloud native application vulnerability reproduction environment | |
| CN109086051B (en) | Application component deployment method and device and computer storage medium | |
| US20170228220A1 (en) | Self-healing automated script-testing tool | |
| CN111144839B (en) | Project construction method, continuous integration system and terminal equipment | |
| CN108228190B (en) | Persistent integration and delivery methods, systems, devices, and computer-readable storage media | |
| CN113434158A (en) | User-defined management method, device, equipment and medium for big data component | |
| CN111162953A (en) | Data processing method, system upgrading method and server | |
| CN109558147A (en) | A kind of continuous integrating platform construction method based on Jenkins and Gitlab | |
| CN105224574A (en) | Method and device for automatically identifying junk files | |
| CN108519951A (en) | Three node BIOS continuous integratings platforms of one kind and method | |
| CN115248700A (en) | Method and system for automatically constructing mobile installation package by product code | |
| CN105468507A (en) | Branch fulfillment detection method and apparatus | |
| CN103026337A (en) | Distillation and reconstruction of provisioning components | |
| KR101599471B1 (en) | Apparatus, system, method and readable recording medium of managing a project file | |
| CN108304184B (en) | Compiling method and device | |
| CN111813382A (en) | Intangible asset management system and method | |
| CN107015831A (en) | A kind of client updating management method upgraded based on server end and system | |
| CN111488275A (en) | UI automation test method and device, storage medium and electronic equipment | |
| CN108536558A (en) | A kind of BIOS continuous integratings platform and method | |
| CN114116471A (en) | Automatic code scanning method, system, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |