Continuous integrated report releasing system and method

Abstract

The invention provides a continuous integrated report releasing system and method, and belongs to the field of cloud computing. The continuous integrated report releasing system includes a report metadata database, a report display style database, a report template database, a markup language display engine, a version management system, a continuous integrated controller, and a versioning report generator. The continuous integrated report releasing method includes; S1, under the control of the continuous integrated controller, the system generates a versioning report from an original report according to metadata of the report, and displays the versioning report; and S2, the versioning report generator generates a structural report from the original report according to a report template.

Description

technical field [0001] The present invention relates to the field of cloud computing, in particular to a system and method for publishing continuous integration reports. Background technique [0002] As cloud computing technology is becoming more and more popular in all walks of life in the social economy, infrastructure cloud technology and products are becoming more and more mature, and platform-as-a-service and software-as-a-service solutions are getting more and more attention. Continuous integration solution, as an important component function of platform as a service, is an indispensable service module for most typical platform as a service and software as a service solutions. [0003] Most of the continuous integration reports generated by existing continuous integration systems are in web page (ie HTML) format, such as figure 1 shown. Although this format is easy for users to browse and read one-time reports, it is not conducive to the long-term update and maintena...

AI Technical Summary

Problems solved by technology

Although this format is easy for users to browse and read one-time reports, it is not conducive to the long-term update and maintenance of project or product reports. In particular, generating reports in the form of web pages is not conducive to version management and is not conducive to two reports for the same project to compare; figure 1 As shown, two reports are obtained by running the same project twice, one succeeds and the other fails. The success and failure can be seen at a glance through the browser, but the report text is as follows figure 1 The display is very complicated and contains a lot of content that has nothing to do with the content of the report, which leads to two problems. One is that the report content is too large and it is not easy to manage the version, and the other is that the two reports are not easy to compare and contrast.

Images