Collecting test results in different formats for storage

• US 10,387,370 B2
• Filed: 05/18/2016
• Issued: 08/20/2019
• Est. Priority Date: 05/18/2016
• Status: Active Grant

• Current Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Original Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Inventors: Shuster, Boaz
• Primary Examiner(s): Brooks, David T.
• Application Number:
  US15/157,873
• Publication Number:
  US 20170337208A1
• Time in Patent Office: 1,189 Days
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/148 File search processing
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

Systems and methods are provided for storing test results. An example method includes receiving a notification that a job has completed execution in a test execution server. The notification includes an identifier and a name of the job, and is sent from the test execution server. The method also includes retrieving a log file from the test execution server and determining a format of the log file. The log file includes a plurality of files storing a set of test results based on the execution of the job. The method further includes extracting, based on the format of the log file, the plurality of files from the log file. The method also includes storing one or more files of the plurality of files into a searchable repository that provides a full-text search engine.

Claims

1. A method of storing test results, comprising:

receiving a notification that a job has completed execution in a test execution server, the notification including an identifier and a name of the job, and the notification being sent from the test execution server;

retrieving, based on the identifier and the name of the job, a log file from the test execution server, the log file including a plurality of files storing a set of test results based on the execution of the job, and the log file being in a format different from at least one file of the plurality of files;

extracting, based on the format of the log file, a first set of text files from the log file;

extracting, based on the format of the log file, a second set of files from the log file, the second set of files being different from text files;

storing the first set of text files, but not the second set of files, into a searchable repository that provides a full-text search; and

logging the first set of text files into a log report, the log report specifying files that have been stored into the searchable repository.

2. The method of claim 1, comprising:

receiving a second notification that a second job has completed execution in a second test execution server, the second notification including a second identifier and a second name of the second job, and the second notification being sent from the second test execution server;

retrieving, based on the second identifier and the second name of the second job, a second log file from the second test execution server, the second log file including a second plurality of files storing a second set of test results based on the execution of the second job;

extracting, based on a second format of the second log file, the second plurality of files from the second log file, the first format being different from the second format; and

storing one or more files of the second plurality of files into the searchable repository.

3. The method of claim 1, wherein receiving the log file includes in response to receiving the notification, downloading the log file from the test execution server.

4. The method of claim 1, further comprising:

reading an offset of the log file; and

determining, based on the offset, the format of the log file.

5. The method of claim 1, wherein receiving the notification includes receiving a JSON message.

6. The method of claim 1, further comprising:

determining whether the job is specified in a blacklist; and

in response to a determination that the job is specified in the blacklist, discarding the notification, wherein retrieving the log file, extracting the plurality of files, and storing the one or more files includes in response to a determination that the job is not in the blacklist, retrieving the log file, extracting the plurality of files, and storing the one or more files.

7. The method of claim 1, further comprising:

parsing the log file;

collecting metadata on the plurality of files included in the log file; and

storing the metadata corresponding to the plurality of files into a search server, wherein the metadata is associated with the plurality of files.

8. The method of claim 7, wherein the metadata includes a status of a build of the job.

9. The method of claim 8, wherein the status of the build indicates whether the job failed or succeeded based on the execution of the job.

10. The method of claim 1, further comprising:

determining whether the log file is in a compressed format, wherein extracting the plurality of files includes in response to a determination that the log file is in the compressed format, decompressing the log file.

11. The method of claim 1, wherein the first format of the log file is different from a second format of a file of the plurality of files.

12. A system for storing test results, comprising:

a memory containing machine readable medium storing machine executable code; and

one or more processors coupled to the memory and configurable to execute the machine executable code to cause the one or more processors to;

execute a job;

store a test result of the job into a log file;

receive from a test execution server a notification that the job has completed execution in the test execution server, wherein the notification includes an identifier and a name of the job;

retrieve, based on the identifier and the name of the job, a log file from the test execution server, wherein the log file includes a plurality of files storing a set of test results based on the execution of the job, and the log file is in a format different from at least one file of the plurality of files;

extract, based on the format of the log file, a first set of text files from the log file;

extract, based on the format of the log file, a second set of files from the log file, the second set of files being different from text files; and

store the first set of text files, but not the second set of files, into a searchable repository that provides a full-text search; and

log the first set of text files into a log report, the log report specifying files that have been stored into the searchable repository.

13. The system of claim 12, wherein the one or more processors are configurable to execute the machine executable code to cause the one or more processors to:

expose the log file through a Web browser, wherein the test execution server is a Web server.

14. The system of claim 12, wherein the one or more processors are configurable to execute the machine executable code to cause the one or more processors to:

store a link associated with the job into a search server;

display the link on a display coupled to the system; and

in response to a selection of the link, retrieving the plurality of files from the search server.

15. The system of claim 12, wherein the log file is not of a text file format.

16. The system of claim 15, wherein the one or more processors are configurable to execute the machine executable code to cause the one or more processors to:

receive from an extraction module a request for the log file associated with the identifier and the name of the job; and

in response to a request, provide the log file to the extraction module.

17. The system of claim 12, wherein the notification includes an identifier of the test execution server.

18. The system of claim 12, wherein the format is a tarball, gzip, zip format, lxz, or bzip2 format.

19. The system of claim 12, wherein the one or more processors are configurable to execute the machine executable code to cause the one or more processors to:

parse the log file;

collect metadata on a file of the plurality of files; and

store the metadata corresponding to the file into a search server.

20. A non-transitory machine-readable medium comprising a plurality of machine-readable instructions that when executed by one or more processors is adapted to cause the one or more processors to perform a method comprising:

receiving a notification that a job has completed execution in a test execution server, the notification including an identifier and a name of the job, and the notification being sent from the test execution server;

retrieving, based on the identifier and the name of the job, a log file from the test execution server, the log file including a plurality of files storing a set of test results based on the execution of the job, and the log file being in a format different from at least one file of the plurality of files;

extracting, based on the format of the log file, a first set of text files from the log file;

extracting, based on the format of the log file, a second set of files from the log file, the second set of files being different from text files;

storing the first set of text files, but not the second set of files, into a searchable repository that provides a full-text search; and

logging the first set of text files into a log report, the log report specifying files that have been stored into the searchable repository.